Question: In Audition, is it possible to set a volume of one audio track to be based on another? For example, to automatically raise and lower the volume of a room-tone track in response to the dialogue mix? I can't see a way to do this in Adobe Audition. Is it possible in other software such as ProTools or Nuendo? Is this even a good idea, or am I going to end up setting it by hand anyway? It certainly seems like it would be a useful first pass.

Have a look at the video, its not in every shot, but there are enough examples of what I mean - most of them are b/w.

• Was this created on set/in camera?
• How did he light the faces?
• Any post production tricks?
• How to do it today?
• How to do it today without tracking every eye and using power windows?

(I wish I could smile like Norman Bates....that would help beeing a teacher ;-)

It has free and paid editions.

http://www.videoartifact.com/va/

Program helps you to prepare footages from consumer or professional video cameras, digicams and V-DSLR.

It can remove MJPEG, MPEG, H.264, H.265 compression artifacts and digital noise, improves sharpness and color resolution up to 16 bit 4:4:4.

Restoration features:

• Script-based to work with unique cases. You can use many filters in any combination.
• 50+ specialized restoration filters work in Y, U, V separately in 8/16 bit.
• Possibility to use dozens of different type denoisers for different noise type.
• Accurate denoising that keeps micro details with no "plastic" effect.
• Removing of sharping halos.
• Linear color high quality spline-based resize to resize up to 4K. Resize halos can be removed.
• Precise halo-free radius-dependent sharping.
• Film grain emulation and 3D LUT grading.
• 4:2:0 8 bit to 4:2:2/4:4:4 16 bit chroma reconstruction.

It can be used in a post-production workflow if you use V-DSLR or consumer cameras.
Currently 50+ camera models supported and hundreds of compatible models.

Special features:

• Batch processing without GPU. Very fast: 5 fps for typical V-DSLR AVCHD source and 2 fps for 4K.
• Automatic joining of MTS, MOV and MP4 spans and renaming to yyyymmdd_hhmmss.mov format.
• Non-standard 16-255 to TV 16-235 levels conversion.
• ITU-R BT.601 ↔ BT.709 floating point conversion.
• NLE and DaVinci Resolve compatible workflow.
• Mastering to webm VP9/Opus or mp4 H.264/AAC 1080p/720p/360p/240p.

Examples with various restoration methods are available at http://www.videoartifact.com/examples/

Some samples:

I've been looking all over the web for forums on how to use my cam (which happens to be a GH3, so ... what mostly) AND to do something with it ... and either there are esoteric and pointedly detailed discussions on the technical bits of shooting OR a highly detailed esoteric discussions of say, specific tasks in DV Resolve ... I'm sure at some point I might find interest in this, but it's not helpful now. It's handy to see that say, several here feel the .MOV on the GH3 is great at lower ISO, but the AVCHD better at higher ISO. Practical and handy.

That said, when I get into Premiere Pro and Speedgrade, where I've been totally lost at the settings to actually make the end result meet what my monitor shows ... I'm not finding a lot of help. I've tried (in SG) various settings from "no calibration" to about everything on that long list ... most things chosen in rendering make for an output that is harshly contrasty/saturated and a lot darker ... except for a couple of the gamma/MOV ones that result in a "thin", bright and washed-out final. No one on the SG forum even responds to requests on things like that, and I can't find any info that isn't contradicted by every other article out there.

I'd just love a practical discussion of what settings, practices, and patterns seem to work smoothly and consistently. Not just shooting or just post, but ... when combined ... make for a smooth workflow from planning through delivery. What kind of rendering settings work best for the files created by this camera? What LUT's or protocols or whatever to look for, what to avoid ... clearly, there are some good folks here at doing this stuff.

ANY comments would be so appreciated!

R. Neil Haugen