|
it seems to take me ages to bounced down my tunes, any tips?
|
View this Thread in Original format
| themonkeylover |
it seems to take me ages to bounced down my tunes (there each 25 tracks min) and there taking about 7mins each. Times that by 9 tunes and that's gonna take forever.
just wondered if theres anyway of doing it quicker, but will also keep the high quality (same as teh realtime)
Also, and this is a really important one...After ive bounded the tracks down, im finding that theres unwanted sounds that have arrived. like loud clips and crack sounds...and by looking at the waveforms, im having to get my pen out and redraw the smooths lines back in...this is a major case when ive used effects on the tracks.
just wondered if theres any tool out there thats helps?
thanks gor you time.
matt |
|
|
| LoveHate |
| i have always wondered what bouncing is...is it exporting a track with effects added to it..and then exporting it back so its easier on the cpu? |
|
|
| DJ RANN |
| quote: | Originally posted by themonkeylover
it seems to take me ages to bounced down my tunes (there each 25 tracks min) and there taking about 7mins each. Times that by 9 tunes and that's gonna take forever.
just wondered if theres anyway of doing it quicker, but will also keep the high quality (same as teh realtime)
Also, and this is a really important one...After ive bounded the tracks down, im finding that theres unwanted sounds that have arrived. like loud clips and crack sounds...and by looking at the waveforms, im having to get my pen out and redraw the smooths lines back in...this is a major case when ive used effects on the tracks.
just wondered if theres any tool out there thats helps?
thanks gor you time.
matt |
Could be any number of things, but unless something is wrong with you system it sounds like you're doing a realtime (not offline) bounce - some soundcards/PC's can't handle bouncing all the tracks while recording so you could get that dstortion from the system freaking out.
Are you using and Onboard or Soundblaster soundcard by any chance?
What sequencer are you using?
Offline bounces are identical to real time, as long as there is obviously no outboard gear used, in which case you have to do realtime.
In logic you just hit the bounce button on the master channel and select your output options and save location - that's it.
In protools you have to set a stereo (if it's stereo you're working in) track to record and bus the master to input.
LH - bouncing is taking one or more tracks and essentially internally recording them (so all fx, automation, etc) are consolidated in to the result.
In the case of the master channel, it's your track.
In the case of a midi/vst/AU track it turns that in to an audio recording. |
|
|
| themonkeylover |
thanks for getting back to us...and i should of explained a little more.
so im boucings each track down individually as i take my tunes to a proper studio to get mixed down/mastered correctly there. i could of course do the whole track mixed down fine at my house, which my system (cubase 4, prosonus firebox) doesnt have a problem with.
but im finding that after ive mixed down a channel, where certain effect come in, they sometimes leave the waveform of that sound looking differntly, obviously thats becuase the (glitch effect for example) is altering the sound, but once i play this sound back, there are small crack sounds (as i call them)...this happens loads if i use the chopper effect in cubase as well.
about your question on bouncing down. well what im trying to do is bounce down each track indiviually but also all at the same time...so instead of the tracks all going into one main track ready for mastering, they'll all be indiviually seperate...
thanks |
|
|
| DjStephenWiley |
| quote: | Originally posted by LoveHate
i have always wondered what bouncing is...is it exporting a track with effects added to it..and then exporting it back so its easier on the cpu? |
yes, that's a very common use of it. Something that I always do, and most others I'm sure do as well, is do my final mix downs with pure audio bounces. I find it to be much more accurate.
I take the loudest part of the song with the most instruments firing and zero out every channel. I slowly raise and lower each channel until I am happy with the levels. There is always of course even more processing done here but it's a bit different. Technical term is stem mastering. It used to be the standard. Mixing houses that used to provide these services (at a very high price) are all but gone.
Anyway, sorry to ramble. But yes, bouncing to audio will save you CPU. Again, I also think things can sound different when you bounce it to audio, which is obviously very important. |
|
|
| DJ RANN |
| quote: | Originally posted by themonkeylover
thanks for getting back to us...and i should of explained a little more.
so im boucings each track down individually as i take my tunes to a proper studio to get mixed down/mastered correctly there. i could of course do the whole track mixed down fine at my house, which my system (cubase 4, prosonus firebox) doesnt have a problem with.
but im finding that after ive mixed down a channel, where certain effect come in, they sometimes leave the waveform of that sound looking differntly, obviously thats becuase the (glitch effect for example) is altering the sound, but once i play this sound back, there are small crack sounds (as i call them)...this happens loads if i use the chopper effect in cubase as well.
about your question on bouncing down. well what im trying to do is bounce down each track indiviually but also all at the same time...so instead of the tracks all going into one main track ready for mastering, they'll all be indiviually seperate...
thanks |
So as I understand it, you're doing individual bounces of discrete tracks, but you're doing them (25+) all at once? There's your problem.
I don't think your system can handle multiple bounces at once, and that crackling sound is IMO the driver buckling under the pressure. You're effectively asking your system to playback all the tracks, with FX (etc) and record 25+ tracks at once.
Try bouncing a lesser number of tracks as see what happens, say like one third of them.
You could also enlarge the buffer on the driver to something very big and that way it *might* perform better.
However if it does that crackle on a single track bounce then you have a problem else where.
At the studio all mixes are purely in audio - yes, 85% of them are audio anyway but everything else gets bounced to audio for the mix.
Stem mixing is a different thing though - you're not giving individual
tracks to a engineer - stem mixing is where you take all the tracks and group them in to stems (i.e. perc, orch, synth, etc.) so someone can mix them later - the relative levels of track within the stem groups are impossible to change, but the stems can be mixed to give a slightly different balance of the groups.
For a mix engineer to produce stems takes nothing - you just set up the session so that the outputs of the tracks for each group are
sent to group channels and the group channels are set to pass through and record. That way you have the stems and the master mix. |
|
|
| themonkeylover |
hi yeah thats right im doing individual bounces of each channel as i then take these to a studio for a proper mix down...but like i said, each bounce of each channel is taking 7mins. times that by 25channels per song, and i have 9 songs. thats a longtime...
i cant afford a proper set up at mine for a longtime yet, so to get my tracks sounding 100% i need to be taking them to this studio (plus the results im getting mixing down on my own, compared to the studio results are 100% in favour of the studio). but im just trying to find a quicker way to bounce down all these seperate channels?
also its the question about the unwanted sounds im getting, its actually the fx. the Audio is being cut
when the waveform is not at a 0 Crossing. i just found a tool in logic called the 'Strip Silence' that instead of me having to go throu and redraw the smooth waveforms, this tool actually does it for you! great news, so fingers crossed theres something like this for cubase.
thanks |
|
|
| rulzz |
get faster computer [/endthread]
it seems that there are multiple things wrong with your setup though
once in a while i get extra pops and clicks but usually i narrow it down to few older VST's i use |
|
|
| DJ RANN |
| quote: | Originally posted by themonkeylover
hi yeah thats right im doing individual bounces of each channel as i then take these to a studio for a proper mix down...but like i said, each bounce of each channel is taking 7mins. times that by 25channels per song, and i have 9 songs. thats a longtime...
i cant afford a proper set up at mine for a longtime yet, so to get my tracks sounding 100% i need to be taking them to this studio (plus the results im getting mixing down on my own, compared to the studio results are 100% in favour of the studio). but im just trying to find a quicker way to bounce down all these seperate channels?
also its the question about the unwanted sounds im getting, its actually the fx. the Audio is being cut
when the waveform is not at a 0 Crossing. i just found a tool in logic called the 'Strip Silence' that instead of me having to go throu and redraw the smooth waveforms, this tool actually does it for you! great news, so fingers crossed theres something like this for cubase.
thanks |
OK couple of different things here.
Firstly, exports (bounce to disk) can sound differnt to "printing" bounces for a number of reasons, but generally the print is better.
This is because most sequencers use a different internal path for each function resulting in different outputs. For instance dithering comes in play when you are bouncing to to 16b 44.1 but working in 32bit float etc. Also, some plugins behave differently in an export compared to a print (automation simplification etc.).
Printing is the best solution because you are "recording" it in the desired format which introduces less artifacts than exporting and have less possibilty of something unexpected happening.
However the issue of cracks a pops coming in to your individual track prints mean something is wrong with your system at a base level.
You don't need a pro system to do prints - try changing the buffer on the soundcard to a larger setting (just for the print). Also, nuendo users and some cubase user reported bug similar to this - you might want to fully update it - if it's a crack, that could be your issue.
Also, make sure you're using the latest driver for your soundcard. That's the only things it can be unless you're using a pentium 2 PC. |
|
|
| cammaxwell |
Quick question for you guys....
Why would you bounce all your channels to audio for the mixdown? Isn't this the stage when you try to make subtle changes to improve the whole track? Wouldn't you need to possibily change some other settings before coverting to audio? Things like the efect settings, reverb and delay for example? Once it's in audio you lose that option right? |
|
|
| DigiNut |
| quote: | Originally posted by cammaxwell
Why would you bounce all your channels to audio for the mixdown? |
The only plausible reason I could think of is a really, really, really slow computer.
Or, well, I guess if all the sound is coming from external hardware, then you need to "bounce" it, but that's different. |
|
|
| DJ RANN |
| quote: | Originally posted by DigiNut
The only plausible reason I could think of is a really, really, really slow computer.
Or, well, I guess if all the sound is coming from external hardware, then you need to "bounce" it, but that's different. |
Humor me - Do an export (bounce to disk) and then do the same project as a printed bounce (record).
Now put them in the same blank project, phase invert one and press play.
they should cancel out and hear nothing but slience because they'll be identical right?
Do it and then report back here ;) |
|
|
|
|
