![]() ![]() Importing AAF project files from Avid Media Composer.Setting up your system for HD, DV, or HDV capture.Use Frame.io with Premiere Pro and After Effects.Use Premiere Pro in a dual-monitor setup.FAQ | Import and export in Premiere Pro.Best Practices: Create your own project templates.Open and edit Premiere Rush projects in Premiere Pro.Backward compatibility of Premiere Pro projects.GPU Accelerated Rendering & Hardware Encoding/Decoding.Hardware and operating system requirements.Best practices for updating Premiere Pro.You can, to some extent carve your own path with this - but it's a great idea to really look hard at the path as it is before you decide how to change it. But if you're going through a LOAD of edits, you can turn a one day job into half a day.and that workflow then exists in your toolbar, your menu, your key commands and your brain. It's going to challenge the way you think about editing, and often you need to stop what you're doing and create a custom action, or define a key command for an action that makes things work in a perfectly fluid way. You just need to work with it until it suddenly clicks into place - but then you realise that there's a really quick workflow to be found when an item selection does not change the track selection, and when the selection of a portion of an item doesn't necessarily represent the location it will be copied to when you hit paste. Now you can make some of these things the same, but when you do that you're tying Reaper up in a way that will never make it perfectly Pro Tools, and never perfectly Reaper. Yeah absolutely - that's a great example of something that makes you say 'Aaaah!' and 'Aaargh!' at the same time when you first move over - The selection of items, the selection of a portion of an item, the selection of a track, and the selection along the timeline are not necessarily always the same. And that should be the bullet point that gets Protools fired if it hasn't been already. You know those lengthly clicky selection procedures you end up doing sometimes? Know how mad you get from an errant mouse click right at the end of a lengthly selection? You can just hit undo in Reaper if that happens and move on. Reaper can undo mouse selections!! Let that sink in for a minute. As soon as that clicks, Protools becomes restrictive feeling. Reaper also has the ability to treat timeline selection and audio item selection as separate events. Action doesn't happen based on groupings though. ![]() Grouping commands are there to aid in making the selection. Things selected together do the thing together. Understand that everything in Reaper is selection based. I changed the shortcut to switch between the mixer and arrange windows from ⌥M to ⌘= to keep that muscle memory active. ⌥⌘-scroll = wave peak height zoom (via custom action) ⌘-scroll = zoom (both vertical & horizontal) Scroll (no modifier) = scroll (both vertical & horizontal) I DID change the scroll/zoom commands in Reaper to a more consistent order: In hindsight that was a big mistake and a waste of time those 2 years! Jump ship right now. I started using Reaper for live sound at first and dragged my feet for another 2 years with Protools in the studio because I was worried about the learning curve. That doesn't mean don't hope for, and ask for, features that you feel would be useful.but it does mean that if you try to make the transition a sort of seamless switch with no change in muscle memory, your friend will wind up frustrated with Reaper, and missing what's so great about it. I strongly advise that you don't try to turn Reaper into Pro Tools. You have to understand how it works, and you have to let go of some simplicity in order to get that flow going. But it really is worth it because you can achieve a great number of things in faster, more efficient way once you get your head around it. There is a massive learning curve here, and to get the best out of it you have to devote time, and effort. Reaper can, but the upshot of that is that behaviours in Pro Tools which change depending on what you're actually doing, may need to be thought of as two or more separate circumstances in Reaper. Pro Tools has some of the most elegant behaviours, which can't really be replicated - but the cost of that is flexibility - they've chosen a way for it to work and it can't really operate any other way. BUT having worked this angle a lot, I'd suggest that it's a bit of a mistake. One of the main things you'd need to look at would be custom actions to better match the behaviour in Pro Tools, and a very close look at the mouse modifiers. You can extensively customise Reaper, and can certainly tweak the key commands to reflect similar functions in PT. I've had some great help here on the forum. I've recently been working between the two, and am at the moment doing a big project entirely in Reaper. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |