Dennis Radeke
Forum Replies Created
-
For Quicktime, yes.
-
It depends on the media itself. Things like Quicktime are ‘containers’ of media and can contain metadata in addition to traditional things like video, audio, timecode, closed captioning, etc. Other formats do not support direct injection of metadata. These include things like MXF files. When we can write into the media itself, we will. If we can’t, we will write a sidecar XMP file adjacent to the media. With Premiere Pro CC2014.1
You can find more about it here: https://helpx.adobe.com/premiere-pro/using/preferences.html#media_preferences
Dennis – Adobe guy
-
Try right clicking on the mono audio file and choosing ‘modify/Audio Channels’ That should hopefully give you a tip to go on.
This also might help: Premiere Pro Audio Overviewl
Dennis – Adobe guy
-
You can do this in CC2014, but not CS6.
-
[Mason Makram] “Does Premiere use OpenCL?”
Yes, assuming the GPU meets certain minimum requirements. Definitely yes, for the card in your system.
-
[Andrew Johnstone] “”Don’t upgrade unless you really have to!””
Agreed. I’ve been of the opinion that the last few Apple OS’s haven’t really added a whole lot in the way of features, but that’s probably a ‘whole nuther’ forum’…
My STRONG recommendation is that users who are moving to a new OS, START FRESH and do a CLEAN INSTALL. Gone are the days when a casual upgrade would just work. There are millions of bits in an OS and the chance to mess a few of those up is probably pretty high.
Yes, it’s a pain and I know because I’ve done my own clean installs many times – from about 10.2 onward. It does make for a better, faster, more stable machine.
My 2 cents,
Dennis -
Hi Mason,
Things like clearing the media cache and trashing prefs would be good ideas.
You are dealing with a weird frame size and a big one at that – it will come with some performance hits in order to do it. You also didn’t mention the specs of your system which are critical to determining where the cause of the issue may lie.
Lastly, you are outputting to a non-standard codec that was installed on the system. It’s great that AME registers it and can encode to it, but you can’t blame the performance of AME on a 3rd party codec.
Maybe some of the above can help point you towards a solution.
Dennis – Adobe guy
-
Hi Travis,
One thing to perhaps do to save you time would be to right click and ‘scale to frame size’
When you double click, you are loading the clip into the source monitor. When you single click on the timeline, you can then use the ECP to affect parameters like scale.
In your example, you can also double click in the program monitor to scale in real-time directly in the program window.
Hope this helps,
Dennis – Adobe guy -
Wikipedia to the rescue!
https://en.wikipedia.org/wiki/Dynamic_range_compression#LimitingWorth a good thorough read. If you’ve got full control of your dynamics processor, then I think that the knob you wish to tweek would be the threshold knob. This is the one that the defines the point at which the compressor/limiter kicks in.
Newer versions of Premiere Pro (maybe CS5?) also include the IzoTope Multiband compressor which is worth some time as well.
Hope this helps,
Dennis – Adobe guy -
Yes, transcode to ProRes or another codec that is standard. A lot of people like 50mbit XDCAM (MXF OP1A) too which is about half of ProRes in size but still good looking.