[Drew Lahat]

Bob, you always crack me up. 🙂 Yes I’m very much aware that they ceased development. I just pulled up my notes from Sep. 2013 when I talked to Bernard Lamborelle and got the first heads up about it. And this morning I read (again) the EOL notice, they will continue to release maintenance updates to support OS updates in the end of 2015, just no new features. So 10.10 is currently supported in MetaSAN (clients only, no MDC) and even 10.11 may be.

If we were to drop $12k on new 8Gb fiber HBAs and wanted to actually enjoy the extra bandwidth, we’d need two new 5802’s ($17k), new storage (another $20k), oh wait, and we’d probably have to replace the OM2 fiber in the walls. In other words, the facility will likely be going straight to 10GbE in 2017, if we’re not all using subspace telepathy by then.

All this, and your reply (and mine) were completely off-topic. How about “the Apple 4Gb HBA still works fine in 10.10”? I’m yet to hear direct confirmation, just people excited about XSAN living strong in 10.10 and 10.11.

[Drew Lahat]

Ah, the good-old “play doesn’t work” problem. This “behavior” has been around since the original CC. Thankfully I don’t see it happen much, but it did just happen to me this week. In my case a restart solved the problem.
One case it always happens is if Transmit is enabled and Resolve is running – since Resolve snatches the Blackmagic card and Premiere doesn’t know “what to do”.

Since it’s happening to you with a specific multicam sequence, can you rebuild that sequence? Sounds like a corruption specific to that project/sequence. Also, can you transcode the footage into another format (proxies) and try?

[Drew Lahat]

Hi Walter, glad to have you aboard in this thread.
I do have a Decklink Extreme 3D+ running HD-SDI to a (calibrated) Sony BVM HD CRT w/ the BKM-142HD board, so I have a 10-bit signal path.. and an infinite-bit panel 😉

But read what I described again, I narrowed the issue down to internal processing in PPro regardless of any video output. There’s banding during playback/scrubbing and no banding when paused – on the same frame and same monitoring chain. The banding comes and goes with a hit of the space bar.

It is possible that the thread title should have been “PPro can only render-on-the-fly at 8 bit”. That’s what I’m trying to figure out.

[Drew Lahat]

But this happens also without an SDI card or with it disabled; in theory it would even happen in a system without any monitor 🙂 My GUI monitors are connected via DVI so they’re 8 bit anyway.
This is about timeline processing.

[Drew Lahat]

Mac OS X 10.8.5 here.

[Drew Lahat]

Nice, I just happened to carry out this same workflow myself (before seeing this thread). Resolve is definitely a useful middleman conform tool in this case. It “speaks” both AAF and XML, and speaks AAF better than Premiere.

[Drew Lahat]

Good idea 🙂 I’ll take you up on that next time I’m at the facility.

[Drew Lahat]

Thanks Joseph, forgot to mention that our SAN tests routinely clock at 350MB/s. And I told the new tech that with a couple hours’ worth of work this bay could be upgraded to 550MB/s.

Do you agree with Sascha that Resolve is hopeless in XAVC-I, or not necessarily? I’ll definitely try 4K ProRes to compare the performance (and when the FS7 firmware upgrade that allows ProRes recording finally releases it could be a solution)…

That said, for our facility, transcoding is so 2010. Since we’ve gone to Premiere CC we managed to eliminate most transcode work on the ingest side, which simplified our life so much and allows the assistants to do other and better things; it cuts through HD Long-GOP H.264 like butter. But Resolve, while they claim advanced format support, hasn’t been quite as magical. As far as XAVC-I goes, I was hoping to hear the opposite of what Sascha said, especially with an intra-frame codec.

[Drew Lahat]

Let me start with an “Avid question”… why would you need to do that?

[Drew Lahat]

There is… just open a QT file (in QT Player 7), hit Cmd+J, choose the timecode track and delete it…

This of course does it one file at a time, not automated. Also note that if you need more QT manipulation capabilities, I recommend VideoToolShed’s QTChange utility. More powerful and useful that my script 🙂