Re: strange or not strange!
I have installed Tracktion 4 on my laptop and configured it. I have connected my laptop to my X32 using USB and configured the X32 to talk with my laptop. Then I downloaded a couple of sample multi-track files and loaded them into Tracktion. I am able to successfully play them into the board and listen with headphones. But my question is: I don't know which parameters can be changed and which cannot. For instance, if I turn a gain knob while playing back a song, the volume changes. But am I really changing the input gain or just using that knob like a fader? I thought I remembered reading somewhere that when you are sending input in through the X-UF card, you cannot change input gains. Does that mean that your input gain levels have to be correct for the X32 before you play them in? I can't figure out where I can read more about this. I want to use this method to do virtual sound checks with my band. I know I will need multi-track recordings of the band taken off the X32 but I don't understand what I can mix when playing it back. Is it everything except head amp levels?
I would suggest that you take it in stages.
- Record your band during the next gig, making sure that the gain structure is consistent (gain will influence the level of recording, and the mix playback - not going into details here), so that you have decent level of recording on Tracktion.
Keep an eye on the monitored levels (on Tracktion PC screen armed tracks) during sound check before the gig so that your inputs are balanced and not clipping. Apply gain +/- if the recording level is too low/too high. This is the only channel setting that will influence the recording. Apply THEN any X32 processing/fading/bussing (that will NOT be recorded) for the venue mix.
- if you change the gain during the recording, the recording level WILL be changing. If you mute the channel, it will mute the recording (if I remember well but not 100% sure). Any other setting (including faders, eq, comp, gate, effects, etc...) will be only for the audience and not applied to the recording.
- remember to save settings and scenes on the X32.
- if you replay the recording through the same channels and channels settings (once switching the inputs from analog to card/pc input) you should have a consistent output.
Then you would be ready to go for virtual sound check. Anyway virtual soundcheck, I discovered, is an illusion, applicable only to large venues (or open air where the stage if far away) or to music genres that have very low direct sound pressure from stage on the audience.
Once you add the direct stage to audience (and stage to mixing position) sound, the sound from the wedges, your nice virtual sound check would be to be recalibrated anyway. At least this is my experience in pretty much any smaller/mid size venue.
Which leads me into my next question: I am using a USB interface between my X32 and laptop because my laptop does not have a firewire interface. However, I have a firewire interface card (Express card for my laptop). Any advantage to using that over a regular USB interface? I have the Behringer ASIO support loaded on my laptop. But I am not clear what the different adjustments on the X-UF USB control panel are. Can someone either point me to where there's more info I can read besides what's in the manual, which does not really explain how or why to adjust anything, or else explain to me the theory of adjusting those parameters? I know a little: I know you don't want dropouts so if get them you have to raise some values until they go away. But when do you raise the different ones on the control panel?
On paper there's no difference. 400Mbps USB 2 vs. 400 Mbps FW. In reality you can find on several sources that USB relies much more on cpu cycles for low level I/O operations, while FW delegates to the chipset. So it's a matter of sustained operation. The PC has to read up to 32 channels bit streams, manage I/O and write the files to disk (ongoing for some hours).
If you have a recent PC, it shouldn't be a problem for the CPU. If your PC is older, using FW will free up some cpu cycles. I would suggest that you run tests with the expected number of channels to be tracked and verify on field or rehersal if the sustained recording is ok or if you have glitches. I would suggest that you listen then to the recording carefully to find any bad spots (yes, time consuming).
I can't help with ASIO settings, sorry.
cheers