Unable to scroll to save button on genre mapping picker with long sub-genre list (ref#IO1BNP) [Fix in Early Access 2.70]

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· App interface looks or behaves oddly

Tell us what's going on

· On the genre mapping picker I can't scroll to the save button

Tell us about your home network

· N/A Interface / UI issue

Hi @j_a_m_i_e,

Thank you for the report. We’ll escalate this to QA.

Does this reproduce across your Roon Remotes or one particular device? What if you try to filter by something with fewer sub-genres? It looks like Italo-Disco has quite a few sub-listings in the nomenclature from your screenshot. Please share a screenshot if a second one might be applicable.

Thanks Connor,

It’s on Mac desktop, don’t think you map genre tags on mobile devices can you?

And yes, looking at it again I expect it’s a side effect of such a long (rogue) tag, but I can’t easily see what track it comes from. If I could I’d just remove it from the file. I don’t actually want the tag.

Happy to accept it as an edge case if there’s no easy fix.

Although this probably speaks to a wider issue of needing better tools for tag management, but that’s a whole other conversation :wink:

Hi @j_a_m_i_e,

Thanks for the additional info. We have a ticket in with QA to see about reproduction. We’ll follow up once more information is shared here! :folded_hands:

Hi @j_a_m_i_e,

This is still in the queue but we’ll reach out once we have more information. Thanks for your patience in the meantime.

Hi @j_a_m_i_e,

Sorry this inadvertently auto-closed. The team has reproduced this problem and there’s a ticket in the queue for a fix. We haven’t released anything yet to Early Access, but we’ll let you know here as soon as a fix is expected in a release. Thank you!

Hi @j_a_m_i_e,

No fix for this yet but this ticket is moving through the pipeline. We’ll share another update as soon as possible so you can finish editing these genres.

Hi @j_a_m_i_e,

The fix for this issue was included in today’s Early Access release:

It looks like you’re already in Early Access, so you should just need to update your server/remotes to test the fix.

Brilliant, thanks Connor!