Nero Suggestion

by **Rich** on Fri Aug 26, 2005 12:46 pm

I am buring a backup to dvd as I write this and I just had a flash idea that would be so cool and in some form probably do-able.

Nero shows the % completion in the taskbar button for the Nero window. It'd be great if it could have the option of showing the % full of the Buffer instead.

I'm piping throught a cardbus adapter and only get 6x tops on burns and I do like to keep my eye on how it's going. If it were right in the task bar it would be much easier to watch.

It cold be a choice in Nero and maybe even flash the percentage in red if it drops really low.

Thanks if you folks can do it,

Rich

by **CCampbell** on Fri Sep 16, 2005 7:44 pm

Once Nero 7 has been released, I'll see about adding this feature. :-)

We have a 'freeze' on new features till Nero 7 is out fully.

Regards,

Craig

by **Rich** on Sat Sep 17, 2005 1:12 am

Hi Craig,

Thanks very much for the reply and the good news!

Rich

by **dodecahedron** on Mon Sep 19, 2005 5:09 pm

going along the same direction as Rich's suggestion:

apparently Nero should show me at the end of the burns how many buffer underruns (more accurately: buffer under-run preventions) have occurred.
i've never seen this.
it would be very nice if it whould show a message in the burning-dialog window saying after "burn completed at 16x" something like "0 buffer underruns have occurred". just so i know.
if this feature were implemented, i would spend much less time watching the buffer meter during a burn.

by **Rich** on Tue Sep 20, 2005 12:15 am

dodecahedron wrote:going along the same direction as Rich's suggestion:

apparently Nero should show me at the end of the burns how many buffer underruns (more accurately: buffer under-run preventions) have occurred.
i've never seen this.
it would be very nice if it whould show a message in the burning-dialog window saying after "burn completed at 16x" something like "0 buffer underruns have occurred". just so i know.
if this feature were implemented, i would spend much less time watching the buffer meter during a burn.

Wow that's a super suggestion.

Rich

by **CCampbell** on Tue Sep 20, 2005 2:11 am

At one time, we did do that for all builds, but at the request of a number of OEMs, this was disabled in the Registry. They were concerned it would cause customer support calls as some users would assume they had a problem with the recorder. Some OEM builds still show this, I believe the Plextor build is one of them.

And this can be turned on in the registry settings, but I'll have to look at this tomorrow, as it's kinda late right now. :-)

Regards,

Craig

by **dodecahedron** on Tue Sep 20, 2005 5:34 am

CCampbell wrote:And this can be turned on in the registry settings, but I'll have to look at this tomorrow, as it's kinda late right now.

if you can check and tell us how to turn it on in the registry, that's super!
thanks.

by **CCampbell** on Tue Sep 20, 2005 1:22 pm

If you go into 'REGEDIT' and go to

HKEY_CURRENT_USER/Software/Ahead/Nero-Burning Rom/General

You will see an option for 'ShowBurnProofCount'

I believe you need only change the 'Value Data' to 1 to enable this feature.

Regards,

Craig

by **dodecahedron** on Tue Sep 20, 2005 5:19 pm

it is already 1.

i think i didn't explain it clearly enough the first time.

as i understand it, if burn-proof is activated during the burn, then Nero will report at the end of the burn how many times it did that.
however, i never saw any such message.

i can only assume that if there were buffer under-runs Nero would report how many times, and if there were none Nero says nothing about it.
but since i never saw any messge at all i'm not sure that's how it really works.

so what i'd like is: if there were buffer under-runs Nero reports how many times, and if there were none Nero reports that there were none!

by **CCampbell** on Wed Sep 21, 2005 2:00 am

Did you check the log file? That is where it should list how many times a buffer underrun was avoided when that feature is enabled.

We did at one time have a message pop up at the end of a write to tell you that you avoided a buffer underrun 32 times or whatever it might be, but that caused too many Support calls, so now it should only do this within the Nero log file.

Regards,

Craig

by **dodecahedron** on Wed Sep 21, 2005 4:54 am

well if it is i don't know where to find it.

