[Tim Kolb]

exporting will respect the duration of the clip and force whatever you have into the frame rate specified for the duration.

As Ivan said up a bit in the thread, there wouldn’t be many frame drops as the frame rate is obviously only slightly different.

However, it isn’t the same as interpreting everything on the front end where each frame is displayed at the new frame rate, adjusting the clip duration as necessary.

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Tim Kolb]

I might at least try exporting one of them and checking it to see if it stays in sync.

What are the file settings you’re exporting to in detail?

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Tim Kolb]

Are the voices synced to the 11 separate sequences, or are they only on the “master” sequence?

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Tim Kolb]

Yes…it’s 50 Mbit/s XDcamHD422 basically…Canon’s take on it anyway.

I assume the files were left in the folder hierarchy they were in on the camera if they worked properly in CS6.

I don’t have any C300 footage around to test myself, but I know that others edit in CC, so I don’t think there’s a specific problem with it…

Can you furnish some more detail? Where the media files are… How your metadata preferences were set in CS6 vs CC, etc.

It’s an odd behavior, certainly.

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Tim Kolb]

Has anything at all been done to the file structure of the camera footage between working in CS6 and CC?

It sounds like a metadata recognition problem (the metadata would be what informs PPro about the clips that are spanned, etc.)

I assume this is 50 Mbit Canon XF (XDcam422)?

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Tim Kolb]

If you change out the video clip, does the problem still exist?

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Tim Kolb]

Software companies all have CC versions out by now.

…what I’m saying is that some users haven’t installed (purchased) the updated plugins yet (they just drag the CS6 or earlier version into the CC plugins folders) and many times the CS6 versions will work…sometimes fine…sometimes 99% of the time with a few odd quirks…it all depends.

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Tim Kolb]

Tough to act upon “glitches” as a problem. it’s a little broad.

Perhaps you could show a short segment where the problem occurs and describe any recurring common traits of footage at the points where some of this happens…

Right out of the blocks I’ll note that plugin effects that haven’t been updated between CS6 (or earlier) and CC can be problematic in certain circumstances.

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Tim Kolb]

I wasn’t so much focused on the differences between CC and CS6…I just looked at CC.

The column doesn’t seem to be very active at any rate. I did get data on XDcamHD media.

QuickTime and CineForm AVI left the column blank for me. Not terribly useful.

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor

[Tim Kolb]

This column seems to be active with codecs that Adobe handles natively in CC…I don’t know if that can harvest that metadata from a QT file…I can’t get that column to work for any QT file here. (on Windows)

TimK,
Director, Consultant
Kolb Productions,

Adobe Certified Instructor