3DS4 and GVRS-950 HELP
10 messages in this thread
Hello,
I'm having trouble sending sequential TGA's to the Sanyo deck. The deck
initializes just fine. If I use Disk to VTR, 3ds starts sending the TGA's to
the buffer, but the deck just sits there. If I stop this process by using the
ESC key and then try to re-initialize the deck, 3ds locks up.
If I use Video Post, the deck begins recording, but after anywhere from
30 to 100 frames the deck stops and 3ds continues spitting out the TGA's.
Again, if I stop the process and try to re-initialize the deck, 3ds locks up.
I've tried booting the system with and without QEMM.
My system is a P-90, with Diamond Stealth PCI and Adaptec 2940 PCI. The
Sanyo is using COM 1.
Thanks,
HH
Harley,
Did you ever get a solution to your Sanyo Problem? We don't have a Sanyo deck
here in product support, but I do remember reports of similar problems when the
tape was not striped properly.
-Brian
Brian,
Thanks for replying. (I was beginning to think no one cared 🙁 ) There
was some conflict involving the com ports on my computer. I finally tracked it
down and the Sanyo will now merrily click away all night long.
Now, problem number 2. When I render to TGA's my machine locks up. I
set up a number of renderings over the weekend, only to come in this morning
and find that the gas gauge was frozen. 3ds locked up on frame 91 of a 400
frame animation. This was the first job in the queue (single machine setup).
Friday I switched from an Illuminator-Pro to a Targa+ card (the Illuminator-Pro
conflicted with EVERYTHING) with no problem. My swap drive has almost 800MB
free. Any ideas?
Thanks
Harley
<<When I render to TGA's my machine locks up… Any ideas?>>
The first thing to always try in this situation is to see if this problem still
occurs in a stripped environment. REM out everything except FILES and BUFERS in
your config.sys and MOUSE in your autoexec.bat. Start rendering and see if the
problem happens. If yes, we need to look at the hardware. If no, then we start
adding things back into your boot files one line at a time until we determine
what is causing the problem.
-Brian
Brian,
Again, this turned out to be something very simple. This time a typo in
the line configuring my Targa card in my config.sys file was the culprit. I ran
the same process with the net queue last night and everything appears to be
normal. So far, life is a lot simpler without that Illuminator-Pro card.
Thanks much,
Harley
<< Thanks for replying. (I was beginning to think no one cared 🙁 ) There
was some conflict involving the com ports on my computer. I finally tracked it
down and the Sanyo will now merrily click away all night long.>>
Could you outline the problem/solution for me so I can add it to our database?
-Brian
Brian,
<< Could you outline the problem/solution for me so I can add it
to our database? >>
Certainly. The problem occured when laying sequential TGA's to tape.
The Sanyo would initialize just fine. If I used Post and IFL's, the machine
would begin recording and then anywhere from 10 to 100 frames later would just
stop. 3ds would continue to churn out frames as if the deck was telling it
everything was fine.
If I tried to use Disk to VTR, the deck would initialize, 3ds would ask
it's usual questions and then start sending out the TGA's. Only this time the
deck would do nothing. If I stopped the process using the ESC key and tried to
re-initialize the deck, 3ds would lock up.
The solution turned out to be very simple. Sometime ago I had installed
another high-speed I/O card to run some tests. I had since forgotten it was
there. After yanking out the card (gently, of course) the problem disappeared.
Since (at least on my system) the IRQ's only allow for two com ports, the third
one was screwing things up.
As is most often the case, it was my own fault. I have had so many card
and IRQ conflicts because of that silly Illuminator-Pro that I can't keep track
of what is in my own system!
Harley
Sometimes people render to Net Queue. They then put their machine into Slave
mode, and if there are any problems during rendering there's usually an
excellent log file to scrutinize for clues.
Nik,
<< Net Queue . . . there's usually an excellent log file to
scrutinize for clues. >>
Turns out (as usual) to be my own fault. In my haste to rip a Matrox
Illuminator Pro from my system and replace it with my tried and true Targa
card, I left a typo in my config.sys file. Everything seems smooth now.
Thanks!
Harley
"left a typo in my config.sys file"
Whew! Now, how many times have *I* done that! Glad you're running.