I recently purchased the Canon XF705, but when I try to load the H.265 files I get nothing. Does anyone know what I can do? I've tried contacting Magix Support, but no one has answered me back.
Please give here the MediaInfo of such a file or show a short one on a cloudservice where we can download and also try.
here is the link to a clip in my dropbox, I appreciate ANY help you can provide!!!!..... Thank You! https://www.dropbox.com/sh/q5m7cxgneq5z5h3/AAAh-d3FdhouZ2bFv2FajR18a?dl=0
Likely this is an incompatible flavour of MXF. You might be able to re-wrap to a compatible version, or you will need to transcode.
Do a forum search on MXF for more details.
Thanks.
I downloaded the file and cannot import it in My Vegasversions, VCL (the Windows app symbol it gets) cannot play it and all other players or decoders on my system can load the file. All said a "unknown codec"
This is what the MediaInfo says:
"XF705\A003C002H1901045W_CANON.MXF
Format : MXF
Format version : 1.3
Format profile : OP-1a
Format settings : Closed / Complete
File size : 301 MiB
Duration : 16s 16 ms
Overall bit rate : 157 Mb/s
Encoded date : 2019-01-04 12:01:59.000
Writing application : CANON XF705 1.00
Video
ID : 2
Format : 0E15000402100001-0E15000500013000
Format settings, wrapping mode : Frame
Codec ID : 0E15000402100001-0E15000500013000
Duration : 16s 16 ms
Bit rate : 153 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate : 59,940 (60000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:2
Bit depth : 10 bits
Scan type : Progressief
Bits/(Pixel*Frame) : 0.307
Stream size : 292 MiB (97%)
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Audio #1
ID : 3
Format : PCM
Format settings : Little
Format settings, wrapping mode : Frame (AES)
Codec ID : 0D01030102060300
Duration : 16s 16 ms
Bit rate mode : Constant
Bit rate : 1 152 kb/s
Channel(s) : 1 kanaal
Sampling rate : 48,0 kHz
Frame rate : 59,940 FPS (800.8 SPF)
Bit depth : 24 bits
Stream size : 2,20 MiB (1%)
Locked : Yes
Audio #2
ID : 4
Format : PCM
Format settings : Little
Format settings, wrapping mode : Frame (AES)
Codec ID : 0D01030102060300
Duration : 16s 16 ms
Bit rate mode : Constant
Bit rate : 1 152 kb/s
Channel(s) : 1 kanaal
Sampling rate : 48,0 kHz
Frame rate : 59,940 FPS (800.8 SPF)
Bit depth : 24 bits
Stream size : 2,20 MiB (1%)
Locked : Yes
Audio #3
ID : 5
Format : PCM
Format settings : Little
Format settings, wrapping mode : Frame (AES)
Codec ID : 0D01030102060300
Duration : 16s 16 ms
Bit rate mode : Constant
Bit rate : 1 152 kb/s
Channel(s) : 1 kanaal
Sampling rate : 48,0 kHz
Frame rate : 59,940 FPS (800.8 SPF)
Bit depth : 24 bits
Stream size : 2,20 MiB (1%)
Locked : Yes
Audio #4
ID : 6
Format : PCM
Format settings : Little
Format settings, wrapping mode : Frame (AES)
Codec ID : 0D01030102060300
Duration : 16s 16 ms
Bit rate mode : Constant
Bit rate : 1 152 kb/s
Channel(s) : 1 kanaal
Sampling rate : 48,0 kHz
Frame rate : 59,940 FPS (800.8 SPF)
Bit depth : 24 bits
Stream size : 2,20 MiB (1%)
Locked : Yes
Other #1
ID : 1-Material
Type : Time code
Format : MXF TC
Time code of first frame : 00:02:15;06
Time code settings : Material Package
Time code, striped : Ja
Other #2
ID : 1-Source
Type : Time code
Format : MXF TC
Time code of first frame : 00:02:15;06
Time code settings : Source Package
Time code, striped : Ja
Other #3
Type : Time code
Format : SMPTE TC
Muxing mode : SDTI
Time code of first frame : 00:02:15;06"
Sorry I cannot help you other than to write: try other settings on the cam to export mp4
This special flavor of H.265 MXF is a Canon proprietary format which afaik currently no NLE on the market is able to read natively (maybe except Edius/Resolve?). It seems not even FFmpeg can decode this one. There is a MainConcept decoder SDK available.
I'm sure your camera came with some kind of conversion utility. Start there
Do you think this work https://www.dropbox.com/sh/q5m7cxgneq5z5h3/AAAh-d3FdhouZ2bFv2FajR18a?dl=0 for file XMF, VLC?
I ordered that trial software, but after trying to install(and maybe use) it, I stopped after more than 1 hour trying while i did not succeed to install.
@Carlos-Marines, I think you talk about Movie Studio but this is the Vegas Pro section. Movie Studio doesn't support MXF except for XAVC. Also, the file you linked above is the same kind of video as Steven linked at the beginning of this discussion. So it seems like those who need to edit Canon XF705 clips either need to wait for a broader system support of this Canon proprietary flavor of MXF or you need to transcode the clips before editing.
here is the link to a clip in my dropbox, I appreciate ANY help you can provide!!!!..... Thank You! https://www.dropbox.com/sh/q5m7cxgneq5z5h3/AAAh-d3FdhouZ2bFv2FajR18a?dl=0
Was not able to import with v16 either but was able to convert it with a recent ffmpeg to h264/mp4. Nice cat. :)
I've got the XF300 and I always use Canon's S/W to extract the MXF content. Have you tried it?
A while back, I loaded a MXF OP-1a rendered in Resolve 15, into Vegas using the Happy Otter Scripts, Import Assist function, you may want to give it a try.
https://www.vegascreativesoftware.info/us/forum/happy-otter-scripts-for-vegas-pro--113922/?page=1
Been playing with ffmpeg (4.1.1.win64-static) on OP's dropbox mxf 4k file and the mp4 conversion seems to be fairly brisk but converts the audio (not sure if it's treating channels 1 & 2 as stereo or what) from 24-bit pcm to aac. Also noted the mp4 loads, reports the resolution and frame rate correctly, but won't display in Vegas14. Works fine in Vegas 16. Here's the ffmpeg command I used in a cmd file to convert the xf705 mxf to mp4 and get a file just slightly larger than the original:
ffmpeg -i %1.mxf -c:v libx264 -preset ultrafast -crf 15 %1_new.mp4
Also made a ProRes mov file kind of like one in a C-200 sample I found online and it worked on both Vegas14 and 16. But the encoding was a slight bit slower. Again I was aiming for an output file slightly larger than the input. Note that I used the the audio codec 'copy' command and it seems to have grabbed the 1st audio stream and put it into the mov as a mono 24-bit pcm stream. If I had that camera I'd probably want to see if there were a camera setting to make it record stereo audio and maybe leave out the 3 timecode streams [edit: NO GO found in the online manual]. Anyway, here's my cmd file line to convert to ProRes Mov:
ffmpeg -i %1.mxf -c:v prores_ks -profile:v 4 -pix_fmt yuva444p10le -qscale:v 25 -c:a copy %1_new.mov
One thing I noticed is that the C-200 sample I found seemed to be about 10x larger than xf705 mxf file for similar runtimes and 4k resolutions. I'm guessing the C-200 gets closer to lossless compression.
Interesting that it has 10 bit but still shoots in rec709 color space. If I was going to spend the extra bits on 10bit, I'd also set color space to rec2020 or similar so I could grade that video into HDR later if I wanted to.
"I'd also set color space to rec2020 or similar so I could grade that video into HDR later if I wanted to."
I thought my TV broke when this aired the other night.
Some groups in the world want to go in the opposite direction.
LOL... Something tells me making their commercial look terrible wasn't the best way to sell their agenda. It also ignores energy savings by using different types of display tech.
The next build of HappyOtterScripts will support import of XF705 footage. Here is a short demo.
In addition to x264-avc, it also supports lossless to MagicYUV or UtVideo. The 4 audio channels are imported as two stereo tracks.
Wow, the script demo above looks pretty slick. Undaunted, I've been playing a bit more with ffmpeg. I think I've made a marginal improvement on my results. Been trying to come up with an ffmpeg cmd command line that will render a single output file having a video stream and a stereo audio stream suitable for processing a directory full of xf705 mxf files so I can pull them onto a Vegas Pro timeline as a group like I do with output from my xf305 camera. Here's what I got for mp4 outputs:
ffmpeg -i %1.mxf -c:v libx264 -preset ultrafast -crf 15 -c:a aac -b:a 512k -filter_complex "[0:1][0:2]join=inputs=2:channel_layout=stereo[aac]" -map 0:v:0 -map "[aac]" -write_tmcd 0 %1_new.mp4
The audio output stream is 512k stereo aac joined from the first 2 audio pcm input streams. It's also pretty easy to adjust to mix the front and rear streams into the stereo output but I would probably want to keep the rears separate till post. It also tosses the tmcd time-code stream. Takes about 86 secs to run on my laptop. Here's pretty much the same thing for ProRes mov output:
ffmpeg -i %1.mxf -c:v:0 prores_ks -profile:v:0 4 -pix_fmt yuva444p10le -qscale:v:0 25 -c:a pcm_s24le -filter_complex "[0:1][0:2]amerge=inputs=2[wav24s]" -map 0:v:0 -map "[wav24s]" -write_tmcd 0 %1_new.mov
The output mov stereo audio stream is 24-bit pcm. Processing time on my laptop using Steven-Porchet's cat sample is 126 secs. Now I think I'm ready to start saving up for that new camera.
Just put the mp4 converter script into a batch file and tried it out on a directory containing a shoot I did with my xf305 of a 1 hour concert and it chugged away on the 8 mxf's (~2gig each) for 16 minutes total on my laptop. Which I do not normally use for video processing because it's not all that fast. But these are 1080p files, not 4K, and I just wanted to get a rough idea of the practicality. If anyone's interested, here's the cmd file:
@echo off
for %%f in ("*.mxf") do (
ffmpeg -i %%f -c:v libx264 -preset ultrafast -crf 22 -c:a aac -b:a 512k -filter_complex "[0:1][0:2]join=inputs=2:channel_layout=stereo[aac]" -map 0:v:0 -map "[aac]" -write_tmcd 0 %%~nf.mp4
:pause
)
Kind of crude but simple to use. Just copy it into the directory where the mxf's are, give it a name ending with ".cmd", and double click on it. It'll create a bunch of mp4 matching the mxf's it finds in that same directory. I adjusted the crf up to 22 to bring the mp4's into a similar size range as the mxf's... smaller crf's make larger mp4s. It assumes ffmpeg is somewhere in your search path. It if's not, just type the path into the cmd. If you want to see the ffmpeg output after each iteration, remove the colon before the 'pause'.