DVD FAB Products Discussion Thread

[StormJumper]

Good to hear from you my old friend, its good to have you jump in. Thank you. I know and that's why I set it to RECOMMENDED so that it would honor the ImgBurn speeds and it did for a while as a bypass but now it somehow manages to further spooge it so that nothing can be done but MAX which is why I am frustrated. I just used a hardware memory adjuster to cap the hardware speed at 4x so that when it forces MAX, it gets 4x like I want, instead of going to the device max of 16x.

hmmm sorry didn't read all of your other posts on this guess I should huh!!, but have you tried uninstalling ImgBurn and re-installing it ? also you sure your hardware memory adjuster <- is not the cause of this issue ?

[GµårÐïåñ]

Good to hear from you my old friend, its good to have you jump in. Thank you. I know and that's why I set it to RECOMMENDED so that it would honor the ImgBurn speeds and it did for a while as a bypass but now it somehow manages to further spooge it so that nothing can be done but MAX which is why I am frustrated. I just used a hardware memory adjuster to cap the hardware speed at 4x so that when it forces MAX, it gets 4x like I want, instead of going to the device max of 16x.

[StormJumper]

Same here, I don't get how it can be configured, sitting there, detected and not know the MID. Nothing has changed and it works just fine at full speed, just not when configured to respect a specific speed. Neither DVDFab or ImgBurn respect it anymore and I suspect is because of how DVDFab sends the values, because it burns at the right speed if the burn is initiated WITHIN ImgBurn, so that tells me its not ImgBurn but DVDFab that is causing the problem by not sending the right values and further breaking something that was already broken but was working using a bypass.

If you have DVDFab setup to use ImgBurn and the write speed in DVDFab is set to any other then "Recommended" it can cause a conflict with the burn speed, at least for me anyway.

.02 cents tossed in

SJ

[GµårÐïåñ]

I'm not sure how one could setup AWS with ImgBurn not knowing the MID.

Same here, I don't get how it can be configured, sitting there, detected and not know the MID. Nothing has changed and it works just fine at full speed, just not when configured to respect a specific speed. Neither DVDFab or ImgBurn respect it anymore and I suspect is because of how DVDFab sends the values, because it burns at the right speed if the burn is initiated WITHIN ImgBurn, so that tells me its not ImgBurn but DVDFab that is causing the problem by not sending the right values and further breaking something that was already broken but was working using a bypass.

[Bob]

I'm not sure how one could setup AWS with ImgBurn not knowing the MID

Edit:

I still haven't had anything to burn to try it out yet sorry.

[90312]

It's my guess that if you rip it to the hard drive and try to burn it with Fab shut down and just ImgBurn, AWS still won't work because it's not picking up the MID.

[GµårÐïåñ]

Yeah I have tried HP ones, Verbatim, Taiyo, Ritek and still same result. This is why I find it asinine that we have to hard code it anyway, because I mean for god sake we should be able to change discs without first having to make sure it is hard coded so it works. But at least when it IS hard coded, it should god dang work. Its so frustrating the amount of hoops you need to jump through to get something that should work as-is and out of the box to work. Its getting ridiculous.

[90312]

Have you got another brand of blank to try? It looks as though it's not picking up the MID on the HPs.

[GµårÐïåñ]

Still no go. It has been configured hard wired like before and as shown in the screen shots according to all present instructions and was working fine before but now it doesn't and it won't respect the selected choices by itself either. So I am at a loss now, WTF?

[Bob]

Happy Caturday everyone

[GµårÐïåñ]

I don't know if it will help or not, I'm just saying.

I will give it a shot and get back to you, we'll see how it goes.

[90312]

I don't know if it will help or not, I'm just saying.

[GµårÐïåñ]

BTW version 2.5.2.0 was released Sept. 1, that's fairly recent.

Yes but I have not updated it since 2.5.1.0 to avoid just this kind of thing, the old saying why fix it if it ain't broke. But I see your point, you think the update might fix this issue? Either way, I will go ahead and install it but still makes no sense to me why its ignoring it.

[90312]

Doesn't seem like it. But here is the reason I am convinced its DVDFab and not ImgBurn because frankly ImgBurn hasn't been updated in a long while, .

BTW version 2.5.2.0 was released Sept. 1, that's fairly recent.

[90312]

I just tried 8.0.2.4 AGJ and it worked fine, AWS set the speed and burned excellent. I also hooked up a USB drive that had never been connected before and inserted a blank disk, AWS picked it up right away based on the MID in discovery mode. Now I’m sure it must pick up the MID during discovery or it won’t set AWS.