You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I am having trouble with a couple of issues. Please help me.
FIRST ISSUE:
I am using OpenElec 4.0.1 and XBMC 13.1 Beta. The Processor is Crestron MC3.
When I use XBMC module version 1.10 I am having following issues:
1. I set Item_Count to 10d. When I request Thumbnails and Titles from the XBMC,
i get them mixed up for Items 7,8,9 & 10.
2. They are mixed in the sense that for example from Movie/Episode_Name_7
output i get the string for year instead of the title, and instead of Thumbnail
URL, on that output I get something else.
3. Than, if I reduce Item_Count to 5d, and request data for some 5 Items of the
Library, I get data only for the first one of those 5.
Interestingly, if I have signals connected to Items 7,8,9 & 10, I first get
outputs for them (which are mixed up), than output for Item 1, and NO outputs
for 2,3,4,5.
I have had the same issues for some older version of OpenElec and XBMC, so I
dont believe the problem is in Beta version of XBMC.
Also I have gone back to XBMC module 1.02 and I don't have this issue, it is
all working properly.
SECOND ISSUE:
When I scroll the list with Page Up and Page Down a little bit faster, and each
time I request Thumbs and Titles for 10 Items, I always have the same issue of
communication breakdown. Probably some overflow. After that happens no commands
are forwarded to XBMC regarding lists. There are no "SendToSocket { "id":20..."
commands. And reconnect to XBMC doesn't help. Only thing that helps is
processor restart. Is there a solution for this, or must I program a limitation
on a speed for which I can send Page Up and Page Down commands ?
Thanks in advance,
Miki
Original issue reported on code.google.com by [email protected] on 21 May 2014 at 8:49
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
[email protected]
on 21 May 2014 at 8:49The text was updated successfully, but these errors were encountered: