Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

FCPX 10.4, Stabilization No Longer Works on 8K

Scot Yount

Scot Yount

Well-known member
Joined
Dec 28, 2014
Messages
1,713
Reaction score
7
Points
38
Location
Marblehead, Massachusetts
Wondering if anyone else is having this problem. I have Helium 8K HD source files. I am editing on the new FCPX 10.4. I edit in a 1080p timeline. I shoot some handheld stuff over cranked and usually use stabilization in the inspector to take out the bumps. Has always worked well, even on 8K source. Now, it no longer works. It takes an hour to analyze a 6 second clip, and once it is done, the clip remains unchanged. However, other .r3d material works fine. I have in the same timeline some 4k HD source material from an old Scarlet MX. Works fine. XDCAM works fine. Blazes. I am on High Sierra (I know, I know) and a 12 core Late 2013 MacPro with the D700 cards. Anyone have any ideas?
 
A few people have posted this week about performance issues after updating to the latest High Sierra 10.13.2
 
Yes. I have some issues that some others have. Like H.264 export. Painful. But I had not seen anything about anything simply not working.
 
Apple really takes the Pro users serious... It's a big plus to get the hardware, the operating system and the software from one vendor... Well, you still have the design statement.
 
Out of curiosity I tried and was able to stabilize 8k Helium footage with FCP 10.4. I am running High Sierra beta 10.13.3, not sure if that is the difference? 10:1 compression 23.98 8kHD R3D format used. I have a 2013 macpro with 64GB ram, D500 cards 6 core model.
 
Jon Dishler said:
Out of curiosity I tried and was able to stabilize 8k Helium footage with FCP 10.4. I am running High Sierra beta 10.13.3, not sure if that is the difference? 10:1 compression 23.98 8kHD R3D format used. I have a 2013 macpro with 64GB ram, D500 cards 6 core model.
Click to expand...

Interesting to note. Was the analysis super slow, as in glacial?
 
Well, looking at it again, I left out perhaps the most important part. I first stabilized it in Proxy mode which was created during import, then switched to optimized/original in FCP as I usually do. When I tried to stabilize directly in original, my experience matched yours and it did not work. Yes, it was kind of slow but not glacial.
 
Another option is to change the project to 4k, then you can stabilize the optimized media directly. I don't think FCP fully supports above 6k. This I believe is why the image can be stabilized with either the smaller proxy, or with a 4k representation in the project.

Another issue is that when R3D's are imported into FCP 10.4 the metadata is changed from WideGamutRGB/Log3G10 to the gamma BT.1886 and in order to get close to the look of the same clip on RedCine-X one needs to change the gamma back to log and then input the correct LUT such as the Log to Rec709 medium contrast/medium size in FCP in the Camera LUT input field. Interestingly, if there was a custom LUT applied such as PhilmColor it does transfer through to the footage. This is by clip, so if you import only the R3D's it can be avoided, otherwise there is no way to get rid of the creative LUT in FCP, but can be added per clip within FCP after import. Even with doing this correctly, it is not an exact match to the RedCine-X version. I have opened a ticket with Red support and they have acknowledged there is an issue with the implementation.
 
Jon Dishler said:
Another option is to change the project to 4k, then you can stabilize the optimized media directly. I don't think FCP fully supports above 6k. This I believe is why the image can be stabilized with either the smaller proxy, or with a 4k representation in the project.

Another issue is that when R3D's are imported into FCP 10.4 the metadata is changed from WideGamutRGB/Log3G10 to the gamma BT.1886 and in order to get close to the look of the same clip on RedCine-X one needs to change the gamma back to log and then input the correct LUT such as the Log to Rec709 medium contrast/medium size in FCP in the Camera LUT input field. Interestingly, if there was a custom LUT applied such as PhilmColor it does transfer through to the footage. This is by clip, so if you import only the R3D's it can be avoided, otherwise there is no way to get rid of the creative LUT in FCP, but can be added per clip within FCP after import. Even with doing this correctly, it is not an exact match to the RedCine-X version. I have opened a ticket with Red support and they have acknowledged there is an issue with the implementation.
Click to expand...


My source material is 8K HD, but my timeline is 1080p, though supposedly, 10.4 FCPX does support an 8K timeline. (never sure why anyone wants to edit above HD unless you have a 4K monitor and want to see your image processing in 4K) So, if I need a 4K output, I just change it to 4K when I export. I am glad you opened a ticket with RED support to fix IPP2 issues.
 
it is not the timeline, try clicking on the project then settings, change it to 4k?
 
Change it from 1080? Ok, will try that but not sure why going up in timeline resolution would fix the problem, however all up for trying everything at this point.
 
Has anyone tried using Warp Stabilizer in AE with Helium footage? I did and it produced horrible results-looked like it hadn’t done anything at all. I assumed this was because the original footage was beyond repair. Assumed the footage, which was an air-to-air shoot, was a waste until I read this thread. I transcoded the footage, stabilized in FCPX, and it’s usable. I’m actually amazed at how well the FCPX stabilizer did with all the shake and rolling shutter artifacts in this footage. I haven’t tried running the transcoded footage through AE, but I’m thinking that it’s possible that the issue could be with helium footage and not FCPX...
 
Quinton Weiskittel said:
Has anyone tried using Warp Stabilizer in AE with Helium footage? I did and it produced horrible results-looked like it hadn’t done anything at all. I assumed this was because the original footage was beyond repair. Assumed the footage, which was an air-to-air shoot, was a waste until I read this thread. I transcoded the footage, stabilized in FCPX, and it’s usable. I’m actually amazed at how well the FCPX stabilizer did with all the shake and rolling shutter artifacts in this footage. I haven’t tried running the transcoded footage through AE, but I’m thinking that it’s possible that the issue could be with helium footage and not FCPX...
Click to expand...

This is good information. Yes, I find the FCPX stabilizer to be quite good for what it is....but like you I find that it no longer works on Helium files. To be clear, is used to work...but in one of the recent updates, that functionality ceased to exist.
 
Hey guys!

Same problem here! Stabilization not working at all on Proxy & Optimized mode...

Any updates on this issue?

Thanks in advance!
 
Transcoding clips that need stabilization to Prores 4444 is the way I’ve been working around this issue.
 
Helpies?

Helpies?

Can anybody confirm if this issue is still present in the 10.4.1 Update or has it been addressed? Not being able to stabilise the raw footage inside of FCPX is killing. :S
 
Christian Fitzpatrick said:
Can anybody confirm if this issue is still present in the 10.4.1 Update or has it been addressed? Not being able to stabilise the raw footage inside of FCPX is killing. :S
Click to expand...

Can confirm its resolved!
 
You must log in or register to reply here.
Back
Top