Cannot Create VCD

jaroslav25 wrote on 7/28/2002, 11:44 PM
ANyone has encounter this before:
after creating a movie file, after which i render to the format required to burn into Video CD,
and in process of burning into a CD-R, the process of burning gets stuck at 0% always, after which , Video Factory will hang??
my systems are as follow: P3, 950Mhz, 128 Ram, WIndows 98 SE, the CD- Burner is ACer USB, 6X4X8...
thanks for your help.

Comments

laz111 wrote on 7/30/2002, 3:44 AM
Have you searched other posts and solved this yet?
jaroslav25 wrote on 7/31/2002, 12:30 AM
Yup.
tried searching for all post under Key word "cannot create"
but no relevant returns....
hope there is someone out there who has encounter this before and has solved it...
really hope there is help.
laz111 wrote on 7/31/2002, 5:27 AM
Your VF version is with 2.0c build and your burner drivers up to date? What file spec are you rendering to for vcd?
jaroslav25 wrote on 7/31/2002, 8:35 PM
Hi laz111
the files that i am trying to render are *.mpg created from a series of *jpg files.
i could write the *.mpg onto the hard disk, and could view it with Window Media Player.
i was thinking if i could use the *.mpg i rendered using VF that is saved on the hard disk, then use my CD burner software to write this file direct to the CD-R.??
anyone tried this before?
i have not tried updating the drivers for my CD burner.. shall try it to see if it works...
kcarroll wrote on 8/5/2002, 7:02 PM
This topic touches on the one problem I have not been able to resolve with Video Factory.

I bought VF after having abandoned the version of Videowave sold to me as part of a Dell Bundle. Because VideoWave didn't frigging work, I had purchased NERO 5.5 to handle my burning chores.

After buying Video Factory, I continued to use NERO to burn my VCDs and SVCDs, because that was what I was used to. Some months later, just for laughs, I decided to try burning a VCD directly from VF. Much to my surprise, I discovered that VF wouldn't recognize my CD burner.

After trying a few of the obvious things, I decided that the problem was probably a conflict between VF and NERO. Since I was producing VCDs and SVCDs using NERO, I was not terribly motivated to mess up a functioning system just to find the cause of this problem, but if someone out there knows the answer, I'd really like to know.

kcarroll
Kalvos wrote on 8/5/2002, 7:29 PM
Now this is interesting. Last week I tried using VF to burn a VCD, and my six-month-old Sony CRX175 died upon completion. The VCD didn't work, and the burner was dead -- it would read, but wouldn't write. I pulled it out and put it on another machine. Still, no write. And the odd thing was that my regular software (CDRWin) and the packaged software (B's Gold) now only saw it as a CD-R, not a burner!

I figured it had lived its life up in six months (it does get daily use) and it was time for a replacement.

Since the price was low, I bought another one at Staples, and attempted to burn the same CD from VF since I was behind schedule. The new burner (another CRX175) didn't even get a minute into it and it died the same way -- read, no write, looking only like a CD-R, not a burner. I returned it ASAP thinking "coincidence, coincidence" and maybe a problem with CRX175s (and why the price had dropped to $70). But I got another CRX175, which is working perfectly.

But haven't dared to use VF to burn another disk! I used B's Gold and it burns a VCD just fine. I tried the CRX175 on two machines, and it worked great. But no more burns from VF for now!

This doesn't sound likely, but is it at all possible that VF might be writing to the flash ROM? I don't know the laser assembly parameters, but is it even possible to damage it via software?

Dennis

Dennis

Vegas Pro Version 21.0 Build 108
Windows Pro 10.0 20H2 build 19042.1110
AMD Radeon R9 280

Processor    Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz   3.30 GHz
Installed RAM    16.0 GB (15.9 GB usable)
System type    64-bit operating system, x64-based processor

 

maltedmedia.com/bathory

Stiffler wrote on 8/7/2002, 1:54 AM
Could it be an ASPI thing???? Software not hardware?
Kalvos wrote on 8/7/2002, 8:03 AM
I suppose that if VF changed the ASPI drivers, it would cause that sort of failure (I have both the Adaptec and CDRWin drivers).

But rebooting didn't help, and my backup machine doesn't have VF on it (only CDRWin and B's Gold) -- and the drives were dead on it as well. My other burners worked fine, but you can bet I didn't ask VF to use them!

My first burner was a 1x Pinnacle in early 1997, and standard burning has been near 100% successful for me. That's why I panicked when hardware started to go south using VF.

Dennis

Dennis

Vegas Pro Version 21.0 Build 108
Windows Pro 10.0 20H2 build 19042.1110
AMD Radeon R9 280

Processor    Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz   3.30 GHz
Installed RAM    16.0 GB (15.9 GB usable)
System type    64-bit operating system, x64-based processor

 

maltedmedia.com/bathory

randy-stewart wrote on 8/8/2002, 12:06 AM
Dennis,
This sounds like a problem I had with ASPI drivers. Check out the below fix from a previous post:
Grazie,
The correct link (http://aspi.radified.com/) takes you to a web site that tells all about the ASPI issue (sorry, I pasted in the e-mail web link that I sent to myself before which wouldn't work here). Go down to the ASPI section. It recommends a couple of options to fix the problem. The one I chose was to download the force ASPI software that replaces the 4.60 (1021) version files on my Windows ME system. To get the software, I had to go to the Cryus.troy site (it's a link on the web page above) and follow the directions to download the force ASPI program files. It takes about 10 seconds to download (I saved it to the desktop). Then I clicked on the folder and got a message that asks me to unzip the files and did I want to do that now. I said yes, then, after it unzipped, I opened the new folder and clicked on the install program (can't remember the full name but it has the word instal in it), ran the program, and voala, a DOS box came up, and installed the files I needed, and after reboot, it worked fine. I know this is a little bit involved but it fixed my problem. Check out the web site (just copy the address into your URL area up top (after you delete the current one, and hit go) as it has all the info needed. Hope you can get it to work.
Randy
marys wrote on 8/23/2002, 12:37 PM
Randy - was reading this post and having similar difficulties and followed your instructions on downloading & installing the ForceASPI files...did that & it seemed to work fine. Then tried rendering my movie to MPEG1 (only option I had) straight to my CDRW drive, but it kept saying "Put a blank CDR in" - made several coasters...it's like it doesn't recognize my Iomega drive (we have burnt regular data cd's to this drive so know it's working)...any thoughts on that? TIA -M
randy-stewart wrote on 8/24/2002, 12:38 AM
MaryS,

Sorry, after I loaded the drivers, my burner drive showed up in VF. I remember having to do it twice (load the drivers) and then checked the ASPI file to verify that they now included all 4 lines. If that didn't work for you, I'm out of suggestions.

Chienworks, can you assist?

Randy
Kalvos wrote on 8/24/2002, 6:44 AM
To follow up to an earlier suggestion, the new ASPI drivers were already installed. The new and replacement Sony drives are working fine with B's Gold and CDRWin, so I'm not going near VF to burn anything in the future. VF was the only consistent factor in two drives being damaged, and even though that's far from conclusive, I'll just use other burning software to stay safe.

Thanks to all for suggestions,
Dennis

Dennis

Vegas Pro Version 21.0 Build 108
Windows Pro 10.0 20H2 build 19042.1110
AMD Radeon R9 280

Processor    Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz   3.30 GHz
Installed RAM    16.0 GB (15.9 GB usable)
System type    64-bit operating system, x64-based processor

 

maltedmedia.com/bathory