[Mickey Power]

Not clear. Adobe has phased out capture? Is that confirmed?

[Mickey Power]

I saw your post only now and went back to AME and tried Quicktime then Match Source (rewrap) but “The Source file’s video stream is not compatible with this preset.” If you switch to .mp4 it re-encodes.

[Mickey Power]

Thanks for response. Had a look in AME and can’t see where and how it will re-wrap clips to mp4 or mov without transcoding.

[Mickey Power]

I updated from 12.0.0 to 12.1.2 and have had continual linking problems. The media is on a RAID drive and on opening a project and relinking I see the saved pathway indicating exactly where the clips should be and are. But it just won’t link to them and/or has this crazy message “Selected file does not contain video media used by clip references in one or more sequences”. Grrr.

I’ve posted here and at Adobe’s forum with not much response in the way of practical solutions.

Mickey

[Mickey Power]

You can work off the translated text in a document with timecode marking off two line segments. I usually have the translation done in a table with the foreign text in one column, then timecode in the next, and the English translation in the third column. So you do a paper edit and then grab only those clips you want and keep the subtitling to a minimum.

Also Youtube has a neat captioning option. If you upload the video files (low res to speed things up) with tc window, your translator can work directly in YT and then output an .srt file for importing into PPro. In Premiere I often throw all my separate clips into a sequence, insert the captions then use that as the source.

Mickey

[Mickey Power]

I take that back. On opening various projects lots of clips were unlinked and were unlinkable! I worked my way up to 12.1.2. (Soon will instal 13.0 on a spare drive and see how that plays.)

Have posted on Adobe forum but there’s just the usual hand-off corporate drivel about a major new version causing “unexpected behaviour”. Were the iterations after version 12.0.0 (12.0.1, 12.1, 12.1.1, 12.1.3) even major new versions?? Doubt it.

The unlinked clips in question were not legacy media, either, but included footage off recent Sony, DJI and Panny cameras which dismisses that argument.

My contention is there should be robust continuity between updates. The posters on Adobe suggest that once you upgdate you shouldn’t bother accessing pre-update projects. Is that how we Adobe customers should feel??

Or is it my Mac OS system 10.11.6 or hardware MacPro 5,1 12 core 3.33ghz 32gb ram? Interested to see how many have had the above issues.

Maybe time to head back to FCPX and/or Resolve but first I want to investigate.

Mickey

[Mickey Power]

Like the first poster I upgraded Premiere to 12.1.1 and found many but NOT all clips were unlinked AND unlinkable. Why some, not all??

The solution above worked for me, so big thanks. How would someone even discover this?

That a bug like this would even happen is a joke and nothing to do with Legacy Quicktime 7 clips (it affects newer formats). Also, I posted on the Adobe forum over the weekend and haven’t had a single response.

I kept a back up version of PPro 12.0.0 and think I’ll keep working with this. Otherwise for the newer PPro for the above fix to work I’ll have to re-import over a thousand clips for the various ongoing projects I’m working on.

Somehow with the subscription software system Adobe runs you would expect better service.

Mickey

[Mickey Power]

Almost all of my work is with Premiere now on my Mac Pro 3.33ghz 12 core machine running 10.116 El Capitan.

I have a couple of projects coming up that build on old FCP7 projects.

There’s a spare drive in the Mac Pro with Snow Leopard installed and all the old Final Cut Studios apps. I’m not sure I can re-boot in it since last year I installed a new graphics card, Nvidia GTX 980 ti which is said by macvidcards to run only on 10.10.5 and newer. If I ever re-booted to it, I assume I wouldn’t get a picture right? And if I couldn’t get a picture I wouldn’t be able to boot back to my main system?

El capitan does open FCP7 but it often crashes, esp with any kind of layering and filters.

Mickey

[Mickey Power]

Sorry, is “under 30” a reference to the video or audio rate? The data rates I’ve been using are as above.

PS does anyone know about a compiling/export process in Premiere that don’t recompress the material??

Mickey

[Mickey Power]

I have a similar set up, Bryan, a cMP 2010 with 2 x 3.33ghz, Nvidia 960 ti, etc. Mostly runs well but I do have regular unprompted shutdowns in PPro 2018 (v12.0.0). Sometimes it’s something as simple as nudging a window to make it larger or smaller, etc. For the most part recently my projects haven’t been long form, but mostly under 10 minute docos with a few titles, color correction, and lots of animation of still frames. This last issue is something that drives it crazy and I’ve found that any stills (jpgs mostly) have to be scrupulously set to no bigger than 1-4mb and 2200 pixels on their longest side otherwise they just won’t render out and there are lots of issues.

Luckily Premier 12 doesn’t crash repeatedly, just 5 times a long day. My question is, how can I upgrade to just 12.1.1 and not the most recent? Every time I go through Adobe Creative Cloud it tries to upgrade me to the latest iteration which I’m always wary of.

Mickey