-
nzfs
i use zoom to give music production lessons. i have a few students running osx, and when they share they screen with me and check 'share computer sound' they can select zoomAudioDevice as the output in ableton live for example, and the sound from live is routed to zoom. haven't tried it with pd but i asume it would works the same way.
-
-
nzfs
@whale-av i didn't had time to run more tests, but searching stackoverflow i found out that when you send a message using socket.io it's converted to a string, that's why it's all being received as a symbol in pd.
-
nzfs
@ddw_music yes, the problem must be in the sending side, i'm gonna check the code to see if i find where the problem is.
thank you for taking the time to do the test with sc -
nzfs
@ddw_music i tried both as an integer and as a flot. so far the only workaround i found is using cyclone/fromsymbol and is working quite nice.
thank you all for the help
-
nzfs
@ingox yes, that might be the problem. im sending the message from the browser using nodejs and socketio, and even if the number is cast to an integer, i guess when it is send it's converted to a string.
-
nzfs
@alexandros i tried to do it the vanilla objects, after netreceive, oscparse and list trim i can print the message like this:
but if after that i try to route the message according to the address, it doesn't work.
EDIT: never mind the routing problem, i'm stupid enough to have misspelled 'wrist', but...
when i get to the end of the message and try to send the number to a number atom, i get the same problem as at the beginning (which i resolve with the fromsymbol object): gatom: no method for '255' -
nzfs
edit: the message, even though it was sent as an int, was beeing received by pd as a symbol, using cyclone/fromsymbol before the number atom did the trick.
hi, im trying to receive an integer via OSC. if after unpackOSC and routeOSC y print the message, i get the number i'm sending, but as soon as i connect routeOSC to a number atom i get this message:
gatom: no method for '529'
can this be a bug in vanilla 0.50.2? i've done exactly the same before and it has worked...
-
nzfs
@whale-av i've already set the path to the folder.
never thought of the dlls being 32bit while i'm running 64bit pd, that's the problem. thank you very much!