MrMc frozen as well as Apple TV

[emistral]

Hi all,

I have a strange and rather annoying behaviour. In fact it is so annoying that I can not use MrMc anymore.
The configuration is as follows:
- QNAP NAS running DVBlink
- DVBLink taking its sources from HDHomerun connect tuners
- DVBLink loaded in MrMc

A couple of days ago, I was playing a DVBlink recording on MrMC. The playback was fine. Then I paused the recording for the night. The following day, I watched the end of the recording on Kodi on the QNAP hybrid desk station. The recording was then deleted and therefore does not exist anymore.
I have configured MrMC to go straight to the TV page upon starting up. Last night I started MrMc. Upon opening the app, MrMc went to the TV page and at the top I could see that it was loading the TV channels. The first time I launched MrMc it reached 100% then froze. I could not do anything else. I tried the menu key, it did not work. The home key on the remote worked and it brought me back to the apple tv home screen.
I double pressed the home key to switch to MrMc and noticed something strange. When I pressed the home button, MrMc was frozen on the Tv screen/channel list. But upon double pressing the home button, what I saw was a snapshot of the recording that was paused 2 days before !
I selected that screen which was loaded - incorrectly since the recording does not exist anymore- and everything was frozen. I mean everything, including the apple TV. Pressing the home button had not effect at all. Same with the other keys. The only solution I had was to unplug/plug the apple tv.
Upon restarting the apple tv, I reopened MrMc. It went again to the TV page, loaded the channels and froze at 98%. Pressing the home button then double pressing it to recall MrMc shows the same snapshot of the paused recording.
As a result I can not use MrMc anymore.
I am not sure where the problem is. Maybe upon starting MrMC, it loads the tv channels as well as the recordings and freezes because one recording is missing.
Hopefully my explanation is clear.

[amet]

we would need debuglog with the issue reproduced to try and track it down.

http://forum.mrmc.tv/viewtopic.php?f=12&t=373