truncated albums (CD1, CD2 etc) #118
Replies: 4 comments 21 replies
-
|
@zedebugger Pros:
Con:
Let me iluustrate that scheme with a different recording of "Die Walküre" (foobar2000 screenshots):
|
Beta Was this translation helpful? Give feedback.
-
|
@klassikmann I think, however, that it is not feasible for me, because a) (if I understand correctly) that would divide each opera of e.g. three acts into three 'albums' and since my Wagner library only is around 60 operas that would clutter things too much for my liking. Then b) there is chamber music (e.g. The Well-tempered Clavier) where Teil I spreads over two CDs and not lend itself to this work around since you want to create artificial segmentation. Finally c), I am hesitant to use such a workaround when it is not a limitation of mpd, as shown by the fact that runeaudio05-beta does not suffer from this problem. Hoping @rern will chime in. |
Beta Was this translation helpful? Give feedback.
-
|
@zedebugger But back to your problem. In the past I noticed inconsistencies in the database handling between RuneAudio and other mpd clients (mpd is the reference). Possible causes were too much identical tag values, multi-track flac files, additional cue sheets,... But I couldn't nail down the problemes to necessary and sufficient conditions. These experiences were one trigger to establish my own directory and tagging scheme. To assist in solving your problem I think it's helpful to know all the tag values of the various tracks. |
Beta Was this translation helpful? Give feedback.
-
|
I think all of us classical music lovers have find our unique ways of tagging music to fit the digital age. I remain agnostic as to whether we will ever be able to unite under the same tagging umbrella. My way of tagging classical music is very simple: I use the album tag to enter the name of the work (Die Walküre (Solti); Goldberg Variations (Gould, -55)) because I tend to listen to a work and as such I find it logical and convenient to queue one (1) work. Although, for "Nibelungen" I have been forced to come up with an unorthodox solution. Foobar2000 (Windows) and Quod Libet (Debian) have allowed me to build really neat pane based navigation systems which remain my main interface to my collection, but Runeaudio+smartphone is nice for when the desktop is shut off (music is stored on NAS). Other than album I am only using track, artist, composer, track number, disc number, year, comment.
Perhaps I misunderstand your tagging suggestion, but I really would not like the prospect of segmenting all my operas into one act per album tag. Just look at the mess I would get for Wagner if there was per-act tagging:
I presume one way out of this dilemma could be the rewrite the filenames of the entire library so that filename numbering follow ID3 track numbers and do not reset for each folder. I used to do that, but then a few years back I started using the disc number tag instead and realized I did not have to rename filenames any more. I kind of liked that. I'd still be interested in to see if @rern could not find a solution to this, rather than having to rely on a work around. also @klassikmann, how would you deal one act ending in the middle of a cd and then the next act spanning over to another cd. Does your tagging system allow for that without altering the file name numbering? |
Beta Was this translation helpful? Give feedback.
-
|
Try this to add the directory to Playlist: mpc ls "PATH/TO/Wagner - Der Ring des Nibelungen (Thielemann) 24-96" | mpc add
|
Beta Was this translation helpful? Give feedback.
-
|
@klassikmann My point of departure in all this is that I have been building my music library since 2004. It is vast and I have gotten used to software that does not impose its own excessively arbitrary ways that I need to conform to. It seems to me that rAudio does require a certain directory structure in order to work as expected. To me that is a no-starter and that's why I raised the issue I have in this thread in the hope that the developer would see my point. Alas. The big image you post suggests that you are using directory browsing mode ("NAS share browsing") and I infer from it that you keep the files from the two CDs in the same folder (or maybe this is where the audacity 'stitching' kicks in?). So that's why you might not experience the problems I have. Otherwise you would get this view:
If instead you browse by album you get this, which shows a departure from the idea that one album equals one musical work:
To me such a segmentation of an album is not just unnecessary, it is also not very elegant, and this segmentation appears to create problems when you browse by artist, composer or genre. If you activate genre or artist browsing in your settings this is what you will see when you browse to Miles Davis (screenshot from artist browsing):
And when you click on the name of the album, this is what you get:
It looks good, but regrettably it's just a mirage. Without queuing up the individual tracks one by one, it's impossible to listen to the entire album from here if you have the files in subfolders for CD1 and CD2. This page only permits queuing up CD1. I find that very puzzling and non-intuitive since the page does list the tracks from both CDs . I hardly think it is intended functionality. Maybe this is a limitation of MPD because I have not seen it in other music players. Whether it is a limitation that rern simply has chosen to accept or a bug in the rAudio implementation I guess we will not know since s/he left the thread without addressing this issue. As a point of curiosity, I am also puzzled regarding how you square the concept of an album being a musical work with saying that you don't think it's a bug, when I describe a situation where you can't queue up more than half of the album from a page that lists the entire album? It's like having a turntable that will only play side A of an LP. |
Beta Was this translation helpful? Give feedback.
-
|
Two topics
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
@zedebugger ad 2. >It's most certainly a bug ... |
Beta Was this translation helpful? Give feedback.
-
Fine with me, we don't have to agree. But, and even though this sounds a bit pretentious of me, I am actually flummoxed that anyone at all would not agree with me on this issue. Okay, it may not necessarily be a bug per se, but if it is not, it is certainly misleading GUI-design and things would only get better if it was addressed. There is no need to compare with other mpd-clients. If someone designs a car with two steering wheels but only one works, I don't need to look at how other cars have been designed to say that the first car is badly designed because it makes it look like there is functionality that is not there. But be that as it may, I think we are reaching the end of this discussion and I thank you for engaging civilly with the issue. Enjoy your David Goode purchase! I will take a 14 min break from the computer and listen to this:
|
Beta Was this translation helpful? Give feedback.
-
|
@zedebugger Now back (for a last time in this context?) to the discussion about how to structure classical music. To demonstrate my approach an excerpt of my structure: Another aspect regarding extra work of the "one act = one directory" practice: It's not uncommon, especially in Wagner operas, that an act (Aufzug) is disseminated on two CDs. In these cases I use audacity to "stitch" together the last track of a CD with the first one of the next CD. It's cumbersome but I like it to do. But also a work nobody is willing to accomplish with an existing big music collection. On the contrary there are CDs containing different compositions of the same or different composers. Every work is a single "album" and a single directory. Two Examples: ├── Telemann, Georg Philipp And my epilogue is the same as the prologue: What does mpc say about your Thielemann Walküre? |
Beta Was this translation helpful? Give feedback.
-
I installed rAudio 1 today, using the "rOS - Build image files with interactive process".
I was hoping an issue from the old addon-days, before +Re1, would be solved but alas it seems no.
Albums that are stored in CD1, CD2, CDxx... folder structures are truncated when inserted to playlist. Only the first cd, CD1, gets inserted in the queue. But all files from all subfolders are properly indexed and in the database because the album view shows tracks from all subfolders with their proper ID3 sequential unique numbering.
Wagner - Der Ring des Nibelungen (Thielemann) 24-96
|
---Die Walküre 24-96
|
---CD1 #holds tracks 1-12
---CD2 #holds tracks 13-19
---CD3 #holds tracks 20-32
---CD4 #holds tracks 32-43
Only tracks from CD1, number 1-12, gets inserted into the playlist.
For example, the structure with 4 subfolders and 43 tracks total with ID3 track numbers from 1-43 but in each subfolder the files are numbered beginning with 1 as they would be on the actual cds. I presume that flips the queueing script up in some sense, and it was like this also when I was using janui's runeAudio 05-beta with your addons, but not when using janui's runeaudio 05-beta vanilla. So it's something in the "rern implementation" that creates this problem. Do you have an idea about how it can be fixed?
Beta Was this translation helpful? Give feedback.
All reactions