input number range for movements in new 3.1 tag

[Bee-liever]

With the improvements to Classical tagging in MB3.1 there can be a small problem.
Sometimes the movement numbers don't align nicely with track numbers. You can get 2 or 3 movements in 1 track or a movement can be spread over 2 tracks.
I propose 2 delimeters be added.
A comma when 2 movements are combined in 1 track;
eg. 1,2/4 where movements 1+2 are combined on one track out of 4 movements.
And a hyphen when a movement is spread over two tracks eg;
track1   1-/4
track2   -1/4

They should also be able to be combined;
track1   1-/3
track2   -1,2/3

[hiccup]

For tracks containing more than one movement/act/piece, I can imagine this could be done while keeping handling of the field numeral.
So that's a +1 for sure.

But for the scenario where a movement/act/piece is split-up over more than one track, that would probably mean transforming the field into an alphanumeric state.
That would also accommodate for what you regularly encounter with classical releases: having something like: II.a, II.b, II.c etc.
(e.g. https://musicbrainz.org/release/7bb5dc26-b988-37cb-a19d-bc232c0320af)

So I agree on the general idea and intentions behind this. I'm just not sure how the implementation for the latter part could/would work.

[Bee-liever]

But for the scenario where a movement/act/piece is split-up over more than one track, that would probably mean transforming the field into an alphanumeric state.
That would also accommodate for what you regularly encounter with classical releases: having something like: II.a, II.b, II.c etc.

maybe to keep it numeric you could have 2.1, 2.2, 2.3 etc (being the equivalent of II.a, II.b, II.c etc) and do away with the hyphen (-) idea.
You could then have
track1   1.1/3            displayed as 1.a of 3
track2   1.2,2/3         displayed as 1.b/2 of 3
track3   3/3              displayed as 3 of 3

[Steven]

is there anything more needed from MB other than simply letting you enter any text you want instead of restricting it to a number?

[Bee-liever]

That would be the totally easiest way to do it  
I've been looking at different tagging sites to try and determine if it should only be a numeric field, and can't find any general consensus, so I was just working on the idea that it was already a numeric only field in MB and sort of had to stay that way.
Suppose I should have stuck with old K.I.S.S. adage  

[Steven]

is there anything more needed from MB other than simply letting you enter any text you want instead of restricting it to a number?

thats done for the next v3.1 update

[Bee-liever]

Thanks for the quick update on this.
Working great!