I was using VideoStudio 10 to create about an 8 minuted video composed of a combination of still photos and short movie clips. Everything looks and plays fine all the way through within VideoStudio. I go to Share->Creat DVD and select the slowest write speed (4.0X) and the burn appears to have completed without error. After I burn the DVD and play it back (on my PC, or on 2 different DVD players in the house) the Video hits a point late in the playback (between 6.5-7.5 minutes, the point varies from burn to burn with the same project) where it either hangs for a while then skips over a few photos and picks back up, or just hangs then ends. Every once and a while (rarely) I can get a burn that works fine all the way through.
I went ahead and upgraded to VideoStudio11 but I am experiencing the same problem.
Please help
Major problem with Create DVD - Help Please
Moderator: Ken Berry
-
heinz-oz
What would you have us base any advice on?
Surely not this:

what are the clip and image properties?
Surely, if there was a wheel falling off your car every second day, you wouldn't put a new engine in it hoping it would fix the problem, would you? What made you think upgrading to VS 11 would fix it?
Surely not this:

what are the clip and image properties?
Surely, if there was a wheel falling off your car every second day, you wouldn't put a new engine in it hoping it would fix the problem, would you? What made you think upgrading to VS 11 would fix it?
-
nethopper
I am new to this forum. I have updated my profile with my system information and posted it below:
Operating System: Windows XP SP2
Graphic Card: ATI RADEON XPRESS 200
Sound Card: RealTek AC'97
Processor: AMD Athlon 64 X2 Dual Core 3800+
Hard Disk: 250GB
Memory: 2GB
The original images pulled in are around 4.5MB and there's approximately 100 of them. There's only 5 short (<20s) video clips pulled in and range from 70MB-100MB in size. The total space taken by the resulting DVD image is 508MB.
Now, a response to your other somewhat rhetorical questions:
1) I expected an initial reponse indicating that either (a) this was a known problem experienced by others with info on how to deal with it or (b) a request for additional information.
2) This is isn't a car, it's software and believe it or not, Ulead has bugs in their software. Software companies, and I'm sure that Ulead is no exception, fix a lot of bugs that they don't inform us about when they release a new version. Since I was on a short timeline to get this project out the door I upgraded in case a solution may be hidden in there.
What I did not expect was a moderator that prefers to demean the people posting here rather than asking helping out with a positive attitude.
Operating System: Windows XP SP2
Graphic Card: ATI RADEON XPRESS 200
Sound Card: RealTek AC'97
Processor: AMD Athlon 64 X2 Dual Core 3800+
Hard Disk: 250GB
Memory: 2GB
The original images pulled in are around 4.5MB and there's approximately 100 of them. There's only 5 short (<20s) video clips pulled in and range from 70MB-100MB in size. The total space taken by the resulting DVD image is 508MB.
Now, a response to your other somewhat rhetorical questions:
1) I expected an initial reponse indicating that either (a) this was a known problem experienced by others with info on how to deal with it or (b) a request for additional information.
2) This is isn't a car, it's software and believe it or not, Ulead has bugs in their software. Software companies, and I'm sure that Ulead is no exception, fix a lot of bugs that they don't inform us about when they release a new version. Since I was on a short timeline to get this project out the door I upgraded in case a solution may be hidden in there.
What I did not expect was a moderator that prefers to demean the people posting here rather than asking helping out with a positive attitude.
-
heinz-oz
You still did not give any details on the clip and image properties.
No, it's not a common problem and, hence, there is no one fix all solution either. It is rather common though that people come here expecting us to be clairvoyants (I¡¦m not) or patient enough to ask the obvious questions over and over again. Incidentally, you may not have liked the tone of my response (in hindsight I don¡¦t like it much either) but, as so often the case, you haven¡¦t answered the questions asked either.
For your information, none of us moderators or admins are getting paid for our activities here, we volunteer. Since we spend our spare time here, I think, people like yourself could be expected to make it a little easier for us by providing at least the info we ask for rather than abusing us for not being polite enough.
As far as I¡¦m concerned, I have been as polite as I could be under the circumstances.
Sorry you took my little analogy about the car as an attempt to demean you, no offence was intended. I should have guessed that you have no sense of humor either.
I shall refrain from trying to amuse you any further.
No, it's not a common problem and, hence, there is no one fix all solution either. It is rather common though that people come here expecting us to be clairvoyants (I¡¦m not) or patient enough to ask the obvious questions over and over again. Incidentally, you may not have liked the tone of my response (in hindsight I don¡¦t like it much either) but, as so often the case, you haven¡¦t answered the questions asked either.
For your information, none of us moderators or admins are getting paid for our activities here, we volunteer. Since we spend our spare time here, I think, people like yourself could be expected to make it a little easier for us by providing at least the info we ask for rather than abusing us for not being polite enough.
As far as I¡¦m concerned, I have been as polite as I could be under the circumstances.
Sorry you took my little analogy about the car as an attempt to demean you, no offence was intended. I should have guessed that you have no sense of humor either.
I shall refrain from trying to amuse you any further.
-
nethopper
I provided information on the original image and clip size and length. I didn't know what other properties might be required. Here is some more info: The images are .jpg 3456x2304 72 pixels per inch. The video is .AVI captured directly from the mini DV camera, the video is 24 bits 720x480 pixels on a 4:3 ratio.
I realize the admins and moderators here are volunteers and appreciate their efforts. I participate in other on-line communities where this is the case as well, such as Flickr where I put in time helping others. I even exhibit a sense of humor every now and then believe it or not. So I appreciate the time people put in here.
Let's call a truce and move on.
I realize the admins and moderators here are volunteers and appreciate their efforts. I participate in other on-line communities where this is the case as well, such as Flickr where I put in time helping others. I even exhibit a sense of humor every now and then believe it or not. So I appreciate the time people put in here.
Let's call a truce and move on.
Last edited by nethopper on Mon May 28, 2007 1:45 pm, edited 1 time in total.
When you go to the DVD Module, are you using the VideoStudio Timeline, or are you using a rendered dvd-compliant video?
If using the Timeline, try breaking it down into separate steps:
1) Share / Create Video File (output a rendered dvd mpeg file)
2) Start a new project (empty timeline), and Share / Create Disc (then manually add your dvd mpeg file from Step-1).
Also, verify that the mpeg file plays fine at the problem spots on your computer (I use WinDVD or PowerDVD to play a media file).
Regards,
George
If using the Timeline, try breaking it down into separate steps:
1) Share / Create Video File (output a rendered dvd mpeg file)
2) Start a new project (empty timeline), and Share / Create Disc (then manually add your dvd mpeg file from Step-1).
Also, verify that the mpeg file plays fine at the problem spots on your computer (I use WinDVD or PowerDVD to play a media file).
Regards,
George
-
nethopper
- Ken Berry
- Site Admin
- Posts: 22481
- Joined: Fri Dec 10, 2004 9:36 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: Gigabyte B550M DS3H AC
- processor: AMD Ryzen 9 5900X
- ram: 32 GB DDR4
- Video Card: AMD RX 6600 XT
- Hard_Drive_Capacity: 1 TB SSD + 2 TB HDD
- Monitor/Display Make & Model: Kogan 32" 4K 3840 x 2160
- Corel programs: VS2022; PSP2023; DRAW2021; Painter 2022
- Location: Levin, New Zealand
It's not really a 'work around' but the standard workflow that many of us here use for each and every one of our projects.
Apart from actually working,
, it also has the advantage of allowing you to test the new DVD-compliant mpeg-2 file to see if everything looks OK, before you ever open the burning module.
And indeed, when I get to the burning stage, I tend always to burn first, not to a disk, but to a DVD-folder as this allows me to play back the final product on a software DVD player, again to see if everything looks OK. And if it is, then I use Nero to burn the DVD Folder to disk.
Apart from actually working,
And indeed, when I get to the burning stage, I tend always to burn first, not to a disk, but to a DVD-folder as this allows me to play back the final product on a software DVD player, again to see if everything looks OK. And if it is, then I use Nero to burn the DVD Folder to disk.
Ken Berry
-
nethopper
