Video Rendering error -50

Got a project I am trying to render and the following error message comes up when trying to Share to Master File

I have tried googling that error number but can't find anything of relevance.

Does anyone know whats happening. I have tried other projects including taking a small clip creating a new project and rendering it, all OK.

I have deleted all render files, re opened FCPX re opened the event and project -- same result

I have consolidated the files because i am using a few external files in the project, but again same result

Any tips greatly appreciated


PS App nap is disabled

I ran into that one recently as well.
Not sure what causes it, but maybe we can figure it out together. For instance: Do you have mObject in the Timeline that won't export?

Ellard

What version FCPX ?

that annoying '-50' is an 'error in parameter list' .. wahtever that means.
usually indicates, your project contains material, the encoders can not handle correctly.

so, Q#1:
is all your material optimized? or do you handle 'raw' material, if so what?

Q#2:
if not, do you use material 'manually' converted, using tools based upon the ffmpg-engine, as Handbrake, or the -zillions of 'converters' avail at Appstore, e.g to conert mts>>mov etc etc?

Q#3:
videos from an iPhone involved...?

I my case it was an .wav file what caused the problem. If you have separate audio clips, try to deactivate them and retry the export.

I've had this before, sometimes it can be fixed by copying the project to a new library.

Thanks Karsten

Re Q1 Yes all material optimised original files left in place
Q2 No to manually converting anything
Q3 No to Iphone

These are two mts clips about 45 min long on total plus a dozen or so stills (jpg) and one MP3 track

Thanks Darren
Just trying this one now, clips are being copied. I will report back

You don't need to copy the files, it can't hurt except for the time it took.

Well I found the problem, but not the fix.

It is the second of the two mts files. This was one shoot (an interview) and the camera split at the 2gb mark, and its the second part that is causing the issue. What I did was try to render each clip seperately in its own trial project and event. The first one was fine, the second came up with the error immediately.

I am thinking there is not going to be a fix, as this is with the original media. Would i be correct (hoping not of course)

Hmm, did you make a disk image or a camera archive of the card that footage is on? If so you may be able to fix that by reimporting it. If you have it, use the import window rather than drag and drop for mts files.

You may be able to transcode it to prores in compressor and then force relink it using FCPXchange.

One of my few big frustrations with FCP X is how clunky importing spanned mts files is. My guess is that the Canon and Sony software required to work with FCP X is likely mostly to blame.

Red has managed to make a very solid background app that rarely causes me any grief. And, this is on top of their codec being so resource heavy. On both Canon footage and sometimes Sony FS700 footage I get black clips at the span break.

It's completely frustrating these brand new cameras are still using cards that need to adhere to the fat32 4GB file size limit. Rant over..

Thanks Darren

I might be stuck, this was originally brought onto the computer when I was using Windows and Premier Pro. I didn't fully understand about the AVCHD structure and simply dragged the MTS files into a raw media file and kept them. Now that I have ditched Windows completely and moved to OSX and FCPX the only file I have is that one. I did use the import function and this is the only clip that has given me trouble so far, from quite a few I had to work on.

Re your comment about black frames -- I have noticed that at the span break on some of my clips, I get a number of frames frozen, but the audio is still going. If I detach the audio and then remove the frozen frames, the audio goes totally out of sync. on playback (without removing the frames) there is a noticable freeze and disconnect between visual and sound. Can you suggest any way to improve the finished product? This didnt happen on Premier Pro, and as you say is extremeley annoying.

You think it is the Sony software and not the FCPX software to blame -- why? I would have thought the other way round, as in PP all was good. (UPDATE - just did a google search on this and found other threads indicating that it happens on Adobe products too. )

Thanks for the help

Try clipwrap on it. I think they have a trial version where it can convert the first minute, but if it can do that, it might work.

How big is the file? If worst comes to worst I could use clipwrap on it via dropbox.

Doug108 wrote: .... I didn't fully understand about the AVCHD structure and simply dragged the MTS files into a raw media file….

AVCHD-strcuture means. it is a standardized folder-within-a-folder structure; and well-hidden inside are the 'videos', h264 inside a mts-wrapper.

The other stuff contains valuable info, for instance, how chunks of a longer clip are connected (and lots of other meta-data… FCPX is all about meta-data). I'm doing long recordings here every week - never had any issues… using the AVCHD files.-

So, what you have done, is NOT copying the whole AVCHD-'folder', which is on Mac a pkg-file, which looks like a solid, single file, but is indeed a package of files?

There's a free tool avail AVCCAM Restorer, which claims to re-enact a fully functionally AVCHD-structure from orphanized mts.. never tried it, but in your desperate situation... give it a try.

Another tool is REMUX, which just rewraps the h264.mts into a h264.mov. In a 2nd step you could 'iron it' using Mpeg Streamclips 'Fix Timecode Errors'; finally, while in Streamclip, convert it to proRes.

Keep your AVCHD intact! ...

Good advice from Karsten and Darren.

What's sad is that, working from AVCHD media and camera archives, I've never had a media spanning problem. For all the criticism levelled at it, I've found AVCHD (and AVCCAM) to be absolutely solid from this point of view. I'm rather surprised to hear that the more 'professional' Canon and Sony formats haven't solved the 4Gb file spanning problem as successfully.

I completely agree with Darren that our continued reliance on FAT32 is absurd. Ironically, I believe the standard file format for large (>=32 Gb) SDXC cards is a licensed version of ExFAT, which doesn't have the 4Gb limit. But which 'professional' cameras use SDXC cards? Huh.

Thank you Microsoft for keeping outdated crap technology alive and kicking! They're so successful these days, they are buying MBAirs from folks to get them to trade to one of their tablet hybrids that don't work. Yep, Microsoft, keeping outdated, limited, junk, legacy technology alive for over three decades.

SOLVED !!

I downloaded Camcorder Video Converter trial from these guys www.etinysoft.com/ and ran it on both files. The result was two perfect clips, no dropped audio, no frozen frames.

So then was able to complete this project.

My misundestanding on the AVCHD structure I think was the initial issue, so through this I have a better understanding, but also I learnt something regarding the importing into FCPX, I had copied these files before I moved over to Mac whilst in my short lived sojourn back to the windows platform but couldn't stand it for long. (worse than purgatory!) So I didn't have any files to compare with from new shoots, until yesterday. I had another interview on camera to start working on, connected it, and using FCPX went to import directly from the camera. Of course you all probably know what comes next, FCPX sees all four 2Gb mts files as one clip and imported perfectly as one transcoded item. Awesome.

It would be good if camera manufacturers could get over this 2Gb limit, but I suppose that will come one day. But jjsandersons last comment made me look at the specs for my camera and it can use an sdxc card, it's a semi pro Sony HXR-NX30p magic little camera.

Meanwhile, thank you all for your input, which has helped me greatly to understand Camera files, AVCHD, conversions, and FCPX, and happy days for a succesful outcome.

Namaste
Douglas

You are welcome! I'm glad you got it sorted.

The spanned nature of some of the camera manufacturer's formats are just crazy at this point. My albeit limited understanding is that not all digital asset management servers for some broadcasters have been updated to a drive format that can handle over 4GB. So then it stays in the dark ages for the rest of everyone else.

It would be nice to get the option for different formatting, but no.

Dealing with prores from Alexa and BMD cameras is heaven. One file, no transcoding, perfect.