framerate :: thenth, hundredth?
NodeBox's Viewer module/window can differenciate hundredths (0.01) whereas a movie export appears to respect integers only (1.00).
To set the framerate for a movie export I use an additional "Divide"- or "Multiply"-node and connect it to the "Frame"-node.
–>
Is there a smarter, shorter way to define the framerate?
-
nb-framerate_2013-12-05.jpg
36.9 KB
nb-framerate_2013-12-05.jpg
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Frederik De Ble... on 06 Dec, 2013 09:30 PM
You should see frames always as integers, not as floating-point values.
Movie export can only work with integers. If you want to slow down the
animation, use a divide node as you do, or use wave nodes and set the speed.
Best,
F
On Thursday, December 5, 2013, thoolb wrote:
2 Posted by thoolb on 06 Dec, 2013 09:43 PM
okay. then it might help to alter the "play" section GUI – it DOES allow tenths and hundredths & in this view it works! Only export ignores those finetuning, right? (if yes: what for? (one or the other)). – How about a framerate setting in the export options window?
And, Yes, I'll try the wave node; its parameters min/max/period/offset/wave-type appear promising!
(p.s.: i still miss a node-reference for non-programmers which f.i. guides to the wave node hint by it- or even myself. Seems such manual/reference might be sorted in chapters other than "math", "string", "list", data" etc, cause those are, imho, not directy related to their character or usage or final, visual result, the node "color" excepted.)
Support Staff 3 Posted by Frederik De Ble... on 05 Feb, 2014 09:58 AM
You're right, it would make sense to make the current frame an integer as well.
With regards to animation, check out the working with animation page.