Support forum for DG Tools

It sometimes happens that the DGI index file is missing some parts. Not always, randomly.

Such as:

corrupted correct The remaining part is always correct.

I can't reproduce it. It just plain happens.

How are you opening the stream when you get these failures?

Rocky wrote: ↑

Sun Nov 21, 2021 7:44 am

How are you opening the stream when you get these failures?

Drag and drop, as I always do, plus mpls selection.

After clicking Open MPLS in the MPLS chooser dialog, did you do anything else in DGIndexNV before doing save project?

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.

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.

1. "error with some cpi"

Non comprende. What is cpi?

2. Are you demuxing when this happens? If so, does it happen when you do not demux?

3. The header is written first and then the frame list etc. You are doing full paths and have only one file, so the source file path must be getting corrupted after it is successfully opened.

4. How often does it happen? I ran 10 index operations in a row and all were fine.

Rocky wrote: ↑

Mon Nov 22, 2021 8:05 am

Non comprende.

In italian: non capisco or non ho capito

Rocky wrote: ↑

Mon Nov 22, 2021 8:05 am

What is cpi?

Sorry, I can't remember the exact error output. I can remember that the error rarely happens and at the end of indexing only. Perhaps an authoring error.

Rocky wrote: ↑

Mon Nov 22, 2021 8:05 am

Are you demuxing when this happens? If so, does it happen when you do not demux?

Usually I index and demux and if not working I rewrite DGI without demuxing. I don't know if it is a coincidence or not.

Rocky wrote: ↑

Mon Nov 22, 2021 8:05 am

How often does it happen?

Lately I am rarely encoding. Anyway, it has happened frequently enough to tickle my attention. If I told a statistic, it could be 1/25.

Any idea how to debug or have a log of what happens to be ready when it will happen again?

"Any idea how to debug or have a log of what happens to be ready when it will happen again?"

I could add a popup if the source file path is wrong at the point of save project. Then if you get the error on encode but didn't get the popup then we could think your encode process is doing something to the DGI file. But easier would be to just check the DGI after save project before starting any encode process. That's what I am doing, checking after the save project. Frankly, the code is so simple I don't see any way to attribute this to DGIndexNV.

I'd want to check into this cpi error thing as a first priority. Who is issuing the error? What does it mean?

Rocky wrote: ↑

Mon Nov 22, 2021 11:07 am

Frankly, the code is so simple I don't see any way to attribute this to DGIndexNV.

Well, it seems that I have found a way to reproduce the bug.

1) Drag and drop the directory of the ripped BD
2) Select a MPLS (the main one, usually) and open it
3) Drag and drop the same directory again
4) Close the MPLS selection window with the upper right X
5) Save the DGI, it will be corrupted plus a nice error will popup at the end of the indexing



It seems the good old drag and drop issue came back.

Ah, now something I can get my fangs into. Thank you, Guest 2, I'm on it.

Rocky wrote: ↑

Mon Nov 22, 2021 11:55 am

WTF. What a nice job by your dentist.

I didn't have the $$$. Bullwinkle did it for me. Normally, I keep my mouth shut. You know I'm famous, right?

Rocky wrote: ↑

Mon Nov 22, 2021 12:30 pm

You know I'm famous, right?

You are the one and only.

Fire your agent. He is hiding your bling bling.

"It seems the good old drag and drop issue came back."

Beauty resides within. The surface is a meaningless mirage.

Did Balti teach you that?

Her mama.

Sherman, we need you to fix this drag/drop issue, as Rocky will be busy for a while. I've engaged a new dentist for Rocky and he will be gnawing acorns as good as new in a jiffy. Don't forget he lost all of his teeth in the BIG ACCIDENT. Sadly, reimplantation was not successful. The monitor will have to wait.

Right away, Mr DG. You can always count on me. If you need any help with moderating the forum let me know. And can we have a Sherman Approved rank?

Nobody wants to be approved by a six-year-old. Get over it.

Mind your own beeswax, curly head.

“Mind your own beeswax” and “it’s none of your beeswax” are common phrases you might hear being shouted by six-year-olds on the school playground. For the uninitiated, they basically mean “mind your own business” or “it’s none of your business,” but some people think it’s more complicated than that.

http://www.todayifoundout.com/index.php ... d-beeswax/

Rocky wrote: ↑

Sun Nov 21, 2021 1:11 pm

So it seems something must have corrupted it after opening.

Rocky was right!

Mr Guest 2, please re-download 236 and update DGIndexNV. Now if you drop again, it will close everything already loaded. If you then cancel, too bad, you'll have nothing. At least it won't get confused and generate a bogus DGI file. Don't hate me. Or more precisely, don't stick me with any poisonous spines!

Marking resolved. Ha ha ha!

EDIT: Wait, I can't do that because I am not a moderator.

Thank you, Sherman. Bullwinkle will mark it resolved when he returns to his stable. Don't feel bad, I can't do it too. What's up with that?