Posts: 185
Joined: Sep 2008
Reputation:
0
hfmls
Senior Member
Posts: 185
2013-03-20, 23:56
(This post was last modified: 2013-03-21, 00:14 by hfmls.)
ok, found one bug that causes (at least, mine) XBMC to freeze, and black screen.
in System-LIVE TV- General, if u press "Use backend channels number) xbmc freezes and u get black screen.
quick question unrelated:
TIMESHIFT USING RAM:
pause,play is so fast, smooth and stable... really nice, thank you so much for this.
(don't know where else to ask, sorry).
I get all my channels that use é í ó ú á ç ã , with crazy charts, what do you think it could be the problem?
EPG and channellist is like that. Is this xbmc, vdr or ubuntu (portuguese) problem?
Posts: 6,810
Joined: Jul 2010
Reputation:
198
When using w_scan to create channels.conf don't forget the switch for utf-8. In case you channels.conf is not utf-8, you can convert it with iconv.
I have set those variables in runvdr:
export VDR_CHARSET_OVERRIDE="ISO-8859-15"
export LANG="de_DE.UTF-8"
Posts: 185
Joined: Sep 2008
Reputation:
0
hfmls
Senior Member
Posts: 185
my channel list is utf-8, i used notepad++.
export VDR_CHARSET_OVERRIDE="ISO-8859-15"
export LANG="de_DE.UTF-8"
where do u set this? should i use ISO-8859-1 and pt_PT ? for portuguese?
use iconv? dunno what's that mate.
thank you in advance
Posts: 6,810
Joined: Jul 2010
Reputation:
198
notepad++ means that you did edit the file on Windows. Did you save it in Unix style?
use file -bi channels.conf to check the codepage. type man iconv, the man pages will tell you more about it.
Some channels do not broadcast the codepage used for EPG. vdr allows to set an override. ISO-8859-15 should do, it's for Portuguese as well.
Yes, use pt_PT.
I don't know how you got vdr and how it is launched on your system. I launch it by a script named runvdr. Export the environment variables in this script.
Posts: 220
Joined: Oct 2011
Reputation:
7
2013-03-21, 19:27
(This post was last modified: 2013-03-21, 19:28 by Nachteule.)
I have the same problem, can not compile vnsiserver4 if I stay directly in the source folder.
Seems, that this is no longer supported. You have to go into the vdr source folder and then run make. This should also make all plugins - and, you have to rename vdr-plugin-vnsiserver to vnsiserver4 first
Kodi 18.6 @ openSUSE 13.1 x86_64 - Asus E35M1-I DELUXE | 8GB Ram | 240G 2.5" SSD
Kodi 20.2 on 1st Raspberry Pi B @ XBian | Kodi 20.2 on Raspberry Pi 3B+ @ XBian | Kodi 21a2 on Raspberry Pi4B @ XBian | Kodi 19.0 on SolidRun i.MX6 @ XBian
VDR 2.4.5 & Tvheadend4.3-1917 (for recording) on Cubieboard2 @ Debian Buster
Posts: 6,810
Joined: Jul 2010
Reputation:
198
You compile in the source tree of vdr?
folders in vdr's path /PLUGINS/src starting with vdr- are ignored. Create a symlink named vnsiserver which points to the whatever/vdr-plugin-vnsiserver
cd to VDRDIR
make
that's it.
Posts: 6,810
Joined: Jul 2010
Reputation:
198
If you compile vdr from source it does not need any other files located out of the source tree. If you compile a plugin directly make looks for a file names vdr.pc. Either you have installed vdr with make install or you specify VDRDIR with make. All relevant information for building is in vdr.pc
Posts: 6,810
Joined: Jul 2010
Reputation:
198
Have you ever installed vdr with make install? iirc this will generate vdr.pc