On 22/12/2021 20:53, Jonas Thörnvall wrote:
> onsdag 22 december 2021 kl. 21:33:03 UTC+1 skrev Jonas Thörnvall:
>> onsdag 22 december 2021 kl. 21:26:47 UTC+1 skrev Jonas Thörnvall:
>>> tisdag 21 december 2021 kl. 00:34:44 UTC+1 skrev Jon Ribbens:
>>>> On 2021-12-20, luserdroog <luser...@gmail.com> wrote:
>>>>> On Monday, December 20, 2021 at 3:19:41 PM UTC-6, jonas.t...@gmail.com wrote:
>>>>>> I have a bit hard to read monkey gibberish, is there a way to explain
>>>>>> this to someone who is not fullfledged retarded?
>>>>>>
>>>>>> .then(res => res.arrayBuffer())
>>>>>> .then(ArrayBuffer => ctx.decodeAudioData(ArrayBuffer));
>>>>>>
>>>>>> Specifically
>>>>>> .then =>
>>>>>> Is there another way to write it that may not be gibberish?
>>>>>
>>>>> I think this is the new fad called "monadic sequencing". If I'm right,
>>>>> the above can be translated into:
>>>>>
>>>>> var x = res.arrayBuffer(); //only it won't be called "res", but the name of the previous result
>>>>> var y = ctx.decodeAudioData(x);
>>>>>
>>>>> Or even:
>>>>>
>>>>> ctx.decodeAudioData( res.arrayBuffer() ); //again, "res" isn't the correct name here
>>>>>
>>>>> It's just a sequence of functions "arg=> expression" where the result
>>>>> of one is passed as the argument to the next. You can do the same
>>>>> thing with a series of temporary variables or by composing all the
>>>>> expressions into one massive expression.
>>>> The important bit you didn't mention is that it's dealing with Promises.
>>>> So you can't do either of the things you suggest above. If you're in an
>>>> async function you could do this however:
>>>>
>>>> const audioData = await ctx.decodeAudioData(await res.arrayBuffer())
>>> Why can't i do this.
>>> const audiostream = new AudioContext();
>>>
>>> async function audioPlay(url){
>>> const audioBuffer = await fetch(url)
>>> .then(res => res.arrayBuffer())
>>> .then(ArrayBuffer => audiostream.decodeAudioData(ArrayBuffer));
>>> const playwav = audiostream.createBufferSource();
>>> var gainNode = audiostream.createGain();
>>> gainNode.gain.value = -0.1;
>>> playwav.buffer = audioBuffer;
>>> playwav.connect(audiostream.destination);
>>> playwav.start();
>>> };
>>>
>>> or this to set volume
>>>
>>> const audiostream = new AudioContext();
>>> var gainNode = audiostream.createGain();
>>> gainNode.gain.value = -0.1;
>>>
>>> async function audioPlay(url){
>>> const audioBuffer = await fetch(url)
>>> .then(res => res.arrayBuffer())
>>> .then(ArrayBuffer => audiostream.decodeAudioData(ArrayBuffer));
>>> const playwav = audiostream.createBufferSource();
>>> playwav.buffer = audioBuffer;
>>> playwav.connect(audiostream.destination);
>>> playwav.start();
>>> };
>> I mean using .start() with an volume parameter, is what any none anal person would do.
> How many models do a programming language need, if you can write the code in a dousins of ways, it will be hard to read without a manual.
> Why did they not just do something like
> playwav.setVolume(-0.5);
>
> Why invent a hierarchy of idioties to write to set the volume?
>
Because Object Orientation Is Kewl and plebs like you dont understand it
so they get your job.

--
"In our post-modern world, climate science is not powerful because it is
true: it is true because it is powerful."

Lucas Bergkamp