@pholypp Soundcards is a difficult one to nail.
I have had a Motu 828 that would run for hours without any problem and then suddenly produce spikes on some or all outputs until a preset was reloaded (much quicker than a reboot).... and then be happy for days until the next time. The driver settings would often not stick when changed..... reopening the driver panel the settings would have changed to something else, but serial data streams have to be negotiated so...?

Other Motu's (different drivers) have never had a problem.
I don't think they are manufactured with problems, or that the 828 had any electronic faults.
It is much more likely that the 828 driver had problems talking to the os, On my mac the keyboard and the trackpad and the CD drive are all on the same hubs as the USB ports, which cannot help.

Some USB soundcards will work on one USB port but not on another, probably because something else (keyboard, something?) is on the same bus and so the bus timing has been downgraded to USB 1 from 3 or 2

Trial and error all the time....... especially with the Adobe updater, where I had force stopped just about every service on the laptop in desperation. Adobe updater always ran as a delayed start service at boot. Adobe licensing also, but fortunately without causing problems.

I am no expert in such things, but with so much software trying to control so much hardware nowadays how can anyone be sure....
It's a bit like a doctor having to hope that you can take aspirin + X when you have Y and Z but they don't yet know what Z is.
It seems to me that if it is mission critical then it should be bare bones and never receive an update.
I don't ever connect my show laptops to the internet.
David.

@kai I think you have to be a member of the audio group....... https://forum.pdpatchrepo.info/topic/14085/solved-problem-with-pd-start-priority-8-scheduling-failed
Or.... https://forum.pdpatchrepo.info/topic/12319/problems-using-pd-on-raspberry-pi/27

Maybe not very useful answers as things change all the time.
There has been some chat about using PipeWire instead of (or with.. I don't know Linux well) Alsa.
You should find that on the forum if you do a google search for pdpatchrepo pipewire.
David.

@KMETE said:

Any example for a simple midi player in Pd?

I'm not completely sure what you mean by "simple MIDI player," but I'll assume you want some Linux software that will play General MIDI sounds.

AFAICS from a quick web search, you would probably have to install a GM soundfont, e.g. sudo apt-get install fluid-soundfont-gm, and play it using software such as FluidSynth.

On my system, it took a little hunting, but I found /usr/share/sounds/sf2/FluidR3_GM.sf2 -- fluid, check, GM, check.

You'd probably have to connect Pd MIDI out to FluidSynth MIDI in. That should do it.

Is there any transport and tempo object in PD same as in max?

"Same as Max" -- well, no. Does Pd have its own way of handling tempo? Yes.

[metro] and [delay] objects respond to "tempo" messages -- see their help files. (Though unfortunately, some other timing-related objects such as [pipe] and [makenote] do not respond to tempo messages.)

Pd doesn't have a global transport. You could make your own bars/beats counter and [send] those values around in the patch. (I'm not sure if you need a master scheduler -- if so, there's one in https://github.com/jamshark70/hjh-abs .)

This appears to handle the different subdivisions.

24-0512-time-notation.pd

hjh

@jameslo said:

I'd still like to know if spaces are legal and possible with [oscformat] though.

I'm a bit surprised to see this, but in fact, according to the OSC spec 1.0, spaces are not allowed in OSC command paths.

https://ccrma.stanford.edu/groups/osc/spec-1_0.html#osc-address-spaces-and-osc-addresses

Each OSC Method and each OSC Container other than the root of the tree has a symbolic name, an ASCII string consiting of printable characters other than the following:

-character-	-name-	-ASCII code (decimal)-
’ ’	space	32
#	number sign	35
*	asterisk	42
,	comma	44
/	forward slash	47
?	question mark	63
[	open bracket	91
]	close bracket	93
{	open curly brace	123
}	close curly brace	125

So Pd has no obligation to support spaces here.

I suppose it depends on the software's OSC handler. SuperCollider doesn't complain (contrary to the OSC spec):

n = NetAddr.localAddr;  // send to myself

o = OSCFunc({ |msg|
    msg.postln;
    o.free;
}, '/test space');

n.sendMsg('/test space', 1);

prints: [ /test space, 1 ]

I did some other tests:

• "symbol patch 1" --> [list fromsymbol]: escape char 92 is not in the ASCII list.
• list "112 97 116 99 104 32 49" --> [list tosymbol]: resulting symbol prints with a backslash. I don't know if the backslash is stored internally, or if it's inserted only for the printed output. A quick look at the source code in x_list.c suggests that the backslash is not stored internally.
• list "112 97 116 99 104 32 49" --> [list tosymbol] --> [list prepend set] --> [list trim] --> [oscformat]: The printed bytes from oscformat do include char 92. But I couldn't see in the source code where the space is being escaped. (This long way around to build the "set" message is to be certain that there's no backslash in my input -- the backslash must be generated internally somewhere..)

