•  Previous
  • 1
  • 2(current)
  • 3
  • 4
  • 5
  • 7
  • Next 
 
Thread Rating:
  • 1 Vote(s) - 5 Average
Release - myth2kodi -- generate Kodi friendly file-names from MythTV recordings.
#16
(2017-02-10, 06:30)stuartk Wrote: @mikewiz38 I had a look through the full debug diagnostics log
you posted. Regarding the two other failures:

Desktop Notification:
The desktop notifications are Disabled by default, so if you
don't want to use them then this failure isn't a problem.

As far as I can see the NotifyUserName is the same user as
the one running myth2kodi, but for some reason it seems that
Ubuntu is configured to not allow a user to sudo to themselves,
which seems weird to me... Anyway, I've added a work-around to
the repository (not the release above), if you want to use
desktop notifications (only works on Gnome) you can grab the
latest myth2kodi file directly from the repo.
If you do try it then can you let me know if it works?

Kodi Communication:
From the log message it seems like your system is running
a web server on port 8080 -- if http access to Kodi isn't
enabled and nothing else is running then you shouldn't get
any response. If you want to Enable Kodi communication
then you'll need to allow it from within Kodi, setting a port
that isn't already in use. In Kodi, see:
Code:
System -> Settings -> Services -> Web Server
then make sure you've set myth2kodi's KODIIPs parameter
appropriately.

