When I delivered my previous audio book to ACX, I remember that one of their requirements was that the audio peak levels should come in at -3dB. I also remember that threw was a super easy way for me to do this in Premiere Pro, the software I use for editing my files. I wanted to do the same thing this week, but I couldn’t for the life of me remember how to dot it!
Consulting this website – as I do from time to time – I couldn’t find a note. Perhaps I didn’t write this vital part down the last time. Let me do it right away, now that I’ve found out how to do it (again).
My first though was that it must be an audio effect we drag onto the timeline in question. But that’s not what I wanted to do. I was happy with the dynamics, I didn’t need to do any compressing or filtering. Instead, it’s as easy as right-clicking on a clip in the timeline and selecting Audio Gain. We can also press the G shortcut to bring up this menu.
This will open a modal dialogue with several options.
The one I needed was Normalize Max Peak to -3dB. This will look through the selected clip(s), find the highest peak, and adjust it to the value of your choice. The All Peaks option below of it would do the same for every single clip on the timeline. While powerful during video editing, it may not be what we want in this case of editing an audio book. It would likely make quieter passages louder at edit points, leading to an uneven listening experience.
To use this technique with various clips, either select all clips before running this command, or create a new sequence from your sequence and run the command on that.
Larry Jordan has written an article that explains more in-depth what this dialogue does. Thank for sharing, Larry!
By default, OBS Studio likes to record files in FLV – for a reason that’s absolutely beyond me. I easily forget to change this setting into something more sensible, which means I frequently end up with FLV files that contain my material. At that point I have no way to edit those properly.
This means I’ll have to transcode my files in order to make them useful.
Or do I? Well, yes and no. Let me explain a bit more about this dilemma.
I made some new lower-third captions for my YouTube channel in Premiere the other day. I had a vision for some animations, and rather than spend several hundred dollars on pre-made snazzy clips, I thought I’d take on the task myself.
For those to be usable on top of other video footage in my screen casting software (Camtasia Studio 3), I needed the animations to be rendered out with an Alpha Channel. That way a mask is automatically created, letting other programmes crop out everything around the titles.
Since I never had to do that before, I asked myself: How do we render a clip with an alpha channel in Premiere?
After careful research, combined with some tireless trial and error, I found the solution to this puzzle – and here’s how to do it.
I did a quick editing job yesterday for Oliver’s new band, a teaser trailer for a project called S.A.F.T.
It’s the German word for “juice”, but it’s also a word made up of the initials of the three band members. Their album is already available, but for an upcoming official release party, the band wanted a quick and snappy introduction to their project, no longer than perhaps two minutes.
After finishing up some of my other projects, I promised Oliver that I’d take a look at it – and here’s the result. The band were all happy, and I sincerely hope they’ll have a good launch gig in my hometown of Bremen, Germany to celebrate their hard work of putting this project together. Rock on, guys!
I had free creative reign over the end result, and I thought I’d share my process on this project with you: the assets I had available, the ideas I brought to the table, and how I turned them into the video you see above. Come to think of it, I never take enough notes when it comes to creative projects, documenting The Creative Process if you will, so let’s change this today.
I’ve finally worked out how to export 4k and 2.7k footage with my 6 year old version of Premiere Pro. That’s exciting news and gives the software a new lease on life!
With the standard export presets, tweaked to a resolution higher than 1920×1080, I’ve always encountered the following error message:
Invalid framesize/framerate for this Level. Please lower the Frame Dimensions, Frame Rate or increase the Profile and Level and try again.
Turns out Premiere has actually given me the answer to my problem right there in that error message, I just never really read beyond “lower the frame dimensions”.
Let me show you how to overcome this 1080p limitation in Premiere Pro CS 5.5 and export hi-res video without a hitch, but first make sure to check video production company phoenix so that you can get a quote.
Adobe Premiere Pro can import a series of single images and turn them into an animation.
All we have to do is import all images into our project, then multi-select them and drag them into a sequence.
If you’ve tried this before you may have noticed that a still image in your sequence may not equal the duration of one frame in your timeline, but something like 2 seconds. Highly undesirable for animations.
There is a way to ask Premiere to apply a default duration for still images:
on Mac this can be set under Premiere Pro – Preferences – General
on Windows it’s under Edit – Preferences – General
Find the option Still Image Default Duration and set it to one frame. In principle, that’s it. No restart is required and the setting is effective immediately.
You should know however that this applies to images imported going forward and will not change the duration of images that are already in your project. You see, Premiere applies this new default duration when images are brought into the project. If your setting was 50 frames, then all existing images in your project will be unchanged.
While you can change the duration of a single image, I haven’t found a way to do this for multiple existing images in a project.
Therefore, the easiest thing to amend existing images is to remove them from your project and simply import them again. As soon as you drag them into a timeline, each frame will be one frame long and play as an animation.
No matter what preset you select for your sequence, Premiere will always default to showing timecode in your timeline. This will be automatically adjusted to the relevant EBU or SMPTE timecode.
Some advice from the Memory Tree Video Production team: “Full frames on the other hand can be very useful for things like animations where timecode is less relevant.” It’s easy to change in Premiere:
In your timeline, right-click the timecode value and select what you like from the context menu:
Select frames (or any of the other options) and you’re set: the timeline reflects this change immediately. Note that the timeline itself will still retain the approximate timecode in the Program Window, in addition to the frame count. Handy!
To complete my migration from PC to Mac I’ve downloaded the trial version of the latest Premiere Pro CS 5.5 yesterday. I bought CS 3 a few years ago and haven’t regretted it, but at work we have CS 4 and now CS 5 and I can see the feature improvements and benefits to our workflow.
As last time, this is a rather large expense for me (£285 for the upgrade, which is still better than £810 for the full version) – however Premiere is a fascinating powerful programme and I know how helpful it is.
My old version has made its money back many times over so I’m sure this version won’t disappoint me either. In fact, I’m quite excited about the new options in version 5.5 and the idea of having it on my laptop.
Here are my hands-on notes, my first impressions and my two cents about Adobe’s rival to Final Cut Pro.
For the geeks: I’m using Premiere on a MacBook Pro with 8GB of Ram, 64 bit OS (Lion) and an Intel Dual Core i7 processor at 2.7 GHz.
Ray was kind enough to give me a statement on how his preparation for the biggest ice cream eating contest in the known universe are coming along. He also talks about portion sizes and that his plan is to eat SIX packets.
Recently, the National Grid have torn down a couple of buildings around the corner from us in an old industrial estate. They want to build a tunnel for some more electricity cables to ensure future supply in our neighbourhood.
Every month they seem to overtake yet another building, which leads me to believe they’re actually on a secret mission doing something dodgy.
Yesterday we had a midnight wander around the area, testing the lowlight performance of our new iPods and compare it to my recent acquisition of a key fob camera (which records HD footage for under £30) when we spotted the National Grid sign on another door. And some ironic flickering lights behind it.