Rocky wrote: ↑Sun Nov 21, 2021 1:11 pm
Drag and drop what, exactly? Can you give the full path to the source thingie that you dropped?
My default working path is dropping the directory of the BD rip, looking if there is something to crop and checking the demux window to look at chosen streams. Last thing is saving the dgi.
I don't play with anything strange. I have, sometimes, error with some cpi (if I recall well) at the end of indexing but it usually doesn't give any problem, if it can help you.
The corruption is absolutely random but the strange thing is that it is in the header of the dgi and not in the frame list, that is way longer. So, I think to exclude any write corruption on the hw side.
Is the header written after the frame indexing and listing (time related) or it is written as first thing and then the frame list occurs?
Rocky wrote: ↑Sun Nov 21, 2021 1:11 pm
Thing is, if the video opens and displays then the source path must be correct and I use that path to make the DGI entry. So it seems something must have corrupted it after opening.
I don't use any "special" or unicode character in path. After indexing to a corrupted DGI, I simply relaunch indexing, without changing anything in the path. Of course, I notice the corruption after closing DGIndexNV, trying to encode, and noticing error. When noticed, I reopen DGIndexNV and index again with the very same steps.