Requesting feedback on DVD Shrink

[dvdshrink]

Hello,

I'm afraid it has been many years since I visited this forum.

Would anybody be able to give me a quick rundown on known DVD Shrink problems?

I'm aware that there is some new kind of copy protection which DVD Shrink cannot handle, but I do not know any specific details. Also I understand there may be a problem with ISO file output, many years ago I was asked to change something about this, but I cannot remember what.

(I should add that I have no plans to release a new version, I'm requesting this information because I am working now on a related project).

Any feedback would be really appreciated.

[dialysis1]

First off I would like to say it's great to see you back.
I have no real issues with Shrink although I would like to see a program that can combine titles into one title instead of two. It would be great for the so called flipper discs.
As of ISO's, I think creating an ISO with the proper handling of the layer break would be nice.

[Chetwood]

Man, it's good to have you back!

I don't know of any ISO related problems but having Shrink do 32 KB IFO/BUP padding would be nice and save an additional working step (putting out to files and building padded ISO with Imgburn, that is). The rare occasions I do rip to DVD-9, ImgBurn sets the layer-break for me upon burning so it's maybe not that important to add layer-break support.

Naturally Shrink doesn't handle new protections but that's not what it's designed for so no problem there either.

Of course it would be nice of you to release a new version 3.2.0.15i which would call up ImgBurn instead of DVD Decrypter when burning and maybe even upgrade the DeCSS-free legal versions to abort upon detection of Macrovision protected DVDs so there would be no need to use other hacks.

[blutach]

Nice to see you back dvdshrink and hope you are well!

The new protections are somewhat complex and basically necessitate an independent ripper for these titles. However, most titles (99%+) remain simply CSS protected, and so can be handled with DVD Shrink.

The ISO file output is, as Chetwood said, one of padding (especially in a reauthored DVD). This is not critical. 3rd party tools such as PgcEdit, VobBlanker and ImgBurn take care of this. More reading here (http://www.digital-digest.com/~blutach/pgcedit_guide/burning_with_pgcedit/burning_with_pgcedit_v2.htm#TechInfo).

As for layer breaks, it is not really relevant as DVD Shrink is not a tool primarily designed for DVD 9 to DVD 9 backup. However, if you were concerned, the issue would be of making a LB on an ECC boundary (sector multiple of 16). This can involve padding. Again, 3rd party tools such as PgcEdit and ImgBurn take care of this perfectly.

There is one tiny issue in respect of reauthored DVDs with more than one Vob ID. The number of Vob IDs in the C_ADT table is always set to 1. This is not major either and does not affect playback.

IIRC, if the framerate was incorrectly set (or not set at all) in VMGM_MAT --> FP-PGC, this was not fixed when backing up.

I'm sure there are other small issues, which we will post when we think of them.

Now, members should take note of what dvdshrink said - there are no plans to do a new version. Hence, feature requests are not relevant in this or any other thread. Please do not inundute this thread with what "would be nice to see" etc etc. Simply give dvdshrink the feedback he wants.

Regards

[cynthia_old]

Always nice to see old members return! :)

Here are some issues collected during the latest years. ;)

When I use author mode to trim the start and end of the movie or chapter, the ac3 timestamp header is not reset to 00:00:00:00 this cause error whe i try to put differents episodes or chapters together in ONE pgc. I have to do it manualy, using HeadAc3he (demux audio-video) and then remux. (is a long process but work 100%)

After shrink a dvd i get all chapter +1
dvdshrink append an empty chapter ! This is in re-author mode.

Just one small issue: after a title is previewed, the audio device isn't released. Most people wouldn't notice, but my card is a semi-pro card that allows you to change its internal sample rate. The problem is that when an app opens the audio device, the card stays fixed at the requested sample rate until it closes it again - so throughout the long backup phase, I can't work at any other rate.

When replacing a titleset with a still image, the audio streams disappear when "Still Image" is selected from the drop down menu, and while the audio is removed, the new VTS_XX_0.IFO and VIDEO_TS.IFO still list the audio streams as present.

When Menu files *_0.VOB of size 0KB exist in the DVD source, they dont get copied over by Shrink 3.2 to the output file. This problem causes a break in the DVD structure and fatal error when burning with Nero.

