Share to Vimeo fails HD conversion consistently

Thank you kindly Russ.

When the projects failed encoding to HD on the Vimeo side, I was simply using the Send to Vimeo option from FCP. The projects are short, typically 5 to 20 minutes, with an opening section, a talking head video, maybe a Screencam clip, then a credits roll. Nothing really sophisticated. The talking head portion is shot against a green screen and I use FCP's Keyer to replace the background with a moving clip. Fairly vanilla stuff. Send to Youtube works fine, I simply prefer the control over viewing, licensing and embedding that I understand with Vimeo. Perhaps I can do exactly the same thing with Youtube, I simply do not know how with the exception of licensing.

I then tried using the Compressor option called Publish to Vimeo, with the subsection called Up to 4K. I then made a copy of that option and adjusted it to be 1080p maximum since Vimeo doesn't do 4K (according to them) but it still failed.

If I copy the 1080p version to a different location in the Custom menu without the Publish to Vimeo option and make a file, then upload it manually it gets imported and encoded without problems.

I have since made a new export configuration using the Matrox Mini with MAX H.264 compression to 1080p with settings for 15mb/s and 320kbps audio per the Vimeo site and so long as I upload them manually, Vimeo encodes both the SD and HD versions successfully. I was really just trying to figure out why the Send to Vimeo option in FCP was failing at Vimeo during their encode process.

Cheers,

Ross

That always works, was really just trying to figure out why a share direct from FCP would fail at Vimeo.

Thank you Russ.

This is the screenshot for the project that Vimeo would fail on .

The project has been encoded by following the separate steps and is running so while I really appreciate your willingness to help, I would not impose on your time and expertise too much. My workaround works, and my question was more a "why fail" than a request for a fix.

Ross

Hi Russ,

Good questions, I probably set the codec to ProResHQ but for the life of me I cannot guess why I would have. Also interesting that it came up as 1080i since the C300 puts out 1080p and all my other projects show up as 29.97fps 1080p. Since I insert other material in the final video, is it possible that I placed something else on the timeline that was 1080i that locked the project settings, removed it, placed the C300 clips but they did not reset the interlaced to progressive? I honestly cannot recall but that is possible because sometimes I rush too much.

I think that if I drop a clip from the C300 on the timeline then that sets the Project settings and other clips are made to fit those settings. Do I understand this correctly? I often use Screencam recordings that should be 1080p but sometimes may not be, or place the opening clip that I thought was 1080p or even a B camera clip from an old Canon video camera that says 1080 but doesn't spec i or p. Perhaps this is why the whole project shows as 1080i?

Do you think that because the project as 1080i, this may be why the Vimeo HD encode failed?

Thanks a ton for all your insight.

Ross

Hi Russ,

The C300 can save internally at 23.98p, 29.97p or 59.94i The thing is that I am pushing the HDMI out from the camera through a Blackmagic ATEM switcher that then takes the signal from the different cameras and puts it out over HDMI to a Blackmagic HyoperShuttle recorder.

I've attached a screenshot of the inspector window and it shows that the file was saved as 1080p (I think) at 29.97fps and encoded as Prores 422HQ (the encoding is set at the ATEM)

I really do appreciate your help. I have found that the default Apple Vimeo encode is a much larger file than the Vimeo encode that my Matrox Mini with MAX produces that looks to be of perfectly acceptable quality. So I will go that route anyway and not worry about uploading direct to Vimeo from FCP.

Cheers and thanks again,

Ross