search

pipelka / xbmc-addon-xvdr

DISCONTINUED - Standalone XVDR addon for XBMC
GNU General Public License v2.0
43 stars 16 forks source link

XVDR Not Working #14

Closed dado483 closed 12 years ago

dado483 commented 13 years ago

Hi Alex,

i've upgraded XVDR addons and plugin to 0.9.5 version. After upgrade LiveTV is no working. Server side no packet logged and client side i can see this messages on the log:

02:15:36 T:139827750889216 M:3790499840 DEBUG: PVR - Create - creating PVR add-on instance 'VDR XVDR Client' 02:15:36 T:139827750889216 M:3790499840 DEBUG: ADDON: Dll Initializing - VDR XVDR Client 02:15:36 T:139827750889216 M:3790499840 DEBUG: AddOnLog: VDR XVDR Client: Creating VDR XVDR PVR-Client 02:15:36 T:139827750889216 M:3790499840 DEBUG: CAddonCallbacksAddon - GetAddonSetting - add-on 'VDR XVDR Client' requests setting 'host' 02:15:36 T:139827750889216 M:3790499840 ERROR: AddOnLog: VDR XVDR Client: Couldn't get 'host' setting, falling back to '127.0.0.1' as default 02:15:36 T:139827750889216 M:3790499840 DEBUG: CAddonCallbacksAddon - GetAddonSetting - add-on 'VDR XVDR Client' requests setting 'compression' 02:15:36 T:139827750889216 M:3790499840 ERROR: AddOnLog: VDR XVDR Client: Couldn't get 'compression' setting, falling back to 6 as default 02:15:36 T:139827750889216 M:3790499840 DEBUG: CAddonCallbacksAddon - GetAddonSetting - add-on 'VDR XVDR Client' requests setting 'priority' 02:15:36 T:139827750889216 M:3790499840 ERROR: AddOnLog: VDR XVDR Client: Couldn't get 'priority' setting, falling back to 99 as default 02:15:36 T:139827750889216 M:3790499840 DEBUG: CAddonCallbacksAddon - GetAddonSetting - add-on 'VDR XVDR Client' requests setting 'convertchar' 02:15:36 T:139827750889216 M:3790499840 ERROR: AddOnLog: VDR XVDR Client: Couldn't get 'convertchar' setting, falling back to 'false' as default 02:15:36 T:139827750889216 M:3790499840 DEBUG: CAddonCallbacksAddon - GetAddonSetting - add-on 'VDR XVDR Client' requests setting 'timeout' 02:15:36 T:139827750889216 M:3790499840 ERROR: AddOnLog: VDR XVDR Client: Couldn't get 'timeout' setting, falling back to 3 seconds as default 02:15:36 T:139827750889216 M:3790499840 DEBUG: CAddonCallbacksAddon - GetAddonSetting - add-on 'VDR XVDR Client' requests setting 'handlemessages' 02:15:36 T:139827750889216 M:3790499840 ERROR: AddOnLog: VDR XVDR Client: Couldn't get 'handlemessages' setting, falling back to 'true' as default 02:15:36 T:139827750889216 M:3790499840 DEBUG: CAddonCallbacksAddon - GetAddonSetting - add-on 'VDR XVDR Client' requests setting 'autochannelgroups' 02:15:36 T:139827750889216 M:3790499840 ERROR: AddOnLog: VDR XVDR Client: Couldn't get 'autochannelgroups' setting, falling back to 'false' as default 02:15:36 T:139827750889216 M:3790499840 DEBUG: CAddonCallbacksAddon - GetAddonSetting - add-on 'VDR XVDR Client' requests setting 'audiotype' 02:15:36 T:139827750889216 M:3790499840 ERROR: AddOnLog: VDR XVDR Client: Couldn't get 'audiotype' setting, falling back to type 0 as default 02:15:36 T:139827750889216 M:3790499840 ERROR: AddOnLog: VDR XVDR Client: Open - Can't connect to XVDR Server: Connection refused 02:15:36 T:139827750889216 M:3790499840 ERROR: ADDON: Dll VDR XVDR Client - Client returned bad status (1) from Create and is not usable 02:15:36 T:139827750889216 M:3790499840 INFO: Called Add-on status handler for '1' of clientName:VDR XVDR Client, clientID:pvr.vdr.xvdr (same Thread=no) 02:15:36 T:139827750889216 M:3790499840 ERROR: PVR - InitialiseClient - can't initialise add-on 'VDR XVDR Client' 02:15:36 T:139828130649856 M:3790499840 DEBUG: Thread CAddonStatusHandler:pvr.vdr.xvdr start, auto delete: 1 02:15:36 T:139828130649856 M:3790499840 DEBUG: Thread CAddonStatusHandler:pvr.vdr.xvdr 139828130649856 terminating (autodelete)

Can you verify what is the problem? Thanks and regards

Davide

pipelka commented 13 years ago

Argh, ... The commit after 0.9.5 also slipped into the release tarball. I created a new tarball and uploaded it. Please download the "new" tarball an check if the problem persists (you have to reconfigure the addon and restart XBMC).

