2009-05-06, 21:45
Hey fekker,
Great stuff you posted there. Just thought I would comment on some of it and maybe add more.
I think that filters, update media info, and auto pilot are essential. It looks like you already have that under control. I did want to comment on the DB tie in. I would love to see some sort of user management as well. This would be even more beneficial if we were to have a central db location as I mentioned above (yes, I am going to plug that again ). It would be great to be able to add/remove movies and shows on a per user basis. So you could set the default action to be "add new movies to all users" or "add to users X,Y,Z." Pretty self explanatory. Then, when editing a movie you could have check boxes with all the users names where you could manually add or remove a movie from a users library. It should work the same way with watched/unwatched status as well. That way you could have an easier way of separating and managing a "master" account and a "kids" or "guest" account.
These are also really great suggestions. I totally agree. I would also like to add the ability to take custom screenshots for episodes. You can do this in MC which is pretty handy. It would be great if you had two levels of control for this.
1) Set a default timecode where it would snap an image. User could specify ex. 100 secs.
2) If the image taken at the default time is bad/blurry you could manually pick the image. Click "Manually Grab Image" and you get a video window where you can drag a slider frame by frame until you find a good one. Click "capture"
To add to that, in the spirit of the community it would be nice to be able to contribute images to thetvdb.com. In the settings menu you could enter your userid and pass. Then if you find an episode that is missing an image you can manually create when then click "contribute to TVDB" and it would upload the image. We would not want to have an option to automatically contribute missing episode thumbs because it would result in a lot of poor automatically generated thumbs. If a user is ok with have an auto thumb locally, fine. We should make it clear that only manually captured images, which should be of better quality and relevance, should be uploaded to thetvdb.
These are just a few things that popped up when I read through your suggestions.
@mafis90
I couldn't agree more. That is what I was referring to in my last post. I think there is so much potential for this application to be more than just "YAAMM" (Yet Another Average Media Manager). It could be the center of all media instead of just a media center helper. Do you see what I mean?
Cheers,
Rand
Great stuff you posted there. Just thought I would comment on some of it and maybe add more.
Quote:Usability
Tie in to the xbmc database (if xbmc is closed, the database will be unlocked)
I think that filters, update media info, and auto pilot are essential. It looks like you already have that under control. I did want to comment on the DB tie in. I would love to see some sort of user management as well. This would be even more beneficial if we were to have a central db location as I mentioned above (yes, I am going to plug that again ). It would be great to be able to add/remove movies and shows on a per user basis. So you could set the default action to be "add new movies to all users" or "add to users X,Y,Z." Pretty self explanatory. Then, when editing a movie you could have check boxes with all the users names where you could manually add or remove a movie from a users library. It should work the same way with watched/unwatched status as well. That way you could have an easier way of separating and managing a "master" account and a "kids" or "guest" account.
Quote:DatabaseI think here you were referring to the database for the program itself, which I totally agree with you on. I would like to address the actual XBMC db again. As we all know, databases can be lost or corrupted. I think we should still write all media specific info to an .nfo file but ALSO manipulate the XBMC db if/when possible and even back it up. Better to be overly cautious in my opinion.
I think a database is good for some areas and not so much for others. I really like XML files myself. A mix of both would prob result in the best overall usability. Cached images/data and information about those images/data, XML.. specifics about just the media itself, database.
Quote:TV Show Specific
Since most tvdb data comes back from the api, it's easy to show what episodes are missing, when the next one comes out, and if the show is already canceled or is active.
Links to tvdb, the network website, and others is very handy
These are also really great suggestions. I totally agree. I would also like to add the ability to take custom screenshots for episodes. You can do this in MC which is pretty handy. It would be great if you had two levels of control for this.
1) Set a default timecode where it would snap an image. User could specify ex. 100 secs.
2) If the image taken at the default time is bad/blurry you could manually pick the image. Click "Manually Grab Image" and you get a video window where you can drag a slider frame by frame until you find a good one. Click "capture"
To add to that, in the spirit of the community it would be nice to be able to contribute images to thetvdb.com. In the settings menu you could enter your userid and pass. Then if you find an episode that is missing an image you can manually create when then click "contribute to TVDB" and it would upload the image. We would not want to have an option to automatically contribute missing episode thumbs because it would result in a lot of poor automatically generated thumbs. If a user is ok with have an auto thumb locally, fine. We should make it clear that only manually captured images, which should be of better quality and relevance, should be uploaded to thetvdb.
These are just a few things that popped up when I read through your suggestions.
@mafis90
Quote:There only one thing, that i have to add and that is seperating the core from the interface. So it runs great into the background and you can programming a create a webinterface, windows form interface, but all seperating from the core.
Somebody write something about this in this thread.
I couldn't agree more. That is what I was referring to in my last post. I think there is so much potential for this application to be more than just "YAAMM" (Yet Another Average Media Manager). It could be the center of all media instead of just a media center helper. Do you see what I mean?
Cheers,
Rand