> I think that rather might be the compiler. "[2 + 2] timeToRun" is "0" for me. :-)

I think that the print-it lag is caused by some UI updating logic. And GC, depending on what you do in your print-it.

Best,
Marcel
Am 28.06.2021 15:28:06 schrieb Thiede, Christoph <christoph.thiede at student.hpi.uni-potsdam.de>:
Hi Herbert,

> did you enable the preference to quick start sounds?

Thank you, that reduced my startup time by nearly 50%!

> Although there seems to be a delay before the sound starts but it seems faster than 2 + 2 print it.

I think that rather might be the compiler. "[2 + 2] timeToRun" is "0" for me. :-)

Best,
Christoph
Von: Squeak-dev <squeak-dev-bounces at lists.squeakfoundation.org> im Auftrag von Herbert König <herbertkoenig at gmx.net>
Gesendet: Montag, 28. Juni 2021 13:15:01
An: squeak-dev at lists.squeakfoundation.org
Betreff: Re: [squeak-dev] Many questions about sounds :-)
 
Hi Christopph,

did you enable the preference to quick start sounds?

Although there seems to be a delay before the sound starts but it seems faster than 2 + 2 print it.

And [[AbstractSound scaleTest play] timeProfile] fork. is faster than your example (79 vs. 92ms vs 139 w/o quick start)
 
Cheers,

Herbert



Am 27.06.2021 um 20:22 schrieb Thiede, Christoph:

Hi all!

As I'm currently developing a small project that uses sounds in Squeak, I have collected a number of questions about the Sound package and am hoping to find some answers here. Even if you are able to answer one or two questions only, I will appreciate your help! :-)

1. What is the difference between QueueSound and SequentialSound? Roughly speaking, they both appear to do the same. AbstractSound >> #, uses SequentialSound whereas QueueSound might be thread-safe. Is there any reason why the two are not unioned into a single class?


2. Why could my coffeeCupClink be broken? It's already the second image in which I, after playing around a bit with sounds, managed to break that sound by accident. In both affected images, Beeper beep just does not beep any more. However, all other SampledSounds still sound fine. SampledSound initialize and VM restart didn't help. I even tried to find out what's going wrong with the help of comparative debugging of #play, but I did not discover any meaningful difference ...

3. SoundService/SoundPlayer/SoundSystem are not thread-safe, are they?

4. Why does it take so much time to start the SoundPlayer? I could reproduce this in two images using: [[PluckedSound default play] timeProfile] fork. In both cases, the image was busy for ~150ms. If another sound is already playing, #play is fast. According to the TimeProfileBrowser, #newProcess eats up all the time (see attachment), but can this really be true? Can you reproduce this on your machines or could this be a Windows-specific thing?

5. Is there any built-in way for loudness normalization (as opposed to "normal" volume)?

6. Can you recommend any further resources in Squeak for other sound concepts such as ring modulation, sawtooth/triangle/square waves, or also other musical instruments? For example, there are flutes and oboes, but I did not find a piano sound. Would it be possible to build one as a combination of FMSounds or are these instruments more sophisticated to program?

Thanks in advance and have a happy weekend!

Best,
Christoph

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20210628/2d6f7f2f/attachment.html>