Bjoern Adamski
Forum Replies Created
-
You can import AVCHD with Log & Transfer in FCP as ProRes, then place into an AVC-Intra timeline and export to P2. You would need two products from us, AVC-Intra QT and MXF Export Suite that includes the P2 exporter.
Best
Bjoern———————
Product Manager
MXF4mac
https://mxf4mac.com -
Yes, we are aware about various solutions and upcoming new ones. Feel free to contact us via mxf4mac.com/contact/
———————
Product Manager
MXF4mac
https://mxf4mac.com -
-
Check your Omneon firmware and configuration. Older versions created MOV files with wrong codec description (MPEG instead IMX).
Our company might be able to repair them.
———————
Product Manager
MXF4mac
https://mxf4mac.com -
Hi,
P2 Flow is a workflow application, you can use the pure MXFs or you can use it with Log and Transfer. You can decide to work on the original MXFs with or without backups, you can even work straight on the P2 card. P2 Flow provides powerful workflow options for FC Studio that no other P2 aware NLE system offers. Time it can save, workflows it can improve and it is worth for those who require it. Many do, many don’t. All is good.
Why don’t you discuss in our beta forum btw.? 😉
Bjoern
———————
Product Manager
MXF4mac
https://mxf4mac.com -
Check this to get video and audio imported as merged clips fully automated:
https://mxf4mac.com/atomic-fusion
———————
Product Manager
MXF4mac
https://mxf4mac.com -
What’s the input format? With MXF wrapped content you can save lots of time in news environments.
For example we can allow access to growing MXF files from Omneon live recordings.
On the export we write MXF “left-to-right” which allows the Omneon system to access the MXF file while it’s being exported from FCP (transfer-while-export, playout-while-exort).
———————
Product Manager
MXF4mac
https://mxf4mac.com -
You’re correct, it’s not stored in the standard P2 metadata.
———————
Product Manager
MXF4mac
https://mxf4mac.com -
Maybe consider that
1. Renaming in FCP costs you a lot of time + the conversion time. The names are saved in the FCP project file, you need FCP to recover the renamed files.
2. Setting custom P2 UserClipNames cost also a lot of time but this information can be used for ever and with all P2 compatible NLEs. You’re not bounded to FCP.
3. Using native MXFs in FCP allows to save this project as XML and then the XML project information is available for other workflows, e.g. you could load it into Premiere Pro on a PC that would also read the native MXFs. Same applies with systems from Autodesk which run under Linux. With MOVs you’re bounded to the Mac and FCS.
———————
Product Manager
MXF4mac
https://mxf4mac.com -
Clips names can’t be set, it’s the User Clip Name that can show up in FCP instead of the real file name.
Don’t change the clip names, this will corrupt your P2 file structure.
———————
Product Manager
MXF4mac
https://mxf4mac.com