[Kieran Matthew]

Hi Gregg,

Thanks for the info and the tip – I’m glad that someone else has had the same issue. I was beginning to think I was going mad, staring intently at noise patterns in the shadows! 😉

Thanks again

K

[Kieran Matthew]

Hi Thomas,

I don’t know what is causing your issues here, but as a work around, set your render settings to DV and try rendering a single title across the top of the whole piece to see if that helps.

I’m wondering if this is a mixed codec issue. Were all elements rendered/created in the same codec?

K

[Kieran Matthew]

Hi Doug,

If you are only seeing problems on one channel of the component input and it appears intermittent then I would suspect a physical problem in the BOB, multi-way or connectors. The BOB is just a plastic box with connectors soldered to the wires. These solder joints can and do fail (I’ve fixed two before) so looking there might be a start. Also check the connectors for bent pins etc.

[Doug Calhoun] “Options: DV600 (which comes and goes!!?!!?- bad omen) “

The DV600 is the daughter card that sits on the P6000 and handles the DV input. Check that it is seated right. If you’ve had no problems with firewire digitising then I wouldn’t worry too much.

[Doug Calhoun] “I’m told the hardware test only tests the card, is that correct? “

Yes. It doesn’t test inputs, just the onboard stuff etc.

[Doug Calhoun] “The hardware test fails at
“SUBSAMPLE WIDTH TEST (87):
Part 1: [1] 00000000 >> READ: 00E9E9E9” “

Does it fail at that point every time you run the test? I have had cards that fail the test every now and again, but have proved usable.

[Doug Calhoun] “Is a P6000 card a P6000 card, what do I need to know when getting another if I can get a used one to get by until this show is done? It’s in a Magma expansion chassis in a Dual 2.5 G5 with PCI-X.”

To use an expansion chassis you need a Lossless capable P6000 card (which you have) and I believe they have to be of a particular revision. Each card is linked to its software with the encryption code, so you can’t just slip another card in without knowing the encryption key tied to it. Effectively you are simply replacing your dead Media 100 with another one so you would also need the other card to be at the same software level as your system or you’ll lose functionality, and the same software version (i.e. 8.2) or your projects won’t open on it.

HTH

K

[Kieran Matthew]

Hi Doug,

First things first. Which software level (XS etc) are you using, which inputs are failing (is it just when you use component or do you lose the green channel with composite etc) and what does the Hardware test fail on?

[Doug Calhoun] “I can get the SDe upgrade for $1995 after trade in or $2995 for HD/SD but would need a new Intel machine and sales said my “experience may not be great” if I ran Producer on my G5. They recommended not testing it on the G5 while “i” is still on it. “

In the past I have run Producer on my “i” machine with no ill effects, but if you are fault finding on a critical machine then I can understand. Note also that the current version (the one that is available as a trial) is OSX 10.5 Leopard only so you wouldn’t be able to test them in the same OS space anyway.

[Doug Calhoun] “Anyone know if Producer will run smoothly on my Intel 2.16 GHz Intel Core Duo with 2 GB ram laptop”

This is a good place to try the producer trial, but remember the Leopard issue.

Another solution is to scour ebay etc for a PCI-X Kona LS or LH card that will fit in your G5. You should then be able to buy the Media 100 HD Suite software and it would (assuming the G5 has enough grunt) run OK with non-processor intensive codecs. Check that out with Media 100 sales first though!

That would leave you able to upgrade to a new CPU and Kona card when you are ready, taking your projects with you.

HTH

K

[Kieran Matthew]

Hi David,

The Nominal Reference selection in the audio window dictates where the little white line on the level meter goes and at what point the bar changes from green to yellow. It doesn’t alter the output levels unfortunately.

Still, good call. Thanks!

K

[Kieran Matthew]

Hi David,

[David Issko] “I have Media 100 V 12.1.3 HDe on an 8 core 3GHz MacPro with 4Gb RAM. “

Arrgh! I was hoping this could be an Intel/PPC thing. And since you are Down Under, I take it you are PAL too?

[David Issko] “Compressor – yes compressor, which works just fine “

Hey, I love Compressor! Much faster than BV, and I can’t tell the difference between them now.

Seriously though, thanks for the info.

K

[Kieran Matthew]

Hi John,

[john smith] ” Now I’ve taken the project back to the G5 and it won’t let me open some of the program files presumably because I made changes in 12.5 – arrgh!! silly me. “

Remember that you should have v11.5 copies of the program files in your Media 100 back-ups folder on the G5. Not that I’m suggesting you shouldn’t upgrade of course!

K

[Kieran Matthew]

Hi David,

Thanks for doing that, the information is useful.

Could you just let me know the specs of your Media 100 system – hardware and software?

Many thanks!

K

[Kieran Matthew]

Hi Tim,

Try rendering a title over the top of your program – this should make sure that the timeline is all in the same codec. Then conform as before.

K

[Kieran Matthew]

Hi David,

Thanks for the info.

Could you do a test for me? If you could place some tone on a program, set the levels to -18db, export out as AIFF, then open in a package that shows audio levels (Soundtrack Pro for instance). What level does the package report the file to be?

Many thanks in anticipation!

K