home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Development
Improvement Suggestions
Update to music database scanning
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="zombiepig" data-source="post: 77291" data-attributes="member: 12049"><p>ok, here's my thoughts on a possible music database structure:</p><p></p><p><img src="http://werewolves.soundslikechicken.com.au/mp/mp_music_db.gif" alt="" class="fr-fic fr-dii fr-draggable " style="" /></p><p></p><p>basic changes are:</p><p>- addition of dateadded and datelastplayed to the song table. would make it possible to have views like 'tracks i haven't heard in a while', 'tracks recently added', etc</p><p>- added 4 replaygain fields to the song table</p><p>- added a 'songartistlink' and 'songgenrelink' table, to enable multiple artists/genres per song. these would be split up from a delimated list in the tags, ie, like how wmp does using the ; character. ie, the artist tag for a song could be "Dr Octagon;DJ Dexter", thus making it appear under both "dr octagon" and "dj dexter". same thing with genres - would let you classify a song as "reggae;hip-hop" to appear under both genres! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin :D" loading="lazy" data-shortname=":D" /></p><p></p><p>- added a 'songtag' table. this is the one i really wanna see <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin :D" loading="lazy" data-shortname=":D" /> basically, when a track is scanned, any non standard tags (ie, not 'artist','year',etc) get put in this table. </p><p>the custom tags could be semi-standard things, like 'composer','publisher','conductor',etc... or something totally user-defined, such as 'record label','mood','speed',.. whatever! totally up to the user <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p>secondly, i propose that the music views setup be changed so it's like this:</p><p>[CODE]</p><p>selection operation restriction limit sort sortorder viewas</p><p>[/CODE]</p><p></p><p>operation, restriction, limit, viewas will be the same as they are now.</p><p></p><p>selection and sort will list:</p><p>album</p><p>artist</p><p>albumartist</p><p>title</p><p>genre</p><p>year</p><p>track</p><p>rating</p><p>favourite</p><p>, then all unique tag names from songtag table eg:</p><p>composer</p><p>conductor</p><p>record label</p><p>mood</p><p>... (depending on how user has tagged files)</p><p></p><p>my theory is that this will allow almost infinite flexibility with organizing music, without penalizing new users or people who don't want to configure things!! </p><p></p><p>here's some example views that would be possible:</p><p></p><p>albums (sorted by artist) -> tracks</p><p>albumartist -> albums (sorted by year descending (newest first)) -> tracks</p><p>composer -> year -> conductor -> tracks</p><p>composer -> year -> orchestra -> tracks</p><p>genre -> mood -> tempo -> tracks</p><p>.</p><p>.</p><p>.</p><p>.</p><p>. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin :D" loading="lazy" data-shortname=":D" /></p><p></p><p></p><p>ok - now let me know what i've got wrong <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /></p></blockquote><p></p>
[QUOTE="zombiepig, post: 77291, member: 12049"] ok, here's my thoughts on a possible music database structure: [IMG]http://werewolves.soundslikechicken.com.au/mp/mp_music_db.gif[/IMG] basic changes are: - addition of dateadded and datelastplayed to the song table. would make it possible to have views like 'tracks i haven't heard in a while', 'tracks recently added', etc - added 4 replaygain fields to the song table - added a 'songartistlink' and 'songgenrelink' table, to enable multiple artists/genres per song. these would be split up from a delimated list in the tags, ie, like how wmp does using the ; character. ie, the artist tag for a song could be "Dr Octagon;DJ Dexter", thus making it appear under both "dr octagon" and "dj dexter". same thing with genres - would let you classify a song as "reggae;hip-hop" to appear under both genres! :D - added a 'songtag' table. this is the one i really wanna see :D basically, when a track is scanned, any non standard tags (ie, not 'artist','year',etc) get put in this table. the custom tags could be semi-standard things, like 'composer','publisher','conductor',etc... or something totally user-defined, such as 'record label','mood','speed',.. whatever! totally up to the user :) secondly, i propose that the music views setup be changed so it's like this: [CODE] selection operation restriction limit sort sortorder viewas [/CODE] operation, restriction, limit, viewas will be the same as they are now. selection and sort will list: album artist albumartist title genre year track rating favourite , then all unique tag names from songtag table eg: composer conductor record label mood ... (depending on how user has tagged files) my theory is that this will allow almost infinite flexibility with organizing music, without penalizing new users or people who don't want to configure things!! here's some example views that would be possible: albums (sorted by artist) -> tracks albumartist -> albums (sorted by year descending (newest first)) -> tracks composer -> year -> conductor -> tracks composer -> year -> orchestra -> tracks genre -> mood -> tempo -> tracks . . . . . :D ok - now let me know what i've got wrong ;) [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
Improvement Suggestions
Update to music database scanning
Contact us
RSS
Top
Bottom