By default some Kodi communication is Enabled, so if you don't
want to have it Enabled, you can Disable it in myth2kodi.conf
by setting:
Code:
KODIUpdate='Disabled'
KODINotify='Disabled'
(The third Kodi communication option, KODIClean, is Disabled by
default so you don't have to do anything for that). If you Disable
Kodi communication then remember that you'll have to manually
update your Kodi library to see changes.

Thanks for the response. I re-ran the patched version and I'm pretty sure it's working now. Here's the code snip below...

I'm also aware of the desktop notification and kodi notifications not working. Those are easy to fix and didn't bother to configure them. I'm guessing they're optional and not necessary....I just won't get kodi to update the library once files are added from myth2kodi.

Thank you for the patches and all the help!!!

Code:
INFO: Critical Filesystem checks ***PASSED***
press any key to test myth2kodi...
INFO: Recordings Database is not used for testing.
      Performing fuzzy logic lookup on database file. Please wait.
      It may take a moment to build the myth2kodi database files.
      Executing: myth2kodi 'testfile.ext' 'mister rogers' 'show 1332'
      Testing exit status...
INFO: Processing: testfile.ext
INFO: Temporarily disabling access to MythTV-DB -- for diagnostics.
INFO: SEARCHING www.TheTVDB.com FOR mister%20rogers
WARNING: FAILED to get series line number from table with standard logic, requiring doover.
INFO: FOUND:Mister Rogers' Neighborhood ID#:77750 WITH CONFIDENCE:-2
INFO: Created myth2kodi Database Folder: /home/mythtv/.myth2kodi/Mister Rogers' Neighborhood
INFO: Seems we've never updated Mister Rogers' Neighborhood from TheTVDB -- no lastupdated.time file.
INFO: Downloading Series: 77750
INFO: Downloaded new information for Mister Rogers' Neighborhood
INFO: Cleaning up old information before processing.
INFO: Parsing Downloaded information from TheTVDB: Mister Rogers' Neighborhood.xml
INFO: LOCAL DATABASE UPDATED: /home/mythtv/.myth2kodi/Mister Rogers' Neighborhood
INFO: Processing SeriesID:77750
WARNING: AIRDATE FAILED. TITLE MATCH ON ABSOLUTE EPISODE NUMBER:
INFO: EPISODE:Show 1332 EPISODE NUMBER:462 S07E07 WITH CONFIDENCE: -1
INFO: ################ OPERATION SUMMARY ################
      JOB: myth2kodi 'testfile.ext' "mister rogers" "show 1332" "" '' ''
      CALLER=mythtv-
      PROCESS_RECORDING_MODE=MOVE-
      SYMLINK=Enabled-
      TargetPathIsInputPath=Disabled-
      FailSafeMode=Disabled-
      A summary table of writeable directories: 0='WRITEABLE' ; 1='NOT WRITEABLE'
      USER SETTING      |FLAG |Free Space  |Folder name
      m2kdir            |  0  |   28024 MB | /home/mythtv/.myth2kodi
      M2K_TMPDIR        |  0  |   28024 MB | /tmp
      originaldirname   |  0  |   28024 MB | /home/mythtv
      MoveDir           |  0  | 1446587 MB | /mnt/kodi-videos/TV
      AlternateMoveDir  |  0  | 1446587 MB | /mnt/mythtv/recordedTV
      PrimaryMovieDir   |  0  | 1446587 MB | /mnt/kodi-videos/Movies
      AlternateMovieDir |  0  | 1446587 MB | /mnt/mythtv/recordedMovies
      PrimaryShowDir    |  0  | 1446587 MB | /mnt/kodi-videos/TV/Misc
      AlternateShowDir  |  0  | 1446587 MB | /mnt/mythtv/recordedShows
      InputPath=testfile.ext-
      InputTitle=mister rogers-
      InputSubtitle=show 1332-
      InputSeasonNum=-
      InputEpisodeNum=-
      showtranslation=-
      ShowName=mister rogers-
      SeriesID=77750-
      NewShowName=Mister Rogers' Neighborhood-
      EpisodeSubtitle=Show 1332-
      Sxx=S07- Exx=E07-
      MoveFileSize=953 MB
      ConfidenceRating=-3-
      ConfidenceReasoning= Attempted Match On Zap2itID: Failed; Attempted match on Standard Logic: Failed; Attempted Title match on Fuzzy Logic: Successful; Attempted match on OriginalAirDate: Failed; Attempted SubTitle match on Standard logic: Successful; -
INFO: ################ END OF OPERATION SUMMARY ################
INFO: Set file name as: Mister Rogers Neighborhood S07E07 (Show 1332)
INFO: CREATING SERIES FOLDER: /mnt/kodi-videos/TV/Mister Rogers Neighborhood
INFO: CREATING SEASON FOLDER: /mnt/kodi-videos/TV/Mister Rogers Neighborhood/Season 7
INFO: MOVE DIRECTORY SET AS: /mnt/kodi-videos/TV/Mister Rogers Neighborhood/Season 7
      exited with status 0
press any key to continue on to the final results...
INFO: RESULTS SUMMARY:
      MythTV Database Test: ***PASSED***
      Installed Packages:   ***PASSED***      
      Notifications Test:   ***FAILED***
      KODI Communications:  ***FAILED***
      File System Checks:   ***PASSED***
      myth2kodi Testing:    ***PASSED***
      Overall Readiness:    ***PASSED***
      -----End of diagnostics-----

ERROR: Notify tests failed
       Notifications to the DBUS have failed. myth2kodi relies upon
       m2k_notify and package lib-notify to display messages on
       GNOME desktop interface. These messages will not be displayed.

ERROR: Kodi communication tests failed: 1 of 1.
       This will not prevent myth2kodi from functioning, it just means
       that myth2kodi can not send messages or library update requests
       to Kodi. There are a few possible causes for this problem:
           1. One or more of the Kodi instances you specified in KODIIPs
              is not currently running. Start Kodi.
           2. One or more of the Kodi instances is not configured to accept
              external network commands. See,
                Kodi->System->Settings->Services->Remote Control.
                Kodi->System->Settings->Services->Web Server.
           3. The settings you provided in KODIIPs are incorrect. Check
              that the IP addresses are correct. If you've set a user and
              password for http access in Kodi, make sure that you've also
              prepended them to the ip addresses in KODIIPs
                user:[email protected]
      

INFO: Diagnostic mode completed: Fri Feb 10 09:24:35 CST 2017
INFO: A diagnostics log file was written to: /home/mythtv/.myth2kodi/diagnostics.log
INFO: Finished running diagnostics.
Reply
#17
One last quick question. Is there a way to append something at the end of the filename? Such as something like

Caillou S03E09 (New Places and New Things) - MYTHTV.ts

It would be nice to tack the "- MYTHTV" part on so that I know it's from myth. I'm sure I can hack my way through the source to figure it out but I don't want to break anything.
Reply
#18
(2017-02-17, 21:11)mikewiz38 Wrote: One last quick question. Is there a way to append something at the end of the filename? Such as something like

Caillou S03E09 (New Places and New Things) - MYTHTV.ts

It would be nice to tack the "- MYTHTV" part on so that I know it's from myth. I'm sure I can hack my way through the source to figure it out but I don't want to break anything.

No, this wasn't supported. Though it's a fairly straight-forward
change, so I've now added support for it via a new user setting
variable called 'SHOW_FILE_NAME_APPEND'.

I haven't made another release yet as I prefer to have new
features around for at least a week or two before I inflict
them on innocent by-standers. Also, see the comments
near the bottom of this post.

So, if you'd like to give it a go you can just grab the latest
myth2kodi file directly from the repo. Then adding:
Code:
SHOW_FILE_NAME_APPEND=' - MYTHTV'
to your myth2kodi.conf file will result in the file-name from
your post.

If you've already processed recordings, I'd suggest that you run:
Code:
myth2kodi --undo
then scan your library again once you've set SHOW_FILE_NAME_APPEND.

That being said, just switching to this, without the undo, should
be ok. The only potential problem I'm aware of is that the current,
limited, protection against processing a recording multiple times
and ending up with multiple copies in your Kodi library is based on
file name. However, if you don't call myth2kodi, either directly or
via --scan, against already processed recordings then this isn't an
issue. Also, if you're using MOVE mode with SYMLINKing Enabled,
then --scan already has some extra protection against reprocessing.

Increasing the protection against unintentional reprocessing is in
my list of tasks, and now that I've added this new feature I'll
address that before I make the next release (probably 1-3 weeks
from now).
Reply
#19
Any idea why Dragon Ball Super will not process? The name matches the tvdb so I am not sure where to go from here. ​
Image
Reply
#20
(2017-02-21, 14:19)jctennis Wrote: Any idea why Dragon Ball Super will not process? The name matches the tvdb so I am not sure where to go from here.

Sent from my Nexus 6 (typie typie)

I did a quick check and, at least on my system, myth2kodi
seems to correctly build the local episode tables for
'Dragon Ball Super'. The plot information is missing
for some of the most recent episodes, though, unless your
guide data is bad and you are falling through to plot
matching, that should not be a problem.


As an aside: TheTVDB is a community database, so if
there is missing information, anyone can create an account
and contribute.


Take a look at the processing logs for one of the failed
recordings, you can identify and display the log entries
for a particular recording with the --log command:
Code:
myth2kodi --log '1099_20151210093000.mpg'
where you should replace the MythTV recording file name in
the example with one of your Dragon Ball Super episodes
that failed to process.

If you can not tell from the logs what went wrong then I'm
going to need some more information to help you. So, if you
could enable debug logging in your myth2kodi.conf by setting:
Code:
LOGLEVEL=3
then reprocess one of the failed recordings and post the
logging information, I'll take a look and see if I can
figure out what is going wrong.
Reply
#21
I just came across this and trying to wrap my head around it.

From the mapping files it makes I assume I could use this for Emby as well?

I'm also assuming that with the delete flag I could set it to move the recording to a new folder and then the delete flag tell mythtv that file was deleted just as if I did it from mythfrontend? Or is it something that runs if I delete the recording from kodi?
Reply
#22
(2017-02-22, 23:57)lviperz Wrote: I just came across this and trying to wrap my head around it.

From the mapping files it makes I assume I could use this for Emby as well?

I'm also assuming that with the delete flag I could set it to move the recording to a new folder and then the delete flag tell mythtv that file was deleted just as if I did it from mythfrontend? Or is it something that runs if I delete the recording from kodi?

Yeah, I only realised after I'd picked a name that the
script is actually more general and probably should have
been named something like mythtv_rename...

As a first thing, you do not want to use myth2kodi --delete
for what you want to achieve, that flag deletes the recording
completely: recording file; MthTV-DB entry; associated
thumbnails; everything... If the recording had already been
processed in the default MOVE with SYMLINK='Enabled' mode
then the link is followed and the recording file is deleted.

There are two ways to achieve what I think you want, that
is to disconnect the recording from MythTV while keeping the
moved recording:

1) The right combination of user settings will achieve it
directly when a recording is processed. Though, keep in
mind that once recording information is deleted from MythTV
it is no longer possible for myth2kodi to undo the processing.
For this approach, the main settings you will want are:
Code:
PROCESS_RECORDING_MODE='MOVE'
SYMLINK='Disabled'
With these settings, if myth2kodi is confident in the
processing it has done then it will automatically delete
the MythTV-DB entry for the recording. On the other hand,
if it is not confident then it will not delete the MythTV-DB
entry and will attempt to create a symbolic-link. If it can
do this then the recording is still in a state that myth2kodi
can process, so you can manually check if the moved recording
is correctly named and then disconnect the recording from
MythTV manually, as described in the second approach below.

