|
|
Post by Johnkenn on Jul 23, 2024 11:02:23 GMT -6
Looks like CTRL/back slash works for me. (The one above the return key)
|
|
|
|
Post by Mister Chase on Jul 23, 2024 11:12:51 GMT -6
I finally had to do the PT crash course and do a huge edit on a long classical guitar ensemble piece, became obvious I had to learn a LOT of shortcut key combo's if I was gonna get anywhere fast. Spent an hour+ in the PT shortcut manual copying things I'd likely use, ended up with about a 2 page list I have to refer to constantly, but it's made it SO much faster to get things done. There's still only a few that've stuck, I'm looking at it constantly, but it'll come. I can recommend the approach! The number of settings that change the available actions is a challenge to remember too. Watching my friend who is a classical producer edit in PT was pretty wild. Super fast and basically all keyboard. Totally different level. |
|
|
|
Post by Johnkenn on Jul 23, 2024 11:27:27 GMT -6
For some weird reason, when using multiple Deres instances, commit freezes PT. No idea why. Seems to work with everything else.
|
|
|
|
Post by ragan on Jul 23, 2024 11:39:43 GMT -6
Looks like CTRL/back slash works for me. (The one above the return key) I was about to post this. I think bgrotto must have thought you were talking about something else. |
|
|
|
Post by Johnkenn on Jul 23, 2024 12:12:35 GMT -6
Anyone else have crashes with commit?
|
|
|
|
Post by Johnkenn on Jul 23, 2024 12:25:20 GMT -6
Yeah...having crashes even with Freezing now. Wonder if the session is corrupt somehow.
|
|
|
|
Post by Johnkenn on Jul 23, 2024 12:31:11 GMT -6
Just tried to import all the session data into a new session...and same thing. Freezes and crashes on "commit"
|
|
|
|
Post by bgrotto on Jul 23, 2024 12:35:03 GMT -6
Looks like CTRL/back slash works for me. (The one above the return key) I was about to post this. I think bgrotto must have thought you were talking about something else. I thought he was asking about pasting a selection to a playlist. Seems he was looking for the new playlist command. Sorry! |
|
|
|
Post by doubledog on Jul 23, 2024 16:24:41 GMT -6
Just tried to import all the session data into a new session...and same thing. Freezes and crashes on "commit" 2024.6? I was committing earlier today (but I'm on Windows...) and it worked fine. I have had PT crash while doing a commit though and that makes a real mess (depending on where it was when it died), so I always try to remember to hit save (CTRL+S) right before I try it. |
|
|
|
Post by doubledog on Jul 23, 2024 16:30:08 GMT -6
I setup a routing folder the other day and when I put a plugin on that folder, it did not behave like an Aux - the plugin was there but didn't function. Not sure if that was a bug or a glitch or if that's how it's supposed to work. So then I had to undo everything and just create an Aux bus (and that worked fine - it just won't collapse like a routing folder). i was thinking that plugins are supposed to be effective across the folder (i.e. all the tracks inside it)? Sounds like you forgot to select the “route tracks to new folder” option in the create folder dialog. That's very possible. I was able to "convert" an Aux to a routing folder today and that worked fine (although it kept the original bus numbers I was using instead of creating one with the folder name) . Then I went back and tried some other sessions and I got those working too. When I create the routing folders, I just create the empty folder and then drag/drop the tracks I want into it and it sets the routing correctly - so not sure what happened the other time I tried it (It was for sure an earlier version of PT) . oh well, working fine now. |
|
|
|
Post by BenjaminAshlin on Jul 23, 2024 23:18:28 GMT -6
Using Cubase... I kid I kid... Not really though... Back on topic.
|
|
|
|
Post by Johnkenn on Jul 24, 2024 8:56:43 GMT -6
Cubase has as many if not more issues.
|
|
ericn
Temp
Balance Engineer
Posts: 16,083 
|
Post by ericn on Jul 24, 2024 13:49:35 GMT -6
Using Cubase... I kid I kid... Not really though... Back on topic. I was waiting for someone to go down this Logic-Al path😎 |
|
|
|
Post by carymiller on Jul 24, 2024 14:59:25 GMT -6
So, I recently discovered a couple of things in PT that...oof...I wish I'd looked into a long time ago. First, the playlist keystrokes (making one playlist the target playlist and just using keystrokes to audition takes and comp to the target playlist). I used to use the manual copy paste way, then moved to the playlist view where you have the little solo buttons per playlist and you hit the up arrow to move your highlighted selection up to your comp track. This is pretty smooth...but just using keystrokes is so much better in my view. You don't have to have the whole mess of playlists expanded, you don't have to mouse around and click things, etc. Second, I do a lot of hardware printing and I've always just done it manually. ie make a new track, route to it, label the new track, route it to the correct subgroup, color it, put it into the right edit group, etc. I just today (after hearing mention of it for a long time) tried the "commit" function. Oof again. PT just...does it all for you. So anyway, that got me thinking. What else am I being a dumbass about in PT? I've used it for so long, I tend to just do the same stuff I've always done. I bet there are other efficiency gains I'm overlooking. I think it would be kind of cool to have tips collected in one thread. Whaddya got? My biggest trick lately? I leave all my pro tools faders at Unity Gain (hear me out). So basically I'm using channel strips with built in faders on all my tracks (Currently I use a mix of the SSL brand newer generation channel strips like the 4000 E/G and the "Channel Strip" which I believe is based off the J depending. I do the gainstaging in the plugin, leaving room for light automations around unity gain on the individual DAW faders. I mix top down exclusively, so I also start with automations at the Submix level first for 90% of my automations (I usually have between 6 and 12 submixes depending on the song). Which cuts down on time spent automating a ton from there. And then I finish up with final automations at a per track level last when I need to dig deeper with automations. Since I don't run an Atmos facility and work primarily in stereo I tend to mix LCR for everything (I have yet to run into a scenario where this hasn't sounded best). This means for something like drums I'm panning as follows:01. Snare, Kick, High Hat (CENTER) 02. Overheads/Room Mics (HARD LEFT AND RIGHT AND MULTED) 03. TOMS (HARD LEFT AND RIGHT DEPENDING ON THE TOM) I spent most of the last year and some change studying a lot of more recent mixes by Paul David Hager (Miley Cyrus, Beck, St. Vincent, Jonas Bros, etc.) and I believe this is where he's migrated from doing MONO checks. It seems counter intuitive at first, but it's yeilded a wider soundstage that colapses to mono better. I also know PDH is punching up a little 5kHz-ish on the kick and the snare (Vs. Say 8kHz like a CLA would), which has resulted in a smoother response overall with drums for me. I also use a lot of parallel processing (like the Andrew Scheps Rear Bus Technique for example which I am a fan of). With a couple of FX SEND/RTRNs for processing vocals in different ways in particular. Lastly there's a series of 5 very light Verbs/Delays in a chain that I blend together into a mult before returning things to the 2Bus, which creates a more natural kind of ambiance similar to real acoustics. This was poached off of my time working for Shelly Yakus at Studio One Media/Aftermaster HD, but it's really a technique Roy Cicala taught Shelly back in the day when Shelly was starting out in NYC. |
|
|
|
Post by doubledog on Jul 26, 2024 20:31:21 GMT -6
anyone else have templates? since I do quite a bit of drum session work, I have templates setup for just that. Different sessions setup for various sample rates (44.1, 48, 96KHz, etc.) and different drum kit configurations. I even have some plugins waiting (but disabled) so that once I get something tracked I can quickly dial in the final sound (or at least final for what I send to the client to hear). I usually open these and do "save session as" and then save it in a new folder and change the disk/file location. Then I add the client's guide track and off we go. If I have a band in tracking I can use these same templates and then just add more tracks for whatever else is in the session. Or sometimes I'll open a brand new session and then "import session data" and just bring in the drum, Aux, master, tracks from the template files (I think that feature came out long after I started using these templates). a lot faster than building a new session from scratch each time.
|
|
|
|
Post by bgrotto on Jul 26, 2024 20:57:41 GMT -6
anyone else have templates? since I do quite a bit of drum session work, I have templates setup for just that. Different sessions setup for various sample rates (44.1, 48, 96KHz, etc.) and different drum kit configurations. I even have some plugins waiting (but disabled) so that once I get something tracked I can quickly dial in the final sound (or at least final for what I send to the client to hear). I usually open these and do "save session as" and then save it in a new folder and change the disk/file location. Then I add the client's guide track and off we go. If I have a band in tracking I can use these same templates and then just add more tracks for whatever else is in the session. Or sometimes I'll open a brand new session and then "import session data" and just bring in the drum, Aux, master, tracks from the template files (I think that feature came out long after I started using these templates). a lot faster than building a new session from scratch each time. I am a big fan of templates. Mine is mostly bussing and some send/return fx, though I have a few 'standard' signal paths and some parallel stuff I like, plus a mix buss preset that I start every mix with. |
|
|
|
Post by carymiller on Jul 26, 2024 21:15:56 GMT -6
anyone else have templates? since I do quite a bit of drum session work, I have templates setup for just that. Different sessions setup for various sample rates (44.1, 48, 96KHz, etc.) and different drum kit configurations. I even have some plugins waiting (but disabled) so that once I get something tracked I can quickly dial in the final sound (or at least final for what I send to the client to hear). I usually open these and do "save session as" and then save it in a new folder and change the disk/file location. Then I add the client's guide track and off we go. If I have a band in tracking I can use these same templates and then just add more tracks for whatever else is in the session. Or sometimes I'll open a brand new session and then "import session data" and just bring in the drum, Aux, master, tracks from the template files (I think that feature came out long after I started using these templates). a lot faster than building a new session from scratch each time. I've been crafting a new main template for mixing all year. And I've been working from templates for years. I really don't have the time to just do everything from scratch to be honest, and it doesn't yeild better work. |
|
|
|
Post by drumsound on Jul 26, 2024 22:29:17 GMT -6
anyone else have templates? since I do quite a bit of drum session work, I have templates setup for just that. Different sessions setup for various sample rates (44.1, 48, 96KHz, etc.) and different drum kit configurations. I even have some plugins waiting (but disabled) so that once I get something tracked I can quickly dial in the final sound (or at least final for what I send to the client to hear). I usually open these and do "save session as" and then save it in a new folder and change the disk/file location. Then I add the client's guide track and off we go. If I have a band in tracking I can use these same templates and then just add more tracks for whatever else is in the session. Or sometimes I'll open a brand new session and then "import session data" and just bring in the drum, Aux, master, tracks from the template files (I think that feature came out long after I started using these templates). a lot faster than building a new session from scratch each time. I use templates on tracking dates most of the time. I, like you, have drum session master. Then drums, 2 gtrs, bass and scratch vocal. A similar one with keys. Then when a band is in, I use the basic one that matches, but I add some specifics like mic and player's names in the notes, and save that template under the band name. Sometimes I make a mix template for an artist, to quickly get some effects, and parallels consistent. |
|
|
|
Post by doubledog on Jul 27, 2024 9:35:13 GMT -6
I definitely always customize it for the session - but a template is almost always my starting point. Another thing my drum template has is the mics (and any settings) I used (in the scribble strip) - usually I know the preamp from the input but I should probably put that in the scribble strip because my I/O can change from time to time. If I patch in something different I always write the whole chain in there. Sometimes I even put the compressor settings (when I use one) so I can recall it if needed - especially helpful for a vocal chain.
obviously not unique or rocket surgery here, but I also find that when I'm recording live bands, it's best to have one session open and just keep recording (like a tape machine with endless tape). We record multiple takes. Then once the basics are done, we can choose a take (or sometimes splice parts from one or more together) and use those "best takes" for any subsequent overdubs and such. Once that's all done, then I'll do some rough mixing. And then finally I'll worry about cutting them up into separate sessions (which makes it easier for mixing). And I can do all that once the band has left. This makes the sessions go smoother and we are almost always recording (although I stop and save occasionally if the band stops). I find even if we are using a click, this still makes it go faster. I can still stop and set a new click tempo, etc. and it still keeps things moving quickly (efficiently).
Of course if we are building up from scratch or working with tempo maps, then that's all different.
|
|
|
|
Post by drumsound on Jul 27, 2024 10:19:25 GMT -6
I used to do takes in a linear fashion like you describe, but not running PT the whole time. The more I got into Playlists for comping vocals, the more I realized how useful it is for basics, so I stopped doing that. If you're worried about hardware resets, get the free Snapshot plugin, which lets you store pictures in a plugin right on the track. SNAPSHOT |
|
|
|
Post by Johnkenn on Jul 27, 2024 12:06:26 GMT -6
I just import session data from a previous session instead of templates.
|
|
|
|
Post by Darren Boling on Jul 27, 2024 12:17:27 GMT -6
anyone else have templates? since I do quite a bit of drum session work, I have templates setup for just that. Different sessions setup for various sample rates (44.1, 48, 96KHz, etc.) and different drum kit configurations. I even have some plugins waiting (but disabled) so that once I get something tracked I can quickly dial in the final sound (or at least final for what I send to the client to hear). I usually open these and do "save session as" and then save it in a new folder and change the disk/file location. Then I add the client's guide track and off we go. If I have a band in tracking I can use these same templates and then just add more tracks for whatever else is in the session. Or sometimes I'll open a brand new session and then "import session data" and just bring in the drum, Aux, master, tracks from the template files (I think that feature came out long after I started using these templates). a lot faster than building a new session from scratch each time. I'm also a big fan of templates, like other's have mentioned mine is mostly all the routing and busses set up with some common plugins and chains there but inactive. I also keep a folder that has the sessions I've made templates from. This helps in keeping the templates up to date as well as an easy place to import session data from when needed. |
|
|
|
Post by doubledog on Jul 27, 2024 15:16:55 GMT -6
I used to do takes in a linear fashion like you describe, but not running PT the whole time. The more I got into Playlists for comping vocals, the more I realized how useful it is for basics, so I stopped doing that. Agree, playlists are absolutely necessary (at least I wouldn't do it any other way any more) if you are doing the same part over and over (like vocals or a guitar solo, etc). But they don't work if you have a band playing multiple takes that are not to a click... cause then nothing lines up. But in the linear recording method, I can still borrow from other takes if needed (copy and paste). |
|
|
|
Post by EmRR on Jul 28, 2024 6:24:52 GMT -6
The thing I love about DP most is the ability to have multiple sessions within a session, and within those, store multiple mixes. Whole album in one project, simple duplication/comparison of anything quickly. I don’t see anything remotely similar in PT. Multiple takes of a song stored as take layers rather than in linear fashion is what I do, makes live take comping easy. No native meter bridge in PT is a no-go on live work too, in DP i hit a tab and have a full screen scaleable 50 channel meter bridge I can see across a room on a laptop. I’m all ears if there are similar PT solutions.
|
|
|
|
Post by Johnkenn on Jul 28, 2024 13:52:09 GMT -6
The thing I love about DP most is the ability to have multiple sessions within a session, and within those, store multiple mixes. Whole album in one project, simple duplication/comparison of anything quickly. I don’t see anything remotely similar in PT. Multiple takes of a song stored as take layers rather than in linear fashion is what I do, makes live take comping easy. No native meter bridge in PT is a no-go on live work too, in DP i hit a tab and have a full screen scaleable 50 channel meter bridge I can see across a room on a laptop. I’m all ears if there are similar PT solutions. I don’t even know what the hell you’re talking about…so I guess that’s why I don’t miss it in Pro Tools. |
|
