|
cubase - mixing down to audio
|
View this Thread in Original format
| djillicit |
ciao,
so i have a bit of a predicament. i have the technical knowledge on how to do this, but i suppose it's setting myself in the right mindset before doing it.
usually i have all of my tracks in MIDI for peace of mind, just in case i want to change something, or tweak a setting, it'll be much easier. before i know it, a chunk of my track's already written, still all in midi (hardware or VST), and i come to a point where i'm like ", i gotta dump this all in audio if i want my computer to run properly!"
at that point, well, it's a pain in the ass. imagine having 6 minutes of a track with complex midi patterns and signals in each. what if i decide to change a knob, change velocities, etc.
ok, long post. going out for some second opinion, how do some of you deal with the midi/audio conversion? when do you feel "it's right?" in the back of my mind, i know you should do it ASAP, but the "what ifs" always get in the way. Input?
Cheers... |
|
|
| dj_kane |
| im the same mate. i cant get my track finished until i mix it down to audio but if i do that and decide to move and change parts then i have to go back. its pretty annoying and is the cause of 70% of my tracks not being finished. |
|
|
| djillicit |
| quote: | Originally posted by dj_kane
im the same mate. i cant get my track finished until i mix it down to audio but if i do that and decide to move and change parts then i have to go back. its pretty annoying and is the cause of 70% of my tracks not being finished. |
haha, amen brotha! now to find a solution... |
|
|
| No Left Turn |
When I use my Virus B, as soon as I find or edit a sound that I'm going to use, I'll record it to audio immediately. Doing this as early as possible forces me to "commit to the sound". There's no coming back to it days later and fussing with it to no end. You might think "what if later on you find something wrong with it?" If it's an amazing sound that you programmed yourself, then I'd hope that you think it's so awesome that you'd want to save [over] it and therefore can go back to it if you really need to.
And with VSTi's... I usually don't ever render these to audio unless I'm using a CPU-killing synth or patch. |
|
|
| supersonik |
| I just bounce everything to audio. Load it up. Then turn off the vst that I was using and if I ever want to change something. Then I just have to turn the vst back on and change whatever. Then bounce it back to audio again. Once I get what im looking for, I dont really change it that much. |
|
|
| mysticalninja |
| Get LOTS of hardware so you never have to bounce to audio again. That's my plan. |
|
|
| SPAWNmaster |
| quote: | Originally posted by No Left Turn
When I use my Virus B, as soon as I find or edit a sound that I'm going to use, I'll record it to audio immediately. Doing this as early as possible forces me to "commit to the sound". There's no coming back to it days later and fussing with it to no end. You might think "what if later on you find something wrong with it?" If it's an amazing sound that you programmed yourself, then I'd hope that you think it's so awesome that you'd want to save [over] it and therefore can go back to it if you really need to.
And with VSTi's... I usually don't ever render these to audio unless I'm using a CPU-killing synth or patch. |
the "committing to a sound" thing is exactly it...atleast its what i do, in production just like in mixing you need to make sacrifices with where you wanna head with your track! |
|
|
| thecYrus |
| quote: | Originally posted by mysticalninja
Get LOTS of hardware so you never have to bounce to audio again. That's my plan. |
i do it this way.. but otherwise there would still be the freeze option.
or buy a powerfull cpu. the new core 2 duo are great. i don't even have cpu problems with my amd x2 4400+ anymore. i could do whole projects on it with only VSTs. |
|
|
| Drik |
I bounce all my stuff. Do a smart midi part, record it to a audio channel, then just copy and paste that part if I need it repeated. If theres a delay or reverb or other tail, I duplicate the audiotrack and sort it that way.
Good example is orchestral samples and strings I use sometimes, I really don't want to wait ages for a track to load plus my memory to get filled, so instead I do this in a seperate project, then bounce it down for my master track.
This makes your computer happy :)
Also, for fx, create loads of group channels and route tracks into them, keeps fx usage low and gives the same result. |
|
|
| richg101 |
if you are selective on the bits you bounce then you shouldnt have a problem. luckily most edm is repetetive so you only have to record a small ammount of audio for a melody, then loop it. instead of recording whole 'track length' tracks of audio you should bounce smaller sections at a time. then keep your midi's moved to the bottom of the project so they keep out of your way but are availabel when one of your sections arnt right..
imo it is a case of getting it right early. get it how you want it before bouncing to audio. i rather spend a lot longer getting it perfect before bouncing so i dont have to piss around later on. |
|
|
| Drik |
| Hey Rich, hows the label going mate? |
|
|
| dj_kane |
| ok say ive eq'ed my bass and synths then bounce them down to audio wil i have to eq them again? |
|
|
|
|
