0 Items in Your cart
Shopping cart ![[]](/sites/all/modules/ecommerce/cart/images/cart_empty.png "View your cart items")
User login
Recent News
Poll
Recent comments
- Less than 2, it says
7 hours 31 min ago - That is not correct
7 hours 52 min ago - Corrupt Anchor Volume Descriptor Files
23 hours 28 min ago - DVDAfterEdit images may not match Scenarist
2 days 4 hours ago - Not changing streams in VMGM
4 days 9 hours ago - Needs to be VTSM or Title Domain
4 days 10 hours ago - Thanks!
4 days 11 hours ago - The GoUp PGC would need a LinkResume command
4 days 15 hours ago - .
4 days 23 hours ago - Hi Steve
Here's a tool which
1 week 1 day ago
Active forum topics
Resources
Syndicate
Macrovision RipGuard Issues
Thu, 2008-05-08 06:19 — justin
Hi All,
I have recently been made aware of a potential issue with AE and the latest version of RipGuard and I was hoping for some help.
I supplied a project for replication that was flagged for CSS and Macrovision Type 2 - RipGuard to be added at the factory.
The replicator contacted me saying there was a problem and that RipGuard could not be applied.
I have spoken to Macrovision, who've analyzed the DLTs and they say there's a corruption of the Anchor Volume Descriptor (AVD) that is causing the problem.
I made a new version of the project and resupplied the DLTs - same issue.
I am running Scenarist 3.2 which macrovision say is rock solid with regards to ripguard so they attribute blame to AE as it is the "unknown" element in my work flow.
Has anyone had a similar incident or is there anyway around this? Can I test the AVD myself prior to sending out DLTs?
Thanks in advance,
Justin
Less than 2, it says
Hi Larry,
When I run Eclipse 5/6 the error I get on all DVDAfterEdit generated DDP file sets are similar to the below (3 warnings):
"Anchor Volume Descriptor Pointer expected at Logical Sector.... DVD-ROM: at 532287 or 53254"
"Less than 2 Anchor Volume Descriptor Pointers....ECMA167: Found: 1 AVDP"
"Less than 2 Anchor Volume Descriptor Pointers....UDF: Expected at LSN (LBA) 256, 532287 or 53254, Found: 1 AVDP"
The above was on a short 15 minute video without menus, going to replication - and no ROM data, other than the empty AUDIO_TS folder.
I emailed you about these UDF errors a couple of years ago (when Eclipse IA beta 5 came out), remember?
Thanks,
Trai
--
Trai Forrester
TFDVD Research Labs
DVDVerification.com
That is not correct
Hi Trai,
The UDF 1.02 spec states that there must be at least two anchor volume descriptor pointers (AVDP's), of the three possible. The possible locations are: sector 256, the last sector of the disc, and the last sector of the disc minus 256 sectors (N - 256). We do not put out the AVDP at N - 256.
We have checked the output of DVDAfterEdit with both Eclipse 5 and the Phillips UDF verifier, and it passes both. We routinely run these verifiers plus our own UDFReader in-house utility on our DDP and CMF output.
We did add the N - 256 AVDP to the output of HDAfterEdit, which makes more sense with UDF 2.5 for HD & BD, because there is always a copy of the disc directory at the end of the disc (the Metafile directory), in addition to the normal one at the beginning, and it falls naturally after that directory.
Regards,
Larry
Corrupt Anchor Volume Descriptor Files
Hi Justin,
Macrovision is correct; DVDAE's formatting does not output the correct number of Anchor Volume Descriptor Pointers in the UDF structure, according to Eclipse Image Analysis 5.0 - earlier versions of Eclipse IA did not verify the UDF's contents, just that it was there.
This warning returned by Eclipse could be what the issue is, or all it can return due to the mentioned AVD corruption.
Take care,
Trai
--
Trai Forrester
TFDVD Research Labs
DVDVerification.com
DVDAfterEdit images may not match Scenarist
Hi Justin,
Each premastering application is free to use its own algorithm to ensure that .BUP files do not occur in the same ECC block as their .IFO file. This means that you cannot guarantee that DVDAE will produce the same result as Scenarist would do. We do always produce legal Anchor Volume Descriptor pointers, and many hundreds if not thousands of our titles have been passed by Eclipse Image Analysis.
I don't know how RipGuard works, it was invented after we completed our premastering software. But I am not surprised that it might expect something other than the exact disc image layout that we produce. One thing you might check for is an empty VTS domain, such as no VMG video or no menu video for a VTS. If so, you might try adding dummy black video to ensure that the BUP is is at least 32 sectors past the end of the corresponding IFO file.
Regards,
Larry
Post new comment