Just a suggestion…
since our setup is quite complex, we load a lot of images and we are very cautious, in order to be on the safe side we were thinking about restarting info-beamer (standalone) periodically so as to avoid memory leakages due to our
node.lua and out of memory errors due to poor resource management on our part.
I know it’s not good programming practice but given the situation (imminent exhibition, first public display of our
node.lua setup… it has a reason to be. It’s just a safety net.
Moreover the same solution can be used just when loading images gives an error (for example) or other well known and documented situations.
We are of course talking about info-beamer standalone.
The problem is, between shutting down and restarting info beamer there’s a black screen for around 1 second (due to resource loading mostly)… not terrible but we were thinking around it.
We came up with this solution:
0) display the background image
menu.png to raspberry framebuffer via
- start info beamer service with the variable
- on certaing given transitions of the UI, issue a sys command (still to be investigated) that will do
service -d /service/info-beamer; service -u /service/info-beamer
- the service will go down and up, and while loading the node, it will be transparent and display the
menu.pngfile. If the first image displayed by our node is the same, the trick is done and it’s almost impossible to notice.
We have dona proof of concept and it works.
2) issue a sys command from LUA
0) with fbv the image does not go in overscan so it’s kinda shrinked and doesn’t reach the border of our monitor