[Feature Request] - make zapping possible by using DB-ZAP

[evroom]

One could introduce the notification DB-ZAP in order to stream the next available service.
It will be a combination of DB-SERVICE-NEXT & DB-PLAY.

Other idea that comes to mind is DB-ZAP-FORWARD and DB-ZAP-BACKWARD.
It will be a combination of DB-SERVICE-NEXT & DB-PLAY and DB-SERVICE-PREV and DB-PLAY.

[Ax-LED]

Hi,
how is the performance of zapping from one service to another?
On my Pi 3 and wifi connection it takes about 10 seconds to change to new stream of service.
So i am not sure if the "user experience" with a zapping function as descriped from you would be useful.

AxLED

[evroom]

I need to test this.
Will try to find time tomorrow.
It looked like going to the next service and then do play was fast enough, considering first omxplayer needs to stop and then starts again.
I thought it was just a matter of merging next and play into a new notification, but perhaps I‘m wrong :-)

[evroom]

It takes my Pi 3 about 10 seconds too to change service.
This is how long it takes omxplayer to start the new stream.
I think for a Pi 3 and MM running this is okay.
There are also users with Thinkerboards, PC's, etc, and they may be able to zap faster.
But ... it is a request not a demand :-)

[evroom]

When I set the gnu_mem higher, zapping goes faster.

pi@MagicPi:~ $ grep gpu_mem /boot/config.txt
#gpu_mem=64
gpu_mem=128

Did not try more, but I suppose it will be a bit more faster.
But I do not not the side effects, so I leave it like this.