OK, for subs counting I was not allowing for subs that require more than one Object Definition Segment (because they are too large to fit in one). I now read the flag that identifies the first one and increment only when I see that. Will be in the next slipstream.
So, in view of the following link, and the fact that in the entire history of DGIndex and DGIndexNV nobody has ever complained about the demuxed audio not removing dialnorm, I don't plan to do anything about it unless someone makes a very convincing case for it.
Maybe someone else can shed some light on the subject
Thanks for looking into the subs counting issue.
renols
eac3to doesn't remove DN on DTS-HD streams (since it never worked anyway).
Before update v3.29, it was only a cosmetic error that says it was removed (when it never really was).
There's lots of posts about it on doom9 forum if you search.
Removign DN is recommended if you want to transcode to a different format.
It's only metadata, no real conversion.
DN is not the same as Dynamic Range Compression, which requires re-encoding the whole stream.
I've been so used to dealing with just AVC progressive streams, that going back to SD content on DVD (MPEG), I find myself brushing up on things I haven't needed to look up for some time.
Would it, by chance, be too much to ask for a cheatsheet for the info in the *.dgi Files?
The info the DGI files is more relevant than screenshotting the live index with DGdecNV.
Just minor things, like what the colormetry of 2 2 2 means in the file.
Probably just the common and expected (legal) formats allowed.
I keep text files of these, but mainly just for AVC as I tend to neglect anything that doesn't use AVC.
And when I upgrade my card to index HEVC, there'll be more cheatsheets for that as well.
I really can't remember where I keep the free documents on the format specifications.
I should be keeping shortcuts on the desktop in a folder, but I like my desktop super clean.
Nvidia GeForce GT 1030 | GPU Caps Viewer
Windows 10 Annversary (x64) | ASVPlus_x64
Region A/R1
OK, that seems reasonable. I'll see what I can do. We'll need to have __ct__ and similar variables in the template, etc. We can debate whether it should be available via CLI.
We can debate whether it should be available via CLI.
IMHO it's a bit hard to clip a video without a GUI, unless you decide to sample some random frames and crop the best case of each of the four sides. Let's think about some IMAX BD, with 2.35 AR on some parts of the movie and then a 1.9 one in others.
Well, now that I am thinking, it could be nice to have an automatic sampling in the GUI too.
Hi Donald
.mp4 files may include the parameter "Rotation" (in degrees). After demuxing with DGdecNV this parameter gets lost, i.e. it is neither kept in the .dgi nor in the elementary video stream.
Would it be possible to include it at the end of the .dgi (similar to the resolution) ?
Mobile phone video clips can be taken in portrait or landscape (at 0, 90, 180, 270 degrees). Preserving the correct orientation is essential for re-encoding to avoid turned and flipped pictures (I think).
I just select three or four spots and compare the crop values
Me too. On really old restored movies, such as ones from Criterion, AR varies according to the found positives. It's really hard and time consuming but, hey, we are talking about masterpieces.
Hi Donald
.mp4 files may include the parameter "Rotation" (in degrees). After demuxing with DGdecNV this parameter gets lost, i.e. it is neither kept in the .dgi nor in the elementary video stream.
Would it be possible to include it at the end of the .dgi (similar to the resolution) ?
Mobile phone video clips can be taken in portrait or landscape (at 0, 90, 180, 270 degrees). Preserving the correct orientation is essential for re-encoding to avoid turned and flipped pictures (I think).
You can't tell what the required rotation is just by looking at the video? I'm reluctant to add container specific data to the DGI file.
Hi Donald
.mp4 files may include the parameter "Rotation" (in degrees). After demuxing with DGdecNV this parameter gets lost, i.e. it is neither kept in the .dgi nor in the elementary video stream.
Would it be possible to include it at the end of the .dgi (similar to the resolution) ?
Mobile phone video clips can be taken in portrait or landscape (at 0, 90, 180, 270 degrees). Preserving the correct orientation is essential for re-encoding to avoid turned and flipped pictures (I think).
You can't tell what the required rotation is just by looking at the video? I'm reluctant to add container specific data to the DGI file.
Yes, I can always look at the video of course. However, when I want to automate the process it would be useful to have the the value automatically extracted.
I understand your reluctance though, so maybe I should better extract that value outside of DGindex; perhaps with MediaInfo or similar.
Hi. I haven't tested our latest release but may I ask how the cropping tool handle border % 2 != 0 ?
( Personally speaking, it should not be over-cropped? )