1 client tunes fine, additional clients won't tune to different channels

[Kevin Calvert <calvert.kevin@…>]

I posted this in the kodi forums (​https://forum.kodi.tv/showthread.php?tid=318598) so I'm essentially going to paste in the thread for a full description...

The backend is using a vanilla apt-get mythtv-backend-master repo.

---

Attempting to migrate a 4 tv mythfrontend household to using kodi frontends with mythtv pvr client (kodi-pvr-mythtv repo) instead.

The first frontend went well. Everything works as I hoped.

I did it on a second frontend today and every appeared to be fine but when I tuned to a new channel... it actually didn't change. It pulled the guide data for the new channel in the fade away info box, populated the new channel info elsewhere on the overlay, but it didn't actually tune the stream to the new channel.

Kodi#1 was already running with Comedy Central tuned.

Kodi#2 tried to tune from Comedy Central to any other channel, but it still displayed the Comedy Central stream. Obviously, this happens with any channel.

Any ideas?

The frontends are Xubuntu 16 boxes using just the standard kodi repo/kryoton.

They ran mythfrontend prior, just fine. The myth bin's are still in place but the myth processes are dead.

---

Just to add, just tried it in in reverse. Stopped Kodi#1 pvr stream. Could tune to different channels just fine on Kodi#2 but now Kodi#1 was stuck to whatever channel Kodi#2 was tuned to.

My setup is fairly vanilla as well, so I really doubt I'd have some configuration issue... but I'm open to having done something wrong.

---

Hm. I think I figured it out. I remembered that my tuners were duplicated (multiplex?) from the number that was physically available. I have 2 hdhomerun prime's with 3 tuners each, for a total of 6. But, before, with default settings, it actually supported 12 tuners.

There's an option in mythtv-setup to specify the number of recordings per tuner, and that was set to 2, as expected. I bumped it down to 1 per tuner and restarted mythbackend and now this "sticky" issue isn't happening anymore.

Now, my mythfrontend's handled this.. but I don't believe there were using the mythtv api, but their own comm method. So either the api is enforcing how it should work now or, more likely, the api doesn't handle multiplex'ing with multiple concurrent streams the right way.

Either way, not a big deal since all I really need are 6 tuners anyway, but I imagine it's a bug I should file somewhere.

This is what my tuner setup (via mythweb) looks like now...

...before it was doubled. There's been no change in the # physical hardware.

---

myth@myth:~$ mythbackend --version Please attach all output as a file in bug reports. MythTV Version : v0.28-2-g15cf421 MythTV Branch : fixes/0.28 Network Protocol : 88 Library API : 0.28.20160309-1 QT Version : 5.5.1 Options compiled in:

linux profile use_hidesyms using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_bindings_php using_crystalhd using_dvb using_firewire using_frontend using_hdhomerun using_vbox using_ceton using_hdpvr using_ivtv using_joystick_menu using_libcec using_libcrypto using_libdns_sd using_libfftw3 using_libxml2 using_lirc using_mheg using_opengl using_opengl_video using_qtwebkit using_qtscript using_qtdbus using_sdl using_taglib using_v4l2 using_x11 using_xrandr using_xv using_profiletype using_bindings_perl using_bindings_python using_bindings_php using_freetype2 using_mythtranscode using_opengl using_vaapi using_vdpau using_ffmpeg_threads using_mheg using_libass using_libxml2

[Bill Meek]

Your setup is now correct, per the Wiki: ​https://www.mythtv.org/wiki/Silicondust_HDHomeRun_Prime#Illustrated_Guide_.28Master.2F.25.29

I have the Prime too (but not Kodi) and have set Max Recordings to 1.