1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Where is Nero Wave Editor at the newer version of Nero?

Discussion in 'Nero discussion' started by happy hopping, Mar 20, 2021.

  1. happy hopping

    happy hopping Member

    Joined:
    Mar 20, 2021
    Messages:
    31
    Likes Received:
    0
    Trophy Points:
    6
    I own 2010 and 2017, but since it costs to upgrade to 2020, I won't do it. As Ashampoo gives out free version (home ver), no charge.

    I'll do the Sony BD-RE and post the error in a moment
     
    Last edited: Mar 28, 2021
  2. aldan

    aldan Active member

    Joined:
    Mar 24, 2007
    Messages:
    1,733
    Likes Received:
    37
    Trophy Points:
    78
    i think what wither is suggesting is an update of your nero products,and not an upgrade to a newer version.big difference.
     
  3. wither 1

    wither 1 Regular member

    Joined:
    Nov 29, 2019
    Messages:
    416
    Likes Received:
    16
    Trophy Points:
    28
    The Nero forum closed last November. I was the primary responder there for 12 years.

    Burning Rom uses something called UltraBuffer and you can watch the buffering action during the burn. It would throw up a visible error message if buffering became a problem.

    Also note that Nero WaveEditor became a free app around 2014.

    I didn't see the other responses before I posted this but, yes, I wanted the author to update v2017. This is free "update" and is not an "upgrade" to a new version of the software for which one has to pay for.
     
    aldan likes this.
  4. happy hopping

    happy hopping Member

    Joined:
    Mar 20, 2021
    Messages:
    31
    Likes Received:
    0
    Trophy Points:
    6
    So just do another "attempt " burn on a Sony 100GB BD-RE 2X media, this disc has only been used to find what's going on w/ the 100GB media, and is brand new. The media is made in Japan, as good as it can get

    the disc burning stops within the first 15 sec., says Burn Process failed at 2X, "Could not perform Write", Write Error"

    I want to point out that each day, using Nero 2010, I burn 1 to 2 x CD-R, and each month, I burn 1 x 50GB BD-R. There is no problem burning any of these disc in the past few years. The only problem occurs w/ burning 100GB media.
    Here's the log
    ====================================================
    Windows 7 6.1
    AMD64
    Wow64Process
    WinAspi: -

    NT-SPTI used
    Nero Version: 10.0.7.100
    Internal Version: 10,0,7,100

    Recorder: <PIONEER BD-RW BDR-207M>Version: 1.60 - HA 1 TA 0 - 10.0.7.100
    Adapter driver: <Serial ATA> HA 1
    Drive buffer : 4000kB
    Bus Type : via Inquiry data
    CD-ROM: <PIONEER BD-RW BDR-207M>Version: 1.60 - HA 1 TA 0 - 10.0.7.100
    Adapter driver: <Serial ATA> HA 1

    === Scsi-Device-Map ===

    === CDRom-Device-Map ===
    PIONEER BD-RW BDR-207M G: CdRom0
    =======================

    AutoRun : 0
    Excluded drive IDs:
    WriteBufferSize: 83886080 (0) Byte
    BUFE : 0
    Physical memory : 4095MB (4194303kB)
    Free physical memory: 4095MB (4194303kB)
    Memory in use : 66 %
    Uncached PFiles: 0x0
    Global Bus Type: default (0)
    Check supported media : Disabled (0)

    29.3.2021
    UDF compilation
    4:39:45 AM #1 Text 0 File SCSIPTICommands.cpp, Line 461
    LockMCN - completed sucessfully for IOCTL_STORAGE_MCN_CONTROL

    4:39:45 AM #2 Text 0 File Isodoc.cpp, Line 6913
    UDF document burn settings
    ------------------------------------------
    Determine maximum speed : FALSE
    Simulate : FALSE
    Write : TRUE
    Finalize CD : FALSE
    Multisession : TRUE
    Multisession type: : Start multisession
    Burning mode : DAO
    Mode : 1
    UDF Mode : pure
    UDF Options : automatic
    UDF Revision : 1.02
    UDF Partition Type : physical

    4:39:46 AM #3 Text 0 File compose.cpp, Line 874
    GenUDF2: 2 transfer items prepared.

    4:39:47 AM #4 Text 0 File compose.cpp, Line 874
    GenUDF2: 2 transfer items prepared.

    4:39:48 AM #5 Text 0 File Burncd.cpp, Line 3566
    Turn on Disc-At-Once, using Blu-ray Disc media

    4:39:49 AM #6 Text 0 File DlgWaitCD.cpp, Line 314
    [G: BD-RW BDR-207M] Last possible write address on media: 48878591
    Last address to be written: 18933919

    4:39:49 AM #7 Text 0 File DlgWaitCD.cpp, Line 326
    [G: BD-RW BDR-207M] Write in overburning mode: NO (enabled: CD)

    4:39:49 AM #8 Text 0 File DlgWaitCD.cpp, Line 2890
    Recorder: PIONEER BD-RW BDR-207M, Media type: BD-RE

    4:39:49 AM #9 Text 0 File DlgWaitCD.cpp, Line 499
    [G: BD-RW BDR-207M] >>> Protocol of DlgWaitCD activities: <<<
    =========================================

    4:39:49 AM #10 Text 0 File ThreadedTransferInterface.cpp, Line 785
    Setup items (after recorder preparation)
    0: TRM_DATA_MODE1 ()
    2 indices, index0 (150) not provided
    original disc pos #0 + 18933600 (18933600) = #18933600/4207:28.0
    relocatable, disc pos for caching/writing not required/ required
    -> TRM_DATA_MODE1, 2048, config 0, wanted index0 0 blocks, length 18933600 blocks [G: PIONEER BD-RW BDR-207M]
    1: TRM_DATA_MODE1 ()
    2 indices, index0 (0) not provided
    original disc pos #0 + 320 (320) = #320/0:4.20
    relocatable, disc pos for caching/writing not required/not required
    -> TRM_DATA_MODE1, 2048, config 0, wanted index0 0 blocks, length 320 blocks [G: PIONEER BD-RW BDR-207M]
    --------------------------------------------------------------

    4:39:49 AM #11 Text 0 File ThreadedTransferInterface.cpp, Line 1001
    Prepare [G: PIONEER BD-RW BDR-207M] for write in CUE-sheet-DAO
    DAO infos:
    ==========
    MCN: ""
    TOCType: 0x00; Session Closed, disc not fixated
    Tracks 1 to 2: Idx 0 Idx 1 Next Trk
    1: TRM_DATA_MODE1, 2048/0x00, FilePos 0 0 38776012800, ISRC ""
    2: TRM_DATA_MODE1, 2048/0x00, FilePos 38776012800 38776012800 38776668160, ISRC ""
    DAO layout:
    ===========
    ___Start_|____Track_|_Idx_|_CtrlAdr_|_____Size_|______NWA_|_RecDep__________
    0 | lead-in | 0 | 0x41 | 0 | 0 | 0x00
    0 | 1 | 0 | 0x41 | 0 | 0 | 0x00
    0 | 1 | 1 | 0x41 | 18933600 | 0 | 0x00
    18933600 | 2 | 0 | 0x41 | 0 | 0 | 0x00
    18933600 | 2 | 1 | 0x41 | 320 | 18933600 | 0x00
    18933920 | lead-out | 1 | 0x41 | 0 | 0 | 0x00
    MediaType: BD-RE

    4:39:49 AM #12 Text 0 File SCSIPTICommands.cpp, Line 248
    SPTILockVolume - completed successfully for FSCTL_LOCK_VOLUME

    4:39:49 AM #13 Text 0 File Burncd.cpp, Line 4276
    Caching options: cache CDRom or Network-Yes, small files-No (<64KB)

    4:39:49 AM #14 PHASE 24 File dlgbrnst.cpp, Line 1827
    Caching of files started

    4:39:49 AM #15 Text 0 File Burncd.cpp, Line 4398
    Cache writing successful.

    4:39:49 AM #16 PHASE 25 File dlgbrnst.cpp, Line 1827
    Caching of files completed

    4:39:49 AM #17 PHASE 36 File dlgbrnst.cpp, Line 1827
    Burn process started at 2x (8,990 KB/s)

    4:39:49 AM #18 Text 0 File ThreadedTransferInterface.cpp, Line 2769
    Verifying disc position of item 0 (relocatable, disc pos, no patch infos, orig at #0): write at #0

    4:39:49 AM #19 Text 0 File ThreadedTransferInterface.cpp, Line 2769
    Verifying disc position of item 1 (relocatable, no disc pos, no patch infos, orig at #0): write at #48878272

    4:39:49 AM #20 Text 0 File Cdrdrv.cpp, Line 10557
    ---- Disc Structure (BD): Disc Information on BD (00h) ----
    Media Type: 1, Layer: 0, Address: 0 (0 h), AGID: 0; Length: 4098
    --- Header ---
    Disc Information Identifier: <DI>
    Disc Information Format: 04 h
    Number of DI Units/Aux Frames in each DI block: 6
    Number of (recording) layer to which this DI Unit applies: 0
    DI unit Sequence Number in DI Block: 0
    Continuation flag: Next DI Unit is the start of a new set of parameters (0)
    Number of DI bytes in use in this DI unit: 99
    --- Body ---
    Disc Type Identifier: <BDW>
    Disc Size/Class/Version: 19
    DI Unit Format dependent contents:
    BD Structure: 52 (34 h):
    3 recording layer (?), BD-RE
    Hybrid Disc identifier/Channel bit length: 5 (5 h):
    no DVD layer present, no CD layer present
    channel bit length of ?
    Push-Pull polarity flag bits: 00 h
    BCA descriptor: BCA-code present (1)
    Maximum transfer rate needed by the application: 0 Mbit/s
    Data zone allocation:
    First Physical ADIP Address of the Data Zone of the related layer (FAA): 21137E00 h (554925568)
    Last Physical ADIP Address of the Data Zone of the related layer (LAA): 02E29090 h (48402576)
    Recording velocities:
    Nominal Recording Velocity: 0.01 m/s (1 h)
    Maximum Recording Velocity: 0.01 m/s (86 h -> 134/100)=1
    Minimum Recording Velocity: 0.00 m/s (46 h -> 70/100)=0
    ...
    34 05 00 00 01 00 00 00 - 02 00 00 00 21 13 7E 00
    02 E2 90 90 00 01 86 46 - 87 02 02 6E 1F 00 58 F0
    F0 00 04 04 2C 2C 2C 30 - 30 04 00 00 50 58 58 F0
    F0 F2 F0 F0 00 00 00 00 - 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 FC FC
    FF F0 00 00 00 00 00 00
    --- Trailer ---
    Disc Manufacturer ID: 53 4F 4E 59 00 00 h <SONY..>
    Media Type ID: 45 54 32 <ET2>
    Time Stamp [m:y]: 0 : 0000 (00 00 h)
    Product Revision Number: 2

    4:39:49 AM #21 Text 0 File BD.cpp, Line 390
    Allocated spare area size on disc 0h
    BD: Start write address at LBA 0, Recording mode: unknown Recording Mode (0),
    spare area allocation: default (no action) (0), Stream recording: NO (0); return code 0

    4:39:49 AM #22 Text 0 File ThreadedTransfer.cpp, Line 273
    Pipe memory size 83836800

    4:39:49 AM #23 Text 0 File CUDFTransferItem2.cpp, Line 718

    GenUDF2 FS Layout:
    =-=-=-=-=-=-=-=-=-=-
    Sectors to be written: 18933920
    Session Start: Sector 0
    Volume Structure: Sector [0, 256] (257 Sectors)
    Meta Data: Sector [257, 10213] (9957 Sectors)
    Data: Sector [10214, 18933598] (18923385 Sectors)
    After Data: Sector [18933599, 18933599] (1 Sectors)
    Trailer Track: Sector [48878272, 48878591] (320 Sectors)

    GenUDF2 Parameters:
    =-=-=-=-=-=-=-=-=-=-
    PrepTime: 03-29-2021 04:39:47
    UDF Revision: 1.02
    UDF Partition Type: Physical
    UDF Special Mode: None
    Bytes per Sector: 2048
    Session Start: 0
    Physical Partition Start: -1
    Total Capacity: 48878592
    Multi Session Mode: Begin
    Disc Type: BD-RE
    OS Class: 0
    Volume ID: DriveD_Photos
    Allow Unicode Labels: 0
    Duplicate Meta Data: 1
    MS Info File: 0F6E0448
    VMS Rollback File: 00000000
    Create ISO bridge: 0
    ECC Block Length: 32
    Sparing Packet Length: 32
    Allocation Unit Size: 32
    Alignment Unit Size: 32
    Make Writable: 0
    Access Type: Read-only

    4:40:17 AM #24 SPTI -1135 File SCSIPassThrough.cpp, Line 217
    CdRom0: SCSIStatus(x02) WinError(0) NeroError(-1135)
    CDB Data: 0x2A 00 00 00 0C 40 00 00 20 00 00 00
    Sense Key: 0x03 (KEY_MEDIUM_ERROR)
    Sense Code: 0x0C
    Sense Qual: 0x00
    Sense Area: 0x71 00 03 00 00 09 40 0E 00 00 00 00 0C
    Buffer x118918c0: Len x10000
    0x05 01 02 00 D0 00 01 00 A3 2A B0 00 3F 0B 00 00
    0x00 00 00 00 04 00 00 00 01 00 00 05 00 00 00 00
    0x00 00 01 00 FF FF FF FF FF FF FF FF A5 14 00 00

    4:40:17 AM #25 TRANSFER -20 File ThreadedTransfer.cpp, Line 1222
    Could not perform Write

    4:40:17 AM #26 CDR -1135 File Writer.cpp, Line 327
    Write error
    G: PIONEER BD-RW BDR-207M

    4:40:17 AM #27 Text 0 File DVDPlusDualLayer.cpp, Line 1460
    SetDriveCaps: Set LAST LBA of layer 1 to 0

    4:40:17 AM #28 PHASE 38 File dlgbrnst.cpp, Line 1827
    Burn process failed at 2x (8,990 KB/s)

    4:40:17 AM #29 Text 0 File SCSIPTICommands.cpp, Line 298
    SPTIDismountVolume - completed successfully for FSCTL_DISMOUNT_VOLUME

    4:40:17 AM #30 Text 0 File Cdrdrv.cpp, Line 11914
    DriveLocker: UnLockVolume completed

    4:40:17 AM #31 Text 0 File SCSIPTICommands.cpp, Line 461
    UnLockMCN - completed sucessfully for IOCTL_STORAGE_MCN_CONTROL


    Existing drivers:

    Registry Keys:
    HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinLogon\AllocateCDROMs : 0 (Security Option)
     
  5. wither 1

    wither 1 Regular member

    Joined:
    Nov 29, 2019
    Messages:
    416
    Likes Received:
    16
    Trophy Points:
    28
    v10 is woefully out of date. I can't specifically attribute the problem to that but you should run the check for updates from the Nero ControlCenter. It's in the Toolbox available in StartSmart. If it doesn't find any, I might be able to get you a copy of the latest.

    If you went to tech support with this issue, they'd tell you to reduce the write speed, try another disc, try another batch of discs or try a different brand of discs. We've covered all those bases. The only thing I can think of goes back to the fact that it's detecting the drive as a BDR-207 with the correct firmware for a BDR-207. As I said before, I don't know if Pioneer used the same engine in both drives but used different designations, depending on the country. Both of these drives had firmware issued on the same dates twice, the last on October 31, 2012 for your drive but the BDR-207 firmware was updated 3 more times since that time and the SO7J firmware wasn't. Those updates may have fixed problems such as what you're seeing for the BDR-207 but, that's not the drive you're using. The only thing I can suggest, besides going to tech support, is to install this firmware- https://www.firmwarehq.com/download_2152-file_BDR-S07XLT_FW160EU.exe.html. You would have to do that at your own risk because once you install firmware, it can't be reverted back to a previous version.
     
  6. happy hopping

    happy hopping Member

    Joined:
    Mar 20, 2021
    Messages:
    31
    Likes Received:
    0
    Trophy Points:
    6
    see I thought it has to be the drive not interacting w/ 100GB disk. That's why I want to buy a newer model, such as the Pioneer BDR-S12J, the only reason I like Pioneer is their drive is made in Japan, the laser is better to pick up any media that has scratch on it. But the newer drive seems to be quite expensive. AT ebay, it's over $400. And I know I didn't pay $400 in my model

    As to the firmware, to try to fix the above problem, I already went to Pioneer website and flash the latest.

    Your link is not from Pioneer, what is it? 3rd party generic?
     
  7. wither 1

    wither 1 Regular member

    Joined:
    Nov 29, 2019
    Messages:
    416
    Likes Received:
    16
    Trophy Points:
    28
    I find it mind-boggling that someone, such as that website, is willing to keep track of the firmware for all those CD, DVD, Blu-ray drives out there and make the files available. As far as I know, the firmware provided is official. Can't imagine trying to make a generic version of a complicated software.

    What is the firmware version you got? I couldn't find the proper Pioneer website the other day but found it this morning. The version is the same as at FirmwareHQ. Pioneer points out that the firmware is only for drives sold in the United States and Canada.

    The drive is interacting with the disc, as shown in the logs. That's what always makes a burn problem similar to yours a head scratcher.

    You said you've already installed it. Have you tried a burn?
     
  8. wither 1

    wither 1 Regular member

    Joined:
    Nov 29, 2019
    Messages:
    416
    Likes Received:
    16
    Trophy Points:
    28
  9. happy hopping

    happy hopping Member

    Joined:
    Mar 20, 2021
    Messages:
    31
    Likes Received:
    0
    Trophy Points:
    6
    no, that model is made in Japan. The ones ends up the letter J is made in JApan

    My drive is not purchase in North America. You can't buy Japanese model from North America. I am 99% sure that back in those years, I bought it from Japan thru ebay
     
  10. wither 1

    wither 1 Regular member

    Joined:
    Nov 29, 2019
    Messages:
    416
    Likes Received:
    16
    Trophy Points:
    28
    I figured the J meant Japan. However, it was my error in identifying the drive I mentioned as a J drive. Not sure that a different drive than the one your using is necessary unless it's actually malfunctioning.

    You haven't mentioned if you have tried a burn yet using the newly installed firmware.
     
  11. happy hopping

    happy hopping Member

    Joined:
    Mar 20, 2021
    Messages:
    31
    Likes Received:
    0
    Trophy Points:
    6
    so when I was trying to fix this problem back Aug 2020, I did have trouble finding the right firmware. As win 7 report my model as BDR-207M, and when I download and launch that firmware, the software does not recogize the drive

    eventually I got the box , and the model no. on the box is slightly different, so I found the right firmware from Pioneer, flash it w/ the latest, and in the end, no difference.

    the error log above, needless to say, is w/ the latest firmware from pioneer of japan. If your link of firmwareHQ is from pioneer, then it would be the same firmware. Noone else would have the latest firmware except Pioneer

    this is the only problem I can't fix in 2020

    the only thing worth mentioning is that the japanese seller who said he sold me made in japan 100gB disc, turns out they are junk from taiwan. But my Sony BD-RE is still from japan and it should have work
     
  12. wither 1

    wither 1 Regular member

    Joined:
    Nov 29, 2019
    Messages:
    416
    Likes Received:
    16
    Trophy Points:
    28
    What was the slight difference in the model number?

    Where are you located?
     
  13. happy hopping

    happy hopping Member

    Joined:
    Mar 20, 2021
    Messages:
    31
    Likes Received:
    0
    Trophy Points:
    6
  14. wither 1

    wither 1 Regular member

    Joined:
    Nov 29, 2019
    Messages:
    416
    Likes Received:
    16
    Trophy Points:
    28
    That doesn't tell me the model number you alluded to.
     
  15. happy hopping

    happy hopping Member

    Joined:
    Mar 20, 2021
    Messages:
    31
    Likes Received:
    0
    Trophy Points:
    6
    I downloaded BDR-S07_FW160EU.exe

    and that was my concern, as it only update to Mar. 25, 2015. It should allows my drive to see current media but my 100GB media is out probably after 2018 or 2019. But it should still be able to see it.

    the problem has to be the drive can't see the 100GB media somehow, eventhough the manual and the spec. shows it does. Because 50GB media, 4.7GB DVD+R, 8.5GB DVD+R or CD-R, all burn fine
     
  16. happy hopping

    happy hopping Member

    Joined:
    Mar 20, 2021
    Messages:
    31
    Likes Received:
    0
    Trophy Points:
    6
    on unrelated matter, what exactly is the difference between:

    1) Reference Strategy
    2) diskspace strategy
    3) disk dependent strategy
     
  17. wither 1

    wither 1 Regular member

    Joined:
    Nov 29, 2019
    Messages:
    416
    Likes Received:
    16
    Trophy Points:
    28
    I figured out why I wasn't getting notifications of your posts. They were going to my spam filter.

    This is from your last log-

    Disc Manufacturer ID: 53 4F 4E 59 00 00 h <SONY..>
    Media Type ID: 45 54 32 <ET2>
    Time Stamp [m:y]: 0 : 0000 (00 00 h)
    Product Revision Number: 2

    so, it is seeing your disc. What really bothers me is that the minimum write speeds are very low. Do you have the option to set the write speed to 1x?

    Nobody has ever asked about that before and this is what I could find-

    Drop down menu entry
    Diskspace strategy

    Saves the audio files temporarily to the Nero Burning ROM cache.
    If there is no space available, a reference is created to the audio file and is not read until shortly before burning. This entry is selected by default.
    Drop-down menu entry
    Tempfile strategy
    Saves the audio files temporarily to the Nero Burning ROM cache.
    If there is no space available, an error message appears.
    Drop-down menu entry
    Reference strategy
    Creates a reference to the audio file and reads it shortly before burning. The source medium can only be a CD/DVD drive, not a recorder. The disc can only be burned in track-at-once mode.
    Drop-down menu entry
    Device dependent strategy
    Creates a reference to the audio file if a CD/DVD drive is available. Otherwise the tempfile strategy is used.
    Button
    Info
    Displayes more detailed information on the CDA file strategy.
     
  18. happy hopping

    happy hopping Member

    Joined:
    Mar 20, 2021
    Messages:
    31
    Likes Received:
    0
    Trophy Points:
    6
    I can't change the write speed to 1X. It default to 2X. The truth is, I did try all of the above w/ the latest free ver. of Ashampoo, I got the same kind of error, that the burning stopped after a while.

    I don't remember if I try doing a BD-RE on the latest Ashampoo, I'll try that tonight

    On unrelated matter, being too lazy to start a new thread:

    how come Nero cannot do this (create a DVD audio disc):


    View: https://www.youtube.com/watch?v=o9u49tBJZ2Q
     
    Last edited: Apr 3, 2021
  19. wither 1

    wither 1 Regular member

    Joined:
    Nov 29, 2019
    Messages:
    416
    Likes Received:
    16
    Trophy Points:
    28
    Would you try wiping the sony disc with a damp towel and let it dry. Open Nero Video and click on Tools. Select "erase disc." If that works, try another burn at 2x.

    If you've burned one of those type discs in Roxio. Open one of them in Windows Explorer and provide a screenshot of it's contents.
     
  20. happy hopping

    happy hopping Member

    Joined:
    Mar 20, 2021
    Messages:
    31
    Likes Received:
    0
    Trophy Points:
    6
    The Nero Burning ROM is what I normally use to erase BD-RE. Anyhoo, I have 1 of those nice piece of cloth from something called "Magneto Optical disc" media cleaning kit, and clean the Sony BD-RE. No difference. The media is flawless, I open it the other month to test on this problem. It's only been use as 100GB attempt burn a few times.

    I don't have any current Roxio. I did buy a 2004 version of Roxio. I don't know if it support today's OS. I seriously doubt a 2004 Roxio will work w/ 100GB media
     

Share This Page