Just wanted to throw in a plug for decoupling the need for the online info from the local info. (i.e. create a database editor so we can do our own files that aren't on tvdb or that disagree with tvdb).
Reason: kids' shows
My son loves "The Wonder Pets" and "Sesame Street".
For "The Wonder Pets", each episode shown on Nickelodeon (and stored on tvdb) is actually two episodes squished together (each episode is like 11 minutes.) I split them and store them separately, and thus where something like "TV Library" for Vista Media Center would let me create my own xml metadata files, MP-TVSeries doesn't because it ties everything in to the online data. (Ultimately, something like this would be helpful for kids' shows on DVD that are in a release order, like "Veggietales" but without all the TV overhead like shown on date and seasons.)
For "Sesame Street" there's more than 20 seasons (maybe more than 30?) and I'm never gonna record anything before, say, three years ago. Additionally, Sesame Street doesn't ever really give guide data, so there's a lot of discrepancy between episodes in terms of title, description, etc. I could fix these on tvdb, I guess, but it'd be simpler to just go to another format (one that didn't care about season/episode) and just let me deal with the files and their descriptions, but still let me use banners and the otherwise pretty cool TVSeries interface.
I can probably code these changes myself (I'm a programmer by trade) but this is such a shift in paradigm to MP-TVSeries I wanted to know if it was welcome before I waded in hip deep in the C#.
EDIT: To be clear, what I'm proposing is that we identify which parts of the online database MP-TVSeries actually needs to use, and then write a separate, external editor that will let you create shows/episodes with enough fake data (like seasons and showing dates) in order for MP-TVSeries to not choke.
Reason: kids' shows
My son loves "The Wonder Pets" and "Sesame Street".
For "The Wonder Pets", each episode shown on Nickelodeon (and stored on tvdb) is actually two episodes squished together (each episode is like 11 minutes.) I split them and store them separately, and thus where something like "TV Library" for Vista Media Center would let me create my own xml metadata files, MP-TVSeries doesn't because it ties everything in to the online data. (Ultimately, something like this would be helpful for kids' shows on DVD that are in a release order, like "Veggietales" but without all the TV overhead like shown on date and seasons.)
For "Sesame Street" there's more than 20 seasons (maybe more than 30?) and I'm never gonna record anything before, say, three years ago. Additionally, Sesame Street doesn't ever really give guide data, so there's a lot of discrepancy between episodes in terms of title, description, etc. I could fix these on tvdb, I guess, but it'd be simpler to just go to another format (one that didn't care about season/episode) and just let me deal with the files and their descriptions, but still let me use banners and the otherwise pretty cool TVSeries interface.
I can probably code these changes myself (I'm a programmer by trade) but this is such a shift in paradigm to MP-TVSeries I wanted to know if it was welcome before I waded in hip deep in the C#.
EDIT: To be clear, what I'm proposing is that we identify which parts of the online database MP-TVSeries actually needs to use, and then write a separate, external editor that will let you create shows/episodes with enough fake data (like seasons and showing dates) in order for MP-TVSeries to not choke.
United States of America