View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002374 | MMW v4 | Burning / Disc Handling | public | 2006-02-16 19:42 | 2006-06-08 21:39 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | sometimes |
| Status | resolved | Resolution | fixed | ||
| Fixed in Version | 3.0 | ||||
| Summary | 0002374: Burns often fail when the source is a network drive | ||||
| Description | Disc burns with MM often fail if the source of some tracks is a network drive. If some of the source content is on a network drive or if tracks are auto-converted, MM should cache the image locally first. Options are: 1) Do this automatically 2) Do it manually If it's automatic, MM would just enable caching whenever burning tracks that are on the network or an external drive. Re. the manual approach, Nero has caching, and it's enabled by default. They have the following two options: [x] Cache files from disk and network [x] Cache files smaller than _64_ KB We could have something similar along the lines of: [x] Cache tracks from network and external drives ...but does MM know if a drive is external?? | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
It's hard to decide what to cache (which drive is slow, which isn't). I think it's too much to ask for MM to handle this. Does Nero handle this somehow? Or, maybe we could add an option to create an image instead of burning, it would help in such a case. |
|
|
Yes, it doesn't need to be automatic. Nero has caching, and it's enabled by default. They have the following two options: [x] Cache files from disk and network [x] Cache files smaller than _64_ KB I supposed what we need is something similar along the lines of: [x] Cache tracks from network and external drives ...but does MM know if a drive is external?? |
|
|
Ok, let's make it the suggested way, assigning to Ludek. |
|
|
I found SetCacheNetworkFiles() and SetCacheSmallFiles() methods in hpCDe doc. I've switched on - both these methods without any UI changes. i.e. Added caching both network and small files automatically. I haven't tested, but should work fine according to hpCDe engine. |
|
|
According to hpCDe documentation, SetCacheSmallFiles() (and SetCacheNetworkFiles() files probably too) really caches only if data source is a file. However, we use streams as data sources and so I think caching can't work as currently is implemented. I'd suggest to wait until we use Unicode enabled hpCDe, then it will be possible to use these methods, because we will probably use file sources instead of streams there (or at least we'll decide then). In any case some user interface should be added then, e.g. something as Nero has. My idea about this is that generally we don't have 'small' file (only .m3u and they are always created locally in a temporary folder) and so we only need an option: [x] Cache files from network |
|
|
Just a note: it's likely that in the future we'll want to write small Album Art files to a CD/DVD, in which case support for small files will be needed. Jiri mentioned that this can be resolved by caching such files automatically when they're source is a network drive. |
|
|
Raising to immediate & assigning to Jiri to undo the changes made for 2.5.3 RC-3. Afterwards, I'll re-assign to Ludek to properly fix for the next major release. |
|
|
Fixed in build 963. The following code was removed until it's fully fixed in MM 3.0 (as outlined above): pDataCD->SetCacheNetworkFiles(TRUE); pDataCD->SetCacheSmallFiles(TRUE); |
|
|
Tested 5.2.3.961 and burning seems to work correctly. Re-opening as urgent for 3.0. |
|
|
Cause we have already enabled unicode for data burning (bug 0002173) I've enabled caching of network files by using the method pDataCD->SetCacheNetworkFiles(TRUE); GUI has been constructed as described above, i.e. [x] Cache files from network checkbox on "Burn settings" page. I haven't tested it so it should be. |
