robbyk
Max Output Level: -76 dBFS
- Total Posts : 705
- Joined: 2009/11/30 17:09:49
- Location: Madison, WI
- Status: offline
General editing Q (vocals, guitars, etc)
Do I bounce to track my raw, dry edited vocals, guitars, etc? For example, I have gone thru all my vocal tracks and edited out the breaths, spaces, etc and have all the various tracks synced up with fade ins / outs so now I have a bunch of clips per track. Is it general practice to bounce these clips to track? I still have, of course, to EQ, instantiate plugins apply envelopes, etc. I am just wondering is there an advantage to a single track over an assemblage of clips. Less CPU, disk mngmt., anything like that? Thanks in advance!
"I'm just workin' on a good life, the way it is." Best, Robby K PC Specs: Dell XPS Tower, Intel Core i5 7400 CPU 3 GHz @, 8 GB RAMHardware: Focusrite Scarlett 2i4, Line 6 TonePort UX1, ART Tube MP, JBL LSR2325P 5" Bi-Amped MonitorsSoftware: Windows 10 Home, Sonar 8.5.3 Producer, Sonar Producer X1, Sonar Producer X2 expanded, Sonar Producer X3, Ableton Live 8.3.4, Ozone, Alloy, Toontrack, Podfarm, IK Multimedia, Garritan, Melodyne, Antares, Bias, Rob Papen, OhmForce, Don't Crack... Music Studio
|
gcolbert
Max Output Level: -67 dBFS
- Total Posts : 1176
- Joined: 2010/11/13 18:34:06
- Location: Windsor Mill, MD
- Status: offline
Re:General editing Q (vocals, guitars, etc)
2012/04/11 08:01:48
(permalink)
☄ Helpful
I'm not an expert here, but I've tried using both methods. What I've found is that I was always going in and making changes to the bounced track and often wishing that I still had the original spliced track to make additional corrections to. On the other hand, it is a lot easier to move and copy the bounced track it you need to do that. I would recommend that, at a minimum, you keep your original comped track around. Glen
|
FastBikerBoy
Forum Host
- Total Posts : 11326
- Joined: 2008/01/25 16:15:36
- Location: Watton, Norfolk, UK
- Status: offline
Re:General editing Q (vocals, guitars, etc)
2012/04/11 08:27:32
(permalink)
☄ Helpful
There's no right or wrong. I rarely bounce now that I have the CPU power to not have to. When I do bounce, I do as gcolbert suggested and always keep the original. IIRC if you use bounce to track the original remains anyway, whereas bounce to clip will overwrite the original. Bouncing and then archiving the original will always save processing power but whether you need to do that is down to how much power you have and how power hungry your projects are.
|
John T
Max Output Level: -7.5 dBFS
- Total Posts : 6783
- Joined: 2006/06/12 10:24:39
- Status: offline
Re:General editing Q (vocals, guitars, etc)
2012/04/11 09:13:13
(permalink)
I very rarely do this either. Perhaps in some really extreme situation where I've had to edit together a passable take out of a load of bad takes and then still have to AudioSnap it or something like that. But as always, avoiding such circumstances in the first place is always the best move.
http://johntatlockaudio.com/Self-build PC // 16GB RAM // i7 3770k @ 3.5 Ghz // Nofan 0dB cooler // ASUS P8-Z77 V Pro motherboard // Intel x-25m SSD System Drive // Seagate RAID Array Audio Drive // Windows 10 64 bit // Sonar Platinum (64 bit) // Sonar VS-700 // M-Audio Keystation Pro 88 // KRK RP-6 Monitors // and a bunch of other stuff
|
robbyk
Max Output Level: -76 dBFS
- Total Posts : 705
- Joined: 2009/11/30 17:09:49
- Location: Madison, WI
- Status: offline
Re:General editing Q (vocals, guitars, etc)
2012/04/11 22:51:37
(permalink)
Thanks all, that is really helpful to know there is no pressing need as long as my cpu is holding up. On the vocal tracks for my current project, it is now ~15 clips per track and multiply that by 6 vocal tracks I worried how that might turn out during heavy mixing sessions upcoming this weekend. I probably will bounce to track before archiving the project but, like you say, save the original. Thanks again, much appreciated, it's good to hear from the voice of experience.
"I'm just workin' on a good life, the way it is." Best, Robby K PC Specs: Dell XPS Tower, Intel Core i5 7400 CPU 3 GHz @, 8 GB RAMHardware: Focusrite Scarlett 2i4, Line 6 TonePort UX1, ART Tube MP, JBL LSR2325P 5" Bi-Amped MonitorsSoftware: Windows 10 Home, Sonar 8.5.3 Producer, Sonar Producer X1, Sonar Producer X2 expanded, Sonar Producer X3, Ableton Live 8.3.4, Ozone, Alloy, Toontrack, Podfarm, IK Multimedia, Garritan, Melodyne, Antares, Bias, Rob Papen, OhmForce, Don't Crack... Music Studio
|
Wave
Max Output Level: -87 dBFS
- Total Posts : 174
- Joined: 2012/04/10 10:14:55
- Location: Sunny Bono Drive; first left on right
- Status: offline
Re:General editing Q (vocals, guitars, etc)
2012/04/11 23:05:53
(permalink)
Bounce only to free up CPU. When you bounce you loose sound quality in many ways if its not done correctly. Pans, Bit depths, optimum levels gain staging etc.. ect.. ect. Even if they say 64 bit we are really in a 32 bit world as far as most synths and plugins go and you will take a hit on quality from a bounce. Do not bounce.
Cheers, Wave Sonar Producer Expanded X1d 64 Windows 7 Pro SP1, i7-2600k 3.4GHz, Crucial SSD Drives, 16 GB1866MHz Ram, Radeon HD6800-3 displays Lynx L22 Sound Card , Mackie HR624 Monitors PCR-500 Keyboard Controller
|
CJaysMusic
Max Output Level: 0 dBFS
- Total Posts : 30423
- Joined: 2006/10/28 01:51:41
- Location: Miami - Fort Lauderdale - Davie
- Status: offline
Re:General editing Q (vocals, guitars, etc)
2012/04/12 00:14:57
(permalink)
Even if they say 64 bit we are really in a 32 bit world as far as most synths and plugins go and you will take a hit on quality from a bounce. Your confusing bit depth and PC architecture. There 2 different things entirely. There is no such thing in recording in 64bit. sound cards canonyl do 24bit. 32bit is a floating point bit rate, not a fixed point. Too much miss info! When you bounce you loose sound quality in many ways if its not done correctly. You can nail your hand to the wall if you use a nail gun incorrectly. Bouncing is 1000% fine to do. Too much kool aid had been drank and its time to get a sugar detox.. If you don't know how to bounce, then just read a couple sentences in the help file, so you can bounce "properly" CJ
|
FastBikerBoy
Forum Host
- Total Posts : 11326
- Joined: 2008/01/25 16:15:36
- Location: Watton, Norfolk, UK
- Status: offline
Re:General editing Q (vocals, guitars, etc)
2012/04/12 02:20:12
(permalink)
When bouncing never dither unless changing bit depth, preferably try and do that only once per project life. For example I work at 24 bit and a project stays at that bit depth right up until I bounce my final stereo 'mastered' track. Even my stereo mix bounce stays at 24 bit until that final stage when it comes down to 16 bit for CD compatibility.
|
Wave
Max Output Level: -87 dBFS
- Total Posts : 174
- Joined: 2012/04/10 10:14:55
- Location: Sunny Bono Drive; first left on right
- Status: offline
Re:General editing Q (vocals, guitars, etc)
2012/04/12 08:04:25
(permalink)
When I bounce a track to "clean it up" it is just as if I had mastered a final mix for just that track alone. All the Pans, internal data calculations for effects, output gains, meter levels and so on are now a permanent part of that tracks data. Hence I just lost the original and if the bounce was not at a "mastered" quality I would not be able to start fresh again. Granted the loss is small IF I know what I'm doing. But when I bounce over and over I take hit after hit on the quality. This is why bouncing should not happen at all. About the 32 bit float: from my understanding a floating integer is happening within the DAW itself "meaning the daw will not "calculate" a level "clip" within the program itself, however when I bounce the float data will needs to be "converted" back to bit data. For example: if my levels "are not at optimum" I take another hit on the tracks quality "ouch". This all happens If I bounce > bounce > bounce. I do not bounce unless I have to. But thats how I do things, you can operate your DAW any way you want your the Boss.  The main thing is that in the end you have that "Big Sound" that makes you proud.
Cheers, Wave Sonar Producer Expanded X1d 64 Windows 7 Pro SP1, i7-2600k 3.4GHz, Crucial SSD Drives, 16 GB1866MHz Ram, Radeon HD6800-3 displays Lynx L22 Sound Card , Mackie HR624 Monitors PCR-500 Keyboard Controller
|