View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0002449 | MMW v4 | Burning / Disc Handling | public | 2006-04-04 12:58 | 2006-06-01 19:43 |
Reporter | peke | Assigned To | |||
Priority | immediate | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 2.5 | ||||
Fixed in Version | 2.5.3 | ||||
Summary | 0002449: MM Can't Burn Data DVD | ||||
Description | No matter what I sellect MM in burning Wizard as soon as I insert Empty DVD detects that DVD can Be only Written on 5x which is unsupported by my Burner (NEC ND-3540A). | ||||
Additional Information | That Includes x-wave DVD-R(8x), Verbatim DVD-+R(16x) & -+RW(4x) also it reports burner as 6x only which is Wrong it can burn up to 16x in other. Tested on various Firmwares of DVD Burner including original one. Burning Audio CDs and Data CDs is OK. I have installed ForceASPI 1.8 (4.70.2) | ||||
Tags | No tags attached. | ||||
Fixed in build | 1000 | ||||
|
As 5x unsupported speed it inits and simulate(same goes for burn) then it can't close disk and it is unreadable even I try RAW access to DVD ISO Structure. Note: HPCDE.Log is uploaded on FTP |
|
Topics on Forum: http://www.mediamonkey.com/forum/viewtopic.php?t=9162 |
|
Thx. Peke, it should be fixed in build 962. Previously the possibility of setting this speeds was tested by hpCD-engine, but as you mention there was a problem that in case of some DVDs the engine returns only 5x speed despite the fact that another speed could be available. By reason that in one demo program of hpCDe they use settings of speeds without testing, it is preferable for now. In addition it should work fine. Please, test it and let me now if there is still a problem. Thanks. The changed PMP3Datab.exe (MediaMonkey.exe) is uploaded on FTP. |
|
Ok I have retested it with Uploaded exe. Now it allows me to select 2x, 4x, 6x only. Burner is Still found as DVD-RW 6x only even it is 16x I uploaded new hpCDE.log and added Saved Infos from Nero InfoTool 3.00 and 4.03 It may help in debuging. Edit: Information found on Empty DVD is same DVD on which all tests are based. |
|
Yes, same to me. 16x certified DVD is recognized by Nero at 16x, but by using MM or engine's demo the method returns only 6x for max. write speed. So I guess that we can do nothing about this. |
|
OK, If we look more closely the problem is related to Reading Manufactured ID (MID)and collecting info regarding that CD Type. This will make big Big Problems in future. I'll see if Firmware update changes anything, but from my point it looks that problem is in Engine detection/reading info. Confirmed that Firmware changes do not affect in MM, as addition same thing happen when I try to burn on Verbatim DVD-RW and DVD+RW (4x max) and X-Wave DVD-+R (8x) it is more likely that problem is in hpCDE Engine. @Ludek Can you confirm that same thing happen in older versions of MM and different hpCDE.dlls? I remembered that in one test versions of MM 2.5 I have tested and confirmed that burning is working OK. |
|
Reminder sent to: rusty |
|
fyi, we're planning on getting the new hpcde engine for the next release of MM. |
|
I have retested it with new hpCDe v 1.96 and the problem of bad recognizing maximum speed of Verbatim 16x DVD+R seems to be still actual :-( It shows only 6x as max. speed. |
|
Testing note: verify that MM degrades gracefully if the user chooses to burn at a speeed that is higher than the supported h/w & disc. |
|
I did some preliminary testing on 2.5.3.961 and the feature seems to be a bit strange in the sense that: -my drive supports 24x burning for CD-R and 4x burning for CD-RW -the media support 4x burning for CD-RW Yet, when I try to burn the CD-RW, I'm given the option of burning at 24x!! Is this what we intended to do? i.e. to completely ignore both the Hardware capabilities and the Media capabilities? I thought that we only wanted to ignore Media capabilities because they are sometimes inaccurate, but I'm no longer certain. I have to say, though, that the current design seems strange since it presents speeds that the user _knows_ aren't supported. |
|
I forgot to mention in note 0007117 that I changed the implementation (in 2.6) in order to add all even speeds less than max write speed. [2x,4x,.....,max Write Speed] i.e. When max write speed is 6x, previously all [1x,2x,3x,4x,5x] were tested by and engine returned only [5x], which was wrong. Now should be available [2x,4x,6x] similar like in engine's demo sample. The whole problem is that engine seems to return wrong values for GetMaxWriteSpeed() method. |
|
But can MM differentiate between the Max Write speed for a -R vs -RW disc? What about the Max Write speed for a CD vs DVD? e.g. for a CD-RW, I would expect that MM should, on my drive, show the highest speed as 4x. e.g. for Verbatim disk on Peke's machine I would expect that MM would show 6x, 4x, 2x Please clarify. |
|
Yes, it is hard to understand what exactly the virtual int GetMaxWriteSpeed() method does. Because its destription in hpCDe doc says: "Gets the maximum write speed supported by the device. This method returns different values for DVD and CD media." But when I insert CD-RW 8x-10x compatible, the 10x is recognized as MaxWriteSpeed, which is right, but it doesn't consist with description above, cause it seems to be max speed of the inserted medium and not max speed supported by device. My results for max speeds are: DVD-R 16x certified - MM 6x - Nero 16x DVD+RW 1x-4x certified - MM 6x DVD-RW 6x certified - MM 6x CD-R 48x - MM 48x - Nero 48x CD-R 52x - MM 52x - Nero 52x CD-RW 8x-10x compatible - MM 10x - Nero 10x CD-RW 2x-4x compatible - MM 4x - Nero 4x So there hpCDe could clarify it, it seems to recognize badly for DVDs. |
|
My Results: DVD-R 16x certified - MM 6x (Available 5x and it is unsuported by my burner) - Nero 16x DVD+RW 1x-4x certified - MM 6x (Available 5x and it is unsuported by my burner) - Nero 4x DVD-RW 6x certified - MM 6x (Available 5x and it is unsuported by my burner) - Nero 6x CD-R 48x - MM 48x - Nero 48x CD-R 52x - MM 52x - Nero 52x CD-RW 8x-10x compatible - MM 10x - Nero 10x CD-RW 2x-4x compatible - MM 4x - Nero 4x So I came to same conclusionb like Ludek |
|
Btw. My drive: _NEC DVD_RW ND-3540A, Type DVD±R/RW DL Recorder, Firmware 1.01 My drive's supported speeds detected by Nero for DVDs: [1,5,8,12,16] So in summary the problem we are pointing to is that GetMaxWriteSpeed() returns wrong result only in case of all kinds of DVDs. Currently, I don't see no way to get a complete list of supported speeds. hpCDe should clarify why its demo samples and GetMaxWriteSpeed() returns always 6x as max. speed for all kinds of DVDs and if exists some way to get list of supported speeds, cause hpCDe demos don't test it (only add max. and some smaller speeds) and our test used in 2.5 if (pDevice->SetWriteSpeed(i) && pDevice->GetWriteSpeed()==i) satisfy only for [5x] from set of {1,2,3,4,5,6} speeds. Note 1: for CDs the 'virtual int GetMaxWriteSpeed()' works fine - returns the desired MINimum of ( MAX speed supp. by device, MAX speed supp. by medium), but I would expect same behaviour for DVDs! Note 2: Another strange thing is that by using hpCDe's functions we can set only speeds that are _INTEGER_ elements (integer type - e.g. 1,2,3,....,n), but Nero sometimes gives us speed like 2.4 in its list of speeds. |
|
Testing build 966. Just noticed that: a) By default it displays lower available speeds first. It should display highest available speeds first AND default to the highest speed. b) It displays a speed of '0.0x (2kbps)'. It shouldn't display any speeds < 1x. c) If MM isn't 'Gold' then the user gets a warning message that they can't burn CDs at > 4x, even when attempting to burn a CD at 4x. |
|
Fixed in build 1000. |
|
Tested 2.5.3.967 a) fixed c) fixed b) partially fixed. The problem is that when the user steps through the wizard, but no CD is inserted, the following speeds appear: .3x [Default] 6.1x 5.1x 4.1x 3.1x 2.0x 1.0x Then when I insert a 2x DVD, the following appears: 2.0x [highlighted] 4.0x 2.4x Or for a 4x DVD, the following appears: 2.0x 48.0x 40.0x ... So there are 2 issues to fix: b1) The fact that non-sensical speeds appear when no Disc is inserted b2) The fact that the speeds are listed in a strange order In addition, when I insert a CD-R in another machine, the following speeds are shown: 23.9x 23.9x 23.9x 23.9x 23.9x 23.9x This implies 2 other issues that should be fixed: b3) Identical speeds shouldn't be listed more than once b4) Speeds should be rounded up or down if they are within .2 of a round number. (i.e. 23.8, 23.9, 24.1, 24.2 should all be listed as 24.0x). |
|
Fixed in build 1000 (968 for MM 2.5.3). - The issues should be fixed now, except for b1) - I can't influence values returned by hpCDe. |
|
Tested the revised hpcde.dll and in summary b1, b3, and b4 are fixed, however b2 is still open. Here are the test results: Laptop: CD-R (Gold): 24x (Why no other speeds listed?) CD-RW (Gold): 4x, 2x (correct) Desktop: Nothing (Free): .3x, 6x, 5x, 4x, 3x, 2x, 1x DVD+RW 4x (Free): 2.0x, 4.0x, 2.4x (MM Free) Nero shows: 4.0x, 2.4x DVD+RW 2x (Free): 2.0x, 1.0x (correct) CD-R (MM Free): 2x, 48x, 40x, 32x, 24x, 16x, 8x (I suggest we should show 4x and 2x in the correct order iff there's a speed higher than 4x available) CD-R (MM Gold): 48x, 40x, 32x, 24x, 16x, 8x note: Nero doesn't show 2x and 4x either DVD-R (Free): 2.0x, 4.0x, 2.4x DVD-R (Gold): 4.0x, 2.4x Nero shows: 4.0x, 2.5x To summarize: b2i) When MM Free is installed, we shouldn't change the order of displayed speeds, we should just use a default that makes sense. b2ii) In some cases, both Gold and Free, supported speeds are missing, and I'm not sure why. Revised conclusion, based on the Nero results: -For the free version, we _should_ add default speeds that enable testing of the burner, even if they aren't reported by the engine IFF the burner supports at least one speed higher than these: 4x, 2x for CD-R/RW, and 2x, 1x for DVD. -These 'unsupported' speeds should be listed in the correct order. -On a system with no 'saved' speed, the default should be the highest supported speed, given the constraints of the hardware and the MM license (I believe that this is already the case) |
|
Verified 2.5.3.968. |