#Rendering in 512×486
18 messages in this thread
I have a problem rendering in 512 X 486 in 3ds release 3. Once I start
rendering the resolution changes to 512 X 480. I have tried other variations,
but If the resoultion is from 512 X 450 to 512 X 490 it resets it to 512 X 480.
If Anyone can help I would really appericiate it.
Thanks.
Jeff,
The default resolution for a Targa 32+ is 512×486 when using RDPADI. You can
render to a broad range of resolutions if you render to NULL, as 3DS is image
independent of hardware. Just out of curiousity why would you want to render to
512×450… etc. ?
John
I'm rendering in 512 X 486 for video, I do logos for a local broadcasting
place. The editor asked me to render in 512 X 486, because it is the easiest to
dump to Beta Cam SP
>> I'm rendering in 512×486 for Video…
Did rendering to Null solve your problem?
John
Ya, I tried setting up the ADI drivers but that didn't work. So I tried null
and it worked fine.
Hi Jeff,
It souds to me that your default rendering resolution is set to 640 x 480. If
you render to with display on at 512 x 486, then, in order to fit the image in
the screen, 3ds will render 512 x 480. Either set your default rendering
screen to 512 x 486 in the vibrant configuration, or click on "no display" when
rendering.
-Kyle
I don't think my graphics drivers support 512 X 486. But I'll try it.
Thanks.
Just render to NULL instead of Vibrant, and you can choose almost any res ya
like!
What are your default settings for rendering display in 3ds vibcfg? As
was mentioned, you probably have them set for 640 x 480, I assume with the
Vibrant drivers. I use the RDPADI (Targa+) driver at 512 x 486 as my default,
so every time I load 3DS I'm ready to render for video.
Have you edited your 3ds.set file for resolution and aspect ratios? You
can change any or all of the four default buttons (settings) that appear in the
render/configure box within your 3ds.set. These buttons are handy shortcuts
for typing in different res & ar, but you may have to select different drivers
depending upon your needs.
Paul S.
I have set the aspest ratio in the 3ds.set file, but I sat the aspect ratio to
1.23, Is that correct?
>> I have set the aspest ratio in the 3ds.set file, but I sat the aspect ratio
to 1.23, Is that correct? <<
The correct AR for 512 x 486 should be 1.266, which gets rounded to 1.27
in the render/configure box. I'm not sure why, but I seem to remember the
default button values for 512 x 486 say 1.23 AR.
Paul S.
Paul, the default button does have 1.23 AR for 512×486. As a matter of fact,
256×243 AR 1.12 and 320×200 AR .82 all vary from what the correct calculation
would have them be. Why do you suppose? Even in that little publication "Planet
Studio" Brian Rudolph (ADesk Support) gave the correct formula for deriving
aspect ratio. Sure had me stumped. If anyone knows of an additional unknown
factor here, please chime in. While on the subject, some of you reading this
string no doubt use the PAR board. All the literature points to output of
752×480 which calculates an AR of 0.8511. I've gone out at that and things look
great. But, if anyone has comments that suggest otherwise, please advise. Note:
I loaded the 1.34b software and things are cranking fine. File management seems
to be managed <LOL< Jeffrey
With the PAR here we go out at PAL res of 756×576 and that works just booo-ful
Stuart, I work in NTSC and was curious to find out if other PAR users overscan
a few lines, and why. At 752,480,0.8511 I am getting good bleed on Prof Prod
Monitor. Does anyone out there use a higher res, and why?
Jeffrey:
>> I work in NTSC and was curious to find out if other PAR users overscan >>
a few lines, and why.
The PAR drivers just chop any resolution higher than the board accepts, so
rendering to a higher rez does nothing for you except waste rendering time and
make your files larger!
Greg Pyros
Greg, <higher res does nothing for you> That's what I suspected, thanks… Your
name keeps popping up on my monitor as I load and unload the PAR, how
reasonable that you should be answering this question as well. <G> Well, back I
go into Orthogonoville and finish what looks to be a very disgusting morph
sequence (ehehhehehehehehehehehehe… cough) Jeffrey
Jeffrey:
>> Your name keeps popping up on my monitor as I load and unload the PAR,
>> how reasonable that you should be answering this question as well.
Yes, we've benn know to have a few ideas with that beastie! But the PAR answer
of the day goes to Don Landis, for his excellent treatise on rotoscoping!
Every PAR user should download it and print it out for reference!
Greg Pyros
Greg, <answer of the day goes to Don Landis>: Righto – That should help any new
PAR users who can't figure out the subtle adjustments to rotos directly off the
PAR. I'm thrilled to be able to rotoscope and simult. write back to the PAR.
Not only does it give me tremendous HD flexibility, but I can check out
activity directly on the NTSC monitor. It also took me a week or so to realize
I could access .STLs directly on the PAR from within 3-DS. Also, when writing
an .STL to the PAR the NTSC Monitor will immediately display same write. So,
now, while developing my scenes and whatnot, I can *SEE* exactly what output to
tape will look like. So the whole thing is functioning as a nifty framebuffer
as well. I noticed a good deal of discussion about PAR and SPBETA / Broadcast
Quality. Here comes a subtle shift in the content of the conversation
::::subtle shift::: I am currently debating buying the Panasonic Pro S-VHS 850
player/recorder series. However, Sony has been offering their relatively new
bare bones BetaSP Deck. A couple of those would not be that much more expensive
than the S-VHS Gear. However, the S-VHS Gear would probably be more flexible as
an all-out editing rig. Any opinions? I'm wondering if by final mixdown it's
going to make much difference. Fully intend to derive final mixdown tape at 2nd
Generation. BTW, if it sounds at times like all these variables are driving me
crazy… COULD BE! <ROFL> Jeffrey