you can configure after how many seconds the client should ask the server is any updates are available. Out of the top of my head it does this once every 15 minutes or so. It is set in the site.cfg file.
What is wrong with the text option, because as far as I am aware this is working on the client. If you mix clients and servers make sure they all are the latest version to prevent incompatability between the client and server data-files.
And YES YES YES last night the first hardware accelerated movie showed its ugly head on my pi. In a frustrated moment I went back to the source of the code I am using, namely hello_video in the hello_pi folder of the VideoCore code ( /opt/vc/src/hello_pi ).
I thought I would test if it ran my video and then try to figure out the differences between this code and the code in libAVG. Seems that this code is only able to play the movie supplied with the code. I tested it with my downloaded version of big buck bunny ( which is H264 in a MOV container ) but it won't show the movie. Playing it with the version supplied with the source code showed the movie. So I included that version in the libAVG sample I use to test my code with and YEAH BABY we have video.
Seems the decoding scheme is hardcoded into the code. Great. I also tested both video's with omxplayer and he plays both just fine, so guess who is crawling through the omxplayer source code right now
. Problem is both were writting with a completely different base in mind so mapping code from one to the other isn't straight forward, but I atleast have a starting point to continue from.
At current the code doesn't :
- scale the movie to size, so it is cropped to fit the canvas window
- end the movie at end of file, so libAVG never ends the player
- clean the OMX components after itself ( ah well we have half a gig of memory, how fast will this memory leak fill it all )
Hope to have more advances in the coming days, but atleast my frustrations about this project lifted a bit now I finally see that this code really does something