I have tried latest build of TVE3 with both MySQL and MS SQL engines without any success - still having problems with russian channel names and EPG. Databases encoding are utf8 (converted in MySQL) so database is not a problem. Perhaps the problem is DVB encoding detection - should be ISO 8859-5 for Cyrillic (windows 28595 code page) that is not match to windows locale.
To MP devteam: is any option to include support for manual per-transponder encoding settings?
For preparation of a file xmltv.xml for Mediaportal in settings tvxb it is necessary to expose the coding utf8:
xmlencoding=utf-8
lang=ru
In Tve3 it is solved as follows:
I install TV Server. Then I do by means of mysql-gui-tools backup bases tvlibrary. The given file I open in Notepad, replace all found 'latin1' on 'utf8'.
In mysql-gui-tools I delete base tvlibrary. Then I restore it from the changed archive.
Then in file C: \Documents and Settings \All Users \Application Data \MediaPortal TV Server \Gentle.config I add in the end connectionstring - 'charset=utf8', that the following would turn out:
<DefaultProvider name="MySQL" connectionString="Server=mserver;Database=TvLibrary;User ID=root;Password=xxxxx;charset=utf8" />
After each updating TVServer file Gentle.config needs to be changed. I act as follows - After each updating I copy in folder C: \Documents and Settings \All Users \Application Data \MediaPortal TV Server kept 1 time a file. After that it is necessary rescanning all which channels of the name not in the coding latin1 and if you use xmltv that compulsorily to start updating.
I installed the new EXE on my MP 1.36 64-bit system (Win 10 laptop), and... it works fine. (y) :)
Thank you for making this change :). I hope that it will be included in the next release.
-- from CyberSimian in the UK
I installed the new EXE on my MP 1.36 64-bit system (Win 10 laptop), and... it works fine. (y) :)
Thank you for making this...
In "MP Config" the following setting enables the display of channel numbers in the TV EPG:
But there is no equivalent setting in...
According to Wikipedia, Windows only uses code pages other than UTF-8 to support legacy (mostly 32 bit) applications and supports two code pages in addition to UTF-8 (OEM and ANSI). According to Microsoft, UTF-8 has been the preferred character set since 2019. If TV Server (or its import routine) were using UTF-8, then umlauts...
According to Wikipedia, Windows only uses code pages other than UTF-8 to support legacy (mostly 32 bit) applications and supports...
Because I have around 200 TV channels and more than a dozen groups, I tried to import the TV channel groups from an old export.xml...
Perhaps... Only way to confirm would be for me to invest in a different USB DVB-S2 tuner (like the Hauppauge WinTV-NOVA-S2), which I might do if the issue persists.
Perhaps... Only way to confirm would be for me to invest in a different USB DVB-S2 tuner (like the Hauppauge WinTV-NOVA-S2), which...
I have a dedicated TV Server x64 v1.36 running on Windows 11, with a Hauppauge WinTV-dualHD tuner for DVB-T channels (Freeview) and...