Thank - useful.
The limitation is CPU speed at the moment. From the limited tests I have run. ffmpeg & raw2gmv is limited by CPU speed.
Quote:
|
Or keep going through an extra shell layer that uses nc to dump that in a local FIFO, but that seems like a waste when you can just do nc's job in C directly ;p.
|
When I only have a hammer in your toolkit, everything looks like a nail. I need to improve on my c & sockets skills. I have not done socket in c for 20 years.... even then not well.... Bare metal is fun. Might investigate
https://github.com/NiLuJe/py-fbink/blob/master/hello.py
However, as per you first reply - a better way could be - transcoder then simply throw the frames at FBInk's print_raw_data. I expect ffmpeg is do that quickly, even if I need to split the screen in to quarters again.
Firing up a debian vm....
I pretty sure - based upon loopback test that the USB HDMI capture is never going to be better than 800ms
https://barwap.com/projects/okmonito...ation/#/laglag But shaving off the other 400ms would be good. Also fbink is on more than just PW1.
Any thoughts on max fps for fbink ?