--
You received this message because you are subscribed to the Google Groups "Tributary" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tributary+...@googlegroups.com.
Visit this group at http://groups.google.com/group/tributary.
For more options, visit https://groups.google.com/groups/opt_out.
I agree that easier is better. Its just about us deciding the use cases /parameters and building the ui. Something like the bv button was but it makes gig frames instead (I removed by button for now)
What are the params?
# of frames
Delay per frame
Loop type (should it go back to start or not) only matters when you have a loop.
If you don't have a loop we need to know how often to take a screencap.
Anything else?
All the gif related features are plugins and will be easy to port to the new tributary.
I whole-heartedly agree, and I'm actually amazed at the smoothness of the GIFs that Paul got just by doing it by hand.I really like the idea of being able to define the total frames, and have it capture it for me. It would also be extremely useful to be able to capture every other frame, or every 3rd frame to cut down on the file size.I really think making a gif should be as easy as defining a trib.anim, and hitting the gif button. That makes a lot of sense. The more "advanced" GIF'ing, with the clicking and holding, is more of a power user thing anyway, in my mind.How transferrable is the gif stuff and trib.anim to the new Tributary.io?Cheers,EJ--
EJ Fox
@mrejfox
--
You received this message because you are subscribed to the Google Groups "Tributary" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tributary+...@googlegroups.com.
Visit this group at http://groups.google.com/group/tributary.
For more options, visit https://groups.google.com/groups/opt_out.