Skunberg wrote:I agree. But lots of people currently have 10ms and it would make it a snap for them to convert and get some more user's on board. They may change after they see the downside but it their call if you give them the option. I'm worried about going to 25ms. Lots of boxes to fill 🙂
Did you mean 100ms? 25ms would give fewer boxes to fill vs. 10ms, but certainly more than 100ms. 10ms is almost certainly overkill for non-video related lighting needs.
pmscientist wrote:Did you mean 100ms? 25ms would give fewer boxes to fill vs. 10ms, but certainly more than 100ms. 10ms is almost certainly overkill for non-video related lighting needs.
I'm guessing your thinking of fps not ms.
Just to make sure I am sync with all of this new and wonderful GUI and timings:
Last year you ran a 20fps rate (50 msec), and I think I hear you saying you will no longer use that rate and will be using a 40fps rate (25 msec) instead?
It really is amazing the amount of code you guys can produce as a side hobby. Just wow and Kudos.
------------------------
10msec rate = 100fps
25msec rate = 40fps
40msec rate = 25fps
50msec rate = 20fps
100msec rate= 10fps
Where fps = a complete refresh of all lights.
smeighan wrote:there is nothing stopping 10ms but i would highly discourage it.
the xseq files will become 5 times bigger than today
the SAVE button will take 5 times longerwe will be working some more on improving the save times. nothing we can do about the larger files.
You may find that the amount of channels that the FPP support without lag would drop
Today I have 32K chanenls @ 20fps
in the future 32K channels at 100fps?There is a new more powerful board the C1-ODROID that is 8 times more powerful that the current raspberry pi.
Not saying it cant be done, just for me I will never go below 25fps. The only reason of 25fps instead of 50fps is for playing back movies to get a more crisp lip sync
Skunberg wrote:I'm guessing your thinking of fps not ms.
The units you presented are ms, though what you're saying would make more sense if using fps. You said you were worried about going to 25ms from 10ms because of all the boxes to fill. That didn't make sense to me, 25ms timing requires fewer time slots/boxes than 10ms. Conversely, 25fps would require fewer boxes than 10fps.
Skunberg wrote:Sound's great! I use 50ms timing and would like to move to 25ms. But for others out there, I know that lots of people use 10ms timing so you might want to include that while your adding.
He actually said he was using 50ms timing and he would be going down to 25ms. He mentioned others were using 10ms.