2) A slightly safer, but more manual, approach would be to
process recordings in the default mode, that is with the
settings:
Code:
PROCESS_RECORDING_MODE='MOVE'
SYMLINK='Enabled'
then, once you have checked that the processing was correct,
you can disconnect the recording from MythTV by running:
Code:
myth2kodi --disconnect '/path/to/my/recordingfile.mpg'
The --disconnect flag removes the MythTV database entry and
associate thumbnails, and then removes the symlink from the
MythTV-recording-file-name to the moved file. This means the
moved recording still exists but MythTV does not know about
it anymore. Once a recording is disconnected, myth2kodi can
no longer undo the processing.

-----------------------------------------------------------

Either way, if you are not using Kodi then you should Disable
the Kodi communication, and unless Emby can use the RSS file
then you should disable that too. That is, in myth2kodi.conf,
you should set:
Code:
KODINotify='Disabled'
KODIUpdate='Disabled'

CREATE_RSS='Disabled'

Hope this helps, let me know if something is not clear.
Reply
#23
Wow, thank you for the detailed description and instructions. I believe I understand now. You were also correct in your assumption as to what I want to achieve. I do use kodi but with the emby for kodi addon. What I was thinking of doing was using your script to rename and move my mythtv recordings to a folder for emby to import. I will use method 2 at first but once I'm sure the files are being renamed correctly, I will use method 1 to make things more automatic. At least with method 1 I wouldn't have to go in to myth to remove the old recordings.

I currently use the mythtv pvr addon in kodi which works well but it doesn't allow for remote viewing. If the recordings were in emby then I could access the recordings when away from home. I love mythtv and have been using it for over a decade now. In the past year I've started using kodi with the emby for kodi addon and have been trying to make everything work from a unified place. Guess you can call the WAF solution. THe wife has never grasped where to watch what she wanted. Do I use mythtv. kodi or cable/satellite? We've had both cable and satellite over the years.

I'm dropping dish in a few months when my contract is up. We switched to dish taking advantage of the 2 year price lock and saved over $80 a month. It was basically a stepping stone to cutting the cord and give me 2 years to setup and teach the wife a new way to watch tv. So if I had everything accessible from one system/interface, that would go a long way with the WAF. Even though I have that with the pvr addon in kodi, the option to have those recordings accessible remotely is an added bonus.
Reply
#24
(2017-02-22, 01:40)stuartk Wrote:
(2017-02-21, 14:19)jctennis Wrote: Any idea why Dragon Ball Super will not process? The name matches the tvdb so I am not sure where to go from here.

Sent from my Nexus 6 (typie typie)

I did a quick check and, at least on my system, myth2kodi
seems to correctly build the local episode tables for
'Dragon Ball Super'. The plot information is missing
for some of the most recent episodes, though, unless your
guide data is bad and you are falling through to plot
matching, that should not be a problem.


