[Ryan Patch]

Awesome summary, Mike. It is a difficult issue to talk about, but one that really needs to be fixed in order to have any semblance of a collaborative workflow.

If this is important to you, please head over and request this feature. You could simply just copy and paste Mike’s writing. https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

This problem also brings up FCP’s slight advantage that you are able to export JUST ONE sequence as XML, rather than the whole project. This enables much easier breakout of a project for multiple / asst. editors.

[Ryan Patch]

We’re not asking for a “feature” in the program like it is in FCP or AVID (although that would be nice). What we’re talking about is a visual representation of the default shortcuts in a form that could be printed and referenced. The fact that this isn’t a part of the help file seems to be an annoying oversight. We don’t need another feature, we just need proper documentation.

[Ryan Patch]

I would also check this out:

https://www.videoguys.com/Guide/E/Videoguys+DIY9+Sneak+Peek+Its+Time+for+Sandy+Bridge+E/0xe9b142f408a2b03ab88144a434e88de7.aspx

[Ryan Patch]

Pressing SHIFT+3 is an okay workaround, but it cycles through tabs in a wonky order, and isn’t really a replacement for the FCP shortcut. Really, we just need the TAB and SHIFT+TAB button to take us through different tabs in a window, whatever they are, in the visual order that they are next to each other. This would help a lot!

[Ryan Patch]

Slowing the footage 40% is one way to do it – I like to right click and hit “Interpret footage”, then enter the framerate of 23.98. You will also need to decide if you want to scale the 720 footage to 1080 for a slight quality loss, or both down to 720. If you’re just delivering internet 720, I would recommend going 720.

[Ryan Patch]

It’s around… keep searching those interwebs…

[Ryan Patch]

No they are not. I have a scratch disk that stays constant, on an external drive I hold as “S:”. This doesn’t change across projects and it certainly didn’t change today when my I opened my project file and the re-conforming started.

Also, I don’t understand how scratch disk would matter, given that it’s not the scratch disk that’s in question here (for the media confirmed files) but the media cache which, for the record, I have set to “same as source media”.

As a side note, I would love to be able to define media cache files’ location on a per-project basis (like other scratch disk items,) instead of globally.

Ryan

[Ryan Patch]

All types of files – .MOV from Cannons, .MOV transcoded in prores, .WAV, .MP3’s. It’s going through everything and creating like the 5th or 6th version of the CFA files.

SIGH.

If project opening is improved in CS6 I’m excited, because already I would say that opening was pretty solid, only the re-generation of .pek, .cfa, and .qtindex files was tripping me up.

[Ryan Patch]

Thanks for all of the replies –

I am definitely using the most recent version of Premiere, I am militant about updating.

Unfortunately, I don’t want to go to XML because I will loose much of my work with Advanced metadata that I’ve tagged in Premiere (at least that’s what I understand.) Given that the error comes from AE, I’m thinking of splitting out all of my AE comps that are in Premiere and not importing them until I’m back in the final stage of editing. Too bad to have to do that.

Speaking of Metadata, does anyone have any information about what parts of the Metadata you assign in Premiere are written to the file, and what parts are only tagged in the Premiere project? It seems like there should be something equivalent to the Lightroom command to “write metadata to files” or something like that to “bake in” the metadata to the files. This would help with conforming to online files in Davinci when you’re trying to link by reel name / #.

I have run into some more serious problems with a drive on this project, putting that fire out right now and will return to this problem at the beginning of next week. Any additional thoughts are appreciated.

[Ryan Patch]

Update:

I just waited it out… through the (Not Responding) messages… mainly because I opened up the system monitor and saw that Premiere was looking through every single one of my media and media cache files. 1.5 hours later, it has imported the project into a new one. The new project seems a bit more responsive, and also can exit without crashing!

However, when I exit, I still get an error in an after effects window – which is odd because I didn’t have the AE app open, only Premiere (although I am aware that AE starts when you have AE projects imported into Premiere.)

Runtime Error!
Program: C:Program File… (truncated, but I’m assuming it’s AE because it’s marked as AE in the taskbar)
R6025
– Pure Vital Function Call.

Any insight would be great. Thanks!