The workaround is to manually copy the 0KB .VOB files from the source over to the Shrink output.

A little bug I discovered in 3.17 and it seems to happen in 3.2 too. When shrinking a DVD folder, the last file open from the source (usually the last VOB from the folder) is not being closed. The file is released only after closing DVD Shrink.

Number of VOBIDs in VOB incorrect after re-author
I have some titles with the last cell being a blank and a different VOB-ID. So, each one has 2 originally, VOB-ID 1 & 2. To prove to you I had 2 VOB-IDs, I opened up my original files in IfoEdit and looked at the VTS_C_ADT table and it should show 2. But after reauthoring, each title now shows 1 in their VTS_C_ADT table even if it shows VOB-ID 2 at the bottom of this table.

If anyone wants to strip out a VOBID in IfoEdit now, it would show only the first VOB ID only instead of both. Editing the VTS_C_ADT table in the DVD Shrink IFOs as the same as the original would have you seeing both again.

as I just recently noticed that Shrink does remember the heigth of the preview window after a restart. Unfortunately the program window size & position and the width of the preview window is not retained so you have to rejuggle the layout after each start on your screen. Looks like shrink does not remember it was closed with the window maximized and behaves like you explained.

I'll try to look in my old papers to find some more stuff. :D

[Chetwood]

There is one tiny issue in respect of reauthored DVDs with more than one Vob ID. The number of Vob IDs in the C_ADT table is always set to 1.

I guess this is what caused the error message in previous PgcEdit versions:

Warning: the number of VOB IDs stored stored in the VTS_C_ADT table of VTS 3 (1) don't match the real number of VOB IDs in the table (2).
(This is a known bug of DVD Shrink in reauthor mode)


Maybe r0lZ can chime in as there seem to be a few more fixes done in his current DVD Shrink-plugin for PgcEdit. For the sake of completeness I'm posting an old bug list I compiled from forum entries when we were doing the german version of Shrink:


When I use author mode to trim the start and end of the movie or chapter, the ac3 timestamp header is not reset to 00:00:00:00 this cause error whe i try to put differents episodes or chapters together in ONE pgc. I have to do it manualy, using HeadAc3he demux audio-video) and then remux.


Similar to this, when you reauthor episodic discs (or strip episodes from them with Shrink for encoding with AutoGK) that have all eps of a DVD in the first PGC, DVD Shrink does not reset the time code. Thus if you open ep 2 in AutoGK both sound and subtitles start at 43 or so minutes which in in turn results in no subtitles being displayed.


I found a small glitch in dvd shrink nothing important really when the file browser window on the left is sized so small that there is need for a vertical scrollbar, and so short that there is no room for the fixed heading row, the program enters an infinite loop between what looks like resizing the fixed row and adding a scrollbar even restarting the program the problem doesnot go away, although it should with a reinstall nitpicking really but thought yall should know.

[setarip_old]

@dvdShrink

Hi!I'm aware that there is some new kind of copy protection which DVD Shrink cannot handleActually, there are several, including:

ARccOS

RipGuard

XProtect (or CrossProtect)

[blutach]

There's one more I remembered overnight and it relates to multiple titles as dialysis1 has hinted at.

If you take a not one sequential title (with many PGCs) and re-author it, it will come out as several titles. This breaks the nav, if for example, it is a game with BOVs, that typically have commands that say Link PGCN x (in the re-authored DVD, each PGC is a title with just one PGC).

After shrink a dvd i get all chapter +1
dvdshrink append an empty chapter ! This is in re-author mode. I have not seen this.

When I use author mode to trim the start and end of the movie or chapter, the ac3 timestamp header is not reset to 00:00:00:00 this cause error whe i try to put differents episodes or chapters together in ONE pgc. I have to do it manualy, using HeadAc3he (demux audio-video) and then remux. (is a long process but work 100%) This is an important restriction in many transcoders that only a full demux/remux fixes. It sometime has bad playback consequences. Good find!

Regards

[dvdshrink]

Thanks everyone for a really positive response :-)

Lots of bugs! This feedback is just perfect. I have a little to say about some of the issues, and the rest, I've definitely taken notice. Not releasing file handles (or audio devices) is just plain bad programming, sorry about that.

