100 track per CD limit [Increased to 180]

maybe i should put this back to 120?

Folks, in the interests of pragmatism, is there anything wrong with using a tagger and setting it up as a multi-disc set, say 50 tracks per disc?

That potentially makes a mess of identification.

I’m having this issue on a three discs, 80 tracks, 24/96 album and first noticed it with a 63 tracks, 2 discs one :frowning:

63? What machine? CPU/GPU? (his is a remote/UI issue, not core)

dedicated, headless, 2011 Mac mini (2.3GHz quad-core i7, 16GB RAM, 128GB SSD)

don’t think hw is the issue :wink:

But what is the client running on?

usually a late 2011 17" MacBook Pro, 2.4GHz quad-core i7, 16GB RAM 960GB SSD or an iPad Air
both connect via wi-fi to an all wired (NAS, Mac mini, Aries, Netgear R7000 router) network

Hrm… and it’s slow with 63 tracks? What album is this?

it’s slow loading multi-disc and high-tracks count and hi-res albums (all three instances at the time)

  • Jacob’s Bach St. Matthew Passion (60+ tracks, DSD and 24-96 versions stacked)
  • Currentzis’ Mozart Don Giovanni (79 tracks, 24-96. also getting drop-outs with this one. but not if playing direct from the Aries)

+1

Actually not sure if this is the same exact issue, butI have an album, WILHELM FURTWANGLER - WAGNER DER RING DES NIBELUNGEN. It is 13 discs with about 320 tracks total (22-24 each). It is painfully slow to come up in the UX; approximately 15+ seconds on a late 2016 MacBook client and an i7 NUC server. Guessing you’ve got an o(n^2) operation (or worse) going on somewhere.

the widget count skyrockets… tens of thousands of hierarchical ui components and then layout :frowning:

we think a solution to fixing these types of screens is to do a constraint based layout system instead of hierarchical layout, but the development problems involved with that would be pretty terrible. we are looking into solutions here

There’s probably a travelling salesman trying to figure the shortest route between [Tracks] Cities in there somewhere …

A post was split to a new topic: Performance problems on a quad core i7

A post was split to a new topic: Disc number tags not being picked up

Hello,

I was wondering if there is any update on this issue. Here is my legitimate use case:

208 tracks, categorized as a single album/disc

At the moment (roon 1.4) it seems to still truncate this to 180 tracks.

Why not add disc numbers, say every 50 tracks? I know it’s not ideal, but it’ll work.

Yes, that is my short term solution. I put the 208 tracks into the 19 unique folders based on date, then used the Roon reorganize album feature to make it look like a 19 disc set.

It actually works well for this. I think having a single 208 track album is dumb.

A post was split to a new topic: Andre Cluytens 65 CD Set - Album Browser does not display all tracks

A while back, I bought https://adrianvonziegler.bandcamp.com/album/the-complete-discography which is (at present) a 327-track “disc” with the composer’s collected works. Periodically, he releases new tracks which he then adds to that release, so it keeps getting larger, but even now Roon won’t display all the tracks without manually breaking it up into smaller chunks.

I’d really like to see this limit removed so I don’t have to fiddle with it every time there’s an update to that release.