Discovered this by accident and not sure if its a bug or by design but:
Buffers of identical names are shared assuming they are initialised in both devices.
Set up 2 tracks both containing a device. In each device place a buffer called test (or whatever).
Read a file into the buffer in one device.
Expand the buffer in the other device.
Voila.
With a bit of jiggery pokery you could have something approaching real time?
Thats whats happening for me anyway. Course it could be a bug!
Passing audio from one device to another workaround
Re: Passing audio from one device to another workaround
Its not a bug.
I have doubt you'll be able to come up with something that really works as audio pipeline from one patch to another.
But there are of course nice possibilities here if you think about creative resampling
Robert
I have doubt you'll be able to come up with something that really works as audio pipeline from one patch to another.
But there are of course nice possibilities here if you think about creative resampling
Robert
-
- Posts: 95
- Joined: Tue Sep 01, 2009 4:22 pm
Re: Passing audio from one device to another workaround
If you want to make a buffer (or other named item) be specific to a single device, prepend the name with three dashes. So, instead of calling a buffer "dogboy", you would call it "---dogboy". During runtime, the "---" is internally translated into a number (like "012") that is unique to each device, thereby preventing unintended sharing of buffers, colls or other named objects.
[ddg]
[ddg]