If you take a not one sequential title (with many PGCs) and re-author it, it will come out as several titles

Yes, DVD Shrink is limited to only re-authoring a single PGC at a time. It cannot handle multiple PGC titles, or even multiple angles in single PGC titles. Definitely this could have been done better.

When I use author mode to trim the start and end of the movie or chapter, the ac3 timestamp header is not reset to 00:00:00:00

It was left like this on the assumption that DVD players don't really care - since they all support jumping into the middle of a stream anyway, with Link#PTTN command. The problem is that you guys all want to do more advanced stuff with the output, and not just play the stream!

blutach is correct when he says this requires a full demux/remux, but I was thinking about this, and you know, I'm not even convinced it is possible. DVD Shrink can start a re-authored title at any arbitrary VOBU index, but audio frames are not typically aligned to VOBU boundaries. So you need to discard any partial audio frames, and start the first complete frame with a 00:00:00 timestamp, but what if you have multiple streams with different bitrates/formats? E.g. AC3 and LPCM. It may be impossible to find a "first frame" of each which is exactly aligned in time, so to maintain sync with each other, surely at least one stream would have to be started with a non-zero timestamp? Also I was wondering if the video timestamp for the first I-picture in the vobu could end up being negative after adjustment, or something bad like this...

There is one tiny issue in respect of reauthored DVDs with more than one Vob ID. The number of Vob IDs in the C_ADT table is always set to 1.

I was looking at exactly that piece of code the other day, and thinking, this can't be right!

After shrink a dvd i get all chapter +1
dvdshrink append an empty chapter ! This is in re-author mode.

An earlier version of shrink may have tried this as a feature. I don't remember exactly, but I recall experimenting with this. It means you can chapter skip to the end of the title.

The ISO file output is, as Chetwood said, one of padding

Just to make sure I fully understand this: the IFO and BUP files shouldn't actually be changed in size or padded as such, but should be arranged in the ISO so that there is at least a 16 sector gap between them? (And the sector offsets in each IFO adjusted accordingly).

ARccOS
RipGuard
XProtect (or CrossProtect)

Great, thanks for the feedback. I'm not sure which is which but I gained some understanding now of how these work.

[blutach]

Just to make sure I fully understand this: the IFO and BUP files shouldn't actually be changed in size or padded as such, but should be arranged in the ISO so that there is at least a 16 sector gap between them? (And the sector offsets in each IFO adjusted accordingly).
Yes - simply adjust the pointers in the VMG_PTT and the VTSI_MAT tables. For an example of how this works, take any reauthored DVD, and save it in PgcEdit with the option to save with 32k gaps on. Examine the differences between the pointers in the various titlesets compared to the DVD Shrink output.

In respect of the timestamps on "cut DVDs", it is not just the AC3 headers but also the cell elapsed time of the DSI stream matching that of the PCI stream (see 0x0045 and 0x0423 of the navpacks). In particular, if a flag is incorrect and the STC clock is not reset, very unpredicable playback can occur.

In respect of adding a tiny cell as an end chapter, this is not necessary anyway for 2 reasons:

1. Subject to 2 below, by making the Next PGCN = the current PGCN, you can skip to the post commands
2. Even if there is a tiny last cell, if PUOp=128 is set (Next PG) in either or both of the IFO or VOB for that cell, you can't skip. You need to eliminate this PUO.

I had 2 other issues pop to mind as well. The first has to do with the jump/link/call flags - this is very minor and most technicians agree it is entirely useless and ignored by almost all players. Please see this thread (http://forum.doom9.org/showthread.php?t=135594), with the definitive answer by (as you would expect) mpucoder in post 17.

The 2nd has to do with eliminating PUOs on a DVD with angles. It is natural to want control of your DVD, however, if the DVD has angles, on many players, if the angle change PUO is unset (in either the IFOs and most particularly, the VOBs) in such a DVD, a little angle icon comes on the screen, which is very annoying. On many players, this can not be surpressed. So, advising users not to eliminate POps where a DVD has angles is required, IMHO.

Hope this helps.

Regards

[dvdshrink]

I never thought of that. You certainly know your stuff. Maybe better to always leave the angle PUOP unchanged (uops &= 0x400000)? I can't imagine it's ever an inconvenience to have it set.

[blutach]

I agree re the PUOps. And coming from you, that's a very big compliment. Thank you.

Regards

[cynthia_old]

There seems also to be an issue with the automatic burning if Nero 8 is used. By reading this thread it seems that the link to call it up is broken by a name change of the .exe in Nero 8.

http://forums.afterdawn.com/thread_view.cfm/579890

[dvdshrink]

Well, the consensus at afterdawn seems to be that Nero should fix it, and I agree ;-)

I have another question - deep analysis. Does everybody use it? Or does everybody hate it?

The reason for deep analysis, of course, is that DVD Shrink can't know in advance exactly what is in the VOBS, until it's checked every sector. And it needs to know what's there, to optimize encoding decisions. End credits are a classic example - they are really hard to compress, and they come right at the end of the movie, so there's no margin for error remaining when you're trying to hit a specific size.

What I'm trying to work out is if people just accept that two-pass encoding is an unpleasant fact of life, or if you only enable it when really necessary, e.g. if Shrink failed to hit the target size?

[Calimari]

I sure love the deep analysis! DVD Shrink knocked down its competitors because of its great quality video output. Don't forget that people have fast machines these days (or at least they should :)) So that extra few minutes won't matter. Besides, the user has the choice, use it or not. IMO it was one of the aspects that made Shrink so great.

[setarip_old]

What I'm trying to work out is if people just accept that two-pass encoding is an unpleasant fact of life, or if you only enable it when really necessary, e.g. if Shrink failed to hit the target size?Based on postings I've read over the years, it seems to be (as we said in the '60s) a "mixed bag" - There are those that swear by it and use it every time they use DVD Shrink. On the other hand, there are those who use it only when the initial indication by DVD Shrink is that the total filesize cannot be reduced sufficiently. And, of course, there are those who use it selectively - e.g. not bothering to use it for CGI DVDs, but using it for DVDs that have high action and/or intense color.

Personally, I believe it to be a valuable available tool...

[Rogi]

I have another question - deep analysis. Does everybody use it? Or does everybody hate it?


Personally, I always use deep analysis.

In my experience, is clearly visible that dvd backup with deep analysis is better than without it.

[Vulcan94]

Well, the consensus at afterdawn seems to be that Nero should fix it, and I agree ;-)

I have another question - deep analysis. Does everybody use it? Or does everybody hate it?

<snip>

What I'm trying to work out is if people just accept that two-pass encoding is an unpleasant fact of life, or if you only enable it when really necessary, e.g. if Shrink failed to hit the target size?



I always use deep analysis. I want the best quality I can get, so I just take a break while DVDShrink does it thing. Great program by the way.


Vulcan94

[Chetwood]

I have another question - deep analysis. Does everybody use it? Or does everybody hate it?


It rocks and I use it all the time! Since it's an option which is also off by default on new installs I don't see why anyone should have a problem with it. Like already mentioned here, computers are a lot faster now so maybe the efficient use of multicore cpus (where possibe) is the way to go on your new project.

[dvdshrink]

Shrink is already multi-core - it'll create as many encoding threads as you have cores. I thought the bottleneck has always been drive speed, or maybe I just need a new drive? It takes over 20 minutes to make one pass.

[Calimari]

I have an Intel Core 2 Duo 6300, 1GB RAM, SATA hard disc. One pass takes about 10 to 12 minutes (full backup). And I see processor load go up to over 90% so the dualcore is used, to confirm dvdshrink.

[blutach]

I'm sorry, but I have come across another little bug.

Automatically remove layer break can be "too aggressive". Take this example:

BOVs Chap. Prog. Cell Type Seam- Ang VOBU Cell Cell Playback End Entry First Last Last VOB Cell
(PTT) Flags less Still Still Cmd. Time Time VOBU ILVU VOBU VOBU ID ID
Joint Time # sector End Start End

