|
|
Post by Randge on Jan 8, 2015 7:44:48 GMT -6
Another Cubase question. Is there an easy way to do crossfades in Cubase? In PT's you just use the crossfade tool in the spot of the crossing regions. I see where you can hit "F" and it puts a fade in, but how does it know which two sections you wanna crossfade? I haven't selected any region to crossfade. I wish I could select the spot I want the crossfade to go and then hit a key and it go there. Or better yet, I wish there was a Crossfade tool. In Cubase, to create a crossfade between two audio events you slide one audio event so it slightly overlaps the other and hit "X" on your keyboard. So, instead of selecting the spot by sliding the selector tool over an area like in Pro Tools, in Cubase you slide one of the events and create an overlap spot which is the crossfade spot. You can double click on the crossfade area if you wanna modify the crossfade curve. You don't even have to do that. Just highlight both regions, even with a big gap, and hit X. Easy peasy crossfade. If it is too far, it will tell you but 99% of the time, you'll have your crossfade. R |
|
|
|
Post by tonycamphd on Jan 8, 2015 15:49:01 GMT -6
Nah I don't dither every channel nor do I worry about it. If my stuff sounds "digitus", I can't hear it. Sounds ok to me. I figure it all ends up in the pot just like a good stew. Am I wrong in this thinking? Probably, but who gives a shit? It's just music. " |
|
|
|
Post by cowboycoalminer on Jan 8, 2015 15:52:18 GMT -6
Nah I don't dither every channel nor do I worry about it. If my stuff sounds "digitus", I can't hear it. Sounds ok to me. I figure it all ends up in the pot just like a good stew. Am I wrong in this thinking? Probably, but who gives a shit? It's just music. " I'll try it and see if I can hear a difference. Either way, I'll be honest. |
|
|
|
Post by jcoutu1 on Jan 8, 2015 15:55:04 GMT -6
Nah I don't dither every channel nor do I worry about it. If my stuff sounds "digitus", I can't hear it. Sounds ok to me. I figure it all ends up in the pot just like a good stew. Am I wrong in this thinking? Probably, but who gives a shit? It's just music. " I was just agreeing with the sentiment that if it sounds good and you're happy with the results, no reason to sweat stuff that isn't bothering you. Ya know? I'm looking forward to sticking a dither plug on every track and seeing what happens. What's the favorite dither plug to use? |
|
|
|
Post by tonycamphd on Jan 8, 2015 16:00:47 GMT -6
I'll try it and see if I can hear a difference. Either way, I'll be honest. the thing that complicates it for us hybrid console guys is, instead of just using the dither on the final 2 buss dump of an ITB mix, we need to instantiate a dither plug on every single DA out to our consoles, i'm thinking that different noise shaping on every instance would be important as well? this is something not a lot of people ever dive deep enough to discover (i would think?), it's nice to have a monster like Bob Olhsson here to help us! i really appreciate him and other guru's taking the time to help morons like myself along 8) |
|
|
|
Post by tonycamphd on Jan 8, 2015 16:03:53 GMT -6
I was just agreeing with the sentiment that if it sounds good and you're happy with the results, no reason to sweat stuff that isn't bothering you. Ya know? I'm looking forward to sticking a dither plug on every track and seeing what happens. What's the favorite dither plug to use? I would chose multiple types of what you have, i believe it only needs to be on the 2 buss for a bounce ITB, you're a hybrid guy as well, and from what i understand(which isn't saying a whole lot 8), we need to dither any DA'd channel out to the console, unless it has no process done to it ITB, and serves only as a tape machine out(so to speak). |
|
|
|
Post by porkyman on Jan 11, 2015 1:02:15 GMT -6
i have been desperate over the years to get out of protools. i can not stand avid. ive tried most of the others. i think protools and cubase are the most different to me. it seems those are the two main platforms. the mac and pc of the daw world. at least as far as editing.
this is what i dont understand. all of the others ive tried, (sonar, logig, S1, reaper) besides samplitude have adopted the cubase style of editing. it makes me believe it must be better, quicker, more intuitive etc somehow but for the life of me i can not figure out why. it is the #1 reason i keep coming back to PT.
the two biggest culprits are having to go all the way back up to the top to highlight a region in order to playback the section youre working on. how can that possibly be more efficient than PT's method of playing anywhere you click on the screen. the other is the channel strip on the left. i dont know what you call it but its also nonsensical to me. in PT anything you want to adjust is right there on each individual track. in cubase you have to highlight the track you want to work on. so what would happen almost every single time is i would be thinking about one track, looking at one track and adjusting the levels on another. then id realize i didnt have the right track selected and id have to go back and fix the one i just ruined. again i dont understand how it could be more efficient to select a track then go all the way back to adjust, then go back and select a new track and then come all the way back and adjust. granted im talking about seconds here but those little nuisances build up, especially when your trying to be accurate with a mouse all the time.
samplitude i found was the most similar to PT. i actually think samplitude is the most advanced daw on the market. especially spectral editing. its such a powerful tool. the only problem is theres like 5 ways to do everything and none of them are easy.
i spent an entire year away from protools trying to find the answer. never went anywhere but backwards.
|
|
|
|
Post by Randge on Jan 11, 2015 12:53:58 GMT -6
You can set up Cubase to start anywhere you click. There is a myriad of ways to set it up actually. It is all in the preferences. Example: Say you were working with a singer and taking multiple attempts to record the chorus. You can set it up with one click to start at the top of wherever you began recording,such as that chorus. I keep my waveform side and the tracks open all of the time on my bottom left side of my bottom screen. There are little squares where you can load in pictures correlating to your tracks. That keeps things very easy to read. Also, you can take away any tracks that might distract you while mixing by clicking them to not be shown. So, you can make it just your groups tracks at mix time, so that nothing but your groups are in view.
R
|
|
|
|
Post by Johnkenn on Jan 11, 2015 17:32:15 GMT -6
In Preferences there's an option checkbox to place the record line thingy (whatever it's called) where ever you click. Under Editing or something like that.
|
|
|
|
Post by drbill on Jan 11, 2015 21:03:09 GMT -6
i have been desperate over the years to get out of protools. i can not stand avid. ive tried most of the others. i think protools and cubase are the most different to me. it seems those are the two main platforms. the mac and pc of the daw world. at least as far as editing. this is what i dont understand. all of the others ive tried, (sonar, logig, S1, reaper) besides samplitude have adopted the cubase style of editing. it makes me believe it must be better, quicker, more intuitive etc somehow but for the life of me i can not figure out why. it is the #1 reason i keep coming back to PT. the two biggest culprits are having to go all the way back up to the top to highlight a region in order to playback the section youre working on. how can that possibly be more efficient than PT's method of playing anywhere you click on the screen. the other is the channel strip on the left. i dont know what you call it but its also nonsensical to me. in PT anything you want to adjust is right there on each individual track. in cubase you have to highlight the track you want to work on. so what would happen almost every single time is i would be thinking about one track, looking at one track and adjusting the levels on another. then id realize i didnt have the right track selected and id have to go back and fix the one i just ruined. again i dont understand how it could be more efficient to select a track then go all the way back to adjust, then go back and select a new track and then come all the way back and adjust. granted im talking about seconds here but those little nuisances build up, especially when your trying to be accurate with a mouse all the time. samplitude i found was the most similar to PT. i actually think samplitude is the most advanced daw on the market. especially spectral editing. its such a powerful tool. the only problem is theres like 5 ways to do everything and none of them are easy. i spent an entire year away from protools trying to find the answer. never went anywhere but backwards. This makes sense to me, although I have not tried all the DAWs you have. There's something about PT that is just so intuitive to me that nothing else has matched to this point.... |
|
|
|
Post by Bob Olhsson on Jan 11, 2015 23:22:03 GMT -6
While it's intuitive, Pro Tools is also lots deeper than most people realize with lots of undocumented twists. It's an erector set much like an old studio patch bay that you can set up to work however you wish solving every problem that comes up. I've never watched somebody else use Pro Tools and not learned something new even though I've been using it since version one.
|
|
|
|
Post by Johnkenn on Jul 21, 2015 13:03:33 GMT -6
I've been using Cubase 8 for the last few tracks I've done - and for me, I repeat, for me - it is superior to PT's. I been wearing Randy out with questions for a while, and just today I did some audio quantizing...It is SOOOO much better than PT's algo...No warbles, no mistakes. I was kind've amazed.
|
|
|
|
Post by jdc on Jul 21, 2015 13:18:34 GMT -6
|
|
|
|
Post by Johnkenn on Jul 21, 2015 15:47:47 GMT -6
Well...maybe I spoke too soon. LOL. Just got a disk overload error trying to bounce a file through HW until I turned off all the Slate plugs...The disk usage wasn't very high at all, don't know what the deal was.
|
|
|
|
Post by Randge on Jul 22, 2015 10:50:32 GMT -6
Well...maybe I spoke too soon. LOL. Just got a disk overload error trying to bounce a file through HW until I turned off all the Slate plugs...The disk usage wasn't very high at all, don't know what the deal was. Did you set it to realtime export? |
|
|
|
Post by Johnkenn on Jul 22, 2015 11:54:57 GMT -6
yeah - in that one session, it gives me disk overload no matter what. Apparently it's a thing...I just offline exported, brought it into a new session and was able to do it realtime in that one...weird.
|
|
|
|
Post by wiz on Jul 22, 2015 16:46:36 GMT -6
yeah - in that one session, it gives me disk overload no matter what. Apparently it's a thing...I just offline exported, brought it into a new session and was able to do it realtime in that one...weird. I have had this kind of thing happen in logic. Now, logic aint pro tools.. but if you have 5 mins this would be a good thing to try. Copy the project to another location (a different drive perhaps?) and make it take all its files with it.. like you were going to move it to another system. Then , if Tools has some sort of "clean up" the project, apply it. In Logic, this gets rid of any unnecessary audio files. Then see if that still has the problem. If it does , then join all your regions together. What I mean is, say you have a track, that has a ton of different separate regions, join them all together and then do the "clean up" project thing again. Whenever I have come across what you are talking about, and its not definitely the processor running out of headroom (a gazillion plug ins for instance) this will cure it. Also, does Tools, have some sort of "freeze" function where it sort of prints all the plug ins and stops the processor having to .. well.. process? cheers Wiz |
|
|
|
Post by Johnkenn on Jul 22, 2015 17:36:58 GMT -6
Well it was in Cubase not Pro Tools. But you know what, I think I had frozen the drums. I'll have to check and see if that is the problem. The drums weren't what I was processing, but maybe it's still an issue.
|
|
