10-bit or higher?

[anton_foy]

I don't know where to post exactly but this would be for development for Avisynth anyway.
Soon SDK will be available for the RED cameras codec and
AviSynth would be in perfect symbios with it if it could handle 10-bit or even 12-bit. I seek a solution to use .R3D or dpx-files with all that AviSynth magic and differnet filters etc.
Though I want to keep the 12-bits(R3D) / 10-bits (dpx).

I guess the answer iss to wait for AviSynth 3.0?
No workaround for image sequences in 10-bit in current AviSynth right?

Thank you

/Jonas

[Blue_MiSfit]

Not AFAIK :(

Some possibility that this will come around in AviSynth 2.6 IIRC, but not totally sure...

For now, 8bit FTW I guess..

[anton_foy]

Thank you Blue_MiSfit for your fast answer!

I would think so too.

[IanB]

2.6 will have some infrastructure added to support 16bit and 32bit (float) per channel internal data paths, but there are no current plans to actually port any filters to use it or how to layout such data.

This means that there will be no need to make any API change (plugin recompile) when someone does start the work.

[Blue_MiSfit]

Gotcha :)

I'm sure the big deal will be updating plugins :(

~MiSfit

[anton_foy]

Wow!
Then it means there is a possibility. For the moment I only need simple commands but all the resizers and stuff will come in handy.

[Mug Funky]

all i need is layer or overlay, and immawrite to support more than 10 bits. masks can stay 8 bit for now.

but it'd be supersweet to be able to do all the whizzbangery we get in 8-bit yv12 into 10-16 bit RGB land. could make weeks of de-spotting go by in a couple of hours :)

@ anton: you shooting red now? cool. what you really need is a Scratch :) it's the bomb

[freezer]

I second the need for 10/12/16/32-bit /float support.
In 1.5 weeks I start shooting a short with the RED and I would die to have the possibility to add AviSynth to my toolset. AviSynth could be one of the best tools around with this support. I am also willing to supply developers with 3rd / dpx files for easier developement and to do betatesting.

[hanfrunz]

@freezer yes that would be great, but ALL filters had to be rewritten to work with the new colorspaces, maybe in avisynth 4 :-)

[freezer]

I just want a resizer, a denoiser and LimitedSharpen. Who do I have to feed with cookies? ;-)

[Mug Funky]

shooting a short with the RED
limitedsharpen

umm... i suspect you wont need a sharpener if you're shooting in 4k.

btw, there's more apparent sharpness for HD in half-res high than in 4k mode. but that's just aliasing. pick whichever looks better of course. half res is much faster (yay realtime on the scratch machine)

[Blue_MiSfit]

If you want to integrate AviSynth with your workflow, I'm sure you could so so at the end - just before encoding :)

It's all going to get converted to YV12 eventually!

~MiSfit

[Mug Funky]

yeah, but encoded files are usually not on the list of deliverables :)

[Blue_MiSfit]

Good point!!! The encoding houses do such a good job of brutalizing content, we should just let them do their thing :rolleyes:

I guess I can dream... but if I'm going to dream - I'll dream of AviSynth with high bit depth support... and CUDA :D

~MiSfit

[anton_foy]

Sorry I did not reply I was on vacation in another country (without internet) hehe!
@Mug
Yeah Mug Im working with the RED ONE all day long now and I love it! Also uses Scratch but it has many bugs and IMHO a very confusing UI. I would just love to be able to script more and use AviSynth with red files in that way. Most for post processing (I had come up with a way to just push the images way more in color and depth) but it would be no point working in 8-bit yv12 I guess :S

[Mug Funky]

you can tie avs into scratch with it's construct_cmd environment variable stuff. i use it for de-graining shot-per-shot. it's a bit of a clunky way to do it though, but thankfully means clients are not exposed to virtualdub and the script window... it's tricky to explain jumping out of a smooth polished interface into code-land.

[anton_foy]

@Mug
Sounds interesting, I must experiment with that but you will still get 8-bit only right?

EDIT: I see, shot-per-shot not frame-by-frame ;)

[anton_foy]

I think in order to get a clean and good result from altering 8-bit images/footage in most ways (such as color adjustments/denoise etc.)
you need higher bits to work in.
When just doing a color grade in Photoshop you clearly see the difference grading an 8-bit source in 16-bit than 8-bit all the way.
I love AviSynth and all its filters/plugins but I have started using other programs to alter my footage/images because 8-bits just isn't enough.
IMHO I really think this should be considered the first priority for the next version. Making this happen will change sooo much.