@gsagostinho

Thanks Gilberto, I updated the subpatch to take an audio signal.

Thanks for all your help everyone.

This is my final solution;'

- subpatch

Hi all,

Thanks for your help guys. I will try out your suggestions this evening when I get home from work.

All the best,
David.

###Status: Resolved
###-
Hi all,

I want to be able to "ask" the dac or a patch if it is producing audio.

I was looking at doing something like this;

[some_signal_producing_object]
|
[evv~ 500]
|
[> 0]

This produces 1 when audio is being produces and 0 when it's not, however the problem is I don't know how to bang this setup to acquire the playing state.

I'd like to ask it, "are you playing audio?" and then get a single response, yes / no.

Does anyone have a suggestion as to how I might proceed with this?

@CannonBall6

Did a internet search and found this?

@gsagostinho

I deleted every patch cord and patched in the exact order I needed everything to happen in.

This appears to have resolved my issue.

Thanks @gsagostinho .

@gsagostinho

Hi gsagostinho, there is a trigger used outside of this sub-patch, I was using it to enforce the bang order. I've included a picture. I'd expect it to bank from the right float (0) to the left symbol (client_1).

I did read about the patch cord connection order being an important part of single flow ordering and I did try and apply it before by doing what you said, delete patch cords and apply again.

It is possible that the patch order is still wrong so I will attempt to do as you advice and remove the patch cords again.

I will report back.

@nlogax

Check out the package prerequisites. It author of the package isn't sure.

[Resolved] - see gsagostinho first reply for solution.

Troubleshooting listed below - you might have more luck understanding the issue by checking here first.

Hello,

I've been working on using [netsend] and [netreceive] for sending OSC data between a series of audio clients.

I'm having trouble working out a way to send a multi part message. My issue is getting the timing right. I want to be able to build a multi part message like the one in black below. The image below is of a sub-patch which is "trying" to build a list which would then be send via netsend.

My real issue is working out how to provide all the parameters before finally sending the list.

If there was a way to use pack to construct a list then bank it to send it's data then I'd be right.

Any ideas?

the_destination/type_of_message/some_parameter/some_value

###-----------------------------------------------------------

###Troubleshooting - Update
Using print I'm seeing this signal flow which I can't explain.

If I send a bang in to inlet 1 - Destination print 5 is triggered first then print 4. Is this normal?

@sebfumaster

Perfect. Thanks sebfumaster.

Hello.

I would like to use the same send argument on multiple patches and have them operate within the scope of the patch they are running only. As in, not to communicate between patches.

Patch 1.pd : [send all] [receive all]

Patch 2.pd : [send all] [receive all]

@portabello

Thanks for checking. I appreciate it.

It's possibly a problem with Linux, only with the current build. Or, perhaps it's just my set up.

I was able to get the OSC part of my program build last night using the help docs you provided me.

Thanks for helping me Portabello, very much appreciated.

David.

@portabello

Thank you for providing me with the help documents.

Out of curiosity, have you tried seen for yourself that the help data is missing from PD 0.46 ?

@portabello

Thanks for the reply. Very useful information.

PD 0.46 does not have help info for [oscparse]. That's a big part of my problem. I get this error message when I right click on the [oscparse] object.

####sorry, couldn't find help patch for "oscparse.pd"

Where did you acquire the info about binary stream using [netsend] and [netreceive] or the** [oscformat] **object? I'm finding it hard to help myself. Typically I'd find the answers I need in the manual but I haven't had any luck of late.

@portabello I installed 'PD 0.46-0' but am having difficulty using it. I don't seem to be able to find any info online about how to use it either.

If I send "/client 1"

Error Message: oscparse: no method for '/client'

How would you parse that message using [oscparse] ?

@portabello said:

oscparse

Thanks, will check it out.

#Hello#

I spent a while yesterday moving away from PD-Extended as I was only using it for the mrpeach OSC objects. Now that 0.45.4 has [netsend] and [netreceive] I shouldn't need mrpeach OSC anymore.

##Issue##
I have moved my project over to pd-vanilla and am now using [netsend] and [netreceive]. My problem is with [netreceive]. I don't know how to handle / parse the bundle that comes out of it.

###Request###
Could someone here explain how I could, for example, print the data coming from [netreceive] to the console? Know how to print the data to the console should show me how to utilise the bundle data coming from the [netreceive] object.

I would greatly appreciate your time and help on this issue.
David.