2015-02-19, 20:13
I am getting an error when trying to open my Pseudo library ap . Anyone else having this problum ?
(2015-02-19, 19:58)xexe Wrote: I dont mind time consuming but it seems with my library size (very very large) it gets bogged down. It just hit 10% so thats 4% more in 1.25 hours.
My problem is everyone is going to use "Auto" on their first try when literally everything about the addon is new to them hence my suggestions that some "quick try on first boot" makes sense. I freely admit though I am an edge case.
What I will do is remove that addon and start again this time not choosing autotune as it doesnt feel right for me to be commenting here on an addon ive never managed to get to the point of using yet.
(2015-02-19, 20:13)scooterboy952 Wrote: I am getting an error when trying to open my Pseudo library ap . Anyone else having this problum ?
(2015-02-19, 20:20)Lunatixz Wrote:(2015-02-19, 19:58)xexe Wrote: I dont mind time consuming but it seems with my library size (very very large) it gets bogged down. It just hit 10% so thats 4% more in 1.25 hours.
My problem is everyone is going to use "Auto" on their first try when literally everything about the addon is new to them hence my suggestions that some "quick try on first boot" makes sense. I freely admit though I am an edge case.
What I will do is remove that addon and start again this time not choosing autotune as it doesnt feel right for me to be commenting here on an addon ive never managed to get to the point of using yet.
Hmm, I'm going to guess you didn't read my reply to you?...
Because this post does nothing more then repeat your initial complaint, it does not mention any of the possible remedies I suggested to you.
I'm guessing you aren't happy with the answers I gave you before? I reduced initial autotuning as you requested, and instructed you how to help troubleshoot why your parsing times are so long...
(2015-02-19, 14:19)lwsfs Wrote:(2015-02-19, 06:01)amcfarla Wrote:(2015-02-19, 00:21)Lunatixz Wrote: Thanks, I'll check it out.
This was a great find, I went through my settings2.xml file and every renamed channel had a space in front after the double quote. I removed the space and all the channel logos populated correctly. Thanks for posting the quick fix.
I cant find my settings2 xml file on a mac so I just put a space before the file name for the appropriate logos. Worked like a charm!
(2015-02-20, 01:00)amcfarla Wrote:(2015-02-19, 14:19)lwsfs Wrote:(2015-02-19, 06:01)amcfarla Wrote: This was a great find, I went through my settings2.xml file and every renamed channel had a space in front after the double quote. I removed the space and all the channel logos populated correctly. Thanks for posting the quick fix.
I cant find my settings2 xml file on a mac so I just put a space before the file name for the appropriate logos. Worked like a charm!
if you go to this folder '/Users/<your_user_name>/Library/Application Support/Kodi/userdata' and then go to the addon_data folder, then script.pseudotv.live folder and make sure pseudotv live is not running, open the settings2.xml file with text editor, and look for the lines ' <setting id="Channel_XXX_rule_1_opt_1" value=" logo name" /> and remove the space in front of the 'logo name' and then save the file. That should fix logo issues...in the future.
(2015-02-20, 01:04)Lunatixz Wrote:(2015-02-20, 01:00)amcfarla Wrote:(2015-02-19, 14:19)lwsfs Wrote: I cant find my settings2 xml file on a mac so I just put a space before the file name for the appropriate logos. Worked like a charm!
if you go to this folder '/Users/<your_user_name>/Library/Application Support/Kodi/userdata' and then go to the addon_data folder, then script.pseudotv.live folder and make sure pseudotv live is not running, open the settings2.xml file with text editor, and look for the lines ' <setting id="Channel_XXX_rule_1_opt_1" value=" logo name" /> and remove the space in front of the 'logo name' and then save the file. That should fix logo issues...in the future.
is this issue only with in-app channel configurations? or do autotune channels also have spaces in front of name?
(2015-02-20, 01:04)Lunatixz Wrote:(2015-02-20, 01:00)amcfarla Wrote:(2015-02-19, 14:19)lwsfs Wrote: I cant find my settings2 xml file on a mac so I just put a space before the file name for the appropriate logos. Worked like a charm!
if you go to this folder '/Users/<your_user_name>/Library/Application Support/Kodi/userdata' and then go to the addon_data folder, then script.pseudotv.live folder and make sure pseudotv live is not running, open the settings2.xml file with text editor, and look for the lines ' <setting id="Channel_XXX_rule_1_opt_1" value=" logo name" /> and remove the space in front of the 'logo name' and then save the file. That should fix logo issues...in the future.
is this issue only with in-app channel configurations? or do autotune channels also have spaces in front of name?
(2015-02-19, 18:04)Lunatixz Wrote:(2015-02-19, 17:57)RockDawg Wrote:(2015-02-19, 17:47)xexe Wrote: Grabbed the zip from this thread OP which seems to come from the official github. Loads perfects with all dependencies on OpenELEC which frankly amazes me. I specifically tried this on windows because I wanted to see it working and expected OpenELEC to be a second hurdle. I dont actually use windows Kodi day to day only for testing.I get extremely slow channel builds also. About 35-45 minutes for maybe around 70 channels and that's on an i7 processor. So there's more to it than just your Atom.
I am probably going to have to abort my OE install as it is taking too long. 1.25 hours and updating channels only @ 6%. I can only assume this is a combination of MySQL, + atom CPU + very large library. Will throw some better hardware at it next time or perhaps leave it overnight.
Chtypes? you can always disable "Find missing guidedata" which greatly increases channel building.
Also make sure system cache and "Override Stream Validation" is enabled.
(2015-02-20, 02:55)reekotubbs Wrote: I found in PseudoTV Live setting the option to choose which channels to autotune. When I choose "Find USTVnow" an error comes up behind the autotune screen and shows that "you talkin' to me?~taxi driver" caused an error. When I go to the USTVnow add-on I don't have this issue.