arcam branch #1
Description
Goal:
Allow to controll springs camera with a augmented reality device (android cellphone).
Thus allowing for a tabletop like gameplay with cardboard vr.
What happened so far:
The Google AR- AP was modified to transfer coordinates to spring.
This worked, as insofar as you are now able with the ar_widget in journeywar to controll the camera in game with a cellphone running the app.
Whats missing:
A way to transfer the desktop view as video with transparent background back to the cellphone and overlay it in the app.
Ideas for the approach:
- Open a Videostream server
- Stream with
https://opensource.com/article/19/1/basic-live-video-streaming-server - OBS streams the video to the server
-https://www.nan-labs.com/blog/embedding-videos-native-android-app/
Plain MediaController + VideoView
A second option, one which allows us to actually play the video within our app, is to use the MediaController and VideoView classes provided by the Android SDK. The solution is fairly simple and you depend on no third party library, but that comes at a price. You have no easy control customization for the video player nor advanced options, you would have to build such features yourself. It goes somewhat like this:
view raw
video-view-layout.xml hosted with ❤ by GitHub
private void loadVideo() {
VideoView videoView = (VideoView) findViewById(R.id.videoView);
MediaController mediaController = new MediaController(this);
mediaController.setAnchorView(videoView);
Uri video = Uri.parse("http://clips.vorwaerts-gmbh.de/big_buck_bunny.mp4");
videoView.setMediaController(mediaController);
videoView.setVideoURI(video);
videoView.start();
}
view raw
video-view-implementation.java hosted with ❤ by GitHub
So if you need very raw video playback capabilities this might do the trick. You will have access to playback controls that fade away but customization is a bit trickier. Take into account you need to provide the actual URI to the video file, you cannot use youtube links. In order to be able to provide YouTube video content you would have to go over our last option in this post.
After that: Its code cleanup. Optimization hell. And then begging beneath the wall of the org repo, with minstrel songs, until kloot shows mercy.