So [oscformat] seems to be where the problem is happening -- but the OSC spec makes no promises that spaces will work, so there wouldn't be any justification to log a bug.

hjh

it gets in the weeds - basically you got a problem if your knob isn't a digital encoder which sends things like +1 or -1 to move numbers - typically these also have a push button.

if your knob is a potentiometer/slider/knob/pot like on an electric guitar - these only give discrete values and will Jump like on the left.

if you use one of those like I am on the right - and I apologize for it seeming messy, I'm cleaning up little problems - but the knob is still a potentiometer, so even tho I changed it into something that compares if its going higher or lower it ends up at weird places - so to do it right these needs to be an encoder type of knob - (which I'm simulating by just hitting the 1 and -1, a little surprised acting like an encoder isn't in [knob] yet.)knob-problems-pot-vs-encoder.pd

Hi, I am using pure data with the asio4all driver. Sometimes when I open Pd there is no output driver selected and I have to select asio4all again. Does anyone know why this happens??

Some time ago I bought an apogee interface that its controllers don't get along very badly with Pd and I'm forced to use asio4all, but I don't feel it gets along with pd either. All these problems with asio drivers come since I upgraded to windows 10. I would like to know if any of you have had similar problems with windows 10 and Pd or if there is a certainty that windows 7 has behaved better with pd than w10. I'm at a point right now that I don't even want to imagine the problems if I upgraded to w11. I wish it was just my problem, but I'm afraid it's not.

/mac rant time - got a 2010 13" macbook pro about 5 years ago because it was an incredible value - (the 13" didn't have the graphics card problems) - I hate it now - its such a brick - but it will never die so I could justify getting a better laptop. the battery life is about 2 hours at best but you can open it up and change it but it still feels like a broken battery

my mom tho decided to go to art school a while ago so I bought her a decked out 2015 15" macbook pro one christmas so she could edit video and look like a cool person (she switched to interior design and ended up working at an SBC but that thing was always a champ at anything) - so jealous of that screen - the 13" is like 30hz 1280x700 - that 2015 mbp is really the best value right now - except the battery is legit glued onto the frame- they replace the whole bottom shell when they fix it at the genius shop - you can buy a repair kit that comes with glue dissolver. Well she was using crappy chargers and it quit charging so either the power part or SMC or the whole thing is broken and it's not worth it to try and fix it - fortunately the newish 16" is finally a decent replacement for it - so merry christmas - she uses it to watch TV when she travels - the audio on that sounds so good, and the over a day long battery life, its just the best laptop because its such a huge amount of tradeoffs to get a laptop right - I kind of wonder if people complain enough about the latency theyll focus in on fixing it. Theyre really deep into their own lore at this point - its annoying - even rosetta 2 - if they follow it then things will smooth out around version 6 and version 12 will be the high point

in summation: dongles

I'm curious tho - pretty sure opening the pd doc for the camomile VST3 with plugdata would fix the midi problem (because theyre both libpd under the hood the midi problem might be with the helper code or the JUCE backend besides the older version of PD/libpd camomile is at) and you can just run plugdata and patch live in reaper as a VST3 - has some extra DAW objects too.

it looks like focusright and motu are in a usb3 dac latency war as well .. I dont own anything with a usb-c port - I got dongles tho

