[Jay Ryscki]

The goofy part is that I have 30 other clips that I am modifying using the same BorisRed “project” specs and they all render out fine. All the footage came from the same M100 4×3 SD video program timeline. It is happening on just this one clip. Driving me batty.

[Jay Ryscki]

THis was a known issue in suite 1.6 and there was a workaround that could be done to settings in the application parameters to avoid the error. You had to log in using Terminal to make the change. THe new version 1.6.1 had the fix installed.

From Media 100-

Engineering says: If he is running Suite 1.6, have him open a Terminal
window and enter this command:

defaults write “com.Media100.Media100 Suite.override”
UseImportMovieCache -integer 0

That should solve your issue.
Also, V 1.6.1 is being posted within the next 2 days and contains a fix for
this issue.

[Jay Ryscki]

Hey Flo,
ClipWrap does not support the XDCam files in native format

[Jay Ryscki]

Hey Matt- Did you get my email?

[Jay Ryscki]

Thanks for all the feedback on this examination. While I have deep understanding and respect for the M100 environment, I struggle with the incomplete “solution” that the Suite 1.6 delivers. I have hung on to the SD M100 model a year longer than I thought I could get away with and continue to produce content on it.

But I am done with tape now. I am happy to compromise to produce the same results I deliver now, compelling content. Where I see the challenge is in the sometimes convoluted media management area. M100 has always let me excel in this area, the current tool falls short primarily with challenges in sorting out files for archive. When the digital model truly emulates the tape model for restoring footage, I’ll be there. In the meantime, this cobbled together approach to integration could use a champion. Calibrated Software has some good ideas, but they are still short on the execution.

If Suite 1.6 could overcome the XDCam conforming choke point, I could live with the results. What I have trouble justifying is sacrifice I make in creative editing energy, every time I need to put the computer geek hat on. M100 has let me leave that hat on the hook for years. I’d like to leave it there…

thanks again to all…

[Jay Ryscki]

This is what I also find to be true. I also suspect that the problem is with the way M100 and XDCam Tx play together, in this case they do not.

It is so much more streamlined as far as file size and sheer numbers of items in FCP. While I could live with the audio being split off as it has forever, I can’t justify the additional overhead of using two programs to do the job of one, and look at a 1.4GB file in M100 while the same file in FCP takes up 225MB. Not a very friendly equation. Unless there is some way I am missing to get the final M100 file sizes down coming out of XDCam Tx, then it just does not compute.

[Jay Ryscki]

It appears that my system(8core-2.8-12gbRAM) is hanging on clips over a minute long. The other thing going on is that it is writing two video movies for each clip imported.

One is a smaller file: Apple XDCAM EX 1080p30 (35 Mb/s VBR), 1920 x 1080 (1888 x 1062), Millions
16-bit Integer (Big Endian), Mono, 48.000 kHz
16-bit Integer (Big Endian), Mono, 48.000 kHz
117MB

Other is Big file: Apple ProRes 422 (HQ), 1920 x 1080, Millions
717MB

Not sure where these files work within the environment, but I do know that FCP has 1 .MOV file related to each XDCAM source file. When I import the same clip as a file from FCP I get the video and two audio .mov files in the M100 media folder.

[Jay Ryscki]

I did the FCP>M100 workaround earlier and I know it works. Problem is that it adds time and reduces drive space for a process that should be one step. I work with the calibrated software plugin in FCP which eliminates the need to recompress the source XDCAM BPAV data. I have to recompress at the 422 codec to see the files to import them into M100. While this works, it is what I call janky at best, and broken at worst.

So, I went back and retested the direct from XDCAM Transfer to M100 after all this and it did import a small batch of short clips with no errors ( 5clips all less than a minute). Now I will clear all the test media, reimport the source, and see if it chokes.

[Jay Ryscki]

What OS version are you using? SLep 10.6.3

Which version of the XDCam tools? Vers 2.12

If the XDCam files are converted, can you import the converted files into Media 100? Need to test this, but if this works, not the best scenario.

What framesize and framerate are your files in? 1920×1080 at 30P

This definitely should not happen. You’re right about that…

[Jay Ryscki]

Just went from firmware 1.12 > 1.20 using the application from Sony. This is my set up:

Sony EX-1
MacPro running OSX 10.6.3

Nuances:
Open the app from Sony first. No other app running.
plug in the USB in the proper port on the EX with it is turned off.
Turn on the camera, if it looks like it is operating normally, you don’t have a connection
IF it asked you to connect via USB, you don’t have a connection
Step through the menu items in the Sony app. Note that you will need to turn the EX on and off about half way through the process.
Red tally light should begin blinking at Restart queue.
Finish the app.
Shut down the EX and disconnect the USB
Turn on the camera and check your firmware by pushing Menu/Select/Cancel and then scrolling down to the “IF” menu.

cheers,
jay