[Gene Colburn — email address bounces notices]

Bob
If you use CCU on a hub each camera shows up as a seperate addressable cam. At least that is how it was explained to me at NAB. Kind of like sharing printers over USB. Also do you have three of these, and what is your impression of this camera. We are looking to buy at least two, possibly three. I have only seen them at NAB, and still a little unsure if I want to jump in now or wait for a something from Sony that competes.

[Gene Colburn — email address bounces notices]

Hi Michael
Just breifly reading your thread here, as I am getting ready to go out of town for a few and my brain is fuzzy. Your analysis however points to some codec rounding taking place. If its any reassurance though, I know there lots of users using BM with Digibeta to Beta work taking place on a regular basis. If there were inherent problems with the cards, we would be seeing large number of similiar posts. I can’t help but wonder though. I have seen SDI devices with some gear pass setup values, that are totally stripped when encoded by the codecs. Looking at the numbers, I see some offsets that appear to be that. If that is in fact what is happening the channel paths can be truncated by the codec. Almost like cliping, which can account for varying path differences.

[Gene Colburn — email address bounces notices]

[miles and Jules] “(seems like the pci-e chipset doesnt know how to use the 4lane pci-e and the 16x graphics at the same time.”

That is exactly the problem. As far as error message, no I did not get that specific one. The drivers registered correctly in device manager, but display properties did not show it as an active device.

[Gene Colburn — email address bounces notices]

Hi Oliver
I am glad you guys were able to get it working. All my posts were based on A variety of A8n (A8N, A8NE, A8N32, and A8n32 deluxe) motherboards, up until March of this year. You may well have a later rev board that works. But I can tell you emphatically there are people out there that will not get theirs working with MBe, and an Adobe certified PCIe graphics card. We tried every iteration of BIOS, drivers, Nvidia updates, XP, XP64, you name it. These boards rock with Adobe, and a PCIe card only. I did not profess to be the final authority on this issue however, but merely to let others know there may be some rocks in their path if they go down it.

Miles and Julles maybe there is hope for you guys with this board. I would certainly like someone from BM to clear this up for once and for all though. I have not found any posts where they have done so. It would be great to see an exact profile of a working system using the 32d. Or even Olivers for that matter.

Best Regards
Gene

[Gene Colburn — email address bounces notices]

Hi Michael.
My continued interest, is in part because we are beginning to build systems with BM prodcuts(although not yet as an authorized dealer), so I am really interested in related posts on this forum. That aside, your problem does appear to suspect BM, which could be some component that is just enough out of tolerance to exhibit the shift. For both of your monitors (LCD and CRT) to exhibit it the same does leave a question. I do question why the necessity to completely remove drivers, and codecs etc. They should be totaly transparent to a native digital import, transfer, or export, and would have little to do with the component output which this thread was originally based on. There are however codec footprints that are not totally transparent. Is that a possibility you are concluding, (BM in particular) or is it still only the component output of the BM? I would truly like to know what you find in your effort to fix.

[michael d] “By the way, I find your comments and Bob Zelin

[Gene Colburn — email address bounces notices]

Hi
Everyone will tell you running XP64 is a little premature as not all hardware and software is debugged to run together yet. That aside, Adobe Apps run fine in XP64 in 32 bit emulation mode, including the AVI and M2v export. No difference. That does not mean it does so with all hardware. Also you can set PPro 2 export settings to be very much the same as Encore 1.5 However, for your exports to just suddenly quit tells me that if your computer is relatively new, you may need to get it back to the vendor it was purchased from. I wish I could be more help, but I do not have any better answer.

[Gene Colburn — email address bounces notices]

OK
Why not try to create a new sequence. Razor ins and outs on your existing multicam sequence, copy,… undo razors,… and paste to a new nested sequence. Work with that sequence doing this where ever needed to build a new timeline, using the elements you need. I am at home, and not in front of a multicam project, and haven’t tried to do this, but I somehow feel confident that it works.

If not, I’m not sure what to tell you. I would rather offer no comment than to give you bum suggestion However another option is skip the multicam feature, and place your sync’d cameras on progressive tracks…2,3,4,5 razor, or double razor,trim, cut, dissolve, copy, move etc. as needed. This is how we used to use the timeline before the Multicam feature was released. I have one 4 camera show edited with multicam this year, and was extremely pleased with how it works. We do two to three multicam shows a year. As time goes on, I may run into a brick wall, just as you have.

[Gene Colburn — email address bounces notices]

Hi Miles

I typically do not make exact component recomendations, because of the boomerang effect they invaribly have.
My reference to the K8WE is the first time I have done so. My prior posts were to discourage forum users from going with the SLI boards. I just checked the decklink site, and they are still showing the A8N-SLI32 deluxe as an acceptible board. It performs well in every way including the SATA raid as you have observed (which by the way performs better than the K8WE). These questions may be better addressed by BM than by me, as they are still showing this combo as working. They may have an exact set of peripherials that work. I just know we put a lot of money into it and other SLI boards trying to use the AMD 4800 when we discovered that all boards with this chipset suffer from the same inability to delegate resources to other peripherials on the bus, including PCI devices, with other hardware including PCI graphic cards. I wish I had a better answer for you.

[Gene Colburn — email address bounces notices]

Michael
I would be interested in knowing how the footage looks if you export back to Digibeta using SDI and then looking again at the digibeta component out on the JVC. You may have already tried it and I did not gleen that. It is possible that MBe is the culprit. But it could also be something as simple as a leaky cap in the input circuit of the JVC that is throwing off DC offset bias of the decklink. The Digibeta may be a little more forgiving of this by the nature of its output circuitry design. I am trying to keep this as simple as possible, but all component analog paths are calibrated with no measurable DC on the path. There are usually trim pots on some gear to set this. In the MBe it could also be that some production component is slightly off in value that has the same effect.

The bottom line is that a very slight DC offset on any channel is observable in the blacks, and can throw the calibration of many monitors off. I know that it’s annoying, but you can look at any two CRT monitors, fed by the same signal, and they will never absolutely look identical for the same reasons. It just may be one of those situations where you need to bring a service tech with adequate test equipment to sort this out.

[Gene Colburn — email address bounces notices]

[Lance Bachelder] “The Cineform codecs are excellent and I’m can’t wait for Mac/FCP support myself.”

Lance I talked to Cineform reps at NAB. I did not get this would be forthcoming any time soon. Has this changed?