DreamsToGo
Wonderful report.
Can you give us some futher help....PLEASE?

Since hello4 showed up, it means that process continued to the 'playing' function. You'll find it in the same /usr/local/pmusic/func, but now section '-playing)'. Some hellos here too could hopefully detect the trouble.

Are you one of those who collects mp3s in directory structure like /Artist/Album/Song.mp3. I have a suggestion of how to 'index' content of directories: During indexing, pmusic can make playlists of content of every directory. If we name these playlists with name-of-directories.pmd, they will show up in index list, but not interfere with the standard m3u files.

I use here an example of the well known band 'Puppies' and their album 'The Kennel'. The mp3s are saved in /private/music/Puppies/The Kennel/*mp3.
There are several models:
1. User indexes the directory /private/music/, so Pmusic will use this as its startpoint. Every music file in /private/music/Puppies/The Kennel/ are applied to the playlist 'Puppies - The kennel.mpd'. This gives a nice overview of your music, but it's easy to see what happens when user indexes / to find all music on system.... The name 'Private - Music - Puppies - The Kennel' is not what we want.
2. A simpler model is to just accept directories that contains music files. We will never get strange names, but our songs from The Puppies album will only be named with 'The kennel.mpd'
3. As nr 1, but now with the option to define how deep Pmusic should dig in the directory structure. This would give a more flexible indexing, but also a lot harder to understand for an average user who don't like talking about file structure at all.
4. So maybe the most logical solution would be to simply include a 'Add all' button in the open-dialog.
5. Or maybe you got some better ideas...

1. User indexes the directory /private/music/, so Pmusic will use this as its startpoint. Every music file in /private/music/Puppies/The Kennel/ are applied to the playlist 'Puppies - The kennel.mpd'. This gives a nice overview of your music, but it's easy to see what happens when user indexes / to find all music on system.... The name 'Private - Music - Puppies - The Kennel' is not what we want.

why not only keep the current directory name and its parent, ie piping your example through ie

I don't know about ffmpeg's difficulties with flac. I got all my flacs also in mp3 files so I could try Pmusic. After some tries it did index my about 7000 mp3 files. Pmusic freezes occasionally my machine but not if I run it from commandline. On the first run Pmusic didn't read metatags of mp3's. But then I noticed error message with libstdc++.so.6. I managed to repair this: libstdc++.so.6 was symlinked to libstdc++.so.6.0.8 and I changed it to point to libstdc++.so.6.0.9. I updated index and Pmusic read metatags right.

I understood that you don't see much value in metatags in musicfiles. I still suggest feature to sort songs by metatags. For example by artist(performer) and title. In flac files there is standard tags for forexample composer, lyricist, arranger and so on. I think it's more important to know the composer of the song as the artist. Especially in classical music. But because I know so little of programming, I don't know how difficult it is to built.

I've used Madman music manager and Wxmusic but didn't really like them. I've tried some java based managers but didn't really like any of them. Pmusic looks like it's gonna be the one.

Are you one of those who collects mp3s in directory structure like /Artist/Album/Song.mp3. I have a suggestion of how to 'index' content of directories: During indexing, pmusic can make playlists of content of every directory. If we name these playlists with name-of-directories.pmd, they will show up in index list, but not interfere with the standard m3u files.

I use here an example of the well known band 'Puppies' and their album 'The Kennel'. The mp3s are saved in /private/music/Puppies/The Kennel/*mp3.
There are several models:
1. User indexes the directory /private/music/, so Pmusic will use this as its startpoint. Every music file in /private/music/Puppies/The Kennel/ are applied to the playlist 'Puppies - The kennel.mpd'. This gives a nice overview of your music, but it's easy to see what happens when user indexes / to find all music on system.... The name 'Private - Music - Puppies - The Kennel' is not what we want.
2. A simpler model is to just accept directories that contains music files. We will never get strange names, but our songs from The Puppies album will only be named with 'The kennel.mpd'
3. As nr 1, but now with the option to define how deep Pmusic should dig in the directory structure. This would give a more flexible indexing, but also a lot harder to understand for an average user who don't like talking about file structure at all.
4. So maybe the most logical solution would be to simply include a 'Add all' button in the open-dialog.
5. Or maybe you got some better ideas...

Sigmund

Sigmund,

From our previous discussions, I prefer option 4.
I just want to be able to select a directory, click add-all and ALL the songs in that directory and any subdirectories get added to the list.
Note that directories will contain files that are not music, eg album covers.

I don't use playlists, so I don't want my system cluttered up with them, and I'm not interested in indexing the collection. With the Library/Artist/Album directory structure it is already indexed and a directory is in effect a playlist.. I don't use tags either. I rarely, if ever, mix up music from different artists.

I have included an 'add all' button in the open dialog. This doesn't mean we also can index the directories. I want to hear your opinion. Here's my initial discussion post:

########################################

Discussion

Are you one of those who collects mp3s in directory structure like /Artist/Album/Song.mp3. I have a suggestion of how to 'index' content of directories: During indexing, pmusic can make playlists of content of every directory. If we name these playlists with name-of-directories.pmd, they will show up in index list, but not interfere with the standard m3u files.

I use here an example of the well known band 'Puppies' and their album 'The Kennel'. The mp3s are saved in /private/music/Puppies/The Kennel/*mp3.
There are several models:
1. User indexes the directory /private/music/, so Pmusic will use this as its startpoint. Every music file in /private/music/Puppies/The Kennel/ are applied to the playlist 'Puppies - The kennel.mpd'. This gives a nice overview of your music, but it's easy to see what happens when user indexes / to find all music on system.... The name 'Private - Music - Puppies - The Kennel' is not what we want.
2. A simpler model is to just accept directories that contains music files. We will never get strange names, but our songs from The Puppies album will only be named with 'The kennel.mpd'
3. As nr 1, but now with the option to define how deep Pmusic should dig in the directory structure. This would give a more flexible indexing, but also a lot harder to understand for an average user who don't like talking about file structure at all.
4. So maybe the most logical solution would be to simply include a 'Add all' button in the open-dialog.
5. Or maybe you got some better ideas...

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum