touch in/out for audio... when...oh when??

This has been an issue for many years now - the inability for touch to pass audio from one process to another. We’ve found a localhost workaround, but now we really need to pass audio
to another computer.

Touch in seems to read at 60hz, not at 44100 or else.

can derivative give us some feeedback on when the ability to pass audio from one process to another through ip addresses will be implemented?

thanks!
dani

As far as I know that isn’t on the feature schedule right now. It’s much more complex than just allowing a higher sample rate as a lot of the code for Touch In/Out would need to re-done.
It would also have limited usefulness since 44,100hz stereo uncompressed audio will require 350KBytes/second transfer rate, which makes it unusable for anything but local area networks. Consequently using audio cables with devices like the Edirol FA-101 that has multiple out/ins is a far better method of getting audio from one computer to another. This is true in terms of CPU usage, latency, and sound quality (The Touch In/Out would likely suffer from popping as it’s not designed for audio).

You can send audio out the Touch Out CHOP, and receive it intact with the Touch In CHOP.

Same goes for the OSC Out CHOP and OSC In CHOP, which also makes streaming audio usable with other audio applications.

yep, thanks. But I think the issue is compression. Uncompressed audio requires too much bandwidth. I guess my question is - for both video and audio - if we can use codec on either end to send compressed data.

d

Compressed audio, no. Mind you uncompressed audio needs less bandwidth than compressed video. What is your bandwidth limit?