Record Now Hangs

[zasco]

I'm Burning a dvd audio project with 198 clips. when It reaches 138th clip I get a run time error R6025 and can't go any further.

I have a gateway PC with 2 gig ogf memory and running Windows Vista home premium. I've tried burning to disc directly and writing to an ISO file with the same results

[ogdens]

I'm Burning a dvd audio project with 198 clips. when It reaches 138th clip I get a run time error R6025 and can't go any further.

I have a gateway PC with 2 gig ogf memory and running Windows Vista home premium. I've tried burning to disc directly and writing to an ISO file with the same results

 

What Sonic program do you have?.

[Fred Flange]

Zasco,

 

I had pretty well exactly the same problem trying to burn a DVD music disc. (I'm using the Music Disc Creator component of RecordNow9.)

 

I have spent the last three weeks or so getting 'advice' from Roxio via their support 'ticket' thing, (they suggested all sorts of 'disable this and disable that' stuff, and a clean re-install of the whole RecordNow program, but it got me precisely nowhere.)

 

I finally identified the problem myself by a process of deduction and elimination, and in my case it lay with the integral 'Quick Sound Editor' (the 'Edit Audio' button in the toolbar) which must have some sort of bug in it.

 

I was getting the Runtime error & crash whenever my burn reached a certain clip, so I removed it from the project and then re-added it. My next burn attempt reached a little further through the track listing, and I did the same thing with that clip, with exactly the same result.

 

I noticed that the clips that the burn was crashing on were all clips that I had tweaked with the integral sound editor. But if I did the same tweak using the separate 'Sound Editor' program that comes in the RecordNow bundle, I could now get past it in the burn.

 

If you have not used the integral sound editor to tweak any clips, and particularly clip 138, then obviously this isn't a solution for you, but if you have used it, it may be the answer.

 

That is the good news.

 

The bad news, for me at any rate, was that I had about 300 clips on the far side of where the program was crashing, and I wasn't sure which ones of those I'd tweaked, and which ones I hadn't. I could have carried on doing attempted burns to identify them, but it would have taken ages. There is no easy way to spot which ones are edited.

 

In the end I decided the only practical way forward was to delete all those clips and then re-add them. Again, the bad news is that the program doesn't provide a way of producing a print or text file of the project clip listing. I resorted to doing about a dozen screen-print .jpgs so that I knew what clips to re-add, and in which order.

 

But, having done all that, the next time I tried burning my project it ran successfully all the way through to the end.

 

Sorry if this post is a bit on the verbose side...

 

Good luck.