[Kieran Matthew]

Have you tried “force rendering” from the Render… menu ?

[Kieran Matthew]

There’s a check box in the general settings pane of the disc that says something like “if 16:9 is used…”. By default in DSP3 this is set to “Force to Pan & Scan” which zooms the centre section of your 16:9 menu. Set it to “force to letterbox” and it should solve the menu issue.

[Kieran Matthew]

Hi,
When using Cleaner I found that reducing the number of frames between keyframes helps a lot in the freezing stakes. Infact when using the “Broadband Download” preset, a figure of 120 frames seems to produce freeze-free video that is of a useful quality for sending to clients. As for web-sized vids I have yet to discover the right-formula, I guess you just have to fiddle.

It seems that a lot of people are using Flip4mac for WMVs out of Media 100 these days. I haven’t used it, but apparently you can export direct from the timeline, and the results are good.

With Cleaner not being QT7 compatible, moving to another package may well soon be the only option.

[Kieran Matthew]

Hi

I have successfully networked two machines via a gigabit ethernet switch without problems or any special set-up, though both were running OSX. you do get issues over permissions etc, but these are managable.

Bearing in mind that Media 100 v8.2.2 projects won’t be openable in a 7.5, and various features in the 8.2.2 aren’t available in 7.5 (extra graphics tracks etc), unless you only want to push projects one way (from 7.5 to 8.2.2) in an off-line on-line config, I would advise bringing the two suites to the same OS/version before networking to save headaches in the workflow.

[Kieran Matthew]

Hi,

When you originally digitized, where you bringing it in one clip at a time, or did you digitize the whole tape in one go ?

I might be wrong here, but it is my understanding that the media100 only samples the timecode directly at the start and end points of a digitize, so any timecode breaks/jumps within the clip will only become apparent when you try to redigitize a part of it. There is the “xxx frames shorter/longer than expected” error that is an indicator, but that sometimes doesn’t kick in in my experience.

Unlike DV, when media100 is digitizing from its analogue inputs any break in the control track is digitized regardless (usually grey screen from a UVW1800) and assigned frame numbers. So if you have two takes side by side on a tape with a short gap between them, even if the timecodes are continuous in the recordings, you’ll get TC offsets when you redigitise. I am forever begging the camera folk to not review in camera for just this problem.

In my experience the only way to get around the problem is to digitize each clip individually, or log a clip the entire length of the tape, place logged clip on a programme, split into bits and the batch digitize the lot. Not elegant, but if there are TC problems, they’ll be isolated to the chunk they occured in.

[Kieran Matthew]

Thanks!

[Kieran Matthew]

Yep after a night of looped tests, a problem was finally flagged up.

[Kieran Matthew]

Good point! thanks for that. I’ll give it a go.

[Kieran Matthew]

Thanks Floh. My P6000 checks out when I run the hardware test – is this the sort of thing that the test might miss ?

[Kieran Matthew]

Thanks Ken, at least I know it’s not just me!