Patch needed?

[TDK1044]

Video Studio 10 seems to me to be the most stable Video Studio software ever released by Ulead. I have no issues at all with it at this point, but I tend to keep my capturing, editing and burning pretty straight forward. I capture DVD NTSC, edit with the same properties, add a few filters, effects and audio layers and then render and burn. So, for me, VS10 is great. I was wondering though whether any of the more demanding users of VS10 have seen anything that would require being fixed as part of a patch release?

[Trevor Andrew]

Hi Terry

Yes, read this post.

http://phpbb.ulead.com.tw/EN/viewtopic. ... highlight=

I have approached tech support but as yet not got passed the auto responce

Trevor

[Black Lab]

Also, see this http://phpbb.ulead.com.tw/EN/viewtopic.php?t=14435

[dblml320]

Video Studio 10 seems to me to be the most stable Video Studio software ever released by Ulead. I have no issues at all with it at this point, but I tend to keep my capturing, editing and burning pretty straight forward. I capture DVD NTSC, edit with the same properties, add a few filters, effects and audio layers and then render and burn. So, for me, VS10 is great. I was wondering though whether any of the more demanding users of VS10 have seen anything that would require being fixed as part of a patch release?

I have seen a weird one ... If I set the default clip time to "N" seconds, and then add a transition somewhere in the time line, after this when I add a new clip, the time will be set to (N-1).29 Seconds, or just about a half second shorter than the default value. I have not seen this in versions before VS10. I also have seen a similar thing where if the clock says a clip is N.29 seconds long, if I hit the 100th of a second arrow to increase, the time round up to the next second, instead of incrementing the hundreth's value.

[Xyzzy2]

I have seen a weird one ... If I set the default clip time to "N" seconds, and then add a transition somewhere in the time line, after this when I add a new clip, the time will be set to (N-1).29 Seconds, or just about a half second shorter than the default value. I have not seen this in versions before VS10. I also have seen a similar thing where if the clock says a clip is N.29 seconds long, if I hit the 100th of a second arrow to increase, the time round up to the next second, instead of incrementing the hundreth's value.

I think frames are counted, not 100ths of second, so you get max 29 for NTSC and me max 24 for PAL.

X.

[dblml320]

I think frames are counted, not 100ths of second, so you get max 29 for NTSC and me max 24 for PAL.

That would explain it. But if that is the case, I wish Ulead would not make the control look like a time setting. It is misleading if it is indeed showing frames for the number to the right of the decimal point.

[Ken Berry]

Sorry, but it is not Ulead's 'fault' -- they are using an accepted standard in showing "H:M:S:F". And you will find exactly the same thing in other video editing programs from other companies (Adobe, Sony, Cyberlink to name a few).