Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VidCoder 6.2 Windows Store - ErrorDetectionType Per level 1 #626

Closed
Seger85 opened this issue Feb 5, 2020 · 16 comments
Closed

VidCoder 6.2 Windows Store - ErrorDetectionType Per level 1 #626

Seger85 opened this issue Feb 5, 2020 · 16 comments

Comments

@Seger85
Copy link

Seger85 commented Feb 5, 2020

Hello, everyone,
Hello @RandomEngy

i am using version 6.2 from the Windows Store and after successful encoding i have an "error" which is displayed via MediaInfo:

ErrorDetectionType Per level 1

The "bug" has something to do with the CRC file, but I don't understand how to fix it? I've already read that it can be turned off via command line, but since I'm using the version from the store, I somehow don't have the possibility to do so or I'm stuck.


if you now specify the command "-write_crc32 false" in your command line,

"ErrorDetectionType Per level 1" is no longer displayed in the file info


Can you help me eliminate the problem or explain how to avoid it?

Is the version in the store (beta) always behind the actual beta? Should I maybe switch to another version?

Enclosed I also send you a log.

Thanks for this great unbeatable program!

Many kind regards,
Seger

2020-02-05 09.33.00 Encode hdsource-schuld.s01e06 (Encoded).mkv-succeeded.txt

Example.txt

@RandomEngy
Copy link
Owner

Currently the store version is not getting updates because the tooling to generate my new Microsoft Store certificate is not working. Also when it is working the updates will be behind by a few days. The installer gets updates the fastest. It has lately also been the most stable. I am considering taking down the store link until this all gets sorted.

What exactly is going wrong with the file? Does it play alright? Or is it just an issue when you open it in MediaInfo?

I don't see anything going wrong in the logs.

@Seger85
Copy link
Author

Seger85 commented Feb 6, 2020

Hey,

thank you for responding so quickly and taking care of it!

Okay, I already switched to the latest beta version (portable) outside the store yesterday.

But unfortunately I also get the "problem" there. I could not find any errors in the log and the file (first sighting), but as you already have Grant I get the error:

ErrorDetectionType Per level 1

in the overview in MediaInfo. The problem exists even after a new encoded file with the other version (Portable).

I will show you a screenshot later if you wish. I am still on the road.

Oh, I was able to reproduce this with several test files (10 series and 2 different movies).

Many kind regards,
Seger

@Seger85
Copy link
Author

Seger85 commented Feb 6, 2020

Screenshot:

original

original

encoded error

encoded error

Many kind regards,
Seger

@sr55
Copy link

sr55 commented Feb 6, 2020

ErrorDetectionType Is NOT an error.

All this means is that the file contains CRC information at a particular level in the file. This is correct and expected behaviour.

mkvalidator validates embedded CRC values when present.

@Seger85
Copy link
Author

Seger85 commented Feb 6, 2020

okay, if it's not a mistake, how exactly do I bypass the message exactly? In not self encoded MKV files I do not have this message. Can you give me a hint and maybe you can automate it?

@sr55
Copy link

sr55 commented Feb 6, 2020

You don't. It's supposed to be there. It's a good thing to have in the file.

Any MKV files that do not have this simply don't have the CRC information present.

This is in no way an error or a problem.

@Seger85
Copy link
Author

Seger85 commented Feb 6, 2020

Okay, thank you for helping me understand more. But I don't understand it clearly because I can't see a pattern.

Source file encoded by someone else does not have this notation and I just have this notation with every file.

Is there maybe a test file somewhere where the information is contained, at the moment it looks like I always have this notation.

Innumerable files, from different files, don't have the annotation, except my encoded files.

Thank you for your help and effort with me!

Seger

@RandomEngy
Copy link
Owner

I would guess that those other files don't have a checksum present. Because you are getting it here, it means you are getting the best quality files.

@sr55
Copy link

sr55 commented Feb 6, 2020

Bingo!

@Seger85
Copy link
Author

Seger85 commented Feb 6, 2020

Well, both files have a different value. I have understood that now, but how can it be that this is shown to me once by a message? maybe my english is too weak, I don't understand it or don't want to understand it ;-)

Hash

THANK YOU!!!

@RandomEngy
Copy link
Owner

When you re-encode a file, you change it, so the CRC/hash codes are expected to be different.

@Seger85
Copy link
Author

Seger85 commented Feb 6, 2020

okay, I got that! Thanks!

But how can I have encoded files here that also have a different hash code CRC than the original files and don't show the note.

Initial situation:

Original file has the code: 123
Encoded file has: 1234 and the note is not displayed.

now I take the source file myself: 123
encode it yourself: 1234 and the note is displayed.

I can explain it this way (found on another page):

Under "ffmpeg -h muxer=matroska" you will find the command:

-write_crc32 E....... write a CRC32 element inside every level 1 element (default true)

if you now specify the command "-write_crc32 false" in your command line,

"ErrorDetectionType Per level 1" is no longer displayed in the file info.

https://www.computerbase.de/forum/threads/verstaendnisfrage-errordetectiontype-per-level-1-im-ffmpeg.1650868/

I now understand that this is the charming hint, but obviously you can switch it off and ignore it via command line and not via gui.

Do you think I get it now?

Seriously, thank you very much for the great help!

@RandomEngy
Copy link
Owner

The hash always changes when you transcode. But that hash code is only embedded in the metadata (for error checking purposes) if that option is enabled.

@Seger85
Copy link
Author

Seger85 commented Feb 7, 2020

Thank you thank you thank you!

I have now understood it completely. Now the last question:

Will you be able to add an option to make sure this exam doesn't happen? Or is that perhaps already possible via the individual settings field in the GUI?

I have understood that it works with other programs, especially via the command line.

Thank you for this little wiki and the effort to explain it to me.

Would / would like to buy you a beer.

Many greetings,
Seger

@RandomEngy
Copy link
Owner

It's not an exam. It's a piece of data that allows players to verify that the file isn't corrupted. Why do you want to remove it?

@Seger85
Copy link
Author

Seger85 commented Feb 7, 2020

I thought until now that it just shows the value 1 and that the change should be symbolized. Since there will always be a change in the original file, the optical value is just the hint. If the value also shows another identifier (like 12), then it is of course a clear indicator for an error. If this is not guaranteed, it makes only limited sense for me in the encoder scene, because I know that I have just sorted and changed a file.

But now I understood it all very well, thank you!!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants