Log in

View Full Version : DVD Shrink V3.1 Bug?


ron spencer
10th January 2004, 02:26
Well V3.1 seems cool but:

I have a properly registered version of Nero 5.5.10.54 and IT WORKS as it should by iteself. However, when I hit backup in DVDShrink it pops-up and says my Nero serial is not good (how would DVDShrink know anyway?). I don't think DVDShrink should be doing this.

Also, has the transcoding engine changed?

ron

mrbass
10th January 2004, 02:28
Perhaps your legit serial somehow got on Nero's serial blacklist. I'm sure they'll reissue you a key if you contact them. Usually if it is blacklisted it may not burn at all or burn only at 1X (?).

Transcoding engine from 3.0beta5 has not changed. If you were using 2.3 then for you it has changed because 'deep analysis' would be new to you.

ron spencer
10th January 2004, 02:43
You mean to tell me that DVDShrink is checking NERO serial numbers?
I most certainly can burn...just did a 4x DVD burn with Nero on its own. It is DVDShrink that is giving me the error and NOT NERO. Please let me know before I contact them.

mrbass
10th January 2004, 02:49
DVDShrink is checking to see if Nero is bombing out so DVDShrink doesn't crash..that's all. This is nothing new. Imgtool did the same thing. Say you clicked to burn with imgtool and nothing would happen even though you had nero installed. It was most likely due to your serial # being blacklisted. I have a feeling there's gonna be a huge slew of this.

Remember you needn't burn with Nero it's just an option. You can output your encoded video files just like before to your harddrive and use your favorite dvd burning software. There's also AutoShrinkIso (http://mrbass.org/dvdsrhink/autoshrinkiso) that'll automate the process of creating an .iso and burning that .iso with DVDDecrypter and that's free. Also today NYPlayer added CopyToDVD support so you could use that too if you wish.

Maybe you should ask in this forum. (or me or dvdshrink himself)
Nero SDK Discussion Forum (http://club.cdfreaks.com/forumdisplay.php?s=&forumid=73)
This is the official support forum for the Nero Software Development Kit (SDK). The forum is monitored by Ahead engineers

Because all DVDShrink is doing is using the NeroSDK (also referred to by NeroAPI).

ron spencer
10th January 2004, 02:53
Thanks..but NERO is NOT bombing...it runs perfectly...As I said I just used it to burn at 4x without using DVDShrink. Does DVDShrink check the serial? I certianly hope not...would be underhanded I think.

ron spencer
10th January 2004, 02:55
I guess NeroAPI within Shrink is checking then? Yes I know about the ISO thing, thanks for reminding me.

ron

mrbass
10th January 2004, 03:08
These are the relevant portions of the changelog. So it's probably the detection algorithm or exception handlers...over my head stuff.


Wrapped NeroAPI code in exception handlers: if a crash occurs
within Nero, then DVD Shrink should be able to continue (without
burning functionality).

If error occurs during Nero initialization (demo version expired,
etc) then burning is disabled and backup dialog displays hyperlink
to http://www.nero.com instead. Backup to hard disk will function
normally.

ron spencer
10th January 2004, 03:28
well DVDShrink does work fine in any case. I get no message to link to nero url.

Might be a good idea for DVDShrink to NOT use Nero API unless user chooses nero to burn in the drop down section that way no error message would pop-up. DVD Shrink remembers user pref so error would not occur again unless the nero option checked again Ok otherwise.

mrbass
10th January 2004, 04:17
http://forum.digital-digest.com/showthread.php?s=&threadid=30480&perpage=15&pagenumber=2

dvdshrink has nailed it. Do you think this is related to your problem?

ron spencer
10th January 2004, 19:16
I read the thread....seems others have the exact same issue. Very strange. I look forward to the update as it is a pain to see the error come up.....I am greatful that it is free though. Should be a quick fix though as would be a user pref. Any idea on a release.

Also, V3.1 takes longer to exit. Any idea why? Have you tried V3.1 with Recode V2...just wondering if Recode has a different transcoding engine.

As always thanks for your superb help.