[mythtv] New thetvdb.com query engine (grabber)
jyavenard at gmail.com
Mon Feb 9 02:57:45 UTC 2009
2009/2/9 Robert McNamara <robert.mcnamara at gmail.com>:
> They were two separate thoughts. ie, if you are curious about the
> structure, why not look at the script? Then, as a followup, I
> explained to you what Doug's script was and how it worked. See below
I guess you miss the intent of my rhetorical question..
I know he wasn't using the same structure... I knew he wouldn't before
even looking at his code.
> for why I did this (as the information is presented in a fashion that
> makes sense for a script called by the UI, not for the batch update
there was no need to explain, all grabbers work in the same manner.
> I'm aware of how Python works. And had you looked at the script, you
> would have seen that it would not be a drop in replacement for
> imdbpy.py. I have already explained what it *is* a drop-in
> replacement for.
And it could have been a drop-in replacement for more than just one program.
> So why not look at the script? Then you would *know* the answer to
> your query-- and if it's *not* the same class structure (and it's
> not), then would you like him to re implement it for your purpose? I
> assume not.
And why not ?
Creating a grabber from scratch for a given movie database is just as
long and cumbersome as starting from an existing one (imdbpy)...
The aim of 0.22 is to scrap all use of imdb and use another source instead.
MythTV currently provides several scripts to work on your metadata,
one of them being something that can scan a given directory for new
What I'm suggesting is not just have a replacement grabber that will
just work in mythtv GUI, but also a grabber that can replace all the
usefulness found with IMDB scripts right now
> And as I mentioned earlier, the script isn't *for* direct usage at the
> command line. It doesn't even use the Myth python bindings (nor does
> it need to). Which as I implied, you would know if you had looked at
How many times do you find appropriate to repeat yourself ?
> the script. Had you done so (and if you had known about how the UI
> calls external grabber scripts in MythVideo) then you would know they
> do not access the DB *at all*. They just dump text or links that
> MythVideo itself then handles the insertion/download of.
Oh? really ?
> Except a batch update script isn't relevant to most people more than
> once when they first start with myth. Doug's script *is* relevant on
> an everyday basis as it's usable by the UI. Which is exactly what I
> apparently wasted my time explaining to you. The script *doesn't use
> the bindings*, it merely formats the information in the way that the
> mythvideo metadata handling stuff expects it and dumps it.
> A batch grabber has limited application-- it can apply to people who
> are first starting with MythTV *exactly once*, and it can help people
> who are pirating file squirrels. As you have been told before, Myth
> won't change to service those who are stealing media (the people who
> would need to regularly batch process large numbers of files). And,
Great.. So it isn't useful to you, as such it shouldn't be useful to anyone.
And following your logic, let's stop any enhancements to mythtv
because guess what, everything could be used by the "pirating file
squirrels" with this project.
Personally, I've only started to use the metadata in mythvideo. When I
did I discovered that while there were tools to do most of the things
I intended, those tools didn't do the job properly. Either it crashed
or it didn't work. I fixed those and submitted my changes.
Personally, I would prefer to thing not be there than having tools
there untouched for years when they are buggy (like find_meta.py)
For an ongoing use, I rip all my DVDs on my macbook laptop then copy
them on the mythtv machine. I like the ability to fill the metadata to
be automatically done, not having to go through some UI.
> as I explained above, taking the longer road of working towards
> multiple grabbers in the UI + automatic scanning + directory
> preferences renders the need for command line batch processors null
> anyway. Sure, it may take a bit longer, but it's contributing to real
One solution doesn't prevent the other to exist ...
> So again, why not ping the MythVideo maintainer for how he sees this
> occurring in the UI itself, then figuring out how we can all
My success rate in getting any of the mythtv developers to respond to
any of my questions is very close to zero so far ...
I must be on their ignore list or something ...
> collaborate on getting myth there? I have done/will do my part, why
> don't we agree to abstain from hacks for a bit and see if we can get
> the job done right?
Abstain from hacks ?
Hacks are useful to many, and that includes your LATM/AAC hack ...
Most things start as a hack and get merged into trunk...
As most don't have write access to svn , everything have to be
developed as a hack and submitted as such in the form of a patch.
I really don't know what we are arguing about.. Seems like you are now
arguing just for the sake or arguing..
The sad thing is that we both want the same thing, and believe it or
not, I do believe that we want to achieve them by following the same
In the mean time I've suggested changes that can be useful to some now
(me in particular)
I've enjoyed what you've done for mythtv, but I don't understand why
you're having such a go at me.
More information about the mythtv-dev