I was planning to make Peppy player the best audio player first and then switch to video
I believe video needs different backend player. It can be either omxplayer as it has hardware acceleration or VLC compiled with hardware acceleration. Currently Peppy player leverages regular VLC without hardware acceleration. Omxplayer is available on Raspbian OS by default and doesn't need installation/compilation but it needs additional code/library to control it over dbus. Peppy player has similar code to control AirPlay server (shairport-sync) over dbus:
https://github.com/project-owner/Peppy/ ... ortdbus.py
There are two main approaches which can be used:
1. Ideally handling video should be done inside of the player itself. This way you could avoid overhead related to the inter-process communication. But the player is not ready for that yet. If you could build VLC with hardware acceleration then it could be used as the backend player for video the same way it is used now for audio. I use Python wrapper to control it. The same wrapper can be used to control video playback. This is the easiest way as you could use the same existing code to control audio and video as well.
2. Another less preferable way is the way which you suggested - scripts started from player. The player has some similar functionality. Have a look at the 'Startup & Shutdown Scripts':
https://github.com/project-owner/Peppy. ... wn-Scripts
Those scripts can be started during startup and shutdown but the same idea can be used for any other script started by the player. If you are going to spawn external process have a look at the 'pexpect' Python library. It's very useful.
The player disk images which I provide right now are based on Raspbian Lite OS and don't have desktop. But separate disk image for Desktop OS could be created if you need it.
If you have more questions you can contact me directly. My e-mail address is available on Github and in all Python source files.