Sorry, Alex

pipelka commented 12 years ago

I double checked that. The wrong commit shouldn't cause this behaviour. It seems your local addon configuration is gone.

kumy commented 12 years ago

Hi

same problem here on a fresh xbmc + xvdr install. (Parameters in the addon settings are correct adn double checked.)

02:29:46 T:2998918000 M:1384996864 DEBUG: InitialiseClient - initialising add-on 'VDR XVDR Client' 02:29:46 T:2998918000 M:1384996864 DEBUG: PVR - Create - creating PVR add-on instance 'VDR XVDR Client' 02:29:46 T:2998918000 M:1384996864 DEBUG: ADDON: Dll Initializing - VDR XVDR Client 02:29:46 T:2998918000 M:1384996864 DEBUG: AddOnLog: VDR XVDR Client: Creating VDR XVDR PVR-Client 02:29:46 T:2998918000 M:1384996864 DEBUG: CAddonCallbacksAddon - GetAddonSetting - add-on 'VDR XVDR Client' requests setting 'host' 02:29:46 T:2998918000 M:1384996864 ERROR: AddOnLog: VDR XVDR Client: Couldn't get 'host' setting, falling back to '127.0.0.1' as default 02:29:46 T:2998918000 M:1384996864 DEBUG: CAddonCallbacksAddon - GetAddonSetting - add-on 'VDR XVDR Client' requests setting 'compression' 02:29:46 T:2998918000 M:1384996864 ERROR: AddOnLog: VDR XVDR Client: Couldn't get 'compression' setting, falling back to 6 as default 02:29:46 T:2998918000 M:1384996864 DEBUG: CAddonCallbacksAddon - GetAddonSetting - add-on 'VDR XVDR Client' requests setting 'priority' 02:29:46 T:2998918000 M:1384996864 ERROR: AddOnLog: VDR XVDR Client: Couldn't get 'priority' setting, falling back to 99 as default 02:29:46 T:2998918000 M:1384996864 DEBUG: CAddonCallbacksAddon - GetAddonSetting - add-on 'VDR XVDR Client' requests setting 'convertchar' 02:29:46 T:2998918000 M:1384996864 ERROR: AddOnLog: VDR XVDR Client: Couldn't get 'convertchar' setting, falling back to 'false' as default 02:29:46 T:2998918000 M:1384996864 DEBUG: CAddonCallbacksAddon - GetAddonSetting - add-on 'VDR XVDR Client' requests setting 'timeout' 02:29:46 T:2998918000 M:1384996864 ERROR: AddOnLog: VDR XVDR Client: Couldn't get 'timeout' setting, falling back to 3 seconds as default 02:29:46 T:2998918000 M:1384996864 DEBUG: CAddonCallbacksAddon - GetAddonSetting - add-on 'VDR XVDR Client' requests setting 'handlemessages' 02:29:46 T:2998918000 M:1384996864 ERROR: AddOnLog: VDR XVDR Client: Couldn't get 'handlemessages' setting, falling back to 'true' as default 02:29:46 T:2998918000 M:1384996864 DEBUG: CAddonCallbacksAddon - GetAddonSetting - add-on 'VDR XVDR Client' requests setting 'autochannelgroups' 02:29:46 T:2998918000 M:1384996864 ERROR: AddOnLog: VDR XVDR Client: Couldn't get 'autochannelgroups' setting, falling back to 'false' as default 02:29:46 T:2998918000 M:1384996864 DEBUG: CAddonCallbacksAddon - GetAddonSetting - add-on 'VDR XVDR Client' requests setting 'audiotype' 02:29:46 T:2998918000 M:1384996864 ERROR: AddOnLog: VDR XVDR Client: Couldn't get 'audiotype' setting, falling back to type 0 as default 02:29:46 T:2998918000 M:1384996864 DEBUG: CAddonCallbacksAddon - GetAddonSetting - add-on 'VDR XVDR Client' requests setting 'updatechannels' 02:29:46 T:2998918000 M:1384996864 ERROR: AddOnLog: VDR XVDR Client: Couldn't get 'updatechannels' setting, falling back to type 3 as default 02:29:46 T:2998918000 M:1384996864 ERROR: AddOnLog: VDR XVDR Client: Open - Can't connect to XVDR Server: Connection refused 02:29:46 T:2998918000 M:1384996864 ERROR: ADDON: Dll VDR XVDR Client - Client returned bad status (1) from Create and is not usable 02:29:46 T:2998918000 M:1384996864 INFO: Called Add-on status handler for '1' of clientName:VDR XVDR Client, clientID:pvr.vdr.xvdr (same Thread=no) 02:29:46 T:2998918000 M:1384996864 ERROR: PVR - InitialiseClient - can't initialise add-on 'VDR XVDR Client' 02:29:46 T:26889072 M:1384996864 DEBUG: Thread CAddonStatusHandler:pvr.vdr.xvdr start, auto delete: 1 02:29:46 T:26889072 M:1384996864 DEBUG: Thread CAddonStatusHandler:pvr.vdr.xvdr 26889072 terminating (autodelete)

