You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was reading the code of postprocessmovieforserial.sh and I've noticed that you're currently using an hardcoded resolution for the videos. I know the reason is that watches record raw streams instead of mp4s, but I was wondering if we could be a bit creative and sidestep the issue. We could get the resolution from some other source. One idea would be to look for that info in dumpsys output (see [here}(https://github.com/dtmilano/AndroidViewClient/issues/41), for example, or we could directly parse that out of dumpsys SurfaceFlinger output), or if that doesn't work, go on a hackier solution, which would be to grab a screenshot and see its dimensions, which will match the video.
Thoughts?
The text was updated successfully, but these errors were encountered:
I was reading the code of
postprocessmovieforserial.sh
and I've noticed that you're currently using an hardcoded resolution for the videos. I know the reason is that watches record raw streams instead of mp4s, but I was wondering if we could be a bit creative and sidestep the issue. We could get the resolution from some other source. One idea would be to look for that info indumpsys
output (see [here}(https://github.com/dtmilano/AndroidViewClient/issues/41), for example, or we could directly parse that out ofdumpsys SurfaceFlinger
output), or if that doesn't work, go on a hackier solution, which would be to grab a screenshot and see its dimensions, which will match the video.Thoughts?
The text was updated successfully, but these errors were encountered: