numbers i like:

i had a revision to a feature, and needed to send a screener to producer's, typical
the post sup is avid centric and asks for screeners to be DNxHR_LB @ DCi2kscope
i rendered the changed section from my master timeline, cut it into the last screener, used the "bypass re-encode" option in deliver;

render 1_1.2.1.jpg (736.39 KiB) Viewed 1709 times

render 1_1.1.1.jpg (891.87 KiB) Viewed 1709 times

running between 450 and 600Fps, took under 6min to export a 91min feature film @ DCi2kScope

many thanks to the dev's, this is very (VERY) useful workflow tool

[Peter Chamberlain]

Is that a new fastest render speed on this Forum?

Hello,
Very very nice score.

Dayum!

Hello,

Records are made to be beaten!
Next...

bypass_dnxhr_lb_2K.jpg

really it's about the software, this ablity opens doors to workflows that will get shows through the endless revisions /notes / tweaks cycle very elegantly, quickly, cleanly

many machines are faster than this one, but if i can get a show exported in a few min rather than an hour it does change my approach to the workflow to make the best use of this new flexibality

thanks again to the BMD crew

Of course, thanks to BMD Team.

Hoping that for a new Beta (Edit TAB? Delivery TAB?), There is an indicator to inform us if a clip or several clips can come with "bypass re-encode" ?

I was doing a piece in standard definition and I was getting 1200fps... does not compare (v15). But, why not.

......I was getting 1200fps...

mdg-0012-4555--62-.gif

......I was getting 1200fps...

mdg-0012-4555--62-.gif

It was Standard definition.... it is easy peasy....

....It was Standard definition.... it is easy peasy....

it is easy peasy .... OK but can you remind me with which CPU did you get this score?
As I study for next year to evolve my system?

Thank you in advance.

It was Standard definition.... it is easy peasy....

converstion with producer last week after reviewing deliverables list:
me: do you really want these standard def deliverables in 2019?
prod: why not, it''s easy?
me: the deliverables contract calls for 4x3 full frame, this film is 2.39 Scope, we will have to pan-n-scan, alot of pan-n-scan given the frameing
prod: what will that cost me?
me: a day at least, prolly more, then it has to go through Qc and revisons - really best sending a master back to the editor and have them do the dirty work, a few days in a Avid is going to cost less than a day in my color suite
prod: it's not worth it, the only place i'll sell 4x3 is to airplanes, and it will cost more to make than i can sell it for - thanks for the heads up, i'll scratch it from the list

Yes, I have not done 4x3 in a while for deliverable, this was different: it was an old recording of a network (ABC? I don't remember), archived from live NTSC broadcast to B/W 16mm (someone remember the name of the machine used at the time?): we scanned the 16mm, give a light contrast check and deliver (for "once upon a time in Hollywood", not sure if they end up to use it).

another thought on the same vein... if i:
- set caches to write DNxHR_444
- set color output to cache
- set timeline raster to match export raster
- set export to DNxHR_444

now the caches and export target match, could it use the caches in "bypass re-encode"?

currently i turn off caches in the deliver page, but in many instances this would be super useful to use the caches if i'm not creating a needless a pass of de/ re-encode

@ Walter, yea i was surprised by the deliverables contract containing 4x3 SD in 2019 too, they wanted it at 29.97 + 25 texted +25 textless with M&E's, so three more masters to run through QC

many shots are already framed to the edge of 2.39, the whole thing was a huge ouch waiting to happen... hence trying to fob it off to an editor, and then i would not have to be around to absorb the outfall when the director looks at the mess and goes balistic....