Support forum for DG Tools

hydra3333 wrote: ↑

Wed Mar 07, 2018 10:26 pm

If your car boot looked like mine you'd never find it if you stored it in there

We call a boot a trunk. Weird, I know, but so is boot.

PS not sure if ffmpeg opencl development is of any interest to you ... some young gun starting off in a career;
http://ffmpeg.org/pipermail/ffmpeg-deve ... 26225.html

vf_convolution_opencl filter as qualification task for GSoC Video filtering with OpenCL project

Never got excited or interested in OpenCL. Maybe one day. Thanks for sharing the link.

Guys and gals, which of these would you like to see next?

* 10/12/16-bit support for my utility filters

* CUDA solution for HDR->SDR. I would probably implement Reinhard tone mapping.

* Something else (please specify).

HDR -> SDR...
You're talking about a specific tone maping, does it mean you've made tests with several and thought this one is "the best" ?

Are you interested (even if you're not doing this feature right now) in an 50GB HDR movie, and in a 25GB file of the exact same movie in SDR ? It seems also that it's (at least for now) a "rare" 4k HDR nits mastering, when actualy almost all HDR mastering are for now at 1k nits.
Or maybe in smaller parts ? But if you want the whole thing, i can provide. The interest of having the whole movie is the possibility to test on a wide variety of scenes.
But maybe you allready have this kind of stuff ?

jpsdr wrote: ↑

Mon Mar 12, 2018 3:03 pm

does it mean you've ...

It means what it says.

Are you interested ...

Not really, but thanks.

first

* 10/12/16-bit support for my utility filters

since 4K movies come with a 1080p SDR version

second

* CUDA solution for HDR->SDR. I would probably implement Reinhard tone mapping.

but you choose, your software and your brain power
and thanks for continuing to improve DGTools

i would like a 10/12/16 bit HDR->SDR...

More seriously, i also agree with gonca on the part "you choose" if finaly one feature request is not more asked than another.
My request was more for curiosity to see what it gives, than a real immediate needs.

Also, i'm sorry, it seems i've badly asked my question.
You choose one method among severals for HDR -> SDR.
Would you share the reason why you choose it ? Unless you've already done that in one of the posts of this 20 pages thread ?

I tested with the available Vapoursynth solutions and liked Reinhard best. It is also easy to implement and has some good literature representation. I have to start with something; that does not rule out adding other methods later. As there is no current Avisynth solution it would be good to get something usable out there.

As I mentioned earlier I am an incremental rather than a big-bang kind of person.

OK, gonna work on high-bit depth support for the utility filters.

admin wrote: ↑

Mon Mar 12, 2018 11:39 am

10/12/16-bit support for my utility filters

This, at least 16 bit, as AviSynth+ 16 bit chain is almost complete. 10 bit as a necessary evil as h265 uses it in Main10 profile.

admin wrote: ↑

Mon Mar 12, 2018 11:39 am

CUDA solution for HDR->SDR. I would probably implement Reinhard tone mapping.

CUDA solution for HDR->SDR and possibly different dithering types even for bit depth decrease (at least none, ordered and floyd or bayer.

admin wrote: ↑

Mon Mar 12, 2018 11:39 am

Something else (please specify).

- High quality resizing (neural or any other hw possible thing)
- Temporal denoising (+ spatial, already existing)
- Make everything work as mtmode 2 in AVS+

Note sure if this of any use or interest https://developers.google.com/media/vp9/hdr-encoding/
under the heading

Convert SDR to HDR with a look-up table (LUT)

Converting HDR to SDR requires the transcoder to understand how to map brightness levels and colors to the smaller BT.709 color space and non-HDR range of brightness. For best results, an LUT describing how to perform that mapping -- usually specific to the content -- can be used. Examples C and D show how to use a LUT. We used bt2020_to_bt709_example.cube https://storage.googleapis.com/media.we ... ample.cube

Note: The LUT above is provided as an example of how to use an LUT with FFMpeg and is not optimized for the content in the example. LUTs are nearly always optimized for specific content.

Interesting, thanks!

Guest 2 wrote: ↑

Thu Mar 15, 2018 12:35 am

- Make everything work as mtmode 2 in AVS+

Sure, why not?

admin wrote: ↑

Sun Mar 18, 2018 3:04 pm

Sure, why not?

Would you please add the duration HH:MM:SS on the right of resolution and fps? And yes, when setting start and end of project range, the duration of that too...

Add them where? Humor me, I'm getting on in years.

Guest 2 wrote: ↑

Thu Mar 15, 2018 12:35 am

- Make everything work as mtmode 2 in AVS+

MT_NICE_FILTER will be better I think
As I understood from explanations and filter examples, programmer must care about memory allocations at getframe requests, not at the filter constructor. Mt mode 2 will care about safe memory allocation if filter allocates memory in the constructor, but it allocate, say, 4 times more memory with Prefetch(4). Imagine my double CPUs Xeon 2665 server running with 32 threads, so Prefetch(32) will eat a lot of RAM.

admin wrote: ↑

Wed Mar 21, 2018 12:36 pm

Add them where? Humor me, I'm getting on in years.

I think you misread. Where can you see duration?

OK, but maybe a status bar or something, not the window title. Lemme think...

admin wrote: ↑

Wed Mar 21, 2018 2:41 pm

OK, but maybe a status bar or something, not the window title. Lemme think...

Let's stay minimal. There is lot of space in the title bar, even when opening half res video.

While we are talking about interface. It would be nice to have something like this



in the status bar, while demuxing and saving project are running, i.e. visual feedback of progress.

You're a tough taskmaster. I'll see what I can do. How about a multiline title window?

admin wrote: ↑

Wed Mar 21, 2018 3:38 pm

You're a tough taskmaster. I'll see what I can do. How about a multiline title window?

Are you talking about duration? Never saw a multiline title window in my life. How is it possible?

Anyway, as most of us are using 16:9 screens, better to expand in lenght than in height.

Owner draw, of course. But I was being facetious.

There's already a cursor that runs along the timeline.

admin wrote: ↑

Wed Mar 21, 2018 6:15 pm

There's already a cursor that runs along the timeline.

I know but most of times I run it minimized. Anyway, no problem

I can't show the duration until after the project is saved. The entire stream must be parsed to count the frames. I do not use heuristics based on timestamps or anything like that, and anyway, elementary streams have no timestamps. So I could show the duration in the title bar after the project is saved or after a DGI file is loaded. It would be better, though, to show it on the Info dialog so that it gets placed in the log file. Showing the project range times would also be difficult for the same reason.

Is any of this any good to you?

admin wrote: ↑

Thu Mar 22, 2018 7:32 am

Is any of this any good to you?

For MKV too you can't get duration info?