User profile for user: LocaAlicia
LocaAlicia Author
User level: Level 2
465 points

Please test proxy creation

There was a case where a file taken with DJI OsmoPocket3 could not be proxy created and stopped at 80%.

⚫︎Final Cut Proにてプロキシメディア作成ができない (Unable to create proxy media in Final Cut Pro)

Validating shared files may or may not create a proxy depending on the machine you use. I don't understand why the results are different even though it's the same file. We ask for everyone's cooperation in verification.


⚫︎File download(10GB) *Until February 16, 2025

Please click inside the square red frame. You'll see lots of banners on ad-heavy pages encouraging you to download more. Please do not click anywhere other than the red frame!



--

Q1: What is the Mac model and macOS version? (🍎 →About this Mac →Screenshot) *Please delete personal information

Q2: What version of FCP is it?

Q3: Can I create a proxy from the original file?

Q4: What kind of errors occur?

Q5: Why do you think the results are different?



--

⚫︎Verification of OP:

-FCP11.0

-Stops at 80% proxy creation

-If you try with a short file on your iPhone, a proxy will be created.

-Many crashes due to fan activation.

-I have deleted the LINE app as per Luis's advice.


⚫︎Verification of LocaAlicia:

-FCP10.7.1

-Stops at 80% proxy creation

-When exporting, frame errors often occur in the second half of the clip.

- Split the file into the first half and second half at 9 minutes 53 seconds. → There is no problem with proxy creation in the first half, but frame errors occur in many places in the second half.

-I advised OP to only use the first half of the clip.



⚫︎Verification of vz.r:

-FCP11.0.1

-There is no problem with proxy creation and export.

-There are no problems with the file.

Posted on Feb 11, 2025 9:45 PM

Reply
Question marked as Top-ranking reply
User profile for user: joema
joema
User level: Level 4
1,155 points

Posted on Feb 12, 2025 11:11 AM

There are numerous encoding errors in the file. Resolve Studio shows frequent "Media Offline" errors just trying to play it. If I disable hardware video acceleration, there are visible video glitches in those regions. This is on an M1 Ultra Mac Studio, Sequoia 15.3, FCP 11.01 and Resolve Studio 19.1.3.


Using Quicktime Player, if you click on the timecode readout on the player controls, it will cycle between 00-based elapsed time, timecode and frame number. Using frame number makes it easier to see what frames are damaged. Some of them manifest as duplicated frames, missing frames, pixelated frames, etc. In general they are toward the end, but there are some starting at frame 31640 (about 70.9%). So just cutting out some at one place likely won't fix it.


The reason for the variable behavior in certain versions and hardware platforms is similar to why various cars may behave differently using the same contaminated gasoline. It is unpredictable and depends on exactly how each engine and fuel system is designed. They can't be individually modified to handle that because the gasoline is supposed to be pure and clean.


Ideally, there should be an integrity checking tool for video files, but the only ones I know of are expensive, high-end QC tools used by broadcasters. There are so many variations of encoding formats that it is difficult to write such a thing.

View in context

Similar questions

11 replies
Question marked as Top-ranking reply
User profile for user: joema
joema
User level: Level 4
1,155 points

Feb 12, 2025 11:11 AM in response to LocaAlicia

There are numerous encoding errors in the file. Resolve Studio shows frequent "Media Offline" errors just trying to play it. If I disable hardware video acceleration, there are visible video glitches in those regions. This is on an M1 Ultra Mac Studio, Sequoia 15.3, FCP 11.01 and Resolve Studio 19.1.3.


Using Quicktime Player, if you click on the timecode readout on the player controls, it will cycle between 00-based elapsed time, timecode and frame number. Using frame number makes it easier to see what frames are damaged. Some of them manifest as duplicated frames, missing frames, pixelated frames, etc. In general they are toward the end, but there are some starting at frame 31640 (about 70.9%). So just cutting out some at one place likely won't fix it.


The reason for the variable behavior in certain versions and hardware platforms is similar to why various cars may behave differently using the same contaminated gasoline. It is unpredictable and depends on exactly how each engine and fuel system is designed. They can't be individually modified to handle that because the gasoline is supposed to be pure and clean.


Ideally, there should be an integrity checking tool for video files, but the only ones I know of are expensive, high-end QC tools used by broadcasters. There are so many variations of encoding formats that it is difficult to write such a thing.

Reply
User profile for user: LocaAlicia
LocaAlicia Author
User level: Level 2
465 points

Feb 12, 2025 11:08 PM in response to joema

Some of them manifest as duplicated frames, missing frames, pixelated frames, etc.
there are some starting at frame 31640 (about 70.9%).

I checked around frame 31640. I think the pixelation is evidence that there was a mistake in recording the shooting.


Frame 31638: Normal


Frame 31640: Error


Frame 31648: Error


Frame 31649: Normal



The reason for the variable behavior in certain versions and hardware platforms is similar to why various cars may behave differently using the same contaminated gasoline. It is unpredictable and depends on exactly how each engine and fuel system is designed.

I see. I think this is an easy to understand example. Thank you for looking into this in detail.

Reply

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Please test proxy creation

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.
Learn more Sign up