As an aside: TheTVDB is a community database, so if
there is missing information, anyone can create an account
and contribute.


Take a look at the processing logs for one of the failed
recordings, you can identify and display the log entries
for a particular recording with the --log command:
Code:
myth2kodi --log '1099_20151210093000.mpg'
where you should replace the MythTV recording file name in
the example with one of your Dragon Ball Super episodes
that failed to process.

If you can not tell from the logs what went wrong then I'm
going to need some more information to help you. So, if you
could enable debug logging in your myth2kodi.conf by setting:
Code:
LOGLEVEL=3
then reprocess one of the failed recordings and post the
logging information, I'll take a look and see if I can
figure out what is going wrong.

Ok yeah, I am not sure what to do to fix this. I grabbed a log. http://pastebin.com/UmyyhTZ6
Image
Reply
#25
(2017-02-23, 16:16)lviperz Wrote: At least with method 1 I wouldn't have to go in to myth to remove the old recordings.
Just to be clear, with method 2 MythTV still maintains control of
the recording. Meaning that if you use mythweb or the MythTV
frontend to delete a recording that was processed by myth2kodi
then this will follow the link and delete the moved file as well.

When you do want to remove a recording, completely, then using:
Code:
myth2kodi --delete "/path/to/recording_to_remove.mpg"
will do the job. If you are using the Python-bindings to access
the MythTV-DB, which is the default, that is with user setting:
Code:
DATABASE_ACCESS='PythonBindings'
then myth2kodi --delete should have the same effect as clicking
delete in mythweb or MythTV frontend.
Reply
#26
(2017-02-23, 20:03)jctennis Wrote: Ok yeah, I am not sure what to do to fix this. I grabbed a log. http://pastebin.com/UmyyhTZ6
As a first thing, I noticed from your debug log that your
guide-data source is SchedulesDirect but you have myth2kodi
configured to use the SydFTA GuideDataType. So, in your
myth2kodi.conf, setting:
Code:
GuideDataType='SchedulesDirect'
should at least have the ProgramID an Zap2itSeriesID that
are in your guide-data identified correctly. This may be
enough to have the Dragon Ball Super episodes process
correctly. However, see my final point below.

I don't have SchedulesDirect data, so this processing has
been less well tested, it is basically still in the state
it was in in mythicalLibrarian. So, even if it works, I'd
appreciate your feedback and a debug log for processing one
recording.

Secondly, the series name was matching properly, so you do
not really need the showTranslations entry you added, though
it will not cause any problem either.

Finally, while changing to the correct GuideDataType may
solve the immediate problem, the fuzzy matching on your
guide-data's subtitle should have worked anyway. I'll look
into this further, but if I can't reproduce it on my system
I may ask you to run some quick tests for me, if that is ok?
Reply
#27
(2017-02-24, 01:56)stuartk Wrote:
(2017-02-23, 20:03)jctennis Wrote: Ok yeah, I am not sure what to do to fix this. I grabbed a log. http://pastebin.com/UmyyhTZ6
As a first thing, I noticed from your debug log that your
guide-data source is SchedulesDirect but you have myth2kodi
configured to use the SydFTA GuideDataType. So, in your
myth2kodi.conf, setting:
Code:
GuideDataType='SchedulesDirect'
should at least have the ProgramID an Zap2itSeriesID that
are in your guide-data identified correctly. This may be
enough to have the Dragon Ball Super episodes process
correctly. However, see my final point below.

I don't have SchedulesDirect data, so this processing has
been less well tested, it is basically still in the state
it was in in mythicalLibrarian. So, even if it works, I'd
appreciate your feedback and a debug log for processing one
recording.

Secondly, the series name was matching properly, so you do
not really need the showTranslations entry you added, though
it will not cause any problem either.

Finally, while changing to the correct GuideDataType may
solve the immediate problem, the fuzzy matching on your
guide-data's subtitle should have worked anyway. I'll look
into this further, but if I can't reproduce it on my system
I may ask you to run some quick tests for me, if that is ok?

Sure, I'll do whatever I can to help. I am not always available immediately but I will try to get back to you ASAP. I'll be able to change that setting a little later and I'll report back.
Image
Reply
#28
(2017-02-24, 02:23)jctennis Wrote: Sure, I'll do whatever I can to help. I am not always available immediately but I will try to get back to you ASAP. I'll be able to change that setting a little later and I'll report back.
Awesome, because I can't reproduce this, the fuzzy subtitle matching works on my system.

I think this is another problem with the agrep on Ubuntu based systems. To confirm this, and give me something to work from, could you run the following commands and post the output from the three agreps:
Code:
/usr/bin/env bash

EpisodeSubtitle='How Dare You Do That to My Bulma Vegetas Metamorphosis of Fury'
agrep -iByn "^$EpisodeSubtitle" "/media/Storage/myth2kodi/Dragon Ball Super/Dragon Ball Super.Ename.txt"
agrep -iByn "^$EpisodeSubtitle" "/media/Storage/myth2kodi/Dragon Ball Super/Dragon Ball Super.Ename.txt" | grep -m1 ^
agrep -iByn "^$EpisodeSubtitle" "/media/Storage/myth2kodi/Dragon Ball Super/Dragon Ball Super.Ename.txt" | grep -m1 ^ | sed 's/:.*//'
Reply
#29
(2017-02-24, 03:09)stuartk Wrote:
(2017-02-24, 02:23)jctennis Wrote: Sure, I'll do whatever I can to help. I am not always available immediately but I will try to get back to you ASAP. I'll be able to change that setting a little later and I'll report back.
Awesome, because I can't reproduce this, the fuzzy subtitle matching works on my system.

