Bjoern Adamski
Forum Replies Created
-
Hm, this doesn’t sound like a perfect workflow.
There is one killer feature with P2 media in FCP and Avid. P2 is the only format that retains untouched when imported by Avid. You need to destroy the original P2 CONTENTS folder structure when moving or copying the blank MXFs to the Avid media bin and this means FCP’s Log and Transfer as well as other tools and NLEs can’t read them anymore. However the MXFs themselves are not changed and this allows our MXF4QT solution to still read them including original timecode and full spanned clip support.
Panasonic P2 is the only format that can be used between Avid and FCP. This does not only allow a shared storage workflow but also establishes the first shared media access between FCP and Avid! It’s the first time that both NLEs can work on the same files.
In terms of XDCAM we have also full support for it natively in FCP, FC Server and other applications. The situation with Avid is that XDCAM is OP1a (video and audio in one file) and Avid will convert the media to OP-Atom (separate video and audio files). This will create Avid MXF files which contain the Avid specific MXF structure that is very different from other common MXF standards. However native P2 and native XDCAM work greatly together in FCP and when keeping the original MXFs you have formats that work for both Avid and FCP. Using MOVs wouldn’t work with your Avids anymore.
———————
Product Manager
MXF4mac
https://mxf4mac.com -
Create a timeline with a frame rate that FCP supports, export this one to XML and edit the frame rate values with an XML text editor. This is not officially supported of course but I developed this workflow to get 50p support long time before this was supported in FCP 6.0.2 by standard. I think this should also work with 12 fps.
Review page 13 and following of this PDF: https://www.aulich-adamski.de/download/720p50_FCP_5.x-6.0.1_en.pdf
This is part of the trick to change a 25 fps timeline to 50 fps. Should work also when changing the value to 12 fps.
The entry in line 9 is what you need to look at:
< timebase>25< /timebase>
Change the value 25 into 50 like this:
< timebase>50< /timebase>
You’ll have to do it again in line 14.
You’re done. Just don’t try and edit the timebase tag in line 34, as this would yield a defunct file. Changing the general frame rate and the timecode seems to be enough, no need to change it for the video characteristics.If you don’t get then I can try to create a 12 fps sequence for you. Just contact me through our website even if this is not related to MXF.
———————
Product Manager
MXF4mac
https://mxf4mac.com -
It’s not only about the best compression type, it’s about the most common standard. In many cases broadcasters require delivery in MXF OP1a D10/IMX.
MXF OP1a D10/IMX (SMPTE 386M) has nearly become a world-wide broadcast standard for SD. Quite all major broadcasters use it for archiving as it’s the most supported native and conversion-free SD format e.g. for use with ingest, archive and playout systems. The specifications and recommendations in the SMPTE 386M document are very strict and guarantee compatibility. Regarding this ProRes would be too exotic to interchange with broadcasters.
Best
Bjoern———————
Product Manager
MXF4mac
https://mxf4mac.com -
What is “good Long-GOP”?
Long-GOP performs well with low action but with very fast action it can end up in incalculable compression artefacts. The hardest test is filming a flurry of camera flashes.
———————
Product Manager
MXF4mac
https://mxf4mac.com -
Just contact us via the website and I put you on the notification list.
———————
Product Manager
MXF4mac
https://mxf4mac.com -
The theoretic access speed of a P2 card is 640 Mbit/s, the theoretic transfer speed of FireWire is 400 and 800 Mbit/s. In real life the transfer speed is much lower. The max transfer speed I ever measured was with a P2 drive via FW800 on a Mac Pro. I got 40 MB/s, so about 320 Mbit/s. I remember it was really strange as the transfer speed was decreased to 20 MB/s when the FireWire hub of my Cinema Display was connected. The FireWire port of the HVX200 is incredible slow.
———————
Product Manager
MXF4mac
https://mxf4mac.com -
Hi Scott,
we will release the 1.1 version of MXF4QT Export next week.
MXF4QT Export allows exporting to standard MXF OP1a D10/IMX (XDCAM compatible).
One new feature of v1.1 is NTSC support for all IMX variations (30, 40, 50 Mb/s).
You can use MXF4QT Import with P2 Flow CM to natively import your P2 footage to FCP just within seconds per P2 card. You can then use MXF4QT Export to export to standard OP1a MXF.
You can contact us for details.
Best
Bjoern———————
Product Manager
MXF4mac
https://mxf4mac.com -
You can use our “MXF4QT Import” solution in combination with “P2 Flow CM” to quickly and fully automated send the native P2 MXF media to FCP. There is no conversion or referencing done, you’re working on the pure and native MXF files.
https://www.youtube.com/watch?v=5MHXOWCgJ5w
You can then select the clips in the Browser and use the ‘Batch Export’ command to export all selected clips to a format of your choice. The workflow avoids to use Log and Transfer thus you save a lot of time and you don’t need the data to be duplicated.
Best
Bjoern———————
Product Manager
MXF4mac
https://mxf4mac.com -
Our P2 import helper application “P2 Flow CM” for “MXF4QT Import” maps all metadata from P2 to FCP. It’s not available in the free demo version but if you contact us through our website then we can send it to you for testing.
Please also review the “Fast P2 Workflow” PDF documentation on our website. You also find a MP4 movie showing the import process for FCP.
https://mxf4mac.com/documentation
———————
Product Manager
MXF4mac
https://mxf4mac.com -
This would only work if the video essence is compatible to a QuickTime video codec.
———————
Product Manager
MXF4mac
https://mxf4mac.com