[Michael J c]

I’m going to try it out… I had the SD version too, but never really sue it… I’ll upgrade and hope it works tomorrow.

[Michael J c]

Just thowing this out there… Are there any newer M100HD/SW codecs on the system that *might* cause confusion?

[Michael J c]

I think I’ll be using the M100 to do any minor color correctiong (if necessary) since the sources have all already been color corrected (they’re a myriad of feature film).

I don’t think drive performance on the client’s end will be an issue since they’re just doing a software encode of the file… They won’t have to play it back realtime before it has been made into an mpeg-2 hd file.

We just finished another project in 10bit M100HD but went to tape (and then a color correction session outside) and our drives have handled it with no problems. But wow… uncompressed hd sure takes up a lot of space… especially if you’ve got a few effects to render.

[Michael J c]

Thanks for the real world info Michael…

On that note, does anyone know if 10bit would make a difference considering it will end up an mpeg 2 hd file?

also, do you imagine 10bit being A LOT more time on that export, or just a fraction more time?

[Michael J c]

That is probably the bug I’m running into Floh… I know it happens with speed ups, slow downs, reverses, and even stills.

Most of the time I’ll create a time effect, position it in the time line… and then have to render it later so I can create a file that I can send out… That’s when the issues happen. Now that I know about the extending issue, I’ll try to avoid it.

Does the same bug exist when shortening a clip (pre-render) in the timeline?

Also, any word on why you can not print a bin in “details” view?

[Michael J c]

WHOA!!! Now that’s what I get for doing my math at 3:45am. 🙁

OK… I now am expecting a 150gb file… not 1.5 tb… Much, much better and more manageable.

oops.

[Michael J c]

I tell you, I have TONS of issues with renders of any motion effects, reverses, stills etc. The M100 is a mess at keeping this stuff straight. It also gives you some really worthless .edl references on those clips.

I always save a version_X_rendered copy of the timeline, then I go through and check each effect. When there is a rendering error, I go back to the unrendered program and bring in the unrendered clip… and just try again. Eventually, doing the SAME thing over and over eventually get the stuff rendered right. Clips where in your bins which may have their audio or video extended from a past L-cut seems to cause problems more often. I don’t know why.

I’m running 10.1.4 and I just renedered a 15 minute timeline… There was only one error out of about 15 effects this time… not too bad compared to usual. 10.1.4 doesn’t solve the issue, that’s for sure.

[Michael J c]

That sounds better, but how are you doing that math?

The way I got to the 1.5tb number was that I exported a self-contained M100HD file from our 1080i timeline. It was exactly 10 seconds in length and size ended up being 1.58 GB.

Is my math wrong? Have you exported a long HD file as a self-contained movie, or are you talking about the size when media 100 captures something in real-time?

[Michael J c]

Well, yeah… and that’s what I’m considering. They aren’t sure what software they’re using yet. They’re trying to do it for as cheap as possible.

I’m not sure I want to get into the encoding business (just because I don’t know a lot of the technical details). I also don’t know what a fair rate for software encoding is and worry about time consuming troubleshooting and re-encoding.

But the software I linked to above is what I’m considering getting. I’d actually prefer a hardware encoder for HD mpeg encoding, but again… not sure if I want to get into that.

But I am considering trying to figure this one out because of the fact that I can use a reference file.

[Michael J c]

I just re-read your last post… I see that it is the re-linking that’s the issue. I’d bet that’s not going to happen automatically in any way.

But let us know if you figure something out.