yes… just like the channel map.
I’ll see about developing some tools to make this process easier.
yes… just like the channel map.
I’ll see about developing some tools to make this process easier.
In lieu of a “tool”, here are some basic instructions. Data for your my.tablo.com via the Chrome browser, the WebSQL is stored into a sqlite database. You need to find it. I don’t do Windows… but on a Linux host it’s store at:
$HOME/.config/google-chrome/Default/databases
And then you’re looking for a strange dir like “http_my.tablotv.com_0” under that, and within that dir, in my case is a sqlite database name “4”
So from: $HOME/.config/google-chrome/Default/databases/http_my.tablotv.com_0 you want to do:
sqlite3 4
.output genre.txt
.separator ":"
select objectID,JSON from genre;
Of course, that’s just genres for know media that Tablo knows about currently (thus the EPG and recorded shows). But still, it’s a start.
With a bit more effort you can get the channel map similarly.
For OSX it’s at:
/Users/USERNAME/Library/Application Support/Google/Chrome/Default/databases/http_my.tablotv.com_0
Okay, not sure if this is a bug in Tablo or the SurLaTablo script so I figured I’d start here since you are usually quicker to respond.
So, here goes. Show is Aquarius and Season 2 started last night. It seems that the episode that aired last night was actually 3 episodes according to the Tablo information. When SurLaTablo extracted the episode it created a file labeling the multi part episode as S02E16 instead of S02E01-E03.
Thoughts?
Check your Tablo recorded show info screen. Does it actually have an episode number there? Mine does not. So the script used the recording date for the episode number, as it does for all recordings without episode numbers.
I would call it a guide data error.
Ah, yes. I didn’t catch that. A definite possibility. So perhaps a Tablo bug after all.
Not a Tablo bug. If there’s no episode number in the guide data, there’s no episode number. The guide data provider should have just marked it with the first episode number, as I see was done for a number of other multi-episode recordings I have. But for some reason, they didn’t. Tablo doesn’t make that info up, they get it from the guide provider.
I agree but since we don’t have access to the guide data provider we need to go through Tablo to get it sorted out, so hence a Tablo bug.
Not really a Tablo bug. It’s a EPG “bug” of sorts. If the EPG provider (Tablo doesn’t own this) doesn’t provide and episode number, the question is “what do we do?”
Because TV shows of various sorts don’t provide episode or series numbers (because they don’t apply in all cases), SurLaTablo decides to replace them with month for a missing series number and day for a missing episode number.
It’s just SurLaTablo’s way of dealing with the missing metadata.
With that said, the current EPG metadata doesn’t really support the idea of a multi episode program (at least as far as I can tell). Which again, is more of a limitation of the EPG. However, if the EPG provides such information I can try to use that.
Yup, agreed and thanks for the reply. I already opened a thread for @TabloSupport about the guide data. The field shouldn’t be empty, it should have something in there so we will see.
I should have checked the meta data before posting here but I got over zealous.
Thanks again for the script and support!
Hi, cjcox.
Continue to be VERY happy with the script; using 1.9. Occasionally an episode won’t convert for this reason:
“UnicodeEncodeError: ‘ascii’ codec can’t encode character u’\u2014’ in position 38: ordinal not in range(128)”
Is there a way I can edit the database, or some other relief for these errors?
Also, I know that deleting recordings was not likely an option. Just wanted to put my vote in again for the feature.
thx - allen
Hey @Allen, I had a similar issue with mine. The problem is due to filesystem limitations of the system you are running the script on. Based on what you provided above and my experience I am guessing you are running it on Linux?
For me I tried and tried to get around it with changes to filesystem settings and such. I even added entries to the surlatablo.conf file like “options[‘no_utf8_names’] = true”. In the end the best option I found was to remove the show title from my file naming.
For example the default is:
‘TV’:'S${plex_season_number}E${plex_episode_number}-${Etitle}
I changed mine to:
‘TV’:‘S${plex_season_number}E${plex_episode_number}’
For me this works great as long as the season and episode number get populated correctly however there are issues with the guide data but that’s a different thread. This works for me since I am importing the shows into my Plex server for viewing and as long as I have valid season and episode information Plex populates the information about the show like title and description.
Hope this helps…
When you see these, what you can do is send me the original Tablo meta data. That is using the ${rec_id} for the show, do:
surlatablo.py -i the_rec_num
Might need to take things to private messaging or even email to debug further.
I might also need your cache db’s (my interpretation of the metadata). And of course, helps for me to know your OS and filesystem.
Forgot to add in the private message, the filesystem is zfs.
allen
I’d be interested in what the resolution to this is as I had similar issues.
Haven’t taken a look at this yet. Maybe sometime this weekend?
I see what you’re trying to do here, and had every expectation this would be a great temporary fix. Sadly, it didn’t work. Not sure why. I’ll try again this weekend. In the meantime, you probably noticed that cjcox is aware of the problem, and may be able to provide a fix this weekend.
cjcox:
I tried the test code; same error. I’m worried that my conf file isn’t set up properly. Until now, I only had a temp directory there, and not sure of format, etc. I added your text below into the conf file, but it didn’t affect it either.
"UnicodeEncodeError: ‘ascii’ codec can’t encode character u’\u2014’ in position 17: ordinal not in range(128)”
Thanks for your continued support.
allen
for the surlatablo.conf file it would be:
options['no_utf8_names'] = true
You can test from the command line by adding:
-o no_utf8_names=true