? 1 1 1 2 no - no 0 0 00:04:27.13 00:04:27.13 5 0 98208 98525 2 1
? 2 2 2 8 yes - no 0 0 00:07:44.09 00:12:11.22 98526 0 245150 245303 2 2
? 3 3 3 8 yes - no 0 0 00:09:05.16 00:21:17.13 245304 0 420359 420814 2 3
? 4 4 4 8 yes - no 0 0 00:08:13.04 00:29:30.17 420815 0 588284 588576 2 4
? 5 5 5 8 yes - no 0 0 00:10:27.08 00:39:58.00 588577 0 798160 798196 2 5
? 6 6 6 2 no - no 0 0 00:03:11.04 00:43:09.04 798211 0 861345 861731 3 1


Note the non-seamless cell between 2/5 and 3/1 due to, amongst other things, the fact that the sectors are not contiguous (there is a (tiny) VCID 2/6 that is not in this title).

After running this title through DVD Shrink, the cell is marked as seamless (flag=10). It should remain as a 2.

Regards

[dvdshrink]

The current algorithm goes like this:

For each PGC in TT_DOM, if the PGC playback time is more or equal to one hour, and the PGC contains more than three cells, and only one cell (excluding first and last cell) is marked as non-seamless, then make it seamless.

I suppose this is not guaranteed to work 100%... is there a definite better way to do this?

[dvdshrink]

And another question!

It was mentioned earlier that shrink doesn't copy zero sized VOB files to the target folder - but why do so? Some DVDs seem to have them, and some don't, but I don't know of anything in the spec which says that a zero sized VOB file should exist.

[blutach]

The current algorithm goes like this:

For each PGC in TT_DOM, if the PGC playback time is more or equal to one hour, and the PGC contains more than three cells, and only one cell (excluding first and last cell) is marked as non-seamless, then make it seamless.

I suppose this is not guaranteed to work 100%... is there a definite better way to do this?I definitely think you need to take account of 2 things:

1. The presence of a cell command at the layer break (e.g. a NOP - yes, these exist!). The next cell can not be seamless after a cell command; and

2. As mentioned above, in order to be seamless, generally, in the absence of ILVUs (and no-one would break in an interleaved cell!), the sectors need to be continguous.


And another question!

It was mentioned earlier that shrink doesn't copy zero sized VOB files to the target folder - but why do so? Some DVDs seem to have them, and some don't, but I don't know of anything in the spec which says that a zero sized VOB file should exist.If the VOB exists, of whatever size, it will be referenced in the IFO (VMGM/VTSI_MAT, in particular, start sector of menu VOBs (0x00c0), and the menu C_ADT and VOBU_ADMAP tables). So, if you are going to exclude these silly 0 entries, just make sure these pointers in the IFO are adjusted to 0 accordingly.

Now, I know you are working on a different project, but there are also issues with logical remapping of enabled streams, which I can set out in more detail if required. You should also try re-authoring a project with more than 50 titles and look at FP-PGC (which hits the 128 command limit).

Regards

[dvdshrink]

If the VOB exists, of whatever size, it will be referenced in the IFO (VMGM/VTSI_MAT, in particular, start sector of menu VOBs (0x00c0), and the menu C_ADT and VOBU_ADMAP tables)

Ah yes, I see. Shrink needs all three pointers to be non-zero (vobs_sa, c_adt_sa, v_admap_sa) before it'll read and write a VOBS, but it doesn't zero any pointers if the condition fails.

Now, I know you are working on a different project, but there are also issues with logical remapping of enabled streams, which I can set out in more detail if required.

Please do!

[traycer]

Any feedback would be really appreciated.
Great to see you're still active! I'm not a hard core DVD Shrink user, but a feature I would love to see is functionality for automation and batching. I know about MultiShrink and cmdDVDShrink, but it would be a lot better to have that built into DVD Shrink instead.

