I don't know if the forum is the right place for this post. If not, could someone let me know how I should have done this? It seems to be a bit dense for the forum, or at least this part of it.
I was wondering if Fengtao could renew their Nero support. Nero 10 Multimedia Suite does not seem to be directly supported (at least under Windows 7 - 64bit). However, I think that could easily be fixed. Here are three well-defined bugs (to get this started?) that it would be really nice to have fixed:
1. When the user clicks "OK" after selecting "Nero Burning ROM" as the burning engine, DVDFab inspects several registry values looking for the directory location of nerocmd.exe, before actually committing to set the burning engine to Nero Burning ROM. Unfortunately, with a clean (no previous Nero information) Nero 10 Multimedia Suite installation, the registry values checked no longer contain that directory location, so this validation-type routine fails (silently), and the burning engine is not switched to Nero even though the user may have entered the correct location in the text box. A user work-around might be to use a registry editor to add the directory location to one of the inspected registry values. I chose to add the directory location to the "\HKLM\Software\Wow6432Node\Nero\Shared" key by entering a new string value named NeroAPISxS and setting its value to the directory location of nerocmd.exe (in my case, it was the default location of "C:\Program Files (x86)\Nero\Nero 10\Nero Burning ROM"). Without users performing some sort of workaround like this, it seems that at least some of them (me included) will not be able to set Nero Burning ROM as their DVDFab burning engine.
2. Once the engine is in use, DVDFab emits incorrect command line arguments to nerocmd in at least two cases (in the Blu-Ray Copy module) and possibly more. The two cases suggest that the DVDFab software has not been updated to take into account the possibility of writing to blu-ray media. For the first example...
In the case of extracting the main movie from a blu-ray disc and creating an ISO file, DVDFab seems to emit the following command line arguments:
--write
--real
--recursive
--create_udf_fs
--udf_revision udf_250
--drivename "Image Recorder"
--output_image "NameAndLocatinOfIsoFile.iso"
--error_log "NameAndLocationOfErrorLog.log"
--iso "NameOfVolume" "Correct Directory Location(s)"
This fails because there is too much data to write. What needs to be added to the command line arguments is the blu-ray media type. In my case, I added:
--media_type media_bd_any
to get this to work.
3. As another example of incorrect command line arguments, take the case of where DVDFab trys to burn a blu-ray disc from an iso file: it emits (in my case):
--detect_non_empty_cdrw
--write
--real
--dvd
--no_user_interaction
--detect_non_empty_cdrw
--force_erase_cdrw
--booktype_dvdrom
--verify
--drivename F
--speed 6
--error_log "NameAndLocationOfErrorLog.log"
--image "NameAndLocationOfIsoFile.iso"
This doesn't work for similar reasons. In my case, I removed "--booktype_dvdrom" entirely and changed some other arguments as follows:
--write
--real
--underrun_prot <== not necessarily required, but perhaps helpful
--media_type media_bd_any <== replaces --dvd
--no_user_interaction
--detect_non_empty_disc <== replaces --detect_non_empty_cdrw (duplicated)
--force_erase_disc <== replaces --force_erase_dvdrom
--verify
--drivename F
--speed 6
--error_log "NameAndLocationOfErrorLog.log"
--image "NameAndLocationOfIsoFile.iso"
I don't have the current nerocmd manual, so I don't know if the changes I made are optimal or will always work, but at least they confirm that the bugs observed seem to be with the command line strings that DVDFab emits, as opposed to the operation of nerocmd.exe.
Hopefully, somebody can work in this area???? I have found Nero to be well maintained and reliable enough compared to other products that I would think Fengtao would want to keep it as a burning option. (No, I am not and never have been connected with Nero in any way, other than having purchased it.
)
Regards.
Ed S.
I was wondering if Fengtao could renew their Nero support. Nero 10 Multimedia Suite does not seem to be directly supported (at least under Windows 7 - 64bit). However, I think that could easily be fixed. Here are three well-defined bugs (to get this started?) that it would be really nice to have fixed:
1. When the user clicks "OK" after selecting "Nero Burning ROM" as the burning engine, DVDFab inspects several registry values looking for the directory location of nerocmd.exe, before actually committing to set the burning engine to Nero Burning ROM. Unfortunately, with a clean (no previous Nero information) Nero 10 Multimedia Suite installation, the registry values checked no longer contain that directory location, so this validation-type routine fails (silently), and the burning engine is not switched to Nero even though the user may have entered the correct location in the text box. A user work-around might be to use a registry editor to add the directory location to one of the inspected registry values. I chose to add the directory location to the "\HKLM\Software\Wow6432Node\Nero\Shared" key by entering a new string value named NeroAPISxS and setting its value to the directory location of nerocmd.exe (in my case, it was the default location of "C:\Program Files (x86)\Nero\Nero 10\Nero Burning ROM"). Without users performing some sort of workaround like this, it seems that at least some of them (me included) will not be able to set Nero Burning ROM as their DVDFab burning engine.
2. Once the engine is in use, DVDFab emits incorrect command line arguments to nerocmd in at least two cases (in the Blu-Ray Copy module) and possibly more. The two cases suggest that the DVDFab software has not been updated to take into account the possibility of writing to blu-ray media. For the first example...
In the case of extracting the main movie from a blu-ray disc and creating an ISO file, DVDFab seems to emit the following command line arguments:
--write
--real
--recursive
--create_udf_fs
--udf_revision udf_250
--drivename "Image Recorder"
--output_image "NameAndLocatinOfIsoFile.iso"
--error_log "NameAndLocationOfErrorLog.log"
--iso "NameOfVolume" "Correct Directory Location(s)"
This fails because there is too much data to write. What needs to be added to the command line arguments is the blu-ray media type. In my case, I added:
--media_type media_bd_any
to get this to work.
3. As another example of incorrect command line arguments, take the case of where DVDFab trys to burn a blu-ray disc from an iso file: it emits (in my case):
--detect_non_empty_cdrw
--write
--real
--dvd
--no_user_interaction
--detect_non_empty_cdrw
--force_erase_cdrw
--booktype_dvdrom
--verify
--drivename F
--speed 6
--error_log "NameAndLocationOfErrorLog.log"
--image "NameAndLocationOfIsoFile.iso"
This doesn't work for similar reasons. In my case, I removed "--booktype_dvdrom" entirely and changed some other arguments as follows:
--write
--real
--underrun_prot <== not necessarily required, but perhaps helpful
--media_type media_bd_any <== replaces --dvd
--no_user_interaction
--detect_non_empty_disc <== replaces --detect_non_empty_cdrw (duplicated)
--force_erase_disc <== replaces --force_erase_dvdrom
--verify
--drivename F
--speed 6
--error_log "NameAndLocationOfErrorLog.log"
--image "NameAndLocationOfIsoFile.iso"
I don't have the current nerocmd manual, so I don't know if the changes I made are optimal or will always work, but at least they confirm that the bugs observed seem to be with the command line strings that DVDFab emits, as opposed to the operation of nerocmd.exe.
Hopefully, somebody can work in this area???? I have found Nero to be well maintained and reliable enough compared to other products that I would think Fengtao would want to keep it as a burning option. (No, I am not and never have been connected with Nero in any way, other than having purchased it.
)Regards.
Ed S.