More > Media Center 13 (Development Ended)

Theater View Is Not Related to Main Database View Schemes

<< < (8/11) > >>

gappie:
in my opinion it should not only be for iso files. i play a part of my videoos outside mc, as 'data' files, but organise them in vidoes in theaterview and start them from there.

Alex B:
I suppose you could change the media type of those files manually to "ISO video" and they would behave like you want.

I.e. they would show up in the video category, but when played they would automatically start an external associated program instead of playing inside MC.

glynor:

--- Quote from: Matt on August 19, 2008, 07:30:53 pm ---I'm not crazy about putting Theater View view schemes under the main library.  They're different, and add noise.

I'll put my helmet on now.

--- End quote ---

I don't think you need a helmet at all.  That's the entire point of the idea of having the checkboxes and the separate section of the main database in the tree to "store" them.  We can all agree to disagree!  You see them as different, I don't.  The default setup would be:

Have a Top-Level Theater View View Scheme under the Tree, with Audio, Video, and Images sub-view schemes (with nice pre-defined Theater Views).  I liked this better than putting a sub-scheme under each top-level option anyway.  Then, have an Option in like was described to allow you to choose any View Schemes in the whole tree that you want to select others, de-select some, or whatever.

This solves a ton of problems:

1. It gets the Theater View items out of the main Audio/Video/Images View Schemes, which you and some other users don't like.

2. It allows us to configure and test our Theater View Schemes by configuring them normally in Standard View.  (Swapping back and forth from Options --> Theater View and back to Options to "get it right" would be a huge pain.)

3. It allows you to easily copy/paste (through the normal method) View Schemes to and from the Theater View Schemes.

4. Simplifies setting up sorting.  Just follow the normal View Scheme rules as they are applied in these special View Schemes.

5. Solves the ISO problem.  Just add ( [Media Type]=data and [File Type]=iso ) to the filters.

6. Allows those of us who would much rather just have a unified system, where the Audio tree in Standard View and the Audio tree in Theater View match to get just what we want.  I might even try setting it up through the Theater View Top-Level item if it were this way though.  (BTW -- darichman, I do change my schemes fairly regularly.  They're in near constant flux.)

7. If you really want to set it and forget it and never see them, go to Advanced options and uncheck the new Theater View Schemes checkbox.  Poof, they're gone.

I really don't see any major negatives to this method, other than coding time of course (not my problem), and it would certainly keep everyone above "pretty much happy".  A good compromise.   :D

skeeterfood:
What glynor said...  plus some easier method of seeing/selecting each of the Audio/Video/Images sub-Views within Theater View.

-John

jmone:
We can already tag any file (inclung ISO) in the D'Base as Audio, Data, Image, Playlist,TV or Video and pending how you tag them they then appear in the relevant ViewScheme.  Unfortunatly at the moment:
a) if you tag your ISO as Video (or Audio) it is is the correct Veiw but if you "play" it, MC does not run/mount the ISO
b) if you tag your ISO as DATA it is not in the correct View but if you "play" it, MC will run/mount the ISO correctly. 

For me the simple solution would be:
1) Let users tag ISO's according to what they contain (eg Video, Data, Audio) - eg this can be done now
2) Always run/mount files with an ISO extension (eg like if they were taged Data) as I know of no other way of treating "ISO" files from a MediaCenter perspective

You may then need to think about the assigning coverart bit as the option I am using is to save the art in the "DATA - NAME" format which may not be the most appropriate naming convension.

Thanks
Nathan

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version