@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.