Those channels don't have full DSP anyway, so using those channels for plugin returns might be ideal. I suppose you 'might' be able to get more than 16 channels by using channels 33-40 for the USB returns. You couldn't run more than about 16 channels of plugins anyway, since you have to take away a second channel for the return. I wouldn't trust it for more than a few channels in a live situation. It's really more a proof of concept than anything. This method that I listed is the only way to run plugins "on" the TF series right now. At the moment, the only card announced for this single NY slot is the Dante card that is supposed to be released early next year. The TF uses a new NY card slot as opposed to the older MY slot found on most other Yamaha consoles. That would also defeat the purpose of the TF being a console aimed at "entry level" engineers and might undercut sales of the bigger consoles. I doubt there ever will be one since the waves card and server would cost more than the TF console itself. Steve, There is no Waves card for the TF series. You can't simply "insert" the USB send/return. So in summary: Use a fast computer Pay close attention to the total latency Use low/no latency plugins Remember that the audio is returned to a different channel. Granted, this isn't as nice and headache free as running the plugins inside a big Avid or Digico board, but at least it's possible to run plugins this way - and it's pretty fun too. 25) when using the custom layer or the DCA roll-out/spill layers. The channel location is less of a concern (i.e. All other channel settings (EQ, Dynamics, Aux sends) should be done from channel 25 (post plugin). Channel one then becomes nothing more than preamp control. (If you want, you could use channel one to route to the auxes (monitors), thereby keeping the plugin sound (and latency) out of the monitors.) You'll then make sure the USB input is selected for channel 25, and route that channel to the stereo and sub busses as applicable. It is very important to turn off the routing of channel 1. That puts the returned audio on channel 25 on my TF console. So, for example, I'll take the preamp signal from channel 1 on the TF, into the VST host, then return the output to return channel 25. In my case, that is returning the audio on channels 25-32. But you'll return it on different channels. You'll need to patch the audio in the VST host (LiveProfessor) to use the inputs from the TF preamps. If you can keep the total RTT (Round Trip Time) under 10ms for FOH sound, then you should be fine. You also have to use plugins with extremely low (or no) latency. Keeping the total latency as low as possible is very important since the TF doesn't have any latency compensation for this type of thing. going from 2ms to 3ms of Yamaha ASIO buffer size, increases the total RTT latency to 11.9ms (a 3ms increase on the entire USB bus for only a 1ms buffer increase in the audio driver). The USB latency is not consistent and increases as you increase the buffer size of the ASIO driver. In my case, it shows to be a total round trip time of 8.9ms (6.9ms of the USB bus itself). If you look under the Control Panel for the ASIO driver, you'll see the latency settings of the entire USB path. The real latency problem is in the USB bus itself - something we can't control. In my case, with the driver set to 96 samples (2ms), LiveProfessor shows the total 2ms of software latency. LiveProfessor tracks the software latency under Audio Options. I use LiveProfessor because it isn't limited to just Waves plugins. I then used LiveProfessor as my VST host, but Waves multirack would work fine too. I tried it at 64 samples but had random brief dropouts. In that computer, set the Yamaha USB driver's latency to as low as you can get it without dropouts. For starters, you have to use a very fast computer. There are some caveats to doing this, but as long as you can work with the limitations and understand the process, it will work just fine. By using the 34x34 USB interface of the TF series, I can route multichannel audio to the computer, process it through native plugins, and return it to the TF mixer. I imagine the process is similar for other low end digital mixers. I have successfully been able to run Waves (and other brands of) plugins on my TF3. Thought I would write about something that I've been able to successfully do with my TF3.
0 Comments
Leave a Reply. |