Code: Select all: ... 23:47:52 #11 Phase 36 File dlgbrnst.cpp, Line 1832 Burn process started at 10x (1,500 KB/s) 23:47:52 #12 Text 0 File ThreadedTransferInterface.cpp, Line 2643 Verifying disc position of item 0 (relocatable, no disc pos, patch infos, orig at #0): write at #0 23:47:52 #13 Text 0 File Mmc.cpp, Line 16883 StartDAO : CD-Text - Off 23:47:52 #14 Text 0 File Mmc.cpp, Line 21663 Set BUFE: Buffer underrun protection -> ON , SMART-BURN : ON 23:47:52 #15 Text 0 File Mmc.cpp, Line 17170 CueData, Len=32 41 00 00 14 00 00 00 00 41 01 00 10 00 00 00 00 41 01 01 10 00 00 02 00 41 aa 01 14 00 00 21 46 23:48:11 #16 Text 0 File WriterStatus.cpp, Line 116 <LITE-ON LTR-52327S > start writing Lead-Out at LBA 2395 (95Bh), lenght 0 blocks 23:48:11 #17 Text 0 File ThreadedTransfer.cpp, Line 228 all writers idle, stopping conversion 23:48:21 #18 Phase 37 File dlgbrnst.cpp, Line 1832 Burn process completed successfully at 10x (1,500 KB/s) 23:48:21 #19 Phase 78 File dlgbrnst.cpp, Line 1832 Data verification started 23:48:24 #20 Text 0 File ThreadedTransferInterface.cpp, Line 1111 Removed 2 run-out blocks from end of track 1. Length: 2395 -> 2393. 23:48:28 #21 Text 0 File ThreadedTransfer.cpp, Line 228 all writers idle, stopping conversion 23:48:28 #22 Phase 80 File dlgbrnst.cpp, Line 1832 Data verification completed successfully ...

needless to say, the registry key you mentioned has value 1 i.e. the feature is enabled. still i don't see anywhere in the log that it says how many times buffer underrun was avoided or that it didn't happen at all.

by **MediumRare** on Wed Sep 21, 2005 7:02 am

I'm very much interested in this option too. I turned the registry flag on and tried a burn with the image recorder last night- but didn't find an entry in the log file. I suppose this is because:
- the image recorder doesn't support burnproof (or whatever)
- no underruns occured
- there is no logfile entry without underruns.

When I get home, I'll try to provoke an underrun on an RW by:
- turning the Nero buffer off
- throttling the source with CD-Bremse
- or burning from a USB 1.1 stick or floppy as a source.

I'd really like to see an example of what the entry in the log file looks like!

G

by **MediumRare** on Wed Sep 21, 2005 5:43 pm

Well, here's what I did as a test:
- set Ultra-buffer to Min 1 MB
- used a USB-stick for the cache (slow, and essentially turned it off)
- used a networked Teac 8x CD-Rom as source
- copied a single ca. 400 MiB file to a CD-RW

It's not that easy to provoke a buffer underrun- and I'm not sure if I succeeded

. The drive's buffer kept bobbing between 10% and 80%, but never went to 0. In any case, there's no trace of an entry in the log file:

