View Full Version : TMPGenC and DVD Shrink
plipton
11th December 2003, 22:47
DVDShrink encountered an error and can not continue.
Can not decrypt VOBS
The reason is: Unknown
I took an avi file and processed it via TMPGenC. I next tried to run it through DVDAuthor and created the files for burning and was successful. As an experiment, I tried to process those output files through DVDShrink. The above error messages were received. The files from DVDAuthor were eventually burned to the media and were viewable.
As a further experiment,I reprocessed the DVD with DVD Decryptor successfully. I again tried to process the output with DVD Shrink. I again got the same error message and the DVD Shrink process failed. How come this "reprocessing" with DVD Shrink will not work either?
Thanks,
Paul
DenFussell
13th December 2003, 05:16
Paul-
I experienced the same problem just today with 'Gone With the Wind'. I did however, get Shrink 2.3 & D2O V 1.3 to work with the same files, so it's an issue between Author & Shrink 3.
Perhaps there'll be more support for Shrink in the near future.
Good Luck!
********************************8
DVDShrink encountered an error and can not continue.
Can not decrypt VOBS
The reason is: Unknown
I took an avi file and processed it via TMPGenC. I next tried to run it through DVDAuthor and created the files for burning and was successful. As an experiment, I tried to process those output files through DVDShrink. The above error messages were received. The files from DVDAuthor were eventually burned to the media and were viewable.
As a further experiment,I reprocessed the DVD with DVD Decryptor successfully. I again tried to process the output with DVD Shrink. I again got the same error message and the DVD Shrink process failed. How come this "reprocessing" with DVD Shrink will not work either?
Thanks,
Paul
DenFussell
13th December 2003, 06:06
Paul-
I just ran the original files through Shrink 2.3 with no compression and then they processed through Shrink 3B5 without a hitch. You could do this if you want to use deep analysis in 3B5 without suffering the lower quality(?) of V2.3.
This would probably be the equivalent of updating ifo's, remapping vob's and Getting VTS sectors in IFOEdit.
I'm doing this exercise just to see if I can really see the difference between 2.3 & 3B5 Deep analysis.
I'll let you know if I draw any conclusions.
DenFussell
DenFussell
13th December 2003, 18:04
FWIW-
I processed GWTW with D2O, Shrink 2.3 & Shr 3B5(After running it through Shr2.3 w/ no compression to get rid of the error message)and the difference is quite clear. Shr 3B5 with deep analysis is the clear winner with this movie.
I hope there is some support for Shrink in the future to the point that it becomes a for-sale product so that support can be counted on.
Good Luck
plipton
13th December 2003, 19:04
Thanks for all of the effort. My original reason for experimenting with DVD Shrink was to be able the eventuallity that the output of TMPGenC was too large for a single DVD. I have not encountered that yet but I am sure it will occur.
After all of your testing it does indicate a limitation of DVD Shrink 3B5. Hopefully the guys that have developed the program will fix the problem. I think it is a great program and seems to be able to handle situations that the commercial programs seem to choke on.
Again thanks for the testing. You are more experienced than me.
Paul
tluxon
14th December 2003, 02:58
[edit out inadvertant link]
This looks familiar. In case you're interested, I reported my observations of the difference between compressing the MPEG with ReJig and compressing the titleset with DVD Shrink here:
http://www.avsforum.com/avs-vb/showthread.php?s=&threadid=335149.
Tim
scifiguy
22nd December 2003, 16:31
Tim -
The URL you posted is an advertisement for a Hard Drive (?!)
tluxon
22nd December 2003, 18:06
Corrected - Thanks.
ddlooping
22nd December 2003, 19:48
Hi all. :)
DVD Author adds a copy protection flag even though it doesn't add any form of copy protection; that's what throws DVD Shrink v3.0b5 off.
The workaround is to use v2.3 with "No Compression", and then use v3.0b5 on the resulting files. ;)
The forthcoming v3.1 might have the option to ignore this flag.
scifiguy
22nd December 2003, 20:04
How complicated would it be to blank out the copy protection flag? Is it determined by the value of a byte (or bytes) within a file header? It would be easy enough for me to write a utility to zap it out if I could get the appropriate positioning and values. And, I'd be happy to post the utility here on the board.
That's gotta be a lot better than running it through DVDShrink twice (doubling the amount of time it takes to process)
I'm trying to use TMPGenC + DVD Shrink to author my own home movies. If I want copy protection, I'll add it in myself...
ddlooping
22nd December 2003, 21:57
How complicated would it be to blank out the copy protection flag? Is it determined by the value of a byte (or bytes) within a file header?
I have absolutely no idea; but hopefully someone who does will tell you. ;)
tluxon
23rd December 2003, 05:58
Originally posted by scifiguy
How complicated would it be to blank out the copy protection flag? Is it determined by the value of a byte (or bytes) within a file header? It would be easy enough for me to write a utility to zap it out if I could get the appropriate positioning and values. And, I'd be happy to post the utility here on the board.
That's gotta be a lot better than running it through DVDShrink twice (doubling the amount of time it takes to process)...
That's a great idea. I don't know if it would help, but I could author a fileset of a very short clip with each DVD Author and MovieFactory 2 and make them available to you if you think that would tell you what you need.
Tim
scifiguy
23rd December 2003, 06:21
Go for it. *IF* it turns out that the copyright setting is a fixed set of bits in a fixed address, or even a fixed set of bytes coming after some identifiable string of characters, it would be easy for me to get a patch together.
The important thing is to create things so all the corresponding files are exactly the same size...
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.