Scrolling title limit
Scrolling title limit
I've encountered a 5K limit exceeded message while compiling a scrolling title. I can work-around by using one title followed by another. My question is; is there an easy way to ensure that the two titles scroll at the same speed?
Cheers,
Simon
Cheers,
Simon
Hi Simon
I'm sure there'll be a more clever/ professional way posted but if it's a simple title, I've just copied and pasted the original title, to ensure it retains the same attributes, then typed over the text in the copy.
One point to bear in mind is to make sure you are satisfied with all the attributes (speed, etc,) before you copy. Otherwise you'll have to redo the copy.
Another possibility is to use CG Infinity if you have that programme.
Hope this helps.
I'm sure there'll be a more clever/ professional way posted but if it's a simple title, I've just copied and pasted the original title, to ensure it retains the same attributes, then typed over the text in the copy.
One point to bear in mind is to make sure you are satisfied with all the attributes (speed, etc,) before you copy. Otherwise you'll have to redo the copy.
Another possibility is to use CG Infinity if you have that programme.
Hope this helps.
Thanks & regards.
Gra
MSP8 (SP1), VS8, C3DPS, MF6+, DAZ Studio, Poser 6, Nero 6, Audacity, Photoshop 7.0
You can see a couple of my movies at [url]http://www.youtube.com/glaustin[/url]
Gra
MSP8 (SP1), VS8, C3DPS, MF6+, DAZ Studio, Poser 6, Nero 6, Audacity, Photoshop 7.0
You can see a couple of my movies at [url]http://www.youtube.com/glaustin[/url]
Whch version of MSP? You probably know that the titlers between 6.n, 7.n and 8.n are all very different from each other.
The MSP7 titler was very tricky with long scrolling titles and many used a vector graphics proggy for their titles, using Moving Path for the scrolling, for this reason.
The MSP7 titler was very tricky with long scrolling titles and many used a vector graphics proggy for their titles, using Moving Path for the scrolling, for this reason.
[b][i][color=red]Devil[/color][/i][/b]
[size=84]P4 Core 2 Duo 2.6 GHz/Elite NVidia NF650iSLIT-A/2 Gb dual channel FSB 1333 MHz/Gainward NVidia 7300/2 x 80 Gb, 1 x 300 Gb, 1 x 200 Gb/DVCAM DRV-1000P drive/ Pan NV-DX1&-DX100/MSP8/WS2/PI11/C3D etc.[/size]
[size=84]P4 Core 2 Duo 2.6 GHz/Elite NVidia NF650iSLIT-A/2 Gb dual channel FSB 1333 MHz/Gainward NVidia 7300/2 x 80 Gb, 1 x 300 Gb, 1 x 200 Gb/DVCAM DRV-1000P drive/ Pan NV-DX1&-DX100/MSP8/WS2/PI11/C3D etc.[/size]
Mmmmm! I wasn't aware of a size limitation or problem in MSP8 - I'll have a look and see whether I can find something.
[b][i][color=red]Devil[/color][/i][/b]
[size=84]P4 Core 2 Duo 2.6 GHz/Elite NVidia NF650iSLIT-A/2 Gb dual channel FSB 1333 MHz/Gainward NVidia 7300/2 x 80 Gb, 1 x 300 Gb, 1 x 200 Gb/DVCAM DRV-1000P drive/ Pan NV-DX1&-DX100/MSP8/WS2/PI11/C3D etc.[/size]
[size=84]P4 Core 2 Duo 2.6 GHz/Elite NVidia NF650iSLIT-A/2 Gb dual channel FSB 1333 MHz/Gainward NVidia 7300/2 x 80 Gb, 1 x 300 Gb, 1 x 200 Gb/DVCAM DRV-1000P drive/ Pan NV-DX1&-DX100/MSP8/WS2/PI11/C3D etc.[/size]
Gra
Thanks for the suggestion - which I've tried. The only problem is, if the text is longer (or shorter) in the subsequent title, the scroll speeds will differ and this is the problem I'm trying to correct. I can do this by increasing/decreasing the clip length but it's trial and error. Ideally, it would be nice to be able to make the correction easier.
Simon
Thanks for the suggestion - which I've tried. The only problem is, if the text is longer (or shorter) in the subsequent title, the scroll speeds will differ and this is the problem I'm trying to correct. I can do this by increasing/decreasing the clip length but it's trial and error. Ideally, it would be nice to be able to make the correction easier.
Simon
OK, I've had a look.
I found that you cannot Import a txt file greater than 5 kb: is this what you mean? Nor, apparently, can you paste in a large text (trying to do so results in "Not responding").
However, a 5 kb txt file of credits is simply ginormous and would bore viewers to tears. Typically, if typed out, it would cover several pages in typical credits formatting.
Just for a laugh, I imported an 11 kb txt into Corel Draw! in paragraph text and exported it as a TGA file with transparent background. The text box was 200 mm wide and about 3 m long (!!!). It imported perfectly into MSP8 as a graphics file and I was able to scroll it, with a Moving Path, over a video, no problem, zoomed for the text to fit the usable frame width. It took less than a minute to render and the clarity of the text was good with perfect overlaying. You may care to try this kind of technique with whichever graphics application you prefer.
I found that you cannot Import a txt file greater than 5 kb: is this what you mean? Nor, apparently, can you paste in a large text (trying to do so results in "Not responding").
However, a 5 kb txt file of credits is simply ginormous and would bore viewers to tears. Typically, if typed out, it would cover several pages in typical credits formatting.
Just for a laugh, I imported an 11 kb txt into Corel Draw! in paragraph text and exported it as a TGA file with transparent background. The text box was 200 mm wide and about 3 m long (!!!). It imported perfectly into MSP8 as a graphics file and I was able to scroll it, with a Moving Path, over a video, no problem, zoomed for the text to fit the usable frame width. It took less than a minute to render and the clarity of the text was good with perfect overlaying. You may care to try this kind of technique with whichever graphics application you prefer.
[b][i][color=red]Devil[/color][/i][/b]
[size=84]P4 Core 2 Duo 2.6 GHz/Elite NVidia NF650iSLIT-A/2 Gb dual channel FSB 1333 MHz/Gainward NVidia 7300/2 x 80 Gb, 1 x 300 Gb, 1 x 200 Gb/DVCAM DRV-1000P drive/ Pan NV-DX1&-DX100/MSP8/WS2/PI11/C3D etc.[/size]
[size=84]P4 Core 2 Duo 2.6 GHz/Elite NVidia NF650iSLIT-A/2 Gb dual channel FSB 1333 MHz/Gainward NVidia 7300/2 x 80 Gb, 1 x 300 Gb, 1 x 200 Gb/DVCAM DRV-1000P drive/ Pan NV-DX1&-DX100/MSP8/WS2/PI11/C3D etc.[/size]
CGI would be better for text with fancy effects while CD! would be better for typical credit screeds, IMHO.
[b][i][color=red]Devil[/color][/i][/b]
[size=84]P4 Core 2 Duo 2.6 GHz/Elite NVidia NF650iSLIT-A/2 Gb dual channel FSB 1333 MHz/Gainward NVidia 7300/2 x 80 Gb, 1 x 300 Gb, 1 x 200 Gb/DVCAM DRV-1000P drive/ Pan NV-DX1&-DX100/MSP8/WS2/PI11/C3D etc.[/size]
[size=84]P4 Core 2 Duo 2.6 GHz/Elite NVidia NF650iSLIT-A/2 Gb dual channel FSB 1333 MHz/Gainward NVidia 7300/2 x 80 Gb, 1 x 300 Gb, 1 x 200 Gb/DVCAM DRV-1000P drive/ Pan NV-DX1&-DX100/MSP8/WS2/PI11/C3D etc.[/size]
-
pennstat
- Posts: 47
- Joined: Tue Apr 19, 2005 2:31 am
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: ASRock M3A785GXH-128M
- processor: AMD Phenom II X4 945
- ram: 4GB
- Video Card: NVidia GTS 250
- sound_card: On-board Realtek
- Location: Pennsylvania, USA
- Contact:
Re: Scrolling title limit
Not only is the limitation on the text annoying as all he11, the ever since MSP7 the credits rendering engine is abysmal and really crushes your CPU and memory requirements. MSP 6.5 at least was clean and worked well.devil wrote:Just for a laugh, I imported an 11 kb txt into Corel Draw! in paragraph text and exported it as a TGA file with transparent background. The text box was 200 mm wide and about 3 m long (!!!). It imported perfectly into MSP8 as a graphics file and I was able to scroll it, with a Moving Path, over a video, no problem, zoomed for the text to fit the usable frame width. It took less than a minute to render and the clarity of the text was good with perfect overlaying. You may care to try this kind of technique with whichever graphics application you prefer.
I will only use the "graphics image as credits" from now on. I absolutely refuse to use the built-in credits function in MSP 7 or 8. Beyond just the text limitations, credits rendering in MSP 7/8 using no special effects except a basic bottom-to-top "fly" would crush my system to death. If MSP didn't crash my system entirely, the rendering plummetted from an estimated 2-3 hours during the rendering of the DV files to over 12 hours once it hit the credits. Additionally, memory and virtual memory usage would hover at around 300 MB through the rendering until it hit the credits at which point memory/VM usage skyrocketed to over 1.5 GB all because of the awful credits rendering engine!! (Sorry, but compared to how cleanly credits rendered in MSP 6.5, the 7 and 8 credits engine is awful.)
Using graphics for traditional, no-frills credit sequences is the only way to go as far as I'm concerned.
