On 3/8/2019 9:50 PM, Alexandre Torres Porres wrote:

what would 'tabbed preferences' be?

Tabs in *one preference window* instead of multiple sub-menus (and many windows) from the file/preference menu.

Some images of TK tabbed:

https://www.google.com/search?q=ttk_notebook&tbm=isch&source=univ&am...

Mensaje telepatico asistido por maquinas.

Em sáb, 9 de mar de 2019 às 06:51, Fede Camara Halac camarafede@gmail.com escreveu:

I misread and, for a minute, I imagined a tabbed Pd, with tabbed canvases and all. I panicked a bit :)

me too, haha

Em sáb, 9 de mar de 2019 às 05:28, Peter P. peterparker@fastmail.com escreveu:

If you are on a cool operating system like Linux, you can simply invertcyour screen

nope, macOS here

what would you do, if i said that it was possible?

try an inverted theme, black background and white font/boxes/cords

Em sáb, 9 de mar de 2019 às 05:51, Seb Shader via Pd-list < pd-list@lists.iem.at> escreveu:

Hi, I thought I'd mention I have a pd mod I've been trying to maintain for a couple releases that has color plugins as well as initbangc https://github.com/sebshader/pdnext/releases/tag/0.49-0n

I don't understand git too well but i'm trying to keep the colors mod updated with the source generally :-)

Wow, that seems like a good starting point to include those in Pd. You could try making a PR, or Dan could check it out and steal from it as he did from other forks already ;)

cheers

michael strohmann wrote:

on rpi / stretch / pd-46 || ESI UJ6 Audiointerface… sometimes the first half second of audiofiles (4 channel) gets swallowed

i am using

[t b b] | | [1( [open audiofile.wav( | / [readsf~ 4]

my first bet was that the amplifier goes into sleep mode and needs time to wake up. but i can rule that out. now i am a bit clueless ….

are you completely sure ? even if you are, maybe reading & playing an arbitrary short soundfile consisting of a 2 hertz sinus at low volume every 10 seconds might make sure that the amp REALLY never goes to sleep.

does anybody else have similar troubles on RPi ???

no, there must be something else blocking the audio engine

you might try a little delay before the "1" message, or even try to run the [readsf~] in a subpatch~ with a higher blocksize (see attached patch again ;-)

that's all i can think of right now

i figure using [tabplay~] (thus preloading the soundfiles into RAM) is not an option ?

best

oliver

omg, i was violating all netiquette do-nots. please forgive me.

i would have expected that it would probably take longer to look for and read the sound file but not that the playback does not start at the beginning.

unfortunately the raspberry has limited RAM….

i was unsing a 2sec delay between [open soundfile.wav( and [start( would it help to delay even longer???

On 09 Mar 2019, at 18:50, IOhannes m zmölnig zmoelnig@iem.at wrote:

On 3/9/19 5:13 PM, oliver wrote:

...

are you completely sure ? even if you are, maybe reading & playing an arbitrary short soundfile consisting of a 2 hertz sinus at low volume every 10 seconds might make sure that the amp REALLY never goes to sleep.

or just use an [osc~ 2] instead.

the bottleneck could well be the access to a slow block device (that is: reading a soundfile from your SD card). try loading everything into memory instead. or at least try loading the soundfile from a RAMdisk. (that is: copy the soundfiles to /dev/shm/ before starting the patch; then read the soundfiles from there)

gfamrds IOhannes

---

Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list

aha, so i will raise the buffer-size for [readsf~] and see what happens. i never suspected readsf~ to be responsible for the dropout in the beginning, since initially it all worked very well. only now after the system is runnin 24/7 for couple of month, those drops seem to occur more frequently. maybe the SD is getting old and slow

more noise: the patch is really quite simple, i just want to play back a couple of 4 channel audiofiles, triggered by sensors or via network. there is only one sf running at a time, and nothing else going on apart from listening to network and reading from GPIO and serial. the puredata uses around 6 % of CPU and 2 % Memory on the RPi B+ in the past i had stuttering and skipping audio which i attributet to 1.) the fact that error messages postet to the console started to use much more RAM 2.) netsend related problems that froze pd ( i hope i got rid of those issues) i’ve set the BlockSize 512 or 2048 but this does not seem to have an effect. the soundfiles use around 1GB of memory. (the rpi B+ got 1GB ram)

On 09 Mar 2019, at 22:49, IOhannes m zmölnig zmoelnig@iem.at wrote:

On 3/9/19 9:46 PM, michael strohmann wrote:

...

i would have expected that it would probably take longer to look for and read the sound file but not that the playback does not start at the beginning.

well, we really only know what is happening from what you tell us what you are observing. e.g. it is unclear whether the entire audio engine stalls (e.g. other sounds that are supposed to play back at the same time stutter as well), or whether the 0.5 seconds are just skipped.

...

i was unsing a 2sec delay between [open soundfile.wav( and [start( would it help to delay even longer???

not without also raising the buffer-size for [readsf~].

...

unfortunately the raspberry has limited RAM….

well, since i have no clue how many audio files you want to play back (and how large they are), it is hard to suggest anything meaningful.

gfdsra IOhannes

---

Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list

extract from readsf~-help.pd:

You must open the soundfile in advance (a couple of seconds before you'll need it) using the "open" message.

this will allow readsf~ to fill its buffer before the actual reading begins.

Le sam. 9 mars 2019 à 16:56, michael strohmann itsnotfair9@gmail.com a écrit :

on rpi / stretch / pd-46 || ESI UJ6 Audiointerface… sometimes the first half second of audiofiles (4 channel) gets swallowed

i am using

[t b b] | | [1( [open audiofile.wav( | / [readsf~ 4]

my first bet was that the amplifier goes into sleep mode and needs time to wake up. but i can rule that out. now i am a bit clueless …. does anybody else have similar troubles on RPi ???

cheers! mkl

---

Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list