I wasn't saying I expected 60 fps and 64 shades, I was saying those were my ideals. I expect/plan to get worse performance (that is, lower frame rate and shade count) if I use an arduino.
why you mentioned bytes and bit stuffing where you did
that will be very difficult for Arduino to handle (read not)
Also not sure how you got 600,000 bps instead of 360,000, or 75,000 instead of 60,000.
Where would this bit stuffing come in?
Why does the baud have to be so much higher than the bit rate for a simple multiplexer
Also bear in mind that 1000 bytes of frame data will take almost half the RAM on a atmega328p. You won't have enough RAM to display the current frame
Could you explain?
I'll be running animation and audio visualization/audio processing software from my laptop
I'm curious what kind of software :QuoteI'll be running animation and audio visualization/audio processing software from my laptopis capable to create 3D animation ? There is a link: http://www.elcojacobs.com/shiftpwm/ , it says limit 768, w/ 75 fps. So you should be o'k with 60 fps.
I haven't written it yet :3Most of that comes after it's built.
Please enter a valid email to subscribe
We need to confirm your email address.
To complete the subscription, please click the link in the
email we just sent you.
Thank you for subscribing!
via Egeo 16