I think this is another problem with the agrep on Ubuntu based systems. To confirm this, and give me something to work from, could you run the following commands and post the output from the three agreps:
Code:
/usr/bin/env bash

EpisodeSubtitle='How Dare You Do That to My Bulma Vegetas Metamorphosis of Fury'
agrep -iByn "^$EpisodeSubtitle" "/media/Storage/myth2kodi/Dragon Ball Super/Dragon Ball Super.Ename.txt"
agrep -iByn "^$EpisodeSubtitle" "/media/Storage/myth2kodi/Dragon Ball Super/Dragon Ball Super.Ename.txt" | grep -m1 ^
agrep -iByn "^$EpisodeSubtitle" "/media/Storage/myth2kodi/Dragon Ball Super/Dragon Ball Super.Ename.txt" | grep -m1 ^ | sed 's/:.*//'
Code:
[email protected]:/media/Storage/myth2kodi$ /usr/bin/env bash
[email protected]:/media/Storage/myth2kodi$ EpisodeSubtitle='How Dare You Do That to My Bulma Vegetas Metamorphosis of Fury'
[email protected]:/media/Storage/myth2kodi$ agrep -iByn "^$EpisodeSubtitle" "/media/Storage/myth2kodi/Dragon Ball Super/Dragon Ball Super.Ename.txt"
agrep: pattern too long (has > 32 chars)
[email protected]:/media/Storage/myth2kodi$ agrep -iByn "^$EpisodeSubtitle" "/media/Storage/myth2kodi/Dragon Ball Super/Dragon Ball Super.Ename.txt" | grep -m1 ^
agrep: pattern too long (has > 32 chars)
[email protected]:/media/Storage/myth2kodi$ agrep -iByn "^$EpisodeSubtitle" "/media/Storage/myth2kodi/Dragon Ball Super/Dragon Ball Super.Ename.txt" | grep -m1 ^ | sed 's/:.*//'
agrep: pattern too long (has > 32 chars)
[email protected]:/media/Storage/myth2kodi$

Does that help at all?

ETA: This is the output after changing that setting
Code:
myth2kodi 1878_20170219010000.ts
DEBUG: ENTERING: log_rotation() ; CALLED FROM: m2k_init()
DEBUG: ENTERING: validate_settings() ; CALLED FROM: m2k_init()
DEBUG: myth2kodi script initialisation complete.
DEBUG: Running myth2kodi as mythtv
DEBUG: ENTERING: validate_args() ; CALLED FROM: main()
DEBUG: Call seems correct: myth2kodi '1878_20170219010000.ts' "" "" "" '' ''
DEBUG: No command flag set. Processing as recording.
INFO: Processing: 1878_20170219010000.ts
DEBUG: ENTERING: process_mythtvdb() ; CALLED FROM: main()
DEBUG: ENTERING: get_mythtvdb_info() ; CALLED FROM: process_mythtvdb()
DEBUG: ENTERING: get_mythtvdb_info_pythonbindings() ; CALLED FROM: get_mythtvdb_info()
       m2kdir: /media/Storage/myth2kodi
       binpath: /usr/local/bin
       InputFileBasename: 1878_20170219010000.ts
       DBPin: 0000
       DBHostName: 192.168.1.78
       MySQLMythDb: mythconverg
       MySQLuser: mythtv
       MySQLpass: mythtv
       InputTitle:
       InputSubtitle:
       InputSeasonNum:
       InputEpisodeNum:
INFO: Accessing MythTV DataBase Using PythonBindings:
INFO: Attempting to pull database information on 1878_20170219010000.ts
DEBUG: Storing MythTV-DB info in temporary file: '/tmp/m2k_recinfo_2017-02-23T201748-O7eS'
mythdb_access: DEBUG:__main__:Establishing database connection
mythdb_access: DEBUG:__main__:Attempting to write data to file: /tmp/m2k_recinfo_2017-02-23T201748-O7eS
mythdb_access: DEBUG:__main__:Calling write_data()
mythdb_access: DEBUG:__main__:Operation complete.
mythdb_access: DEBUG:__main__:Closing out the file/stdout
DEBUG: Guide data as extracted by: get_mythtvdb_info_pythonbindings()
       chanid=1878
       starttime=2017-02-18 20:00:00-05:00
       endtime=2017-02-18 20:30:01-05:00
       title=Dragon Ball Super
       subtitle=How Dare You Do That to My Bulma! Vegeta's Metamorphosis of Fury!
       description=
       season=0
       episode=0
       category=Children
       hostname=tvserver-OptiPlex-760
       bookmark=0
       editing=0
       cutlist=0
       autoexpire=0
       commflagged=1
       recgroup=Default
       recordid=34
       seriesid=EP02576133
       programid=EP025761330007
       inetref=ttvdb.py_295068
       lastmodified=2017-02-21 02:42:03-05:00
       filesize=2208349520
       stars=0.0
       previouslyshown=0
       originalairdate=2017-02-18
       preserve=0
       findid=0
       deletepending=0
       transcoder=0
       timestretch=1.0
       recpriority=2
       basename=1878_20170219010000.ts
       progstart=2017-02-18 20:00:00-05:00
       progend=2017-02-18 20:30:00-05:00
       playgroup=Default
       profile=Default
       duplicate=1
       transcoded=0
       watched=1
       storagegroup=Default
       bookmarkupdate=2017-02-21 02:42:03-05:00
       recgroupid=1
       recordedid=1614
       inputname=5: MPEG2TS
       startdata[0]=0
       startdata[1]=22424
       startdata[2]=47035
       stopdata[0]=587
       stopdata[1]=30225
       stopdata[2]=54063
       xmltvgrabber=schedulesdirect1