Hello, first of all I want to say that I have been using Pd for 6 years on a PC i5 (fourth generation) 16gb ram and Windows 7 ultimate. Pd and other DAWs I have have always worked without any stability problems. A year ago I upgraded to Windows 10 home (I have always optimized Windows following the indications offered by Merging Technologies and some professional DAWS) Today all the software related to audio works perfectly and without any problem except PS that drives me crazy.

Just create a new patch with 2-3 tables and 2-3 signal objects to start the instability in Pd.
The first symptom that appears is the "feeling" of "overloaded". For example, when dragging an object with the mouse, the object is delayed with respect to the mouse pointer (the more the object patch is loaded, the more noticeable the delay is)

If I save the content of a table of only 8820 samples for example (200ms) with [soundfiler], it can take between 2 and 3 seconds to wait until the message appears in the console

It has also happened to me (although on fewer occasions) that when I press a bang button, the button remains pressed in black and Pd blocked (although I am not aware that this problem is directly related to the other comments).

I want to make it clear that I have not had any problems related to the audio, it is with the GUI that makes me think that something is not right. The first of the problems that I have named is the one that I consider serious for me, because it prevents me from working at ease and in the end I end up not going ahead with any patch. This happens to me in version 0.53.0 that I have now and in the previous 4 versions. I have used the same patches on a laptop that I have and everything works normally. I can't get to understand what is really happening and what the blissful problem may be related to, I have asked several Pd users on telegram and they have not been able to help me either...

Any ideas that occur to you will be welcome. Thank you!

@Coalman Maybe define the send as ascii or convert to a string of the decimal values of the ascii characters in python before sending? ......... https://www.codegrepper.com/code-examples/python/ascii+to+decimal+python
[list tosymbol] will convert the decimal back to characters in Pd........ and it might then be easier to diagnose any problems.

Also there is a dedicated binary in your Pd distribution called pdsend (it is in the bin folder along with the Pd binary). It can be called in Python (probably needs to be copied to a folder where Python will find it).
Then use [netreceive] in Pd to receive what is sent through pdsend.
There is a code snippet here........ https://guitarextended.wordpress.com/2012/11/03/make-python-and-pure-data-communicate-on-the-raspberry-pi/ ...... unfortunately a screenshot so it will need to be typed out again.

BUT the comma in the message "IU.SFJD.00.BHZ | 2021-08-19T12:45:49.019538Z - 2021-08-19T12:46:05.269538Z | 20.0 Hz, 326 samples" will split the message when it arrives in Pd.
AND more importantly.... I am pretty sure that a pipe "|" in Python passes information (before the pipe) to an operator (after the pipe) and that could be why the message fails....... trying to pass "IU.SFJD.00.BHZ" to a non-existent operator "2021-08-19T12"
David.

I think I finally figured it out!
Well, not sure it solves all my problems, but at least here is a limitation of pd~: midi inputs and outputs (obviously)! There were a few of those in one of the libraries called by mybigpatch.pd (r_cycle).

So here is my way around it, in case it might help others:

• In the main patch, capture notein and send [notein $1 $2 $3( to [pd~]:
  
• in the pd~ subprocess, capture the incoming in an abstraction ./myfolder/notein.pd:
  
  and replace all instances of [notein] with [./myfolder/notein]
• similarly for noteout, an abstraction ./myfolder/noteout.pd to use in the pd~ subprocess:
  
  and replace all instances of [noteout] with [./myfolder/noteout]
• in the main patch, replace noteout with [r noteout]:
  
• and the same thing with ctlin, ctlout, bendin, bendout, midiin, midiout, etc.

And the command line magic trick (that it took me a while to figure out) in order to replace all this easily in all pd files:
$ sed -i 's+\(touchin\|polytouchin\|bendin\|notein\|ctlin\|midiin\|midiout\|noteout\|ctlout\)+'./myfolder/'&+' *.pd, which will prepend any instance of notein & co with ./myfolder/.

Improvement suggestions are of course welcome.
Cheers!