Actually, DSP 1 is even delayed several seconds to allow loading of the samples a little bit faster. The same patch is working with the older Linux version.
Anyway, never mind, I already took the time to create an abstraction with [loop~] and [samphold~] that takes the same parameters (for my purpose) as [susloop~].
Ingo
Long shot.. cause you probably already tryed this:
- Isn't that that typical -nogui issue? (the delayed one...) Just put a
delay of about 100ms between your loadbang and the activation of the DSP 1; (the sound computation trigger). The thing is in -nogui sometimes stuff boots too fast =P
On Wed, May 5, 2010 at 9:15 AM, Ingo Scherzinger < mailto:ingo@miamiwave.com ingo@miamiwave.com> wrote:
I'm having a strange problem with [susloop~].
[susloop~] does not produce any sound since I've changed to Ubuntu 10.04 with the -nogui flag. With the graphics turned on there is no problem at all.
I had this problem before but didn't trace it down which was the reason why I stayed with Ubuntu 7.10 until now. Now I boiled it down to where I found out that the problem is definitively [susloop~]. I used the same sound path and simply "bypassed" [susloop~] by feeding some other signal into [tabread4~] and I got sound again. Garbled - but sound!
Has anybody else experienced this problem? Does anybody have a workaround (exept for using [loop~] which doesn't accept the same data format)?
I'm using Pd-0.42.5-extended-ubuntu-lucid-i386 dated 03-May-2010.
Thank you, Ingo _______________________________________________ mailto:Pd-list@iem.at Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list http://lists.puredata.info/listinfo/pd-list