Normal
I have this afternoon installed MediaPortalSetup_x64_1.36.100_2025-04-07-21-35.exe on 64-bit Windows 7, performing an upgrade install over MP 1.33. Some points:(1) The install proceeded without error.(2) The install of the MP part seemed to take longer than I remember. In contrast, the install of the TV Server parts seemed to take about the same time as previous releases. This is the opposite to [USER=54906]@catavolt[/USER] 's observation.(3) After rebooting, TV Server was not started. Starting "TV Server Config" detected this, and offered to start TV Server, which I accepted. TV Server then started without problem. This happened each time the system was rebooted (it was not a once-only occurrence on the first boot after the install).(4) DVB subtitles were enabled, and worked without causing the system to crash. However, this was with the client and server on the same system, so not the same scenario as [USER=11575]@AberDino[/USER] . I don't have a separate client that I can test with my Windows 7 system.(5) One error that I did notice was the preservation of the subtitle setting:If I enable DVB subtitles on a DVB-T channel, the setting is preserved when I switch to another DVB-T channel.If I enable DVB subtitles on a DVB-T2 channel, the setting is preserved when I switch to another DVB-T2 channel.However, the DVB subtitle setting is not preserved when I switch from a DVB-T channel to a DVB-T2 channel, or when I switch from a DVB-T2 channel to a DVB-T channel.For users who have impaired hearing, preserving the subtitle setting is desirable. It would be unnecessarily annoying to have to re-enable subtitles every time the channel is changed. I think that the behaviour when switching between DVB-T channels, or switching between DVB-T2 channels, is the correct behaviour. The error is the non-preservation of the subtitle setting when switching between DVB-T and DVB-T2 channels.I have checked this on my MP 1.33 production system, and it has the same behaviour, so this is not a bug that has been introduced recently. It is more likely to have been an oversight when support for DVB-T2 was added.I don't have a satellite system, so I don't know whether the same bug exists when switching between DVB-S and DVB-S2. We also need to check (and fix if necessary) DVB-C and DVB-C2.-- from CyberSimian in the UK
I have this afternoon installed MediaPortalSetup_x64_1.36.100_2025-04-07-21-35.exe on 64-bit Windows 7, performing an upgrade install over MP 1.33. Some points:
(1) The install proceeded without error.
(2) The install of the MP part seemed to take longer than I remember. In contrast, the install of the TV Server parts seemed to take about the same time as previous releases. This is the opposite to [USER=54906]@catavolt[/USER] 's observation.
(3) After rebooting, TV Server was not started. Starting "TV Server Config" detected this, and offered to start TV Server, which I accepted. TV Server then started without problem. This happened each time the system was rebooted (it was not a once-only occurrence on the first boot after the install).
(4) DVB subtitles were enabled, and worked without causing the system to crash. However, this was with the client and server on the same system, so not the same scenario as [USER=11575]@AberDino[/USER] . I don't have a separate client that I can test with my Windows 7 system.
(5) One error that I did notice was the preservation of the subtitle setting:
For users who have impaired hearing, preserving the subtitle setting is desirable. It would be unnecessarily annoying to have to re-enable subtitles every time the channel is changed. I think that the behaviour when switching between DVB-T channels, or switching between DVB-T2 channels, is the correct behaviour. The error is the non-preservation of the subtitle setting when switching between DVB-T and DVB-T2 channels.
I have checked this on my MP 1.33 production system, and it has the same behaviour, so this is not a bug that has been introduced recently. It is more likely to have been an oversight when support for DVB-T2 was added.
I don't have a satellite system, so I don't know whether the same bug exists when switching between DVB-S and DVB-S2. We also need to check (and fix if necessary) DVB-C and DVB-C2.
-- from CyberSimian in the UK