[David Eells]

All I know is at the time, the techs said “Here you go-everything’s working” and then hightailed it. And of course, the system wasn’t working.

Because they were determined to make the SDI work, they came back and did it again. This time, I could ingest and lay to the timeline, but I could tell by looking that I wasn’t getting the full picture – the item properties checked out, but the picture was expanded 10-20% and washed out. Any idea what would cause that?

I get the logic of capturing to 10-bit, but since the project wasn’t begun that way, and it’s a high-pressure situation, I’m stuck with what I’ve got.

[David Eells]

Hey Jeremy

So I see you’ve wandered back to this thread, and inadvertently addressed another question I had.

So I’m the second editor on this fairly large project that was started out of house. My instructions were to capture a bunch of new footage, matching the original project AT ALL COSTS. Now the in-house techs are all Avid guys and have connected to the 1200 deck using SDI. Result-footage doesn’t match (bigger data rates, footage won’t play on timeline without render). So I connect using FireWire, and everything works.

So when you capture using SDI, as opposed to FireWire, is there a conversion going on? Hence the higher data rate?

Meanwhile, the lead editor and the techs are all convinced that SDI is a better way to go, but I haven’t found any reason to think so. Walter Biscardi weighted in on an earlier thread, and he can’t see any quality difference between FireWire and SDI when ingesting.

[David Eells]

As you can tell from my thread, I may not be the best source of information for this format. I suggest you start a new post – you may get more attention that way.

Good luck!

[David Eells]

Thanks for an enjoyable evening. I’ll make it throouhg this project somehow. See you around the pasture.

[David Eells]

Maybe so, but the footage and the timeline play perfectly happy together. I’m inclined to think it’s a side-effect of the long timeline.

[David Eells]

The different size phenomenon is intermittent – it just started up. On the new titles I’m making now, the frame size field is blank. Earlier it was 960×720, but I still had the render problem.

Capture/Render disk has 355 GB available.

[David Eells]

I’d be shot if I changed anything (high pressure situation, and as I said, I’m the assistant here), but here are the settings:
Sequence Preset: DVCPRO HD – 720p24
Capture Preset: DVCPRO HD – 720p24 48kz
Device Control Preset: DVCPRO HD FireWire
Playback Output Video: Blackmagic HDTV 720p 59.94Hz – 8 bit (1280 x720)
Playback Output Audio: DeckLink Audio
ETT and PTV same as Playback

Storage is 2 x 1TB, 1 x 500 GB – both G-TECH drives.

[David Eells]

It’s a 2×2.66 dual core Xeon running 10.4.9 with 3 GB. It’s not my rig.

Just now I went to make a new title – looks perfectly normal in the viewer, but when I lay it into the timeline, and then toggle between the viewer and the canvas, the video looks bigger in the line monitor when I toggle to the viewer, and normal when I toggle to the canvas.

And yes it’s a long timeline – 2 hours. I’m the assistant editor, so I’m stuck with how the editor wants to work.

[David Eells]

So I rendered out all the titles, and went to drop in a new one. Same problem. Vexing.

[David Eells]

Sounds good. I’ll give it a try.