Depending on the disc, I can transcode an ISO (with deep analysis) in 8 to 12 minutes. This is on a 3.3 GHz quad-core Vista machine. DVD Shrink only uses about 75% of the CPU during the encoding phase, yet it is not limited by disk (it's only reading at a rate of 15 MB/s or so... the drive is only reporting 20% busy).

Having to check back every 8 to 12 minutes means I can't really do too many other things in the meantime. My workaround (before I discovered MultiShrink) was to have 7 or 8 DVD Shrinks all running simultaneously, and then come back a couple of hours later to check on things.

Being able to create batch queues, or the ability to specify backup parameters via a command line or a file-based script (e.g., to choose audio/video streams, specify compression parameters, backup paths, etc.) would be just lovely.

:thanks:

[m1ckran]

Hello, DVDShrink and thank you for sparking my interest in DVD backup. I think I would not have bothered without your software (and dvddecrypter) which would have meant that I would have bought far fewer DVD's than I subsequently have.

Although I tend to use DVDRebuilder nowadays, I still use your program for speed and when very little compression is required. It's also very good for stripping unwanted audio and subtitle streams before using Rebuilder.

Thanks again.

[blutach]

@traycer

From post 4

Now, members should take note of what dvdshrink said - there are no plans to do a new version. Hence, feature requests are not relevant in this or any other thread. Please do not inundute this thread with what "would be nice to see" etc etc. Simply give dvdshrink the feedback he wants.


Regards

[Chetwood]

cmdDVDShrink

:)


So, has the topic "logical remapping of enabled streams" already been covered by PM? Cause I also have this as a FAQ entry in my repository that I could post here.

[wildchild77]

(I should add that I have no plans to release a new version, I'm requesting this information because I am working now on a related project).

That is great news! The only thing better IMO, would be a Linux based project...

DVD Shrink remains one of my favorite and dependable DVD tools.

:thanks:

@dvdshrink will you be keeping us updated on this new project?

[brobear]

That is great news! The only thing better IMO, would be a Linux based project...

DVD Shrink remains one of my favorite and dependable DVD tools.

:thanks:

@dvdshrink will you be keeping us updated on this new project?


It would be interesting to know what the project is.

As for Nero 8 not working with Shrink, that's no real inconvenience. It still works with DVD Copy and the others. If a user looks around, they can find a modified Shrink exe that calls up ImgBurn instead of DVD Decrypter as a supported burner. That gives all users a free and up to date burning program. For those not aware, Lightning UK is still supplying support for ImgBurn, which is more or less the updated burning software from DVD Decrypter.

[dontasciime]

Can I also just add a little bit of info.

The out of memory errors some people may get.

"DVD Shrink encountered an error and cannot continue. Out of Memory Not enough storage is available to process this command."

This is due to the buffered amount just rising and going above 1.6 gig [well 4 me with 4 gig of ram with 3+ being in use]

Easier if I just quote myself from another forum on a temp fix etc.

Tue Jan 08, 2008 3:10 pm I can only speak about my use and I have to say the only time I ever get this error is when I am outputting ISO to an external Hard Drive (USB2) Flash pen etc.

The buffered amount just keeps rising not like when I use Internal Hard drive where it rises and falls.

[edit 17/07/08] actually 1 of my 32meg cache hard drives keeps rising like this but never reaches the threshold 1649mb to error out as its writing ISO that fast at 114 meg a second.

You can get round this error but it involves you being present in front of your computer.

The buffered amount with 4 gig of ram on 32 bit system can go as high as 1649mb* (give or take a few mb depending on ram resources) before you get out of memory error (not enough storage space etc)

As I mentioned above you can get round this when it's writing the ISO to hard drive and you see the buffered amount rising when it reaches 100 meg or any value upto 1649 you can press pause and leave it for 5 secs or 10 secs or maybe longer if you want, anyway when you unpause the buffer will have dropped back a little, you can also watch the led on hard drive. Eg press pause. When the LED goes from red to green unpause, this will have cleared the buffer back to 0-67 mb.

At the end it may get to 99% and say time remaining 0 seconds and seem to lock up....Leave it to clear buffer and finish writing the ISO to disk.

[alxtorrentazos]

Maybe the new project is BDSHRINK? who knows.....he he

[Chetwood]

Yep, that would be my guess too.

[LoloMc]

No bug to give but just to say a little word to dvdshrink, as I did not gave you a feedback in the old days (I was NOT using shrink during the time you were coding it)

I love your software and I love what you did ! Thank you very much for what you did

Hope to see your next project soon ;)

NB : shrink is working perfectly under Linux + wine. That's SO GOOD !!!

[mister_handy]

Shrink is already multi-core - it'll create as many encoding threads as you have cores. I thought the bottleneck has always been drive speed, or maybe I just need a new drive? It takes over 20 minutes to make one pass.

