[Ryan Patch]

Yes, Tim, please refer to my original post, as well as the post that I have linked. This is an ongoing problem and is not remedied by those options, as I said in my original post. Internal or external drives, nor media type don’t seem to solve it (as I said in the linked post, happens with H.264, MP3, WAV… now I can add HVX MXF files and R3D to this list).

Does anyone have a lead on why this happens?

R

[Ryan Patch]

No, I’m talking about the general disarray that Premiere manages CFA and PEK files with. This includes –

#1 Re-generating CFA and PEK files for media that already has them generated, at seemingly random project opens when they are already generated.
#2 Re-generating CFA and PEK files when you move a project and media between computers, even if files are already next to media.
#3 Re-generating CFA and PEK files when you use the same media in different projects when it already has these meta files from other projects.

#1 is straight-up a BUG that’s been around for a while (see linked in first post). #2 and #3 are just things that should have been fixed.

I’m asking if anyone has found a solution to #1

R

[Ryan Patch]

Windows 8.1.

R

[Ryan Patch]

This does not work for me.

[Ryan Patch]

1 SSD for OS and Apps
1 SSD for Projects
1 HD for scratch & Cache files

Other drives per project as needed.

[Ryan Patch]

I do agree, though, that there should be some sort of media manager that allows you to “bake in” AE comps that you’ve embedded.

[Ryan Patch]

Unfortunately, there is no workflow to transcode all media in timeline and “bake in” effects like you can in Avid. With the ease of integrating Dynamic Link into your editing process, this generates this new problem when you need to go to DaVinci, yes.

There’s two options: export a “baked in” whole timeline and then use shot detection / EDL to cut the shots back up in Davinci. This is painful if you have fades, though.

Other is this: Delete every timeline from a project except the one you will color. Duplicate this sequence. Save as NEW project file.

Remove all effects from new sequence, import this sequence into Davinci. Manually add source files from AE comps. DO all color without effects on clips. Export clips. Relink clips in Premiere project. You can also duplicate AE files, relink to colored source media in AE comps and to new AE projects in Premiere (if you duplicated). Re-apply speed effects, copy and pasting from original sequence you duplicated if they’re fancy or complex.

It’s a pain the butt, but that’s the way to go. Basically, if I am doing anything that I know is going to Davinci, you need to wait until AFTER color to do heavy work on it. That’s just the way the pro toolset works. You can do everything out of order, free-wheeling and neauveux-editing style… but it limits you when you want to use pro tools like Davinci or Protools. There’s a post workflow that is followed for this reason – there’s only a certain number of effects that translate between programs.

Ryan

[Ryan Patch]

There is no possible way to edit in an increment smaller than a frame. A video will run at a fixed FPS (23,98, 24, 19.97, etc) and to try to make a half-frame duration would throw everything out of whack. There isn’t and has never been a video editing system that will allow you to edit “sub-frames”.

This was the case in FCP7. You could only edit as detailed as a frame. There may be other reasons that FCX might be preventing you from editing the best you can, but this is not one of them.

You CAN, using Premiere, FCX, and Avid, edit AUDIO at the sub-frame level. I know in Premiere you can make edits up to the precision of the sample rate (usually 1/48,000th sec).

I would say that, in my opinion, even if an audio hit is 1/2 frame “off” (the most it ever would be) you don’t notice the .05 second difference. If it’s really that important to you, you can slip the audio in subframes.

R

[Ryan Patch]

This is Ryan Patch and I approve this workflow.

R

[Ryan Patch]

Hey Kim –

I have used exfat for editing drives before. I have found it to be slightly less stable then NTFS on Windows or HFS on mac. Slightly. Like, if you work with any drive long enough, it will get corrupt. I found that the exfat architecture was just slightly less reliable. I still read and wrote to the drive for 8+ months before anything happened.

A word of advice, though: because of some quirk, macs don’t like exfat volumes created on PCs under certain circumstances. Save yourself some headache and just create the volumes on the mac.

R