Jump to content

discuser

Members
  • Content Count

    46
  • Joined

  • Last visited

About discuser

  • Rank
    ISF Newbie

Profile Information

  • Gender
    Male
  1. discuser

    CD red-book audio DAO write

    Thanks for the clarification. I did already successfully write one CD-RW in red-book audio format with the WRITE MODE in CD and WRITE TYPE in DAO/SAO, and the outcome was normal, though I couldn't be absolutely sure that the disc was closed though I assumed that it was more likely than not that it would have been closed / finalized. The original reason why I set WRITE MODE to CD was that I was looking for that one control in Imgburn which would tell the program that I was writing a CD-Audio disc rather than a CD-ROM disc which had a group of WAV files but I'm fine with setting it back to AUTO mode since it was always on that mode and the program had no problems recognizing various BD-RE media I have used very successfully with it so far.. I later on found out that I apparently need to use a new CUE file in Imgburn inserted with WAV files to be written in red-book audio to produce a CD-Audio disc. Otherwise, if I used the DISC LAYOUT EDITOR, I would just end up with a CD-ROM with WAV files and not red-book audio, right? I'm going to rewrite that CD-RW a second time. I think it's probably time to replace the media because checking the error rates after writing with Opti-Dirve Control showed a rather high C1 error rate though no C2 errors. But I'm going to experiment with OPC on to see if that makes a difference with C1 error rates on an older CD-RW disc. It's all part of the experimentation / learning process for me with Imgburn.
  2. discuser

    CD red-book audio DAO write

    I was wondering about writing CD red-book audio with Imgburn. Usually, I would normally use DAO disc-at-once mode to write a single CD-audio session, after which the disc is closed / finalized. I didn't see any options in Imgburn WRITE SETTINGS for closing the disc after write. However, I did set the WRITE MODE to CD and WRITE TYPE to DAO/SAO. Do these manual settings force DAO with disc finalization / closure for red-book audio? Secondly, when I insert a writeable CD which previously had red-book audio recorded on it, which part of the DEVICE tab information CONFIRMS that it was written with DISC AT ONCE or TRACK AT ONCE, and also which part of the device information details confirms that the disc is FINALIZED / CLOSED or that it is still open for more session writes? I noticed that the DEVICE details says: Status: Complete State of Last Session: Complete Does STATUS: COMPLETE confirm disc closure / finalization and that the CD-RW can no longer be written without erasure? Regarding the PERFORM OPC BEFORE WRITE tick box, would it be more advantageous or not to enable optimum power calibration on the ODD normally, than to disable OPC? What scenarios would OPC disable be desireable with CD and DVD media? OPC is only applicable to CD and DVD media and not BD media, yes? Thanks for any clarifications.
  3. discuser

    BD-RE virgin disc write pre-erasure

    They don't have any internal slim ODDs. Sony-Optiarc had one or more such products up until nearly shutting down operations, but that option is gone too.
  4. Yes, I do normally insert blank formatted media first before using the disc layout editor. But as L-UK says, the disc layout editor (DLE) calculation is only an approximation even with inserted media, whereas the information panel calculation is the exact correct value. So if I'm using the DLE then I still have to flip back to the information tab to get the exact updated result. I don't always have the information tab AUTO box ticked because the auto calculation can generates one or more prompts depending on the files added to the DLE. So I'm currently using the information tab calculator only manually. As for my reply above, I was asking L-UK about the AUTO box in the DLE (to the right of the disc consumption bar).
  5. Thanks for confirmation of program behaviour. Your description confirms my suspicion, that the disc layout editor is just using a generic media capacity value based on the currently selected media type on the pull down menu to the right of the disc space consumption bar. I was hoping the disc consumption calculation in the disc layout editor would reflect the actual remaining free space based on media inserted, as this would now mean that when I try to pack a disc as close to maximum capacity as possible, I will have to go into the layout editor, play with adding or deleting a number of files and each time changing the file layout slightly, to go back outside to the calculator panel on the information tab to recalculate. But at least I know for sure this is the expected behaviour of the software at this time. Otherwise, my very long write and verify session to the BD-RE-TL media worked normally and in general Imgburn works very well with this media even though this BD-RE capacity wasn't readily available for testing back at the time this version of the software was released. The write-with-verify session took about 6 3/4 hours and the separate verify against source file portion took around 2 1/2 to 3 hours, which means a full 90 GB (formatted capacity with spare sectors enabled) packed BD-RE-TL disc can take nearly 10 hours to fully complete write and verification. I noticed there's an AUTOMATIC TARGET MEDIA tick box next to the layout editor's disc space consumption bar's media type menu. When that box is ticked, does this mean that the software will detect the type of disc inserted and at least select the correct media type, even if not taking into account the actual effective available space on the particular media inserted? Or does this just mean the media type required to accommodate the disc space consumption will be automatically adjusted by the software so to inform the user what media type / capacity to use?
  6. I very recently attempted to prepare a disc layout for a BD-RE-TL 100GB disc and was attempting to squeeze as many files as possible into the available formatted free space of approximately 94 GB (which may vary up or down slightly depending on whether spare sector areas are enabled and what size spare sectors were specified during disc formatting). It was noticed that there are discrepancies reported in different areas of Imgburn under varying conditions, as follows: 1. When there was NO formatted BD-RE media inserted, and the disc layout editor was used to produce a draft disc layout and the disc space consumption bar was monitored (disc type next to disc space consumption bar was manually set to BD-RE-TL in this case in the disc layout editor) when files were dropped into the layout, I added files so that it was within 1% to 2% of maximum disc space, i.e. disc consumption was 98% to 99%. After closing disc layout editor, and returning to the INFORMATION tab of Imgburn, clicking the CALCULATOR button resulted in a disc consumption result of 99% (which was correctly rounded up from 98%+ shown in the disc layout editor). 2. However, when the BD-RE-TL media was inserted into the BD writer and the relevant BD writer drive was selected in Imgburn, and the INFORMATION tab CALCULATOR button was clicked again, the INFORMATION tab now showed that the disc space consumption was BEYOND actual available free disc space on the blank but formatted media (with spare sectors enabled in preferred mode) and the information tab showed the consumption at 102% and free disc space was NEGATIVE 2 GB, both figures highlighted in red. At first I thought these discrepancies might be a bug, but then realized that the probable reason this occured is that after formatted blank media with enabled spare sectors was inserted, the effective free disc space was reduced from the initial calculation due to disc space reservation / consumption by spare sectors areas. Is this what is happening? This is the only immediately obvious logical explanation I could surmise. If this is correct, then I would need to remove some files from the disc layout to meet the reduced free space available on disc. If this is not the reason for the reduction in available free disc space calculation, then this may be a bug or due to other factors. If the reason for the available disc space discrepancy is as surmised, then I would suggest that the disc layout editor's DISC SPACE CONSUMPTION BAR PERCENTAGE also take into account the same factors that affect available free disc space. Because currently, I have observed that while the INFORMATION tab calculation takes into account actual available disc space after formatted media is inserted, the disc layout editor available free space percentage does not re-adjust to reflect this and thus there's a major discrepancy between the free space percentage reported in the disc space editor and the information tab calculation, by as much as 4%. In the above example, the disc layout editor's disc space consumption bar is a little over 98% but the information tab reports it as 102%. Thus a free disc space discrepancy of nearly 4% in this particular example. I also noticed that when the AUTO box is ticked in the INFORMATION tab, and another ODD is selected which may not have any media inserted, the disc space consumption is not updated to reflect this, even though I do understand that the AUTO box is for auto updates of disc space consumption after disc layout editor is closed rather than when the selected ODD drive is changed, but this may be a point of enhancement worth considering for a future release to maintain constantly correct calculation relative to the currently selected drive and whether it has writable media inserted where the effective available free disc space could be determined by Imgburn that could be used to update disc space consumption / free space available values.
  7. discuser

    BD-RE virgin disc write pre-erasure

    Interestingly, that BD-RE which caused problems with the NO SENSE INFORMATION error I encountered earlier on the Pioneer 06-series drive, I re-ran the erasure-formatting on the Pioneer 09-series drive again with the exact same disc and at around the same percentage location of the disc, I could hear the drive's pick up carriage seek noise ticking back and forth and the drive activity light blinking irregularly. Yet, there is no activity entry on the Imgburn log when these disc errors were encountered. This would appear to suggest that the 09-series drive is indeed handling the defect management correctly and has hidden these events behind the hardware as you described. So this would imply the older 06-series drive choked on the errors instead. It may not have performed sector reallocation correctly and/or did not handle the spare sector areas correctly. I will use the newer drive to perform erasure-formatting from now on. A bit of brain fog again on my part about the file system on an erased disc. I guess what I should have said is that an erased disc (provided that spare sectors are made available) resets the inner and outer spare areas on each disc player to full availability again, as well as clearing the defect list which should then contain no entries - until the disc's user data area is written by a BD drive which then starts to add any necessary defect entries and sector relocation as necessary / detected. I hope I got that right. If so, having understood this now, it would mean that in fact a full erasure with zero writes across the entire disc space would be beneficial as a bad sector pre-detection pass to pre-populate the defect list with any possible entries. Then the BD-RE would then be written with user data on a second write session which will respect the populated defect list from the zeroing pass and possibly add additional defect list entries if new ones are detected during the user data writing pass (such as if some sectors were marginal and escaped detection during the zeroing pass initially). From what I understand in reading up about BD defect management, the spare sector areas and defect list are cumulative as long as the BD-RE isn't re-erased / re-formatted, so the defect list should continue to accumulate and past defect entries should persist in the defect list. However, having gotten used to DAO writing with CD / DVD write-once and rewritable media, is it possible with BD-RE having already written a DAO session, to record additional sessions without full erasure? And since BD-RE is random access format, if the answer to that question is yes, then it is possible that the next write to the disc could start at any spot within the remaining free space and not necessarily immediately following the end of the last writing location? If so, what write mode should be used? DAO or something else?
  8. discuser

    BD-RE virgin disc write pre-erasure

    I've done some internet searches on the subject of NO SENSE INFORMATION in terms of ODD writing and also found some past threads on this forum from users with similar errors. I think it amounts to some spots of unreadable disc areas, possibly on a low level in terms of tracking logical blocks or sectors or something to that effect, but essentially means that disc area is inaccessible / unuseable. Tell me if I'm understanding this correctly now, after having used Imgburn for a while now lately. I'm seeing that the erase-formatting procedure in the program defines the use of defect management or not merely when the "directory" or "header" area is of the UDF is initially (re-)written during formatting. Beyond that, the zeroing of the entire disc area during the full erasure procedure is operationally exactly the same as the user writing their own data, with the difference being only in the data written to the disc where the former is just the ODD software sending data-zeros to the hardware (with no separate verify phase later performed after zeroing completion) and the latter sending user data from a source. But on the drive / hardware level, functionally there is no difference in the write operation between zeroing the disc space or writing user data, and that the drive would handle defect management and bad sector relocation as an operation completely shielded from the ODD software (Imgburn) itself, provided the initial formatting of the file system enables spare sectors. So I think this would make sense to me why disc space zeroing over detected disc defects should not result in an activity log event (per your explanation) provided spare sectors aren't fully depleted.
  9. Don't really have use for U-HD playback on the computer myself, so since Pioneer is charging almost twice for the 11-series at the moment, I just ordered another premium S09 drive, whose inventory is nearly all depleted now but was available almost at the same price I bought the first one four years ago when 09-series was first released. 09 series has had a good four year run. At some point I might consider the S11-J-X ultra-high end version but that's just nice to have, not a must have. I hope I never have to deal with DVD-RW/+RW media again.
  10. discuser

    Verying X/TL and QL BD media

    Yes, but BDR-2XXDBK is not the same drive as BDR-2XXM. They did use the M suffix in the first generation of products that supported BDXL, namely the 07-series, but the M suffix is no longer used since 08-series, even if M is used internally to reference whether a drive supports BDXL or not. They are using geographical suffixes nowadays. So you could say that BDR-2XXM could refer to BDR-2XXJBK/UBK/EBK.
  11. 09-series is officially a discontinued product. Only the new 11-series is current, even though Pioneer USA web site still lists 09-series products.
  12. discuser

    Verying X/TL and QL BD media

    BDR-209DBK has no BDXL media support and has deleted (D) support for DVD-RAM media (hence the D suffix). BDR-209UBK has BDXL media support and is for North American region (USA / Canada). BDR-209EBK is for European region, BDR-209JBK is for Japan domestic region. All drives are OEM versions with no software bundling, no retail packaging and plain drive bezel. BDXL media support has been present since 07-series. BK suffix is just simply black bezel, because in Japan, previously there was a choice of W white bezel and KR which is another dark colour close to black that is no longer available since 09-series.
  13. Not all BDR-209 BD writers don't support BDXL media. There are 4 sub-versions of BDR-209. North America gets the worse version of course, which is the BDR-209DBK and that is the only sub-version of BDR-209 that doesn't support BDXL and DVD-RAM media. Without specifying the drive model suffix, it's not possible to determine the exact drive specs.
  14. discuser

    Verying X/TL and QL BD media

    With BD-RE media I get up to around 5X to 6X or thereabouts at maximum speed. It's clear to me that the drive is under CAV mode during BD-RE reading. When I said 09-series, I'm just referring to the drive generation, which started with 02 series - BDR-202. It went from 02 to 11 at present day. 09 is the previous just discontinued series. The official current series is the 11-series which has U-BD/U-HD playback capability with lots of very specific system requirements. Mechanically, performance wise each series is basically identical amongst variations with some minor differences from enhancements. Pioneer BDR-209xBK, where X may be one of three possible suffixes, is the OEM version with no software bundle, basic embossed drive bezel and no retail packaging. The BDR-2209 is a product version for North America (USA / Canada) distribution with licensed bundled software in English language. If the user doesn't want bundled software they can choose the OEM version. In general, both are essentially the same drive and performance with minor differences. But the 09-series product has 9 sub-versions for different geographical regions and each sub-version has difference enhancements (some significant and some minor) even though the basic drive is the same in performance.
  15. discuser

    Verying X/TL and QL BD media

    On my all my Pioneer BD writers all BD-RE media verifies only at constant 2X speed. Could never figure out why as I wish it would go faster. I suppose the up side of it is that when it reads at a low speed of 2X and the data can be read error free, it means that in the worse case it could read slowly and the data is error free. It only happens during the verify phase of ODD software, but during normal reads it does read up to 6X depending on data position as I have also confirmed this performance characteristic with with Opti-Drive Control. I have a Pioneer 09 series drive as well.
×

Important Information

By using this site, you agree to our Terms of Use.