This is the work flow we use this using PPro, AE and Audition. Fair warning: We're enthusiastic amateurs, It's not perfect, it's not quite finished, and there's certainly inefficiencies, but perhaps bits of it will prove useful to know.
Then we put together the edit using these sequences, not the source files. Note that we haven't bothered with transcoding before editing and at this stage we're just using the camera audio.
The idea of using nested sequences is so that technical colour grading, denoising and audio work etc. can be done in the nested sequence and these changes will just "propagate" through into the master sequence, wherever that shot is used. It also means if you are looking for a good area to find a good shot to noise profile for NeatVideo, or a quiet bit of the scene to grab an audio noise print, that you have the entire shot easily at hand.
Sometimes I will do a rough technical grade (in Colorista) or denoise (in NeatVideo) inside PPro while I'm editing. But this is really just to make sure it's going to work. The final work is done in AE.
When we've happy with the edit we sync up the audio from the Tascam. We place the tascam WAV files into the nested sequences containing the original video and sync them up by hand. Again, we only have to do this once in the nested sequence. Obviously we don't bother syncing the audio files in sequences that didn't make the final edit. Because the audio and video files are named by creation date it's relatively easy to pick the matching audio files.
Using nested sequences in this way isn't without it's problems. Adobe's engineers obviously don't expect it to be used this way, and you do lose some functionality. Because the files you edit with are sequences not "sources" you can't use the source window to view them, set in and out points etc. But honestly, I can't say I've missed that functionality.
Any dips, fades, transitions or colour correction we apply in PPro is all considered a draft. Most of these effects don't make the transition into After Effects properly so we leave the real work for there.
Once we're happy with the edit we duplicate the PPro project and place it into a separate folder. If edit lock is correctly maintained the main project file and it's copy will always be identical.
We render out a guide video track with audio, and an uncompressed WAV.
Once it's edit locked we import the PPro sequence into AE. AE muddles up the project quite a bit if you import with sound so we import the PPro poject into AE without audio and then add the guide WAV file (from the Edit Lock step) as a single layer.
I don't really have a set work flow once I get into AE, it depends on the project. But all the compositing, CGI and grading etc. is done in AE.
One set of scripts I find very useful are the DV Rebel Tools (http://ae.tutsplus.com/articles/news/dv-rebel-tools-for-free/). "Make Blank CC Layer" creates an adjustment layer for colour correction on top of the selected layer and already trimmed to the same length. "Make Thumbnail Comp" creates a composition of thumbnails of all your selected shots - this is very handy for visibly checking the colour balance across an entire scene.
This is the bit that's been the biggest pain. Ideally I'd like to be able to still treat the project as hierarchy of nested sequences and apply non-destructive changes, but the Adobe software doesn't want to play nice.
Another major problem with the nested sequences if you select "Edit Sequence in Audition" in PPro it will render nested sequences as single WAV files. Sometimes our projects have several levels of nested sequences (scenes assembled into a larger piece). Exporting to OMF does the same. It looks like AAF may just reference the original WAVs, but the AAF exports seem to be buggy and wouldn't open in a trial version of Nuendo.
Eventually after going round the houses a fair bit, we've started using the following. It works, but I'm not completely happy with it.
If any of the audio needs noise reduction we apply that at this stage in a separate audio editor. I apply the noise reduction to the original WAV or video file. Because we have the entire shots worth of audio (rather than just the bit that's made the edit) it's easier to find a quiet bit to get a decent noise print. I save the noise reduced version as a new WAV file and again I place this back into the nested sequence in PPro. I leave the original audio track(s) enabled but mute the volume. This way it will still be available in the DAW later should I want to check the original. (To be honest I would rather apply this noise reduction in the DAW, but I've found that when exporting to Audition or OMF Adobe will we re-render each bit of used audio as a new WAV file, so it's easier to do it once this way).
Then I have to workaround the inability to export nested sequences into Audition properly. Here are the steps:
Once it's like this I can then open this new PPro project and select "edit sequence in Audition". We don't render any of the clip effects, and we don't render a copy of the video out since we already have a guide video track from the Edit Lock stage.
Annoyingly this process of flattening the project will now mean that the audio is all over the tracks, so the first step is to select all the clips and select "Lock in Time", and then re-arrange them into a decent structure. Then it's the usual levels, EQing, etc.
We export out the mix from Audition, and use it to replace the guide audio track in the "Grading..." After Effects project from earlier; then we render out the final video from inside of AE.
@sam_strickland Thanks for that detailed workflow.
Thank you very much. Alot useful info in there!
Quite funny following this as every recent Sat I'm mixing 5D shot profile VTs "Synced" and then watched like a hawk by everyone in the dub and lay-off - post video manager confidence is low even though it's obviously "as near as" - I may be missing something but, clap + visual sync worked for a while in film ?! I've lost count telling producers that what they ware watching on the spangly OLED etc in the dub isn't "quite in" but trust me! Can elongate the day! Must be a nightmare for you lot.
What are people doing for large (i.e. > 1hr) projects? One giant render, or multiple renders and a 'join' afterwards.
If it's the later which codecs / containers are good for that (that can avoid another encoder pass)?
And would the audio be handled in similar sized chunks also? If so, I guess this places this some limits on J/L cuts over scene changes. And if not, it seems to me there could be sync issues arising at the 'join' stage.
Just starting to explore editing, so quite a basic question, I am using Premier and after effects cs5.5, with some footage in need of stabilisation (Warpstabiliser in AE) would I stabilise first then export it towards Premier or edit sequences in Premier then use the dynamic link to stabilise?
Thanks for any help :)
Has anyone worked with photoshop elements organizer to organize ingested originals and/or use it for further (non premiere) edits for example in sony vegas pro.
This organizer seems to be more resposive than lightroom for video pics, you would have photoshop elements 11 for pictures and could use pro editors of your choise...
In Europe you find at the moment latest premiere elements 11 for 50 EUR at amazon.
@roberto @brianluce I've been married to vegas for quite a while. I made my first edit ever on windows movie maker, than I discoverd vegas shortly after (I think it had a different name and then sony bought it?) Anyways, It's my go to NLE for about 13+ years now. I know how to use others, I just don't find the workflow of them near as fast, and people really don't give vegas enough credit becasue each new version becomes more powerful.
@matthere look up proDAD mercalli for stabilizing. I typically stabilize before I do any other work to the clip. Typically a stabilizer can only do so much, so if you have handheld footage of an earthquke happening, don't expect it to look like it was shot on a tripod ; )
My workflow as of today:
Shoot Sync sound via ART Duo Pre and Sescom GH cable (everything mounted on a rig with XLR inputs in line with shoulder plate)
Edit natively in Premiere CS6 (cuts and cross fades only); there used to be a problem on Windows where sound in the MTS wasn't seen, it's ok now.
a) Prep Edit: Assign meaningful clip names (Seq1Slate2Take3) in Project Mgr and Rename footage to match (Reveal in Explorer/Make Offline/rename in Explorer/Replace Footage)
b) Edit each script sequence in its own...well Sequence
c) Pull all (nested) Sequences together in a master sequence (final cut); this is Picture Lock. Optionally: checkerboard pattern
d) Duplicate nested sequences on (video above, audio below). Hide/mute original tracks. Replace (video duplicate) with After Effects composition. Looking for a similar audio workflow to Audition.
All picture post in AE (Edit Original). AE project to 32bpc. Sound post in Audition
In Adobe Media Encoder, import Premiere project and render out master to RGB codec (Prores4444, DNxHD444, Cineform444, RGB Uncompressed). This is the only time I render (forever and a day).
step 6 is only done if i'm applying film convert, and the step of opening PP is only temporary until they release the vegas version.
i've recently got a computer with enough power to run resolve issue free, so I'm in the process of learning it, then eventually my workflow will change. but honestly, my workflow isn't ALWAYS the same, it just depends if it's a documentary style video, artistic, test edit, music video and so on.
@radikalfilm, sounds similar to my current workflow, minus my inclusion of neatvideo in AE. ive been rendering out the denoiser in PP via bridge and saving before jumping back into AE for color work. for some reason if i try to denoise and color edit at the same time i run into hiccups. do you always use media encoder? i use PP if outputting small format for vimeo.
@hay: I said "post", not that I'm not using NeatVideo in AE :) . Define hiccups. I put NV at the "top" (first downwards) in the filter stack, so it gets processed first.
I always use AME, yes, it renders out faster than AE, plus I can easily access my custom presets, and render multiple targets in parallel (e.g. 360p, 540p, 720p).
Actually I do it in two steps:
render out to mastering codec (single target)
render multiple (broadcast, web) targets from the master
If the project doesn't require substantial post (it happens) I skip AE and use Premiere for minimal finishing; in this case the master is AVC-Intra 100. If I do post in AE the master is an RGB/444 codec. I edit on an AVC-Intra timeline for speed regardless (Premiere is optimized for AVC-Intra). If I do an RGB master I create the appropriate sequence (say Cineform), and copy over the final cut from the AVC-Intra timeline.
With this workflow I can stay platform agnostic and Quicktime-free, avoiding the 32-bit QT engine on Windows, which is a drag for real-time playback. Windows is a requirement, since I monitor out of a Blackmagic Decklink card. Only the Decklink driver on Windows does real-time pull-down from 23.976 to 59.94i, which the TV/monitor requires. On the Mac (Hack) it only does 25p to 50i.
I have old Macbook Pro and I'm using Premiere CS6. Because my computer is pretty slow I think the best way is to transcode .mts files to Apple ProRes 422 Proxy using Clipwrap.
Question: How would you replace edited ProRes Proxy files in timeline with original .mts files before exporting into final media?
Question: When transcoding GH2 1080p AVCHD footage to prores 422HQ with 5dtorgb, what would be the correct project settings in Premiere Pro CS6? DSLR 1080p, or do I still edit in AVCHD even though the footage has been transcoded?
In the project window just right click each file and select replace media. Make sure that your sequence is set up for original files and not for proxy ones.
Create new sequence and don't select any of the presets, go to settings tab and from the
Editing mode: choose Custom.
Also manually select your framerate in Timebase drop down menu, If you shoot 24p in GH2 choose 23.976fps here.
Type in your frame size, 1920x1080 or whatever your footage is
Pixel aspect ratio: you should probably choose "square pixel" unless you want to de-squeeze anamorphic footage.
Fields: Select progressive or interlaced.
Audio should be at 48kHz. You can select your audio display format here, default is "Audio samples"
The bottom part is for preview settings. Those are the files that PPro creates when you render something on the timeline. When you do the final render of your project, you have the option to use those previews, so it should probably be set to be the same as main footage.
Preview file format: choose "Quick time (desktop)"
Codec: select "Apple Prores 422HQ" and type in proper frame size for previews, by default it will follow the main sequence frame size.
Now save your preset, and it will appear on the bottom of sequence presets menu. That's it.
My workflow :
shoot footage with La7200
dump memory card into a folder
drag into iffmeg or squeeze and create prores 4444 2580x1920 pixel 1:1
drag MOV into vegas or Pr ( depends of OS.) minor color correction (only on clips that's needed)
export to whatever format is needed (obviously different for web, dvd, bluray) watch the video and make sure everything looks right, then export final.
Thanks man!
I'm working in Premiere as my main editor and I have NeatVideo for Premiere and After Effects but I want to do my color grading in DaVinci Resolve. I know that it's appropriate to denoise before grading the footage but what I don't know is the most intuitive way to go about denoising and then grading. Right now my thought is to denoise every shot individually (NeatVideo in Premiere), render each clip individually (DNxHD), and the slap all of the shots in a new sequence in Premiere. From there save it off as an XML and import into DaVinci and have a ball with ColorGHear.
Does that workflow sound about right or am I just brain farting and there's a way easier and less time consuming way to go about this? Any advice would be greatly appreciated as I'm on a fun deadline....
@MagicMountainMan That's what I would do myself, but I wouldn't denoise every shot - only the ones that need it. So if every shot doesn't need denoising, then I would edit the avchd first, then denoise particular shots, then render out to DNxHD. Bring it back as a single clip and cut all the splices and use a second track for crossdisolves, then xml it out to Davici.
This is my workflow, I know that there are no "right" ways or wrong ways, each person has its own methods...so I guess I'm sharing my way of workflow for web video, if anyone knows/uses more efficient one, please chime in :)
I'm sure that I'm doing some bad steps here, most likely with mov conversions...so I'm open to suggestions. :)
You should compress to mpeg4 or h264 only once, if that your delivery codec, at the very end. So IMO you should export from resolve lossless (Animation or ProRes HQ which is very close to lossless codec).
@inqb8tr : thanks for the advice...
Is there any Premiere export setting I should use to bring the best possible quality to Resolve?
Premiere can handle most formats ... you might want to consider editing "native" in PPro, then in the export for Resolve do your first transcode. Of course, if you're running a stream of different formats into each project you might prefer an "ingest" transcode to a single codec. Otherwise ... skip the transcode till you're out of PPro might be wise. Less times messing with transcodes.
Neil
Is there any Premiere export setting I should use to bring the best possible quality to Resolve?
Well that's not just Premiere specific thing, and there is no special thing that you can do in Premiere to improve your pipeline. It depends on original footage, and what you want to do with it in post/delivery. For 8bit 4:2:0 AVC footage, such as GH2, you should be ok with 4:2:2 intraframe 10-bit codec for some resonable color grading, such as ProRes HQ or DnxHD for example. QT Animation is lossless at 100% and robust but it is more demanding on hardware.
I use ProRes HQ from PPro to Resolve, and sometimes ProRes 4444 if I know that I'll grade the hell out of it.
It looks like you're new here. If you want to get involved, click one of these buttons!