MusicLibrary2 : 4.3

[pz1]

havent really thought about artists where there maybe is only one track or folders which conatin many single tracks by various artists etc

Our main interest is in classical music. We like to compare how a song is interpreted by different performers. From that perspective I would like to have a view composer/artist/title or composer/title/artist. Others are likely to prefer other arrangments, and not see any of my suggestions. It might therefor be worth to consider making the views configurable, and leave it to the user to define which views (s)he wants to cycle through with the blue_button

[smelcher]

psycik,

Thanks for reading my posts and considering my requests.
As for "2) After I queue a song jump to the playlist" my main goal is to get some notification that the track has been added succesfully. If this became an option in the configuration then it wouldn't bother your current users.

That being said, have you contemplating giving the ability to remap all of the buttons? In the configuration you could then set up what you want each button to do.
I will try to reproduce my crashing problem and get back to you.
Thanks again!

[psycik]

Our main interest is in classical music. We like to compare how a song is interpreted by different performers. From that perspective I would like to have a view composer/artist/title or composer/title/artist. Others are likely to prefer other arrangments, and not see any of my suggestions. It might therefor be worth to consider making the views configurable, and leave it to the user to define which views (s)he wants to cycle through with the blue_button

The only trouble I see with this arrangement, is yes the layouts could be configurable, but the fields needs to be read from the mp3 track and stored in the db. The more stuff we shove in there the slower it is going to go.

I'd never heard on the composer field being used before and I'm sure others have other uses for other fields.

[tkgafs]

The only trouble I see with this arrangement, is yes the layouts could be configurable, but the fields needs to be read from the mp3 track and stored in the db. The more stuff we shove in there the slower it is going to go.

I'd never heard on the composer field being used before and I'm sure others have other uses for other fields.

To allow people to do this could you not give a choice of fields to be read at plugin config time and the subsequent views of the data would of course have to be based on the fields you had actually stored.

For myself all the fields I need are already there in the db but I can certainly understand other people with other needs wanting something different.

as long as I get album art and random playing I'm a happy bunny


Can I make one request can you change the code that excludes folders from random playing so that if I have a folder containing the file noindex.txt then that folder and any sub-folders should be omitted from random playing, I'm fairly sure this is how it orginally worked, but now it only seems to omit the tracks which are in the same folder as the noindex.txt file.

Tkgafs

[psycik]

To allow people to do this could you not give a choice of fields to be read at plugin config time and the subsequent views of the data would of course have to be based on the fields you had actually stored.

For myself all the fields I need are already there in the db but I can certainly understand other people with other needs wanting something different.

Yeah i can understand that as well but it actually makes for a very radical change in how i should write things. Those current selectable screens are hardcoded, and the reason is that is the for main sql that selects the titles from the db...this would probably require a radical rethink -

since pz1 is the only one who has asked fro something different (and been a long time user like yourself), I'll add this one - then I'll have to give it some thought....that select stuff from db area is getting pretty large!!

Can I make one request can you change the code that excludes folders from random playing so that if I have a folder containing the file noindex.txt then that folder and any sub-folders should be omitted from random playing, I'm fairly sure this is how it orginally worked, but now it only seems to omit the tracks which are in the same folder as the noindex.txt file.

Tkgafs

I don't think this would have ever done that (been recursive I mean). I certainly don't remember havingthat funtionality. I'll have a look.

[psycik]

I looked into it, it has never done that. I can - but if you use the "Show Excluded" then they wont show up any more. I'd prefer to get you to add the noindex.txt to the various folders - or to use the collections functionality (create two collections one for your noindex stuff and one for your normal).

[psycik]

I'll give it a couple of days then close off this 4.3 thread.

I've added most of these requests to the wiki under the todo section