Exit Only

I was wondering if pluggo can somehow send audio to Max/MSP using the s/r, send~/receive~, or plugsend~/plugreceive~ objects?

i.e. I have [plugsend~ thisname] in a pluggo insert plugin in logic, and a [plugreceive~ thisname] in max/msp receiving the audio.

I have tried all the combinations and can't get any of them to work.

..and I know audio hijack can do this, but i've had some issues with the jack-inserts, and was hoping to go another route.

I'm currently running Max/MSP 4.6, Pluggo 3.6 and Logic 7.2.2

I was wondering if pluggo can somehow send audio to Max/MSP using the s/r, send~/receive~, or plugsend~/plugreceive~ objects? 

i.e. I have [plugsend~ thisname] in a pluggo insert plugin in logic, and a [plugreceive~ thisname] in max/msp receiving the audio. 

..and I know audio hijack can do this, but i've had some issues with the jack-inserts, and was hoping to go another route. 

I'm currently running Max/MSP 4.6, Pluggo 3.6 and Logic 7.2.2
I'm on OSX 10.4.7.


can-pluggo-send-to-max

I just tested inter-plugin send/receive with each of possible s/r pairs. I was unable get a signal to go from one insert to another.

Here are the two patches that I compiled as vsts and ran in logic 7.2.2

I just tested inter-plugin send/receive with each of possible s/r pairs. I was unable get a signal to go from one insert to another.
Here are the two patches that I compiled as vsts and ran in logic 7.2.2 

Pluggo is basically a runtime version of MaxMSP with a VST interface. So the normal rules for communicating between different instances of MaxMSP apply.

My preferred method of communicating between Pluggo and MaxMSP is to use the udp objects and OSC. For audio the use of network sockets is not very effective, so for all practical purposes it is best to do all of your audio processing inside your pluggo plugin.

Thanks for the reply! I guess I don't understand what the rules for 

communicating between different instances are!

Just to get a feel for it, I made a test patch consisting of a number box connected to [send blah]. I made another patch with [receive blah] connected to a number box.

I then opened the receiving patch in max runtime while the sending patch was in separate instance of max/msp. I found that the send receive pair between the two didn't work. This is good to know!

However, plugsend~ and plugreceive~ exist to send audio to one another, so I don't know why I can't get audio from one plugin's plugsend~ to another plugin's plugreceive~. I thought this was the whole point of PluggoBus.

These are the two most stripped down versions of the plugsend~/plugreceive~ tests that I can come up with:

Could someone please verify for me whether the plugsend~/plugreceive~ objects function as intended with Pluggo 3.6, Logic 7.2.2 on an Intel based mac running osx 10.4.7?

Thanks for the reply! I guess I don't understand what the rules for 
communicating between different instances are! 

Just to get a feel for it, I made a test patch consisting of a number box connected to [send blah]. I made another patch with [receive blah] connected to a number box. 

However, plugsend~ and plugreceive~ exist to send audio to one another, so I don't know why I can't get audio from one plugin's plugsend~ to another plugin's plugreceive~.  I thought this was the whole point of PluggoBus. 

These are the two most stripped down versions of the plugsend~/plugreceive~ tests that I can come up with: 

----------------------
And "plugreceiveTest"

Could someone please verify for me whether the plugsend~/plugreceive~ objects function as intended with Pluggo 3.6, Logic 7.2.2 on an Intel based mac running osx 10.4.7? 

Yeah - perhaps it would have been useful if I had explained that!

The scope of all the send and receive type objects is the instance of MaxMSP they exist in. There must be a better way to say that.

Your patches work fine here in Logic 7.2.3 on Intel 10.4.8.

One thing to remember about Logic, and a disappointingly growing number of other hosts, is that they "intelligently" switch off the processing of plugins when there is no audio present. What this means is that unless your plug recieve patch is actually "processing" audio data in the track, Logic will not let it operate. To get it to work, I loaded the receive patch you posted on a blank track, then imported some audio on to it. In order to use this effectively in a musical way you'll either need to have a way of setting wet/dry in your plugins or have a bunch of zeroed audio files lying around I guess.

That did the trick! Thank you very much for your help! I ended up just sending audio to the bus that the receive plugin was on and it worked. I also was unaware of the logic 7.2.3 update, which I'm currently downloading.

>> One thing to remember about Logic, and a disappointingly growing number of other hosts, is that they "intelligently" switch off the processing of plugins when there is no audio present.

steinberg should have let us turn it off and on for 

individual slots in SX 4 (while remembering the plug-in

steinberg should have let us turn it off and on for 
individual slots in SX 4 (while remembering the plug-in
ID for next time) but no ....


Quote: Andrew Pask wrote on Tue, 03 October 2006 18:12

----------------------------------------------------

> My preferred method of communicating between Pluggo and MaxMSP is to use the udp objects and OSC.

Same here. But I am curious about your experiences with timing accuracy from a pluggo in Logic to Max vs. Max to Max. I experience a big difference: Logic to Max is very unsteady compared to Max to Max.

> For audio the use of network sockets is not very effective, so for all practical purposes it is best to do all of your audio processing inside your pluggo plugin.

Another option (our solution) is to do all audio processing in Max/MSP and use Logic for sequencing only.

Quote: Andrew Pask wrote on Tue, 03 October 2006 18:12
----------------------------------------------------
>
>
> My preferred method of communicating between Pluggo and MaxMSP is to use the udp objects and OSC. 

> For audio the use of network sockets is not very effective, so for all practical purposes it is best to do all of your audio processing inside your pluggo plugin. 

Can Pluggo Send~ to max?