![perian xdcam component perian xdcam component](https://perian.org/img/logo_niceplayer.png)
This worked very well as long as the deck supported baseband playback of the frame rate. This had to be done prior to decomposing but the sequence could be decomposed and batch digitized. My suggestion was to add a custom view with disk label and tape name heading modifying the clips so the tape name matched the disk label. The other option was to modify the clips used adding a tape name. This would often be faster and Media Composer can easily relink a sequence to the highest quality.
![perian xdcam component perian xdcam component](https://cdn.shopify.com/s/files/1/0240/0498/4912/products/pmw-400-1_2_1024x1024.jpg)
The first was to import the entire clip used and not batch import just what was used with trim handles. There are a number of ways to work around this. Still with 3.0 and earlier if the majority of the master the clips were short, clearly possible and common with XDCAM optical, the batch import process worked very well.
![perian xdcam component perian xdcam component](https://newprovideo.com/user_files/08-02-2013/ex3_back_1360345357.jpg)
![perian xdcam component perian xdcam component](https://cdn.shopify.com/s/files/1/0240/0498/4912/products/pxw-fx9-2_1024x1024.jpg)
Proxies can now import 40 - 50x real-time. Its this process that has been resolved starting with MC 3.5 and the import time has been dramatically improved over all. Have a 20 min clip that 10 seconds was used 50 times, that 20 min clip would have to be read 50 times. Let me try to explain what was happening with 3.0 and earlier importing a 20 min high res clip would be faster than real-time and the proxy would be much faster than real-time nothing to complain about.īut when a number of short pieces were used from a long master clip, the entire master clip would have to be read each time the clip was used. This has always worked since the feature was introduced. I'm not sure what you mean by not being able to import parts of clips. I will do some tests myself when my projects finish at the end of January but for now have you ever tested this batch digitize work-flow yourself?
Perian xdcam component Patch#
That's why my XDCAM's are still connected through video and rs422.īut if in the past MC3.5 versions this has been fixed and maybe if there will also be some kind of ftp plug-in for AMA and XDCAM then upgrading all systems to MC 4 (or 5 when the patch dust has settled) becomes very attractive. Back then when we bought our first 3.x systems I extensively tested with the XDCAM work-flow and became aware of MC not being able to import parts of clips during batch importing. While I have several MC 3.5, 4 and 5 dongles, most of my systems are running MC3.1.3 due too system compatibility between clients on unity. P2 Clips to Bin reads the Meta Data in the MXF header where there isn't near as much. AMA will index a P2 card faster than the P2 Clips to Bin command and now reads the Meta Data in the XML file. Overall the improvement is frankly fantastic.Īs far as P2 goes. On top of that some of the work done for AMA in 3.5 dramatically improved the read times to the point that the much faster decks are now the bottle neck. And they released U1 and the HD decks that have much faster read times vs the older decks. It wasn't the actual importing of the media that took so long, it was the reading of the Meta Data in the MXF file that took a long time.Īlmost at the exact same time Sony changed the way the MXF files are written to the disk with the XDCAM HD 50Mb that improved the ability to read the Meta Data in MXF files. Prior to SN/MC 3.5 batch importing (The Non-AMA work flow) of long XDCAM clips would take a long time. This is not available with other imported media but a similar end result is achieved using AMA to Link to Files. Specific work was done for XDCAM disks to allow for the import of the proxy clips and the batch import of the high res clips only importing what was used in the sequence.