T2.0 Slower ???
9 messages in this thread
Has anyone noticed that the 2.0 software is slower. It seems like it takes
twice as long to save and especially load framestores and the CG even seems
like it takes longer. I thought it had all been optimized! Anyone else
experience this ? I have an unaccelerated 2000. I am considering having the
1.0 software available to load for live work. any suggestions? thanks,
brian
I hope that some one here can tell you how to fix this problem, because as
far as I am conserned it's very noticabley faster. I have an A2000 w/ 030
but I had them before the new software. Frame loads use to take 3 to 5
seconds but now they load in about a second. However frame grabs in to
TPaint are consederably slower. The CG May be faster or not I did not do
alot w/ it before….
Gut Luck Brad Hayes
Brian, I use 2.0 on an acellerated 2000 and quite honestly I have noticed a
definite speed up in saving and especially loading framestores. As far as
CG slice loading time, that can be slowed down by the amount of fonts you
have in your book. I suspect however that you are probably having stack
overhead problems with your HD. Your HD might be too fragmented or too full
to the brim, you might try reformatting and re-installing 2.0. Hope this
helps.
Frank
Frank,
unfortunately, that is exactly what I did to my hard disk before loading up
toaster 2.0 . I did change hard disk controllers (from an IDE adSCSI to a
GVP series II, but I didn't think that would translate into seconds of time
difference.) Maybe I just have a bad memory, but it sure seems slower to
me. Incidentally, the CG time difference wasn't slice loading but render
time. Come to think of it, I guess it must be my memory. I'm trying to
remember how I flipped one CG set of text into another using the single
tumble transition. Now that I have 2.0 loaded up, I get it to work any
more! How the heck do you use the transitions to change the CG text over a
single program input…. I must be loosing it. (Most of my recent video
work has been 'on location' and I've been waiting months for the 2.0
software to edit it). I've turned into a vidiot !!!
Brian
Brian, 2.0 definitely is faster. make sure you have the newest GVP
rom(4.x) Also make sure the mask setting for your drive has seven F's
listed in it. (in GVP's faastprep) To tumble CG text do the following: Load
your CG page. spacebar it up then back down so your overlay is no longer
flashing. Put it up into overlay and adjust your clip level so it's keyed
out right. Turn the keyer off and make sure the buffer with your page is
loaded on preview. Turn the keyer back on (just by clicking on scissors)
and then execute your effect. This will automatically key the buffer over
your source.
How do I check the version of the ROMs? Is it on them duh duh duh ??? I
called them and got told some procedure that didn't work. Man, I just don't
undersTAND why I'm having so mch trouble with the Amiga!! Thanks for the
refresher on tumbling CG, I'll try it tonite. Brian
Brian, the version # sjould be on the rom chips but I know GVP for awhile
had old labels on their roms…go figure…
Frank, I saw your note to brian about a speed up in saving and loading
framestores with 2.0 on an acellerated 2000. Do you mind me asking "How
accelerated?"
I'm thinking about an 040 at 25 MHz, but I heard from someone that the
68040 accelerator is actually SLOWER than the 68030 with a 68882 math
co-processor , especially when doing texture mapping and with fractals and
bump mapping of 3D objects in Lightwave. This is supposedly because the 040
does not have a math co-processor and the math libraries are incomplete.
What do you know of this?
Cheers,
Jim in Kobe
Jim, I'll have to plead ignorance on the 040 question since I don't have
one. I have a GVP 030 w/coprocesser running at 28mhz and I am reasonably
happy with render times. My note to Brian had to do primarily with
framestore saves and loads. The 1.0 version of Toaster would actually SLOW
DOWN the saves of framestores because of internal video timing issues,
that's all been fixed in 2.0 which is a big help for those of us who use
the framestore function frequently. The new framestore format also uses a
compression algorythm which saves a lot of space. Something you will have
less of after installing 2.0!
Frank