DEBUG: Created a temporary comskip markupstart file: '/tmp/m2k_markupstart_2017-02-23T201748-k7qR'
DEBUG: Created a temporary comskip markupstop file: '/tmp/m2k_markupstop_2017-02-23T201748-Chyx'
DEBUG: ENTERING: generate_comskip() ; CALLED FROM: get_mythtvdb_info_pythonbindings()
DEBUG: Created a temporary comskip markupframes file: '/tmp/m2k_markupframes_2017-02-23T201748-fCZQ'
DEBUG: COMMERCIAL DATA START:0 STOP:587
DEBUG: COMMERCIAL DATA START:22424 STOP:30225
DEBUG: COMMERCIAL DATA START:47035 STOP:54063
DEBUG: Not removing the temporary markup files: '/tmp/m2k_markupstart_2017-02-23T201748-k7qR'; '/tmp/m2k_markupstop_2017-02-23T201748-Chyx'.
DEBUG: Setting the following variables based on MythTV-DB guide data:
       InputTitle=Dragon Ball Super
       InputSubtitle=How Dare You Do That to My Bulma! Vegeta's Metamorphosis of Fury!
       InputSeasonNum=0
       InputEpisodeNum=0
       ShowCategory=Children
       MovieAirDate=
       OriginalAirDate=2017-02-18
       StorageGroup=Default
       Stars=0.0
       Plot=
       LocalSeriesID=EP02576133
       ProgramID=EP025761330007
       ChanID=1878
       ShowStartTime=2017-02-18 20:00:00-05:00
       XMLTVGrabber=schedulesdirect1
DEBUG: Not removing the temporary MythTV-DB info file: '/tmp/m2k_recinfo_2017-02-23T201748-O7eS'
DEBUG: ENTERING: process_mythtvdb_schedulesdirect() ; CALLED FROM: process_mythtvdb()
INFO: Processing MythTV database info as SchedulesDirect.
DEBUG: Input and MythTV-DB guide data for 1878_20170219010000.ts
       RECSTART:2017-02-18 20:00:00-05:00
       DATE: 2017-02-18
       PROGRAMID:EP025761330007
       ShowCategory:Children
       InputTitle:Dragon Ball Super
       InputSubtitle:How Dare You Do That to My Bulma! Vegeta's Metamorphosis of Fury!
       Sxx: UNKNOWN
       Exx: UNKNOWN
       PLOT:
DEBUG: ENTERING: show_translation() ; CALLED FROM: main()
INFO: USER TRANSLATION: Dragon Ball Super = Dragon Ball Super
DEBUG: ENTERING: process_ignore_lists() ; CALLED FROM: main()
DEBUG: ENTERING: periodic_maintenace() ; CALLED FROM: main()
DEBUG: ENTERING: download_series_identification() ; CALLED FROM: main()
INFO: SEARCHING www.TheTVDB.com FOR Dragon%20Ball%20Super
DEBUG: Created a temporary zap2it file: '/tmp/m2k_zap2it_2017-02-23T201748-26QT'
DEBUG: Not removing the temporary working file: '/tmp/m2k_working_2017-02-23T201748-6zNv'
DEBUG: ENTERING: get_serieslinenumber_zap2itid() ; CALLED FROM: main()
DEBUG: TESTING FOR ZAP2ITID MATCH: Dragon Ball Super
WARNING: get_serieslinenumber_zap2itid() couldn't find serieslinenumber with Zap2itSeriesID
DEBUG: ENTERING: get_serieslinenumber_showname() ; CALLED FROM: main()
DEBUG: ENTERING: set_seriesid_newshowname_from_serieslinenumber() ; CALLED FROM: main()
INFO: FOUND:Dragon Ball Super ID#:295068 WITH CONFIDENCE:-1
DEBUG: ENTERING: make_m2k_database_dir() ; CALLED FROM: main()
DEBUG: ENTERING: check_m2k_database_up_to_date() ; CALLED FROM: main()
INFO: DATABASE MAINTAINED. Current: 1487897536. Next update: 1488134563.
INFO: Processing SeriesID:295068
DEBUG: ENTERING: set_absolute_episode_number_by_airdate() ; CALLED FROM: main()
WARNING: AIRDATE FAILED. TITLE MATCH ON ABSOLUTE EPISODE NUMBER:
DEBUG: ENTERING: set_absolute_episode_number_by_ename() ; CALLED FROM: main()
WARNING: AIRDATE/STANDARD LOGIC FAILED. FUZZY LOGIC ABSOLUTE: . Requiring doover.
DEBUG: ENTERING: set_absolute_episode_number_by_ename_fuzzy() ; CALLED FROM: main()
agrep: pattern too long (has > 32 chars)
DEBUG: ENTERING: increment_total_matches() ; CALLED FROM: main()
DEBUG: TOTAL FUZZY LOGIC MATCHES:3910
DEBUG: TOTAL VERIFIED FUZZY ERRORS:27
WARNING: Couldn't set Sxx and Exx from MythTV-DB or set them based on InputSubtitle.
DEBUG: PlotMatchFallback is Enabled
DEBUG: ENTERING: getAbsoluteEpisodeNumberWithFuzzyPlotMatch() ; CALLED FROM: main()
       AbsoluteEpisodeNumber:
       NewShowName: Dragon Ball Super
       Plot:
       PlotLength: 1
