Matthew Ross
2
After Effects Coins
3
COW Coins
Forum Replies Created
-
Well, I finally found the answer; I found find a post on the Adobe forums that answered the question. I had tried searches before but figured I was just not using the right terminology or something, and sure enough, the post that I found it under was just titled “Exporting H.264.” It’s one of my pet peeves when people use non-descriptive or vague subject headings in help forums.
Anyway, on to the solution: sure enough, AME was adding a data overhead at the end of the encode: the metadata sidecar file! Once I went into the Metadata button at the bottom of the export settings panel and changed the Export Options from “Create Sidecar File” to “None,” that solved the problem. Makes perfect sense now; wish I’d thought of it before!
-
Thank you for your response. I was excited to try one of the presets you mentioned thinking that maybe there was something about how I had been doing it previously that was just incorrect, and that a preset could rule that out. Unfortunately, even using the presets I’m getting the same results.
First I tried various presets for Apple, Android, and even Kindle, but modified them so that they were the correct resolution for my project. No change; I was still getting the jump up in file size at the last moment, and MediaInfo was showing the “phantom bitrate” that simply didn’t make sense compared to the video bitrate.
Then I tried just using one of the presets without changing it at all, even though it wasn’t going to give me the resolution I needed. I tried the “Android Phone & Tablet – 960×540 29.97” preset, and didn’t touch and thing, and still got the same result: video bitrate says 1,500kbps, but the overall bitrate says 6,578kbps, and the file ends up being 6.27MB, way bigger than it should be.
Then I tried installing an older version of Media Encoder, CC2014 (version 2014.0). No change, still getting the file size jump at the end and the “phantom bitrate.”
Oh well, off to Adobe I go.
-
Is there any way to change the resolution an SRT on import into Premiere? Every SRT I import comes in as 720×480, which doesn’t fit my 1080p project. And so far I can find no way to specify 1920×1080, either upon import or once it’s already imported (like right-clicking and choosing Modify…).
With the release of CC 2017 I was excited that we now seem to have all the tools we need to get subtitles looking exactly as we want them, but since we receive our translations from a service that supplies us with SRTs, so far even with the release of CC 2017, we still don’t seem to be quite there since they all come in at the wrong resolution.
-
[Michael Hancock] “This forum is my guilty pleasure, in a way. “
Mine too. FCP X isn’t even an option for me because we’re PC-based, but I like to read this forum because:
- I like to keep up on what’s going on in the world of editing.
- It’s damn entertaining sometimes!
-
[Blaise Douros] “this would happen whether you were in Avid, FCP, Premiere, Pro Tools…anything that edits audio.
“Earlier versions of Vegas would do a “micro fade” on audio by default at cuts to prevent this. The downside would be that if your audio floor was high enough you might hear that micro dip down and back up, but this default behavior could be turned off. Since Vegas came originally from an audio editing pedigree, I guess it’s no surprise they tried to address this early on.
-
Another consideration especially since we’re talking about a few shots on one project: rent a macro lens. Place like LensRentals.com and BorrowLenses.com have a number of macro options. Not sure where you’re located, though, so that may be a factor if you’re outside the US. Not sure if other countries have similar sites to rent from.
-
If your issue is that you can’t get to those keyframes to delete them because they’re beyond the bounds of the individual cut-up clips, you can un-check “pin to clip” to get to them: with the audio clip selected in the timeline, go to the Effect Controls panel and click on its panel menu (three little stacked dashes). At the bottom is Pin to Clip which you can un-check. Now you’ll be able to drag out the range bar over on the right side of the panel exposing the hidden keyframes, and you can now select and delete them.
-
That’s the way I remember it. In fact, that’s the primary reason we bought into Vegas back in… oh, 2002 I think when it was still with Sonic Foundry before Sony bought it. For broadcast work we were using IMC InCite (anybody remember THAT program?), but we started having to do a lot of quick-turnaround web-bound projects where the sources were all over the map in terms of file format, resolution, frame rate, etc. As I recall, Vegas was the only NLE at the time that would take pretty much anything we threw at it without any additional fuss, and I liked elements that came from its DAW pedigree to boot.
-
Have you tried deselecting “pin to clip” (in the Effect Controls window, click on the options icon to the right of “Effect Controls.” Pin to clip is at the bottom). You can then drag out the scrub bar on the bottom of the keyframe window to get to keyframes outside the clip length. If that doesn’t work, then maybe it is a bug with multicam.
-
The other methods mentioned would be more efficient for lots of files, but I just wanted to point out that there is a more direct way in QuickTime than copying and pasting to a new player. Once you’ve got your in- and out-points marked, go to Edit->Trim to Selection. Then File->Save As to your new file, making sure “Save as self contained movie” (as opposed to “save as reference”) is selected.