Mon, Dec 2, 11:25 AM CST

Renderosity Forums / Vue



Welcome to the Vue Forum

Forum Moderators: wheatpenny, TheBryster

Vue F.A.Q (Last Updated: 2024 Nov 30 5:12 am)



Subject: Animation and problems co-ordinating with Poser


toashzadel ( ) posted Mon, 02 September 2002 at 4:14 PM · edited Mon, 02 December 2024 at 9:05 AM

I am just trying to get to grips with this Mover business, and I noticed something; the timeline in Vue is in seconds, and the timeline in Poser is in Frames! is there any way to change one of them to match the other, it will make things easier for my poor little brain! I'm no good at math!!! thanks Steve :o)


gebe ( ) posted Mon, 02 September 2002 at 4:38 PM

In Vue, 1 second=15 frames when in default mode. This is also the problem what I have to resolve, because there is something not clear for me yet. I supposed that 300 frames in Poser=20 seconds in Vue, but it's not:-(. It's 11 seconds as far as I understood. We have to find out the relation together. Hm?? Guitta


wabe ( ) posted Tue, 03 September 2002 at 1:18 AM

file_22311.jpg

hi, wouldn't it solve the problem to switch simply the default 15 frames rate in Vue to 25 frames per second? Walther

One day your ship comes in - but you're at the airport.


gebe ( ) posted Tue, 03 September 2002 at 3:16 AM

No Walther, because it takes too long to render for a simple animation:-) Guitta


wabe ( ) posted Tue, 03 September 2002 at 5:23 AM

i fear that this answer is too easy! If you want to save render time, why are you rendering 15 frames per sec and not only 10?? The reason for 15 frames per second in an animation is only, that in the older days computer were not fast enough to show all 25 frames (of a second) while playing videos. So somebody thought 15 would be enough (and nobody would see a difference). But if you want to do animations properly (and professionally) you must use the video standards - full stop. And these are 25 frames per second for PAL, 30 frames per second for NTSC. And if you are a high pro, even these 25/30 frames per second are not good enough. You have to go to 50/60 frames because in fact each video-frame is separated into two images with half the resolution. Anyway, Poser is right to deal with the frame rate professionally (the only minus is, that you can't change the frame rate there). :-)) Walther

One day your ship comes in - but you're at the airport.


gebe ( ) posted Tue, 03 September 2002 at 5:30 AM

I don't do professional videos Walther. Just for fun. I'm just a beginner in animation and I have not the pretension of doing something as great to need a professional render. Rendertime for my swan video (300 frames, 20 seconds) was 21 hours on a network (two computers). :-)Guitta


wabe ( ) posted Tue, 03 September 2002 at 5:56 AM

Sorry Guitta, that was not the intension. I only tried to explain why Poser is dealing with frames and why they are right to do it like this. I really love your work - including your animations! But frame rates are a little like resolution in stills. You have to deal with some givens. And 21 hours of rendering doesn't sound bad at all. I can remember a lot longer rendering times for animations in this early days of computer animations. By the way, our record in rendering for one frame (in Bryce) is three weeks!!!! That hurts. :-)) Walther

One day your ship comes in - but you're at the airport.


gebe ( ) posted Tue, 03 September 2002 at 6:03 AM

WOW, 3 weeks! I cannot do that, because my computers are my working instruments. And when I render animations, I have to take care what I'm doing. Other (Windows) programs I'm working (my regular work) witch needs lots of memory and they also may crash and I have to reboot the computer. This means I loose all my animation renders, because AVI cannot be resumed. Very bad:-( for me. :-)Guitta


gebe ( ) posted Tue, 03 September 2002 at 6:04 AM

What I have to add: We NEVER can pass 3 weeks without a Poxer cut. That's again another story:-(


wabe ( ) posted Tue, 03 September 2002 at 7:33 AM

Yeah Guitta, three weeks. The computer (Mac G3) was not needed for that time (luckily we were able to do our regular work on other machines). And Bryce hasn't told before how long this renderer will take. I remember, after 2 days i wanted to know who's nerves are better - mine or the computers. After 4 days i disconnected the mouse to reduce the possibility that somebody kills the renderer by accident. After 2 weeks i became a little nervous. The rest was waiting! And waiting. And waiting. :--)) Walther

One day your ship comes in - but you're at the airport.


toashzadel ( ) posted Tue, 03 September 2002 at 1:54 PM

thanks guys for the interesting insights! 3 weeks?! I've never waited longer than 18 hours for a still! I'd just get bored ;) But, in conclusion, we still don't know how to co-ordinate frames? :( 300 frames at 11 seconds is 27ish fps.... I don't get it! :(


gebe ( ) posted Tue, 03 September 2002 at 2:00 PM

Sorry, it was 10 seconds, not 11. Mea Culpa! guitta


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.