WARNING: getAbsoluteEpisodeNumberWithFuzzyPlotMatch() - Plot is too short to attempt fuzzy guess.
WARNING: Failed in last ditch attempt to identify episode with fuzzy plot match, we have no SxxExx.
WARNING: Identified recording as episode but failed to determine episode number, requiring doover.
WARNING: ConfidenceRating low. Requiring doover.
DEBUG: ENTERING: check_filesystem() ; CALLED FROM: main()
DEBUG: ENTERING: check_write() ; CALLED FROM: check_filesystem()
       Called with 3 arguments
       arg 1 = 2106
       arg 2 = 1194069
       arg 3 = /media/Storage/Videos
DEBUG: ENTERING: check_write() ; CALLED FROM: check_filesystem()
       Called with 3 arguments
       arg 1 = 2106
       arg 2 = 132027
       arg 3 = /home/mythtv/recordedTV
DEBUG: ENTERING: check_write() ; CALLED FROM: check_filesystem()
       Called with 3 arguments
       arg 1 = 2106
       arg 2 = 1194069
       arg 3 = /media/Storage/Movies
DEBUG: ENTERING: check_write() ; CALLED FROM: check_filesystem()
       Called with 3 arguments
       arg 1 = 2106
       arg 2 = 132027
       arg 3 = /home/mythtv/recordedMovies
DEBUG: ENTERING: check_write() ; CALLED FROM: check_filesystem()
       Called with 3 arguments
       arg 1 = 2106
       arg 2 = 1194069
       arg 3 = /media/Storage/recordedShows
DEBUG: ENTERING: check_write() ; CALLED FROM: check_filesystem()
       Called with 3 arguments
       arg 1 = 2106
       arg 2 = 132027
       arg 3 = /home/mythtv/recordedShows
DEBUG: ENTERING: check_write() ; CALLED FROM: check_filesystem()
       Called with 3 arguments
       arg 1 = 1
       arg 2 = 1194069
       arg 3 = /media/Storage/mythtv/recordings
DEBUG: ENTERING: check_write() ; CALLED FROM: check_filesystem()
       Called with 3 arguments
       arg 1 = 5
       arg 2 = 1194069
       arg 3 = /media/Storage/myth2kodi
DEBUG: ENTERING: check_write() ; CALLED FROM: check_filesystem()
       Called with 3 arguments
       arg 1 = 5
       arg 2 = 132027
       arg 3 = /tmp
DEBUG: ENTERING: msg_operation_summary() ; CALLED FROM: main()
INFO: ################ OPERATION SUMMARY ################
      JOB: myth2kodi '1878_20170219010000.ts' "" "" "" '' ''
       m2kVersion=myth2kodi Version 1.2.2-
      CALLER=mythtv-
       m2kdir=/media/Storage/myth2kodi-
       Timeout=50-
       APIkey=3B054E548E3F4FBE-
      PROCESS_RECORDING_MODE=MOVE-
      SYMLINK=Enabled-
      TargetPathIsInputPath=Disabled-
      FailSafeMode=Disabled-
       FailSafeDir=/media/Storage/FailSafe-
       Notify=Disabled-