I always rip to hard drive first (used to use DVD decrypter, now the free DVD Fab Decrypter) before using DVD shrink. Saves a ton of time, especially if I have multiple disks to back up - I can run 3x backups to HD at once, and DVD Shink flies going HD-to-ISO-file on a quad core, while DVD Shrink directly from the CDs takes longer.

I realize folks said "no feature requests" but one nice thing would be to be able to open an ISO file to shrink from the UI (although DVD Shrink will currently do that via file associations or the command line, just not via the UI... or if it can, I haven't figured out how)

[blutach]

@mister_handy

Ctrl-I or look in the file menu.

Regards

[oRBIT]

Maybe the new project is BDSHRINK? who knows.....he he

I'd love a BDShrink. I've tried backing up my BD's for awhile and I am pretty amazed what a complicated process it is with the tools that are available today. And the amount of tools you'll need to accomplish it is simply horrible.
I'll cross my fingers for BDShrink. :-)

[blutach]

@orbit

Now, members should take note of what dvdshrink said - there are no plans to do a new version. Hence, feature requests are not relevant in this or any other thread. Please do not inundute this thread with what "would be nice to see" etc etc. Simply give dvdshrink the feedback he wants.


Regards

[blutach]

@dvdshrink

Blame this one on M$. Having IE8 (Beta 2) installed somehow causes DVD Shrink to crash when you hit the Reauthor button. Reverting to IE7 makes all OK. But, if you are looking at things, add this to the list.

Also, FYI, when IE8 B2 is installed, Ner0 Rec0de works OK in copy main movie mode.

Regards

[Chetwood]

I'm always amazed how many people have time to test crappy beta software (from Micros~1 at that). There were so many having this issue that I added it to the FAQ (http://www.dvdshrink.org/forum/viewtopic.php?f=1&t=2396#p23445) over at dvdshrink.org. If for some weird reason you must use IE 8 you can set DVD Shrink 3.2.exe in Win95/98/ME compatibility mode (Properties > Compatibility) and it will work.

[blutach]

I saw your posts there and also the proposed fix. If you look at the error report on the M$ site (https://connect.microsoft.com/IE/feedback/ViewFeedback.aspx?FeedbackID=377770), it says that this fix is not 100%, due to ASPI issues (although I suspect that the poster may not have had ASPI installed).

Anyway, here's hoping dvdshrink can remedy the problem (if he does decide to update the program).

Regards

[Chetwood]

Since none of those posters came back after being told to switch compatibility mode I never bothered about verifying it might be less than 100% a remedy. Also because I think Vista is bloatware like Nero so I'm staying away from it ;)

[Videoman58]

A couple weeks ago I started having the same error message when I was backing up with DVDshrink, I have been using this program for a few years now. Aside from the occasional can't decrypt with DVDshrink it has worked just fine, but since early 2011 it's been more often that I’ve run across the new CSS so about 30 days ago I started using Anydvd to rip my movies to backup. I have 3 very high performance PC's, and have Mirror Dvdshrink & Anydvd on all system, the first error I got was on my Windows 7 PC quad core. I tried uninstalling Dvdshrink and reinstalling it which worked for a couple backup jobs so I switched to another PC with XP thinking it was incompatibility problems with windows 7 and dvdshrink ((NOT)). It also happened on the other systems. I thought this very odd because never ever have I had this problem before, so I started to back step what I have done in the past few weeks, maybe it was windows updates, maybe it was Norton.
So I backed out a few updates which had no effect on the problem, then I started thinking maybe another program was causing an incompatibility issue. I uninstalled DVD Decrypter, no change. I then thought to myself the only new program I have installed in the past month was AnyDvd so I uninstalled AnyDvd and (( Problem Solved )). I removed AnyDvd from all my PC's and problem solved on those as well, It must be a registery problem when both DVDSHRINK & ANYDVD are installed on the same systems. I have used DVDSHrink for 8 days now and no issues at all with it. If you have Anydvd on your system along with Dvdshrink remove either one and problem is SOLVED. If you like dvdshrink like I do then if you get and install DVDfab 8 QT which is also available in a free version, they work fine together