[Scott Erlinder]

Aaron,

The adapter gives you better glass but does not decrease depth of field like the “cine adapters” do- and being that the CCD chips are so small, you’ll have a hard time finding 16mm lenses that give you wide angle (The widest common lens for 16mm is a 5.9 Angineux).
Look at the lens/chip relationship like a cookie cutter- the smaller the chip, the less area of the lens is used, so what was wide angle in 16mm would be a “normal” lens in 1/3″ CCD

[Scott Erlinder]

OK, after some serious troubleshooting I found out that the JVC update 0109 seems to be the problem with the decks. I borrowed 3 other decks with the o1o8 update and they work fine.
Unfortunately, JVC does not post the 0108 update on their site now, so I can’t re-flash the firmware. I am waiting to hear back.

The camera information is more interesting and I should have not trusted the camera tech who told me they weren’t being seen either. 2 had bad firewire ports, 6 were working and 3 had other problems.
The tech staff apparently chose the cameras with existing problems or bad firwire ports as alternatives to the decks. They needed to be more methodical in keeping track of what they were doing, but as of now, I do NOT recommend updating the BR-HD50 to firmware 0109

[Scott Erlinder]

Thanks for the info folks-
I’ll be trying to do what Jerry suggested today.

Rafael- Regarding Pro Res-
We were able to do Pro Res capture for at least 8 months before this deck control issue came up. The best part of this was that we got matching timecode to the tape original versus the HDV capture which was always off from the tape.
While the file size was bigger, the timecode thing made a BIG difference in keeping track of large projects.

If it wasn’t supposed to to work, it definitely did for us!

Thanks to you both, and I’ll keep you updated on what I find.

Scott

[Scott Erlinder]

I found a little box to click on the multibridge settings- my bad! Look Harder! Duh!

[Scott Erlinder]

RGB (or Y pB pR) IS component, I know that.

If the output of the HDV deck is working through the loop through on the Multibridge, that tells me everything IS wired right. What ISN’T working is the output signal from the multibridge from FCP (which is DVI).

Scott

[Scott Erlinder]

Thanks for your help on this…I really appreciate it!

[Scott Erlinder]

Floh,

There must have been something that corrupted the FCP export on the files used in the M100 edit. Even though my partner was able to export his bit yesterday, the files now show the same issues as my problem.

We had the client re-exported the FCP stuff as an animation, not the M100 codec, and now everything is back to normal…Albeit, it has to be re-cut.

Thanks for your help though…I’m not really sure just what happened.

[Scott Erlinder]

Floh,

Thanks so much for your quick response!

Yes, it’s Media 100 8.2.1, it was a long day and fingers didn’t connect to brain.

I did a little more investigating and my co-worker had used the same footage (a few clips from the master clip that’s giving me fits) in another program using the same master clip- no problem, no rendering.

Another set of clips from the same extracted DVD media created in FCP (because of the need for more B-roll) does not exhibit the re-rendering issue in my timeline.

I think I’m going to noodle around with the original FCP quicktimes to see if I can fix the problem (different export settings than M100).

Luckily, this isn’t a long piece and I’ll just loose a day.
(Oh JOY!)

I’ll let you know what I find out.

[Scott Erlinder]

Thanks Steve and Floh!

I really appreciate your quick reply! Somehow the drivers did not install properly the first time I did it and since it has been so trouble free for so long, I forgot the methodology. It’s up and working again- except for the DV port..Durn it!

But thanks again guys!

[Scott Erlinder]

The board is fried according to Media 100 (at least as far as the DV component)

Thanks anyway!