Code: Select all: 22:24:30 #12 Text 0 File ThreadedTransferInterface.cpp, Line 1043 Prepare recorder [LITE-ON LTR-48246S] for write in CUE-sheet-DAO DAO infos: ========== MCN: "" TOCType: 0x00; Session Closed, disc fixated Tracks 1 to 1: 1: TRM_DATA_MODE1, 2048/0x00, FilePos 0 307200 533975040, ISRC "" DAO layout: =========== __Start_|____Track_|_Idx_|_CtrlAdr_|_RecDep__________ -150 | lead-in | 0 | 0x41 | 0x00 -150 | 1 | 0 | 0x41 | 0x00 0 | 1 | 1 | 0x41 | 0x00 260580 | lead-out | 1 | 0x41 | 0x00 22:24:30 #13 Phase 36 File dlgbrnst.cpp, Line 1832 Burn process started at 12x (1,800 KB/s) 22:24:30 #14 Text 0 File ThreadedTransferInterface.cpp, Line 2609 Verifying disc position of item 0 (relocatable, disc pos, no patch infos, orig at #0): write at #0 22:24:30 #15 Text 0 File Mmc.cpp, Line 16578 StartDAO : CD-Text - Off 22:24:30 #16 Text 0 File Mmc.cpp, Line 21356 Set BUFE: Buffer underrun protection -> ON , SMART-BURN : ON 22:24:30 #17 Text 0 File Mmc.cpp, Line 16865 CueData, Len=32 41 00 00 14 00 00 00 00 41 01 00 10 00 00 00 00 41 01 01 10 00 00 02 00 41 aa 01 14 00 39 38 1e 22:31:11 #18 Text 0 File WriterStatus.cpp, Line 116 <LITE-ON LTR-48246S > start writing Lead-Out at LBA 260580 (3F9E4h), lenght 0 blocks 22:31:11 #19 Text 0 File ThreadedTransfer.cpp, Line 228 all writers idle, stopping conversion 22:31:19 #20 Phase 37 File dlgbrnst.cpp, Line 1832 Burn process completed successfully at 12x (1,800 KB/s) Existing drivers: File 'Drivers\ASPI32.SYS': Ver=4.60 (1021), size=25244 bytes, created 10.09.1999 12:06:00 File 'Drivers\PXHELP20.SYS': Ver=2.03.01a, size=20368 bytes, created 04.12.2004 23:16:40 (Prassi/Veritas driver for win 2K) File 'Drivers\atapi.sys': Ver=5.1.2600.2180 (xpsp_sp2_rtm.040803-2158), size=95360 bytes, created 03.08.2004 22:59:44 (Adapter driver for rec) Registry Keys: HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinLogon\AllocateCDROMs : 0 (Security Option)

I doublechecked the reg. key to make sure it stayed on. So, either I didn't get any buffer underruns or Nero didn't report them.

G

by **CCampbell** on Wed Sep 21, 2005 8:19 pm

I'm on the road till Friday, and on Friday I have 1 or 2 meetings. If I get the time, I'll look into this on Friday.

If there is no buffer underrun, you will not see any messages. If there is, it should state how many times you avoided a buffer underrun.

But to be honest, it's been 6 months or more since I've seen this message pop up, but I havnt exactly been looking for it. :-)

I should have a response by Saturday at the very latest.

Regards,

Craig

by **dodecahedron** on Thu Sep 22, 2005 2:55 am

CCampbell wrote:If there is no buffer underrun, you will not see any messages. If there is, it should state how many times you avoided a buffer underrun.

thanks for clarifying that.
but that's just what we want: a message saying that there were no (zero) buffer under-runs.

by **CCampbell** on Fri Sep 23, 2005 8:52 pm

I just ran a test on an XP system using Nero 6.6.0.16 and a Plextor PX-716UF and by setting the Ultra buffer to 1, and launching programs such as Explorer, WMP, Outlook, etc I was able to cause it to have a buffer underrun occur 3 time. At the end of the write, a popup window indicated a buffer underrun was avoided 3 times. I did not make any changes in the Registry settings to cause this, I left it as default.

If there is no buffer underrun, you do not get a popup and you do not see anything in the log file.

Here is an excerpt from the Nero log file:

5:42:36 PM #23 Text 0 File Mmc.cpp, Line 16352
<PLEXTOR DVDR PX-716A > start Close Session

5:42:49 PM #24 Phase 37 File dlgbrnst.cpp, Line 1832
Burn process completed successfully at 24x (3,600 KB/s)

5:42:49 PM #25 Text 0 File Burncd.cpp, Line 4604
Buffer underrun error was avoided 3 times.

[/img]

Regards,

Craig

by **MediumRare** on Sun Sep 25, 2005 7:40 am

Thank you for posting this information, Craig. That is pretty well how I'd want to have the information shown.

Actually it's a Good Thing that buffer underruns are so hard to get (but I'll try again to confirm that this works with my rig too).

G

Nero Suggestion

Nero Suggestion

Who is online