Alex Smith
Forum Replies Created
-
Thanks!
-
Thanks for posting your solution. I never solved my issue, but I was able to get away with it because it was a music video. It wasn’t more than an annoyance for me, luckily. Glad you found a way to make it work. Hopefully the issue will be fixed before I am working on a project where it’s a big deal!
-
Yeah, I’ve used After Effects for years, but only for shots that are a few seconds long. I’ve spent most of my time with FCP since it came out, and exports have always been quick if your timeline was rendered (which you normally wanted to do before exporting because if you didn’t, it only rendered for the export and you lost all that time and the render files). But either way, short-form stuff (where I work mostly) only takes a few minutes to export. I didn’t have to plan for that break or overnight process. I’d just go read half an article on the internet and then start compressing or uploading my edit.
Anyway, thanks for the help. As long as it’s working like it should, I’ll just get used to it. It’s still a much better choice for me than Kamikaze Cut Pro X. I expected some changes in workflow.
-
Thanks again. This type of support in a public forum like the Cow is not something I’m used to coming from Apple. Still love their OS, but I digress.
Thanks for the link to performance as well- I like how it’s not all about hardware. I’m dreaming that Adobe adds OpenCL support to the Mercury Playback Engine, but I’m also poised to get a new set-up when I really need to.
I guess the bottom line with the slow export is simply that’s just how it is? I love the fact that I don’t waste time transcoding, and I’ll be more conservative about what I render from now on and enjoy that. But for the last 12 years in FCP, I started working in DV25, rendered when I had to and quickly exported. Then I moved on to DVCPRO HD with the same story. Eventually, Red and DSLRs forced me into the multi-day joy of transcoding to ProRes, but again, once over that hump, an export took a few minutes on most projects. It simply was not something I had to think about. Is this just not a reality for Premiere, or am I still missing something?
-
I’ll be more specific:
The audio issue is this- when opened in Premiere (source monitor or placed in timeline), the video plays fine, but the audio will play about 2 seconds, then jump ahead 2 seconds, and play 2 seconds, then jump ahead, etc. It winds up ending early and depending on the length of the clip, usually the second half of the video just has no audio simply because it had already jumped through it and reached the end. The waveforms reflect it, too. Again, the clips all play perfectly fine in QuickTime, so I could workaround by exporting them to another format. This project is a music video and the audio was just for reference so it’s not worth that, but I’d still like to sort out the issue.
It’s occurring so widely, I’m pretty certain it’s a Premiere or settings in Premiere thing, not cameras or card issue, but here are the camera specifics:
We shot at 24 fps on the 5D. 8 clips are fine and then the last two have the audio issue in Premiere.
We shot about 30 clips on a T2i. Most were at 60 fps and I interpreted the footage in Premiere to playback at 24 (23.976). Though obviously I won’t be using the audio from those clips, they seem fine. In the middle of those clips are a handful of clips at 24, and they do have this audio issue.
We have about the exact same sort of footage and issues with clips from the 60D as the T2i.
Any ideas? I wouldn’t be surprised if this was operator error and someone just needs to say, “Did you check this box?” but it could also be a bug in the program- or maybe just funky files that QuickTime can handle and Premiere can’t.
-
Thanks for the help.
They’re all 48KHz and all the same format. That’s what’s so weird to me. I’ll have one clip that plays properly, and then the next clip won’t (though they all play properly in QuickTime). I have three cards from three different cameras and all of them have clips that play correctly, yet also have clips that have messed up audio in Premiere.
For instance, on a single CF card from a 5D, I shot a 2 minute clip, stopped recording for a minute, then recorded again; the first clip plays back perfectly and the next one skips and drops audio. No change in any settings that I’m aware of. I’d say it was my card or the camera or even the operator, except that it’s happening across three cards from three cameras and I haven’t asked Premiere to interpret any clip differently from the other (AND it plays perfectly in QuickTime). Any other ideas?
-
Great article. Thanks!
I’m still having a bit of trouble wrapping my head around this. Are there settings that you can suggest that would allow me to render preview files at a quality that would be acceptable (say, ProRes 422) and then also be able to export using those already-rendered files to create an also acceptable final file? Does this make sense? I feel like this was how FCP worked in the background, but I also understand it’s a different game when you’re allowed to edit natively with so many formats.
I’m open to changes, but exports that take 10x what I’m used to are a massive change for the workflow I’ve used for a decade. Still trying to understand this.
-
Ah, that was very helpful. Thanks. I had not noticed that checkbox, and I bet it will speed things up in the future. I understand how it could be dangerous and will use it with care.
As far as the green bar throughout comment, I think it’s probably me coming from an FCP world where a red bar means it won’t even attempt to play. I’d put some simple color correction filters on everything and DigiEffects filters on a few clips, which understandably will not play. I just went ahead and rendered the whole timeline even though much of it would play back fine. Part of that thinking was that it would speed up the export when it came time, but now I see I missed the setting to do that.
I’m really trying to learn this program and just jumped in head first, so please let me know if you have any other tips or if anything I’m saying is in the wrong mode of thinking. I used Premiere in the late 90s but then jumped on the FCP bandwagon with v1.0. Now I think I’m back. Great program, but I’m still trying to get my bearings and also hoping that Adobe will polish this program up, especially for us Mac users/FCP converts. I just got the book, An Editor’s Guide To Premiere Pro, and it looks like it will be a great jump start.
-
I think you’re totally right about the windfall. Whether it’s Adobe, Avid, or something completely different (I won’t even count FCP X out), Final Cut’s debatable suicide leaves the door wide open for someone to jump in and take over the NLE space, prosumers and pros alike. Though both great apps, Avid and Premiere just sort of subjectively feel to me like they were written before they had a clue they might have the opportunity to win back all the market share that FCP had. I expect they’ve kicked up their games a notch since June 21. Good for us.
Sorry to derail the thread. The export is still killing me. I ended up having to do it in chunks (I think Dynamic Link to AE is what was crashing me after all) and what’s weird is that after throwing the chunks back into a timeline (with a yellow bar?) they exported fairly quickly. It’s like Premiere makes itself re-render everything that’s already been rendered when you export. Why is this? Is there a benefit I’m not aware of?
-
So this is becoming a big deal on the project I’m working on. I’m using a plugin from DigiEffects and I believe one of the plugins is making it crash on export. The real sting is that the video is already rendered and if Premiere just wrapped up the render files and made a nice little video file I’d be fine. Instead, I’m having to do this in chunks to figure out which clip/filter is crashing the program (even though it’s already rendered and plays back fine). Not to mention that each time I export it takes closer to an hour than the five minutes I’m used to for rendered video. Any thoughts?