Page 1 of 1

Very Slow editing of text in Ulead video Studio

Posted: Tue Jul 08, 2008 2:53 pm
by johanns
Hi

I would like to know what the maximum amount of characters is one can enter as a text overlay in a project. I need to add half a A4 page of text to scroll over the screen. I have done it before but can not remember it it was this slow to change or add text in the texbox. It is painfully slow¡K¡K¡K. Is this an Ulead VideoStudio thing :?:

Thanks
Johann

Posted: Tue Jul 08, 2008 4:21 pm
by Black Lab
I don't know of any character limit, nor have I experienced it being slow when editing text. Have you tried entering your text in someting like Word then cutting and pasting it to VS?

Also, updating DirectX seems to fix many preview related problems.

Posted: Tue Jul 08, 2008 7:31 pm
by Clevo
I have experienced the extreme slowness with a lot of text when using a long list of names for some end credits.

I had to break the list up into 3 parts to resolve the slowness but to be fair I was also using a drop shadow effect on the text, which seemed to add a lot of the slowness when either editing th text (in the preview screen) or changing alignments or fonts (formatting). any changes took a very long time to change onthe preview screen and my first attempts crashed VS

To resolve this... I did all my editing in the word document, imported using cut and paste into smaller sections, removed any text effects till I was finished editing and timing the scrolls.

Everything rendered fine when it came time when it came to sharing the project perhaps a tad slower.

The end result was excellent

Posted: Wed Jul 09, 2008 8:26 am
by johanns
Hi

The word option is how I am currently working. I have updated the directX as well. I will have to break it up then into sections as Clevo suggested. I was playing around with this idea but it is not optimal.

Clevo, you are correct the moment you start with different formatting it gets stuck before the changes are applied. Both my CPU¡¦s run at 100% for about a min or two. In my experience this points to a sub optimal .dll file.

Lets hope that Video Studio 12 have addressed this with an updated .dll file or something.

Thanks Clevo, Black Lab for the feedback