Wavelab 6.x Compatibility With Current Burners - Issues, Tips, Tricks, Fixes :

[TAFKAT]

Anyone here having any luck with Wavelab 6 on any current SATA burners.

I have always found Wavelab flakey at the best of times with burner compatibility, but I am getting more reports lately of current burners not being recognised and/or working correctly.

One of the recent error reports is below:


Unknown CD writing error
Complementary error information notified by the CD recorder's driver:
An error occured while writing track 1 at position 416.

Pioneer DVD-RW DVR-215 (F:) NO SENSE NO ADDITIONAL SENSE INFORMATION 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2A 00 00 00 01 A0 00 00 1A 00

This burner is working 100% with Nero.

Of course being locked out of the Cubase forum, I can't ask PG directly.. :-(

Any suggestions welcome

:009:

[The Guru]

http://cubase.net/phpbb2/viewtopic.php?t=9253&start=0&postdays=0&postorder=asc&highlight=

[TAFKAT]

Thanks Nate,

I am sure the ASAPI patch only covers earlier versions updated to the latest, the listed error was on a brand new install that was already the latest build.

Worth a shot tho.

FWIW: The burning engine has always been a crap shoot , a shame that such an awesome application is still consistently hobbled by burning issues, I have been navigating these issues for years :-(

The burning engine is reported to be having a complete rewrite for 7, so it will be interesting what transpires there.

[Michael Tibes]

I wonder if the new engine ever gets finished before noone uses CDs any more at all. It is somewhat sad to see WL fade out like this, it was the first program I used after the Atari era and has been an 'old friend' since then.

I managed to get WL burn audio CDs on my I7 under XP32 on an SATA burner, if I remember right I had to mess with the ASAPI patch and after audio CDs were going ok with WL I couldn't burn data CDs any more :angryfire:, not with WL nor with XPburner. I finally found a Nero free version that worked for data CDs / DVDs. I don't remember my burner model, gotta look it up if that is interesting for you (it's about a year old).

Has anyone experience with Samplitude for CD burning? If I got it right, it can create DDPs - which seems to be a real must for a mastering program to me nowadays. I don't wanna do 'real' mastering, but being able to deliver a professional format when I make a compilation or some edits would REALLY be nice. Delivering just a CD-R is so 1998...

Michael

[TAFKAT]

Thanks Michael,

As I suspected, fix one issue and possibly create another, I really can't afford to kill the regular burning app , Nero in this case , to get the burning happening in Wavelab on my new systems.

Toying with ASPI and ASAPI is always a gamble.

The burner revisions are constantly being updated, and Nero even version 7 will work effortlessly with any new burner , obviously their burning engine is inherently far superior.

I'll have a poke around with WL 6 in the next week or so on a few systems with SATA burners, some being 1-2 years old now, one being a brand new system yet to be delivered.

:009:

[kdm]

Has anyone experience with Samplitude for CD burning?

I use Sequoia for CD burning and it works fine, but will have to get back to you on whether my latest rig has an IDE or SATA DVD/CD drive (I didn't build this one).

I don't think Samplitude offers DDP, but maybe v11 does now - that used to be a Sequoia-only feature, (and part of a handful of unique Sequoia features only worth the extra $2000 if you were a mastering engineer, and even then...).

[The Guru]

It's been a long time since I helped a few friends with this issue so I'm a little rusty.

IIRC, Nero is what breaks the WL burning in a lot of instances. There's a registry tweak that resets something but as I said, it's been a while. I'd have to research it some more.

Did you follow the other links in that thread?

[TAFKAT]

Hey Nate,

I did have another browse thru the K.B , thanks.

BTW: The actual links are useless as they do not actually link to the required docs anymore, but I did find the relative pages manually.

I'll have a dig thru and report back

:009:

[The Guru]

Vin, what OS?

[TAFKAT]

Hey Nate,

All on XPSP3 , haven't arm wrestled Windows 7 as yet, but will be during the testing.

[The Guru]

If the burner isn't listed in WL then the ASAPI patch is what fixes that, it doesn't matter if it's an upgrade install or virgin.

Also, Google Nero and Window's registry. There's something that needs to be deleted that gets entered by Nero, IIRC. It's a holiday weekend here, so I'm a little tied up or I'd look into it further.

[The Guru]

Oh, and there are people who can't get CD burning to work in WL no matter what.

[The Guru]

Here's a link to the Registry tweak.

http://support.microsoft.com/kb/314060

[TAFKAT]

Quick heads up..,

Fresh Install of XPSP3 , Wavelab 6.10.340, I have tried all of the suggested tweaks in relation to ASPI/ASAPI listed on the Steini K.B to no avail, burner is recognised, all burn speeds are listed, on initialising the burn it looks like its about to start then quickly reports that burn was successful without actually doing anything, incredibly frustrating.

This is different to the error on the first clients system , but still no cigar in being able to successfully burn a CD.

Nero is not installed on the system as yet.

Out of interest, I downloaded Sony CD Architect 5.2 Demo , installed, compiled a quick compilation CD, burned successfully without issue. For those that aren't already aware, CDA 5.2 is the integrated Red Book Burning Engine of Sound Forge Pro, but can be purchased separately.

As much as I love Wavelab, I am way over trying to navigate the B.S over and over again with burning CD's , and there just isn't any avenue to get a clear answer on what is actually required.

BTW: An interesting and quite telling article in the Steini K.B Here (https://www.steinberg.net/en/support/knowledgebase_new/show_details/kb_show/burning-cds-in-external-applications-by-exporting-cd-image-and-cue-sheet/kb_back/2020.html?tx_p77sbknowledgebase_pi1[productfamily]=10&tx_p77sbknowledgebase_pi1[product]=14) gives instructions on how to export a cue sheet and iso image to burn in a 3rd party application, now if thats not a give away that there is something seriously wrong with the burning engine , I don't know what is.

FYI: The cue sheet and image failed in Nero.. :-(

[The Guru]

One last try. Some have had success with this, some not.

http://cubase.net/phpbb2/viewtopic.php?t=120000&start=0&postdays=0&postorder=asc&highlight=

[TAFKAT]

Thanks Nate,

Worth a shot , I'll report back once I have had a chance to run up the reg change suggested.

BTW: On a whim I installed Wavelab 5 and updated to the latest version on the same machine , exactly the same issue.

I also am not convinced Nero is the problem in a lot of these cases as I do not have Nero currently installed , and have had dozens of clients systems actually working in the past with W5 and W6 with Nero installed.

There just isn't any clear consensus when you do run into problems.

It is something to do with the ASPI sublayer, thing is Nero, SoundForge/CD Architect , etc, etc, never have a problem even with the latest burners.

What I also find very disturbing is that there is never any viable solution with P.G on this matter past the usual B.S spin. I suppose after years of being in the lair, the M.O has rubbed off, I mean really, use a non SATA device to resolve the issue, I would just say one thing to P.G in that respect... F.O and fix it , why would I use an ATA burner on a new system.

[The Guru]

I hear you Vin. To add to that last link, some added a User line with a decimal value of 1 in that key with success.

Still, a lot of people can't seem to get it going with any of the fixes.

Trying to keep it positive, so that's all I'll say about the situation.

[TAFKAT]

Hey Nate,

Quick heads up, success.. :-)

There is so many different options listed in that thread, so I took a gamble and tried the last registry change suggestion that made the most sense to me , which is this one.

HKEY_LOCAL_MACHINE.Software.Vob.CDRApp.Writer..(na me of CD Writer) DAOSupported value="0"

Change to "1"

The other changes I made, which I am not entirely sure are necessary now was to change to the ASPI driver, removed the ASAPI driver and also ran the patch WL6 ASPI patch after updating.

FYI : The burner I successfully got running is the latest Pioneer DVDR 218L , so it looks like the registry fix works across the board, fingers crossed, as the client with the original issue has an earlier burner, but I am a lot more confident now that I can resolve it.

Thanks for helping me follow this up , very much appreciated, and as per usual, a big no thanks to the Steinberg support and developers , who again relied on end users to fix the problem while they assumed the ostrich position.

Also a big thanks to the guys on the original thread for chasing this down.

I digress,

So heres the quick 101 that I did to get this resolved for others reading in.

-----------------------------------------------------------------------

Guide to Wavelab 6.x CD Burning Support For Latest Burners.

1: Download wnaspi32.dll Here (www.frogaspi.org/download/wnaspi32.dll)

Place the file into the WaveLab application folder.

Uninstall ASAPI (Control panel -> Add/Remove programs)

2: Install the WL6 ASPI Update : Download Here (ftp://ftp.steinberg.de/Download/WaveLab_6/6.10.340/WaveLabAspi.zip):

Note: Needs to be re-applied after every update.

3: Change the Reg key entry:

HKEY_LOCAL_MACHINE.Software.Vob.CDRApp.Writer.( name of CD Writer ) DAOSupported value="0"

Change to "1"

4: Restart System :

-------------------------------------------------------------------


:009:

[The Guru]

Cool :icon_cool:

Yeah that's the tweak I was refering to. I thought I had linked to that post, but I guess not. I've been tracking the last couple of days and was doing this on breaks.

That's the Registry key where the User value can be added as fix, also.

Maybe the title of this thread can be changed to reflect the fix contained here-in.

[TAFKAT]

Done.. :D