hi all,
i'm beginner user in raspberry world, please exuse stupid questions on side. grounds query simple - looking new gaming tv myself. , of course there issue of input lag, modern 4k tvs of large sizes.
thinking - instead of looking endlessly through input lag databases (which not have many tv models still) or paying 70.gbp hw tester (like leo bodnar's device http://www.leobodnar.com/products/lagtest/) wouldn't possible realize on raspberry?
need battery packed rp camera , hdmi cable. raspberry issues timed hdmi signal , registers picture changes own camera. response timed - , need know input lag+pixel response!
pros:
standard stuff may used. simple , closely @ no cost @ all. (i'm not counting program development @ moment
)
cons/thoughts:
- have no idea real time applications in rp. how precise can made on 'standard' platform? presumably, milliseconds range no problem?..
- 'standard' platform use? real-time linuxes? or raspbian? trade-off between programming simplicity , highly customized solutions...
- best way time hdmi signal being given out?
- best way detect picture change through camera? or maybe black white photo element? , how quantify delay of such detection assess measurement error?
- can issue 4k signal pi2?..
- inventing bicycle , there existing (i did not find anything)?..
guide points, thoughts , comments welcome!
time functional nicely round tv testing software developed out of this... i'm worried input lags
in advance, all-knowing-all!
i'm beginner user in raspberry world, please exuse stupid questions on side. grounds query simple - looking new gaming tv myself. , of course there issue of input lag, modern 4k tvs of large sizes.
thinking - instead of looking endlessly through input lag databases (which not have many tv models still) or paying 70.gbp hw tester (like leo bodnar's device http://www.leobodnar.com/products/lagtest/) wouldn't possible realize on raspberry?
need battery packed rp camera , hdmi cable. raspberry issues timed hdmi signal , registers picture changes own camera. response timed - , need know input lag+pixel response!
pros:
standard stuff may used. simple , closely @ no cost @ all. (i'm not counting program development @ moment
)cons/thoughts:
- have no idea real time applications in rp. how precise can made on 'standard' platform? presumably, milliseconds range no problem?..
- 'standard' platform use? real-time linuxes? or raspbian? trade-off between programming simplicity , highly customized solutions...
- best way time hdmi signal being given out?
- best way detect picture change through camera? or maybe black white photo element? , how quantify delay of such detection assess measurement error?
- can issue 4k signal pi2?..
- inventing bicycle , there existing (i did not find anything)?..
guide points, thoughts , comments welcome!
time functional nicely round tv testing software developed out of this... i'm worried input lags
in advance, all-knowing-all!
afterthoughts:
1. photosensor easier camera picture analysis. if photosensor supplies voltage according light strenght - black out screen, analyse voltage second base line send hdmi signal "black-->white" , measure when peak in readings appear. choosing sensor question.
2. realtime kernels read give predictable latency of not more 200 microseconds. find more acceptable task @ hand - no need account detection delays. if measure between 10 , 200 milliseconds error of kernel below 2% good. hope rest of processing hw shall not give in addition.
3. hdmi signal "black->white" got me thinking. dont want display black or white image because take time sort out image... best way make transition? smth "all pixels on" command?...
4. there no adc learned, tutorials show rc sensing schemes... try begin with, can achieve cycle times measurements of ca. 1000 microseconds ok time being...
usual, comments on improvements welcome...
1. photosensor easier camera picture analysis. if photosensor supplies voltage according light strenght - black out screen, analyse voltage second base line send hdmi signal "black-->white" , measure when peak in readings appear. choosing sensor question.
2. realtime kernels read give predictable latency of not more 200 microseconds. find more acceptable task @ hand - no need account detection delays. if measure between 10 , 200 milliseconds error of kernel below 2% good. hope rest of processing hw shall not give in addition.
3. hdmi signal "black->white" got me thinking. dont want display black or white image because take time sort out image... best way make transition? smth "all pixels on" command?...
4. there no adc learned, tutorials show rc sensing schemes... try begin with, can achieve cycle times measurements of ca. 1000 microseconds ok time being...
usual, comments on improvements welcome...
raspberrypi
Comments
Post a Comment