[Doug Calhoun]

Andy, thank you very much.

[Doug Calhoun]

Thanks Floh, I’ll see if I can set up an overlay in Compressor. I appreciate your input.

[Doug Calhoun]

In the deck controls, under Setup menu-> video control-> STD/NON-STD, I switched to “Forced Non-Std”. It now seems to have settled the machine into a cooperative editor. The deck had an STD issue apparently….;)

I’ll keep you posted, now gotta find an old install disc and get my leaders/trailers back….

[Doug Calhoun]

I will do so and reply. Thanks all for your help so far, look forward to getting it running the way it should and editing.

[Doug Calhoun]

[Floh]Hmmm, what Yellow cable? You have to disconnect Y (Luminance) from the deck input or you are creating a video feedback, which will cause the jumps. This is completely normal and I think it would also have happened with Media 100 i. There is not much you can do about it except e.g. getting a video patchbay, which makes disconnecting inputs easier.

Yes Floh, luminance. I thought I’d need to run a ref of some kind for sync but AJA and M100 both said it wasn’t necessary and that it was a deck setting relating to PB or EE. It happened with M100i but I ran composite to the ref and it was fine. Neither Genlock or Ref Loop out of the AJA Breakout Box to Ref satisfies the sync issue. I was told by AJA that the Genlock setting in the AJA Control Panel should remain in Freerun while digitizing…the fact that when M100 switches it to Video in is not correct but I’ve no idea? Will a blackburst generator solve the issue and if so, any recommendations? I always worked around with the i and am not sure how to resolve this.

[Doug Calhoun] “The image quality is substandard both in DV acquire and component. I’ve digitized to Media100i, DVCPro50 and DV Codec with miserable results. I was advised to get the AppleProRez422 codec from someone with FinalCut…..anyone have it? I was shocked to hear not to expect the image quality of my old 8.2.3a M100i system due to the fact that the P6000 was a dedicated video board.”

[Floh]This is simply wrong. The codec of the P6000 board was a hardware device, since CPUs in these days were not fast enough to compress or decompress PAL/NTSC video. It has been reworked in Software, so that clips digitized into Media 100 i codec should look exactly the same, regardless if they are digitized on a P6000 board or an Aja board. If you are seeing issues this is not something related to a codec. Both DV and Media 100 i should look good. How are you monitoring your signal? How are you getting the signal into the system? Compoenent? FireWire? What kind of format (PAL, NTSC)? It sounds like there still is something very fundamentally wrong with your system. You can expect the video quality to be much better than with Media 100 i.

The signal is NTSC SD component in 525i 29.97 (601 4:3) brought in Media100i Codec as well as DV, DVCPro(25mb/s), DVCPro50 (50mb/s) and again over Firewire again minus the Media100i codec. The signal is monitored out composite from the deck to the monitor. These are the only codecs not grayed out that I can select. The video flutters a bit during camera tilt and is not clean. I’d agree, something is fundamentally wrong.

[Floh]If you bought the system recently you should have free techsupport from Media 100. Try giving them a call, since they are very helpful and they should be able to talk you through your problems. Or post some more details about your setup (cabling for input and output, where you are seeing the problems,…) and I try to get back to you with some answers.

I’m editing on a MacPro Nehalem 2X 2.66 Quad Core Xeon with 8 GB Ram, AJA drivers v 6.0.3. The only things installed are Media 100 and AJA Drivers. Been on and off the phone with M100 today. They stated my settings are correct, to try the AppleProRez 422 codec and to not expect the image quality to be as high as with the i system! I’m dazed and confused….

[Doug Calhoun]

Thanks Floh,

I’ll likely just pick up a new cable so I don’t have to mess with it, this one is 9 pin to serial with a Keyspan serial to USB adapter.

Doug

[Doug Calhoun]

Matt,

I’m installing and HDe system now. If you have a link or a driver #, I’d much appreciate it.

Doug

[Doug Calhoun]

Floh,

the Graid 2 is connected directly to the G5 via a FW 800 cable and is formatted exactly as delivered from GTech. The M100 P6000 is in the expansion chassis, the SCSI card is in the Mac, not the expansion chassis.

I’m not rendering directly to a M100 codec, I’m rendering to Animation codec and importing via M100 and it’s rendering it in to it’s codec.

All other footage digitized through the card plays back fine from the drive. I’ve digitized 40 secs of 300 kb, created a graphic, effected to another (dissolves/wipes etc.) clip and back and added 4 tracks of audio and it plays and scrubs across it fine.

It seems to only be the clips I import into M100 that are from AE and only on this drive. My lacie FW800 drives operate flawlessly.

Does the drive need to be formatted as a Raid 0 since it has two internal drives that total 1.8TB? Gtech says no….

The same clip imported onto a Lacie Drive works perfectly….

[Doug Calhoun]

Thanks Kieran,

In response to your questions:

Kieran wrote: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?

I’m running v8.2.3a using OSX 10.3.9 with hardware test v8.2.2

The specs on the card are as follows:
System Rev: 802
Hardware Rev: 32
SW Comp Rev: 63-02
Component Rev: 14
Options: DV600 (which comes and goes!!?!!?- bad omen)
Card Type: P6000 (LL)
ISP Rev: 802
FPGA Rev: 801
Diags Rev: 10-31-2003
FCode Rev: 03

It occurs intermittently during component in, I’ve digitized a few clips composite with no issue so far………I’ve switched the cables around to test them as well. In addition sometimes it appears to be fine then after digitizing and playing out, the color is off- redigitize it and it’s fine. That’s when I did the hardware test and got concerned it wasn’t something simple……

I’m told the hardware test only tests the card, is that correct?

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

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. I’d have to get an older AJA card and would likely step into an Intel machine and upgrade to HDe if the pre-Leopard Producer demo didn’t work on my G5…..

[Doug Calhoun]

Thanks. Is there a workaround?