Originally Posted by enovison
-That makes sense for the IP address as I am in fact running a vpn. Look forward to seeing what solutions you come up with!
- I agree with your assessment of the auto downloading recommendation. I actually wrote this before checking out the new version. All of those issues were addressed. I suppose the only solution to any user legwork would be if it could listen to the movie and know the movie and timestamp similar to Dbox. I imagine that would be no easy task and prob far off in the future.
Btw, don’t get me wrong, it’s working great and Like you said I already can see the groundwork being set for using a headless processor like raspberry pi
I am actually planning an audio sync method to sync from a microphone in the room connected to the computer or pi. This will expand the user base to many more people as they will be able to use any movie source, like disc players and even streaming services.
This is also why using a ras pi will be so important as these disc player and stream box users wont have a windows PC anywhere near their theater.
However, there is another challenge potentially preventing the full automatic movie loading even when using audio, and that is that the database for doing audio matching is not small. Something like 100MB per movie.
And given the spirit of this project, I want to try to keep it cheap, and a ras pi is cheap, but it's not some super fast processor. If I wanted fully automated audio matching, I would need the user to have every 100MB audio fingerprint database entry downloaded ahead of time stored on their ras pi. And second, the pi needs to be able to process this audio and perform the database search. This works significantly faster if the database can be stored in RAM rather than on disk like the SD card. But you can't store so many audio matching database movie records in the limited RAM in a ras pi.
So even with audio matching, it's likely the user will need to open the phone app and pick which movie they are about to watch, so the software can load just that database record from SD card into RAM. This will make the time code lookup (sync) for just that movie more accurate and significantly faster on the limited processing power of a Pi. I don't think it's too much to ask that a user pull out their phone and select the movie they are watching on it. It only takes a few seconds.
I don't know if the audio sync will actually ever work, but I will certainyl try.
If I can't get it to work, I will probably try to add other sync methods like Plex, so people can play their movies on any Plex client (roku, appletv, fire stick, smart tv app, etc) and sync via that as well so they aren't limited to basically Kodi on a Shield.
The ras pi compatible build of this software is coming very soon. However I am a bit of a ways away from knowing exactly which Pi will work best for the audio lookup method (if it ever works). If that is something you want to future proof yourself for, then I would have to say you should buy the 8GB Pi 4 just to be safe. (They are $20 more than the 4GB model). I don't know if the 4GB Pi 4 will be sufficient for audio matching until I can actually write that code and do testing on it.
Otherwise, for the current MPC / Kodi / (maybe layer Plex) media player sync method I will be supporting any Pi 3 and Pi 4.