#Anim.Studio&PAR
11 messages in this thread
I am trying to write sequential TGA's to my Personal Animation Recorder without
any success. I get a message saying that this drive (the PAR) is a read-only
drive (which is not true) or I get a message stating that Anim. Studio cannot
write a temp file to the PAR (of course it can't). I can write these targa
files from all of my other windows graphics programs so is there a way to send
the export temp files to a standard drive rather than the destination root?
Also why can't I create compressed sequential TGA's? (Since I can't go to the
PAR I tried temporarily placing them on a standard drive but, WOW! lots of big
files – too slow and cumbersome!!!)
Mark,
I was able to get seq. targa's to my PAR drive, however it was in a kind of
round about way. First I created a simple anim. Then saved it as a targa (you
need to name it something like test0001.tga, Ani Studio detects this and saves
the anim as a seq.) I then tried to import these files to the PAR. No luck, PAR
told me that I had an incompatable file type (gave up trying the PAR software).
I then loaded the seq. into Razor/Pro and rendered to the PAR. TADA! It worked.
I think the problem was that Ani Studio created 32 bit tga files which are
incompatable with the PAR. Razor converted them to 24 bit.
Hope this helps
Pete, Imaginators
Mark,
Unfortunately, the PAR is not supported in r1.0 of Animator Studio. We are
aware of the problem and are looking at options for supporting it.
As a work around now, you can try Peter's suggestion of saving out to
sequential .TGA's and then dumping them to the PAR.
I had also heard of a PAR driver for Windows that would allow writing directly
to the PAR drive from within Windows apps. Haven't seen or heard about it in a
while though.
Jh
Jeremy —
<<Unfortunately, the PAR is not supported in r1.0 of Animator Studio. We are
aware of the problem and are looking at options for supporting it. >>
Does this also include support for Fast Video Machine DP/R, or are these
totally different animals?
Thanks,
— Marc
Marc,
Different animals, same problem though. I'm not an expert on the FAST system,
but a quick (& temporary)solution for the PAR is this:
1. Save out your animation as sequential images from AAS to a non-PAR hard
drive.
2. Use the PAR's software in DOS to assemble the sequential images into a file
that it can play back from the PAR drive.
Try it out and let me know what happens.
Jh
Jeremy,
Thanks for the response. The reason for my question is that I am considering
the purchase of a either PAR or a FAST DP/R.
<<Different animals, same problem though. I'm not an expert on the FAST system,
but a quick (& temporary)solution for the PAR is this:
1. Save out your animation as sequential images from AAS to a non-PAR hard
drive.
2. Use the PAR's software in DOS to assemble the sequential images into a file
that it can play back from the PAR drive.>>
I believe the process is similar with the FAST, but it would be more efficient
to be able to work in the native format and not have
to make the extra two conversions (one in each direction).
<<Try it out and let me know what happens.>>
I will do that once I have my system set up….
— Marc
Jeremy,
Thanks for the response. The reason for my question is that I am considering
the purchase of a either PAR or a FAST DP/R.
<<Different animals, same problem though. I'm not an expert on the FAST system,
but a quick (& temporary)solution for the PAR is this:
1. Save out your animation as sequential images from AAS to a non-PAR hard
drive.
2. Use the PAR's software in DOS to assemble the sequential images into a file
that it can play back from the PAR drive.>>
I believe the process is similar with the FAST, but it would be more efficient
to be able to work in the native format and not have
to make the extra two conversions (one in each direction).
<<Try it out and let me know what happens.>>
I will do that once I have my system set up….
— Marc
The PAR problem is so little of a problem that I wish Autodesk would fix it
with a simple patch.
The reason the PAR doesn't work in "native" format, is that when it writes to
the PAR, it writes more than Targa files. (The PAR can ONLY take TGAs in
sequence, anything in the middle messes up the aquisition.) AAS is writing a
temp file, or something, as it goes along. All we want is a simple fix… the
ability to specify a different "scratch" disk, or whatever.
Do you guys at Autodesk have any suggestions? Its so simple (in my little
mind) that with a little knowledge of the architecture a work-around could be
found.
Please. I can't afford the 1.8GIG per minute that an animation needs on a
standard HD. (On the PAR, its more like 200 meg/minute).
Jeremy,
I do all my work on the PAR. I just bought Animator Studio and ended up here
for an answer to my problem of outputing to the PAR. I'm very disappointed,
but will use the Razor Pro workaround.
Here's a suggestion. Instead of sending me (and probably others) the Animator
Studio Demo CD sales info in the mail every two days, put the money into
development. Bitching aside, a very impressive software package even for r1.0.
Congrats to everyone.
byron
Byron,
Thanks for the input. Sorry about the marketing dump on you-we're just so
excited about Animator Studio!<g>
Jh
Jeremy,
>>Sorry about the marketing dump on you-we're just so excited about Animator
Studio!<g>
I understand. You definitely have a reason to get excited. A perfect
companion to 3DS.
byron