Skip to main content
Participant
March 10, 2017
Answered

Sony FS5 in camera Proxy issue linking in PremierPro

  • March 10, 2017
  • 5 replies
  • 5406 views

Hi

One useful feature of the Sony FS5 camera is its ability to generate Proxies (h264 .MP4 files at 1280x720)  in camera whilst recording .MXF Masters.

The issue is that these files can not be Linked in PremierPro due to the audio channels not matching the Master .MXF files. the .MXF files have 4 audio channels, whilst the .MP4s have only 2.

Is there a way to quickly add audio channels in Media Encoder to .MP4 files? Or is there a way of removing 2 audio channels from the .MXF files... the 2nd 2 are always empty anyway..

Any help, or work arounds, that others have found would be great to hear!

Thanks

Tom

www.thomashogben.com !

This topic has been closed for replies.
Correct answer R Neil Haugen

Jim's comment is spot-on. I would not choose to use a long-GOP type CPU intensive codec like the H.264 for a proxy. An all i-frame like the Cineform Jim recommends, the Avid DNxHD/R which is actually newer designed and more optimized for 4k and such than ProRes, or ProRes would be the main choices I'd look at.

Neil

5 replies

Participant
January 29, 2021

I see that many Sony users have the same issues with the proxy files created by the camera. Here's something I did that solved me issues with Sony Proxy files. 

First I have the Sony PXW-Z90 wich records 4K using MXF files. Impossible to use the proxy files from the camera because the original 4K files contains 4 audio channels and the proxy files generated by the camera only 2. (Hope Sony will wake up and create a new firmware to correct the situation)   So because of the audio files mismatch, Premiere Pro can not match the files, indicating an error message. I have tried using the ProRes or CineForm presets: Not bad, it a Quick Time proxy, very fluid, but I realised that the proxy file under Quick Time is LARGER than the 4K original file. For me, that was a nonsense. I'm talking of a proxy file that is almost 1.5 times larger than the original. So I tried something else to have good proxy files and lightweight and I found a very efficient solution for my needs.

I created a new preset, not using ProRes or MP4 format, but as my original format is a MXF file, no matter what the resolution I choose, I openned Media Encoder and did the following:

First, in the export settings, I selected the video format  MXF OP1a   wich is similar or identical to my original MXF file from the camera. Then, in the video section, as my camera is a Sony XDCAM, I selected   XDCAMEX 18 NTSC 720p (4:2:0)   wich gives me a very light file.  With this selection, by default, I get a 1280 x 720 resolution, wich is fine by me. Images are at 29,97f/s with square pixels aspect. It can be different to match your camera system (PAL or NTSC) .

In the video section, leave the rest as it is. In the Audio section, the audio codec is uncompressed, I selected the same settings that the original files (16 or 24 bits, 48, 44.1 or 32 khz), this is not realy important for making a proxy file. Finally, and THIS IS THE MOST IMPORTANT, I selected the number of audio channel that match the number of audio channels from my camera. As my Sony PXW-Z90 records on 4 audio channels, I selected  4 channels. If you don't match the number of audio channels of your camera, it won't work, so this adjustment is crucial for the success of the new preconfiguration.

That's it.  I Recorded my new preset with a specific name (the choice is yours for that part), so every time I have to create proxy files from my PXW-Z90 footage, works like a charm every time and it takes no longer compare to using ProRes. The big difference is the file size: The proxy file are now much smaller with very good quality to work with: for a MXF file of 3,90G, I get a proxy file of 390mo. The bit rate goes from 100MB/s to 10MB/s. Its super fluid, smooth and very very easy to work with. That's the solution I found and it works like a charm for me. Hope it will help.

MiguelAgain
Participant
August 7, 2021

Thanks very much for sharing this info.

Participating Frequently
September 27, 2019

Has anyone figured out a solution to this premiere must be capable of doing it as when I use the 4k xavc l 4 channel files in premiere rush it creates 2 channel 1080 h264 proxies which I can edit on mobile or desktop rush and then when I open rush project in premiere it replaces the 2 channel audio proxies with the 4 audio channel xavc l files with no problem. 

The workflow I'm trying to achieve is mobile edit in premiere rush with the Pxw fs5ii in camera proxies then open project in premiere and replace proxies with full resolution. 

This would enable me to start editing in rush mobile on my way home from job, eliminating having to have computer with me having to load project into rush desktop and having to have computer generate proxies 

Participating Frequently
September 29, 2019
I figured out if I delete the proxy files (720 in camera proxy 2 channel audio)in the cloud assets folder then open rush project in premiere files come up as offline then use link media to the full res(4k 4 channel audio) it works
David_Swinehart
Participating Frequently
June 6, 2020

I realize that this comment is from a while back, but are you able to pull the full files from the FS5 in to Rush on mobile? (or only the proxy files?) I'm stuck trying to do the same as you - edit on an iPad Pro on the road, the.n finish in Premiere Pro, but I've had no luck in getting Rush to recognize the XAVC files from the camera. 

Participant
July 11, 2017

I have the same issue. We are utilizing Sony Ci to upload the proxies created in camera directly to the cloud. In turn, we can then download immediately and start editing. But due to the Audio Channel issue, we can not Attach Full Rez files, but rather have to manually ReLink each clip.... Transcoding the Proxy files to a different Proxy format is an option, but seems like an unnecessary one...

Ryan A Bullock

Legend
July 11, 2017

seems like an unnecessary one.

Well, if it solves the issue...

R Neil Haugen
R Neil HaugenCorrect answer
Legend
March 10, 2017

Jim's comment is spot-on. I would not choose to use a long-GOP type CPU intensive codec like the H.264 for a proxy. An all i-frame like the Cineform Jim recommends, the Avid DNxHD/R which is actually newer designed and more optimized for 4k and such than ProRes, or ProRes would be the main choices I'd look at.

Neil

Everyone's mileage always varies ...
Legend
March 10, 2017

I recommend skipping the in-camera proxies and using PP generated Cineform proxies instead.