userdata/addon_data/pvr.vdr.xvdr/settings.xml (Note: i've manually added a spaces after "<" as it was not displayed) < settings> < setting id="audiotype" value="0" /> < setting id="autochannelgroups" value="false" /> < setting id="compression" value="2" /> < setting id="convertchar" value="true" /> < setting id="handlemessages" value="true" /> < setting id="host" value="192.168.125.5" /> < setting id="priority" value="0" /> < setting id="timeout" value="3" /> < setting id="updatechannels" value="3" /> </ settings>

kumy commented 12 years ago

hi

I've used git bisect to find from where it doesn't work, here are my results:

9d3d6ea534643dd0283da44fab4bfed681c8262c is the first bad commit commit 9d3d6ea534643dd0283da44fab4bfed681c8262c Author: Alexander Pipelka alexander.pipelka@gmail.com Date: Mon Oct 31 22:16:53 2011 +0100

version 0.9.5

:040000 040000 5b27089ab1e4a5067e9837551d440de6b916e21c 112626b3cd563d5f8ae864a6576a053af2e4afe9 M addons :100755 100755 d76a4ba676390f1e9781b19c13b3eb30263d90ec abc49bc5c9a45a2eaf5093eb272b9f01d05cec6e M configure.in :040000 040000 cbab75b2d2104d823df8d3d2c9f38afbbd517545 2c0845346b8ad60403f2c396f18700983190fbac M debian

hope this will help

pipelka commented 12 years ago

This commit doesn't change any code. It just changes the version numbers. What happens if you just reconfigure the addon ?

kumy commented 12 years ago

This commit doesn't change any code. It just changes the version numbers.

I've also saw that... And it shocked me too...

What happens if you just reconfigure the addon ?

I've tried this (multiple times) unfortunately it doesn't change anything...

I've manually tried other revisions (just before/after) the "bad commit"... The commits after don't work.

Actually, I'm sticked to previous commit...

I've just tried the latest commit (3c80488e32a797887d746e854678b7e29651943d) compil / remove / install / reconfigure / test

but no luck. The addon IS enabled and configured. Live TV is Enabled. (No other PVR addon activated) And I get the message "No PVR client have been started yet. Wait for the ... Please check your configuration or check the log fo..."

Bests

pipelka commented 12 years ago

Ok. Please post your xbmc.log (the part till XVDR addon initialization)

kumy commented 12 years ago

here it is... (tested on 3c80488e32a797887d746e854678b7e29651943d )

http://pastebin.com/raw.php?i=bwAfuFzr

pipelka commented 12 years ago

hmm,.. I have no idea why this happens. One possibility would be some kind of permission problem reading/writing the settings file. You could also try to wipe out your .xbmc directory. I'm sure it has nothing to do with the addon (i have several boxes running the latest version).

kumy commented 12 years ago

As suggested, I've removed my .xbmc, but no luck.

I've reconfigured xvdr and as soon as I've enabled "Live TV" option, I got "falling back" messages as explained above.

I'm sure it has nothing to do with the addon (i have several boxes running the latest version).

which version do you use ?

mine is from lars opdenkamp ppa... $ apt-cache policy xbmc xbmc: Installé : 2:11.0-pvr+odk44-eden~git20110731.60222aa-0ubuntu1~ppa+odk44~natty Candidat : 2:11.0-pvr+odk44-eden~git20110731.60222aa-0ubuntu1~ppa+odk44~natty Table de version : *\ 2:11.0-pvr+odk44-eden~git20110731.60222aa-0ubuntu1~ppa+odk44~natty 0 500 http://ppa.launchpad.net/lars-opdenkamp/xbmc-pvr/ubuntu/ natty/main i386 Packages 100 /var/lib/dpkg/status

dado483 commented 12 years ago

Removing the "category" tab in resources/settings.xml addon is working good. I think is a problem on the added category tab.

Alex, what do you think about?

pipelka commented 12 years ago

@kumy This version is way too old. I always assume issues are reported for current versions.

@dadoy483 I think both of you should update your XBMC versions.

So please, update and close this issue.

kumy commented 12 years ago

This version is way too old. I always assume issues are reported for current versions.

hum... according to the xbmc roadmap, I don't think my version is too old... but on the opposite too fresh (?!) -> http://trac.xbmc.org/roadmap

my version is 11.0 from git20110731

could you please tell me what is (the good) current version? thx a lot

pipelka commented 12 years ago

odk44 is old in development time measures. i will not discuss which versions are good or bad or whatever. this means: current xvdr versions need current xbmc versions (from the git repositories).

kumy commented 12 years ago

this means: current xvdr versions need current xbmc versions (from the git repositories)

That is the information i was looking for.

I'll build it from git, and tell you the result. :)

Bests

kumy commented 12 years ago

okay, using xbmc compiled from source works. (https://github.com/opdenkamp/xbmc/tree/pvr-ppa)