DEBUG: ENTERING: msg_dir_summary() ; CALLED FROM: msg_operation_summary()
      A summary table of writeable directories: 0='WRITEABLE' ; 1='NOT WRITEABLE'
      USER SETTING      |FLAG |Free Space  |Folder name
      m2kdir            |  0  | 1194069 MB | /media/Storage/myth2kodi
      M2K_TMPDIR        |  0  |  132027 MB | /tmp
      originaldirname   |  0  | 1194069 MB | /media/Storage/mythtv/recordings
      MoveDir           |  0  | 1194069 MB | /media/Storage/Videos
      AlternateMoveDir  |  0  |  132027 MB | /home/mythtv/recordedTV
      PrimaryMovieDir   |  0  | 1194069 MB | /media/Storage/Movies
      AlternateMovieDir |  0  |  132027 MB | /home/mythtv/recordedMovies
      PrimaryShowDir    |  0  | 1194069 MB | /media/Storage/recordedShows
      AlternateShowDir  |  0  |  132027 MB | /home/mythtv/recordedShows
      InputPath=1878_20170219010000.ts-
      InputTitle=Dragon Ball Super-
      InputSubtitle=How Dare You Do That to My Bulma! Vegeta's Metamorphosis of Fury!-
      InputSeasonNum=0-
      InputEpisodeNum=0-
      showtranslation=Dragon Ball Super-
      ShowName=Dragon Ball Super-
       LastUpdatedTVDB=1487869643-
       CurrentTimeTVDB=1487897536-
      SeriesID=295068-
      NewShowName=Dragon Ball Super-
       AbsoluteEpisodeNumber=-
      EpisodeSubtitle=How Dare You Do That to My Bulma Vegetas Metamorphosis of Fury-
      Sxx=- Exx=-
      MoveFileSize=2106 MB
      ConfidenceRating=-4-
      ConfidenceReasoning= Attempted Match On Zap2itID: Failed; Attempted match on Standard Logic: Successful; Attempted match on OriginalAirDate: Failed; Attempted SubTitle match on Standard logic: Failed; Attempted SubTitle match on Fuzzy logic: Failed; Could not get Sxx and Exx from MythTV-DB or set them based on InputSubtitle;  Guide Data did not match a specific Episode;-
       XMLTVGrabber=schedulesdirect1-
      ShowStartTime=2017-02-18 20:00:00-05:00-
       MovieAirDate=-
       OriginalAirDate=2017-02-18-
      ProgramID=EP025761330007-
      ChanID=1878-
      StorageGroup=Default-
      ShowCategory=Children-
       GoForDoover=0-
      ProgramIDType=Series With Episode Data-
       rating=0-
      Zap2itSeriesID=2576133-
       LocalSeriesID=EP02576133-
      Plot=-
INFO: ################ END OF OPERATION SUMMARY ################
DEBUG: ENTERING: msg_unable_to_identify_recording() ; CALLED FROM: main()
ERROR: Operation failed, unable to identify episode info for recording:
            1878_20170219010000.ts
      This means that insufficient information was provided to myth2kodi
      and the missing information couldn't be determined by other means.
      If you know the correct information, provide it at the command line,
          see: myth2kodi --usage
      Normally myth2kodi can determine this information from:
          your MythTV-DB; TheTVDB; or tvmaze.
      Check that information on www.TheTVDB.com is complete for this series.
      #### If not, Please consider helping out and adding to TheTVDB. ####
      #### http://www.thetvdb.com/?tab=series&id=295068           ####
      To force processing of unrecognised recordings, disable ShowStopper.
DEBUG: ENTERING: exit_job() ; CALLED FROM: main()
       Called with 1 arguments
       arg 1 = NameCouldNotBeAssigned
WARNING: NAME COULD NOT BE ASSIGNED BASED UPON DATA SUPPLIED
DEBUG: Either: Notify=Disabled; scan mode; recording is in an ignore list; or NOTIFY_MSG was not set.
$

For the record, I'm not super concerned with that one show so much as helping make this bulletproof for everything. I know it misses something once in a while so I figured anything that helps sort this issue will make an improvement all around.
Image
Reply
#30
(2017-02-24, 03:15)jctennis Wrote:
Code:
[email protected]:/media/Storage/myth2kodi$ /usr/bin/env bash
[email protected]:/media/Storage/myth2kodi$ EpisodeSubtitle='How Dare You Do That to My Bulma Vegetas Metamorphosis of Fury'
[email protected]:/media/Storage/myth2kodi$ agrep -iByn "^$EpisodeSubtitle" "/media/Storage/myth2kodi/Dragon Ball Super/Dragon Ball Super.Ename.txt"
agrep: pattern too long (has > 32 chars)
[email protected]:/media/Storage/myth2kodi$ agrep -iByn "^$EpisodeSubtitle" "/media/Storage/myth2kodi/Dragon Ball Super/Dragon Ball Super.Ename.txt" | grep -m1 ^
agrep: pattern too long (has > 32 chars)
[email protected]:/media/Storage/myth2kodi$ agrep -iByn "^$EpisodeSubtitle" "/media/Storage/myth2kodi/Dragon Ball Super/Dragon Ball Super.Ename.txt" | grep -m1 ^ | sed 's/:.*//'
agrep: pattern too long (has > 32 chars)
[email protected]:/media/Storage/myth2kodi$

Does that help at all?

Yes, that definately helps, the agrep on my system does not
have that limitation. I think I have a fix, just to confirm,
could you post the output of:

Code:
/usr/bin/env bash

EpisodeSubtitle='How Dare You Do That to My Bulma Vegetas Metamorphosis of Fury'
agrep -iByn "^${EpisodeSubtitle:0:32}" "/media/Storage/myth2kodi/Dragon Ball Super/Dragon Ball Super.Ename.txt"
agrep -iByn "^${EpisodeSubtitle:0:30}" "/media/Storage/myth2kodi/Dragon Ball Super/Dragon Ball Super.Ename.txt"
agrep -iByn "^${EpisodeSubtitle:0:30}" "/media/Storage/myth2kodi/Dragon Ball Super/Dragon Ball Super.Ename.txt" | grep -m1 ^ | cut -d':' -f1
agrep -iByn "^${EpisodeSubtitle:0:30}" "/media/Storage/myth2kodi/Dragon Ball Super/Dragon Ball Super.Ename.txt" | grep -m1 -o '^[0-9]*'

Thanks.
Reply
  •  Previous
  • 1
  • 2(current)
  • 3
  • 4
  • 5
  • 7
  • Next 



myth2kodi -- generate Kodi friendly file-names from MythTV recordings.51