-
Multi track audio editing in Vegas Pro-10 issues
I have been using Vegas mainly as a Multi track editor for audio.. Kind of like how folks use pro-tools and I’m hearing some disturbing characteristics in the audio when I mix..
Perhaps I can explain how I work .. I have a recording studio that has the Sony DMXr-100 as a console and I track everything to my Alesis HD24. I have ADAT cards in the Sony which transfer the audio back and forth to the HD24 Via the light pipes… I know I have very clean tracks from the studio, through the board to the HD24. I do not track with EQ or compression (usually recording acoustic styles of music).
Once I finish tracking a project I digitally from the HD24 hard drives to my computer using the Alesis fireport, again, staying all in the digital domain.. I record at 44.1 Khz and tracking to the HD24 which stores in 24bit all audio.. Once I move my the files to my computer I start my editing, creating a project and import all the files across the tracks to the Vegas Audio Editor.. and the files sound great, just like on the hd24.. then things happen and I do not know why.. so hopefully someone can look at this and let me know what I am doing wrong.
I have a house clock running everything digital and I can see everything locking just fine…
My main edits consist of cleaning up the tracks, lining up vocals just the normal stuff… I do not add EQ, I do not add any effects to the tracks. From time to time, I’ll do a quick mix to a 2 track file for reference, but that’s’ about it.. it usually sounds fine….
Since I love mixing on the console I render each of the tracks .. since the files were 44.1 @24bit when I brought them in I have been rendering each individual file using the render function and set up a 44.1 @24bit mono option to use for these tracks. I can have up to 24 tracks of audio but in most cases I find 16 is about all I use. Once I render the files, I just transfer the files from the computer (after rendering) via the Alesis fire port back to the Alesis Hard drive as a new song.. all edited tracks are moved back (very fast) to the Alesis hard drive for my mix.. That’s where things start to sound a bit “Fuzzy” and I have been unable to find any info as to why… (even Sony has not been able to come up with an answer)..
If there is anyone out here that uses Vegas in a similar work mode I’d like to hear from you .. here are some of my questions..
1. am I correct in selecting render as when I want to render an edited audio track (there is no save as like Sony Soundforge).. so, my concern is the render process creating a problem … the tracks after rendering them seem to lose resolution or definition and it really starts to show up as I add a little EQ and then start to bring up multiple files in the mix. It seems like there is something going on when rendering the tracks and they sound thinner and loose depth..
I love Vegas, although I’m wondering if my tracks are getting screwed up when I render the file to a new file/track? I know my clock is solid It is a Lucid clock in a star configuration and as I have said everything seems to be locking just fine!
My sound card in my computer is a Lynx one and I connect to and from the board digitally via the AES-EBU…. from what lynx said is that the AES-EBU locks in to the system when playing tracks or mix’s on the computer…..
I am just finishing a gospel project, Bass, Guitar, Banjo and Dobro and I just feel that my edits in Vegas have compromised my original tracks… The best way I can describe it is they sound “fuzzy” and before I do a bunch more of this I thought I’d ask here and see if anyone here has a similar issue… ..
Am I correct in choosing the option to render 44.1 @24bit… Is there a safer way to render the edited tracks?
Hopefully someone out here works with audio and has some suggestions and or ideas of what I am doing or not doing
Thanks in advance.