Author |
Message |
Registered: November 24, 2008 | Reputation: | Posts: 1,284 |
| Posted: | | | | Quoting rdodolak: Quote: Quoting GreyHulk:
Quote: People are still submitting new Disc IDs under Windows 10 with no tool to correct it. Sigh.
If you have AnyDVD and have it enabled you'll get the correct Disc ID. I'm aware of that (I have Windows 10 and AnyDVD myself) but I've asked three people in the last few weeks who were submitting 'new' Disc IDs under Windows 10 and they had no idea that they were 'fictional' Disc IDs. Too many people now have a 'faulty' Windows 10 and are not aware that this is an issue. |
|
Registered: November 24, 2008 | Reputation: | Posts: 1,284 |
| Posted: | | | | As my attempt to get this 'pinned' has not been answered by support...
Bump! |
|
Registered: March 14, 2007 | Posts: 115 |
| Posted: | | | | Submitting new "faulty" Disc ID's inside the profile is annoying but not that big issue.
Bigger issue is that folks are submitting boxset child profiles (without own UPC) with these "faulty" Disc ID's.
My suggestion would be that we should change the Alternate Version rule a bit. And start using alternate UPC from boxset parent profile for child profiles, because UPC is what it is, it's printed on cover.
Boxset example: Awesome Movie Trilogy (UPC: 123456789) - Awesome Movie (UPC: 123456789 #1) - Awesome Movie 2 (UPC: 123456789 #2) - Awesome Movie 3 (UPC: 123456789 #3)
I thing that this would tackle the issue that database is full of profiles created with "faulty" Disc ID. One issue is how to remove and clean up database from those bad profiles.
What do you folks think about this? | | | Last edited: by JaLe |
|
Registered: March 13, 2007 | Reputation: | Posts: 767 |
| Posted: | | | | Quoting GreyHulk: Quote: As my attempt to get this 'pinned' has not been answered by support... Good luck with that... |
|
Registered: May 25, 2007 | Posts: 127 |
| Posted: | | | | Quoting JaLe: Quote: Submitting new "faulty" Disc ID's inside the profile is annoying but not that big issue.
Bigger issue is that folks are submitting boxset child profiles (without own UPC) with these "faulty" Disc ID's.
My suggestion would be that we should change the Alternate Version rule a bit. And start using alternate UPC from boxset parent profile for child profiles, because UPC is what it is, it's printed on cover.
Boxset example: Awesome Movie Trilogy (UPC: 123456789) - Awesome Movie (UPC: 123456789 #1) - Awesome Movie 2 (UPC: 123456789 #2) - Awesome Movie 3 (UPC: 123456789 #3)
I thing that this would tackle the issue that database is full of profiles created with "faulty" Disc ID. One issue is how to remove and clean up database from those bad profiles.
What do you folks think about this? It's not a bad idea but it would have to factor in all the child profiles already in the system. And there might be the odd set that while legal does not have a UPC for whatever reason, so the Windows 10 issue would still apply there. And there are cases where two or more 50 movie sets use the same UPC but sub out some of the movies. You'd quickly get some really large numbers for each variant set that could get confusing. Probably the biggest issue is the people who can make these kinds of decisions haven't been heard from in a while. Don't get me wrong, I like that it gets away from the disc ID aspect but we'd need to get the decision makers' okay and work out how to minimize the extra work to make the switch. |
|
Registered: March 18, 2007 | Reputation: | Posts: 1,639 |
| Posted: | | | | The underlying issue really lies with the faulty Disc IDs. The reason for using the Disc ID is to avoid having duplicate profiles in the database when a given disc is shared across many releases.
Part of the problem with the way the database is setup however is that non-disc information is store with the Disc ID profiles since they use the same template/layout at the release profile. |
|
Registered: March 13, 2007 | Reputation: | Posts: 3,197 |
| Posted: | | | | Someone with programming skills ought to be able to create a free utility that reads the disc ids the old way, for those who don't own AnyDVD. | | | First registered: February 15, 2002 |
|
Registered: May 19, 2007 | Reputation: | Posts: 5,715 |
| Posted: | | | | The problem is, you can't enter the Disc ID manually into DVD Profiler... | | | Complete list of Common Names • A good point for starting with Headshots (and v11.1) |
|
Registered: November 24, 2008 | Reputation: | Posts: 1,284 |
| Posted: | | | | Also, these phantom Disc IDs seem to be generated rather randomly. Currently under Windows 10, If you use one utility to read a DVD, it gives you a Disc ID. Use another utility, it gives you ANOTHER Disc ID. One of my friends got 3 different Disc IDs just from one disc. |
|
Registered: June 6, 2007 | Reputation: | Posts: 950 |
| Posted: | | | | Quoting GreyHulk: Quote: Currently under Windows 10, If you use one utility to read a DVD, it gives you a Disc ID. Use another utility, it gives you ANOTHER Disc ID. One of my friends got 3 different Disc IDs just from one disc. Now this surprises me. Can you specify which are the three "utilities" in question? |
|
Registered: March 13, 2007 | Reputation: | Posts: 3,197 |
| Posted: | | | | Quoting AiAustria: Quote: The problem is, you can't enter the Disc ID manually into DVD Profiler... That was not the intention. Apparently, AnyDVD is able to "hijack" the Windows system call seamlessly, which another utility should also be able to do. | | | First registered: February 15, 2002 | | | Last edited: by Nexus the Sixth |
|
Registered: May 19, 2007 | Reputation: | Posts: 5,715 |
| Posted: | | | | Yes, but AnyDVD implements a Windows driver to reach its goals. And driver programming is a little bit trickier... | | | Complete list of Common Names • A good point for starting with Headshots (and v11.1) |
|
Registered: October 22, 2015 | Reputation: | Posts: 275 |
| Posted: | | | | I believe the correct description is AnyDVD acts like a rootkit, it inserts its own driver that sits between the operating system layer and the hardware layer. |
|
Registered: October 22, 2015 | Reputation: | Posts: 275 |
| Posted: | | | | Quoting Wigram: Quote: Quoting GreyHulk:
Quote: Currently under Windows 10, If you use one utility to read a DVD, it gives you a Disc ID. Use another utility, it gives you ANOTHER Disc ID. One of my friends got 3 different Disc IDs just from one disc.
Now this surprises me. Can you specify which are the three "utilities" in question? It may not be the same person, but DJ Doena submitted examples on April 25, 2019. You will note he found for the same disc, three different DVD disc-IDs on Windows 10 ver 1809 using no 3rd-party software, Passkey and AnyDVD. Which makes the prospect of manual entry of disc-IDs more frightening, and don't forget to factor in typo-errors as well! |
|
Registered: March 15, 2007 | Posts: 122 |
| Posted: | | | | Hm somehow I only have this issues with DVDs - BDs and UHD are working fine!
I'm using the latest Win 10 x64 1909 + Asus BW-16D1HT (UHD friendly with 3.10 MK firmware). I tried a few older and newer BDs and a UHD, the Disc ID matches.
The only strange thing I found is, that on some discs DVDP recognizes the ID and jumps right to the profile, on others I doesn't find it and doesn't do anything (there is no Popup with disc not found). When trying to create a new profile of those existing ones teste discs are not found either. But when I go to the profile in my collection the disc IDs a are 100 % identical. Even when I try to assing it to the side b field it says that they are already assigned to side A.
With DVDs I always get the popup disc not found and I get different IDs (tried several DVDs, most of them 10-15 years old)
Then I installed DVDfab Passkey Lite (+Trial) to see if it makes a difference, but it doesn't, acts the same. I don't have AnyDVD. | | | Last edited: by Assassin |
|
Registered: March 13, 2007 | Reputation: | Posts: 3,197 |
| Posted: | | | | The "bug" is still present in Windows 10 release 2004 (aka May 2020 update). DiscIDs are still reported correctly with AnyDVD running. The Lady Vanishes, Criterion #3 (UPC 037429122129) DiscID read without AnyDVD: 75CAF101823A9417 [UNDEFINED] DiscID read with AnyDVD (which also matches the id stored online): 5F81EE6FBB60CC21 [UNDEFINED] | | | First registered: February 15, 2002 | | | Last edited: by Nexus the Sixth |
|