#Imagine starts working!
12 messages in this thread
I moved this thread from the NewTek forum over to hear. Peter, thanks for
getting me going. I finally got to page 172 in the Imagine manual and found
out that I had to click on the "NEW" button in the project editor window to get
to the output choices. Ohmygawd. How in the world do these guys stay in
business? Anyway, I got my PC version of Imagine today and now I am cooking on
both the Amiga 3000 and my clone 486-33. The clone is a bit faster. Is your
plan to generate sequences of 24 bit ILBM files on the PC and then null modem
them to the Amiga for compiling as DCTV anims? The PC version is uncannily
close to the Amiga version. You can't use any DOS6's EMM386.EXE. I find I
have no problem just rem-ing that line from my start up sequence. I notice on
the Amiga version that when I call up DCTV as the output format in full
overscan (736×482) that things really slow down quite a bit. I wonder if it
makes more sense to generate a 24 bit ILBM and then convert it with DCTV
itself? Is the Imagine movie version worth rendering in? Is it any better than
a DCTV 4 bit anim in anim7 format?
Imagine version Anims are kinda useless IMHO tho they are EASILY editable
in a Text Editor but are incompatable with everything.
Yes I plan to Null modem or possibly Ethernet the Amiga and Clone together
to share files.
>I notice on the Amiga version that when I call up DCTV as the output
>format in full overscan (736×482) that things really slow down quite a
>bit.
What other format are you comparing it to? HAM? If so the answer is
simply, HAM is Lores (320 pixels wide) while DCTV is Hi-res (640 pixels).
More pixels slow down rendering.
>I wonder if it makes more sense to generate a 24 bit ILBM and then
>convert it with DCTV itself?
You will spend the time converting 24-bit files to DCTV as well, so if you
are only going to DCTV then I would suggest to render directly to that
format.
>Is the Imagine movie version worth rendering in?
I would have to say, No. It is not that it is bad, just no support as far
as viewers go.
<<< Tony D. Tracer >>>
It's better to render at IFF24 then convert to DCTV as the Imageprocessors
do a better job of it than Imagine does. Not a Huge Difference but
noticeable
>It's better to render at IFF24 then convert to DCTV as the
>Imageprocessors do a better job of it than Imagine does.
You are right but I thinking more in terms of a person with limited
resources and/or knowledge. It is also faster to go directly to DCTV but
you will loose slightly.
<<< Tony D. Tracer >>>
Ahhh Very True. It will save space if you have only a small HD if you
Render Directly as DCTV mode images than to do the IFF24's
The rendering system in Imagine makes a lot of sense if you thing about
it. You start a New rendering subproject and get the requester to set your
resolution. You can modify the subproject and reset the resolution or
start a New subproject. This way you can have one project rendered in
lo-res scanline and have another project in hi-res trace for your final
animation.
I've been using DCTV with Imagine for quite a while. If you're short on HD
space it makes more sense to render to DCTV. Imagine writes a 24 bit file
to the DCTV.library which converts it to a DCTV image and stores it to the
disk. The DCTV files are a lot smaller than the 24 bit files would be so
you can save a lot of hard drive space doing this. For some animations you
can save a lot of time by rendering lo-res 24 bit images and converting
them to DCTV. (Imagine can't save lo-res DCTV images)
Playback speed can also be a consideration. I often render 24 bit images
and convert them to DCTV in Overscan-lace-4 bit, then Overscan-no-lace-4
bit, then Overscan-no-lace-3 bit. Since I'm starting with a hi-res 24 bit
image I can just keep decreasing the quality of the DCTV images till I get
decent playback speed without re-rendering.
The only advantage of using the Imagine movie format is that you can loop
certain parts of the anim. For instance: You've modeled a torando and you
want to do an anim of the camera backing away from it. You make the anim
400 frames. The first 200 are of the torando spinning and the second 200
are of the camera backing away. Render as an Imagine movie and edit the
text file to make the first 200 frames loop 5 times then play the last
200. This way you get a good look at the torando before the camera backs
away. You get an effective playback of 1200 frames but you only had to
render 400. :^)
BTW Jeff, I uploaded a 100 frame DCTV anim last night to Amigaarts area if
you'd like to see a example of some of my work. 640K download.
filename is Armoury.LHA
Hi Peter,
have you ever made any .FLI or FLC files? I have a PC so I can't play any Amiga
files, but I would like to see some animations made with Imagine.
TIA
-David
I've only done 1 FLC so far, it used the BD-Girl object(been having alot
of trouble with Commercial objects turning up in PD download areas lately
haven't I?) and had the Camera Zoomed in on her Rear while she went thru a
Walk Cycle. I no longer have a copy of the FLC tho. It is Available for
Download on a NY area BBS tho, the BBS is called Insprivision and is a
IBM/Clone based BBS.
their phone # is 718-854-6411
Jeff thanks for the tips on Imagine. I have been having many crashes on my PC
version of Imagine 2.0. I hope 3.0 is more stable. Everything I do eventually
ends up in DCTV 3 or 4 bitplane anims, so your tips about generating DCTV
frames makes a lot of sense. Do yo compile the frames with rend24?
I have used Rend24 to convert my anims to DCTV. I haven't had time or hard
drive space to do any anims for a while. I've also used a custom program I
hacked together a couple of years ago to do the same job. (I prefer Rend24
though)