Disc 0 / Track 0 (MINOR request)

[Mike48]

A minor request, not critical.

My Minim log has many entries for illegal disc #0. These come from podcasts.

Would it be possible to accept disc #0 by default? This would be no worse than the many computer languages in which one has 9 fingers.

I have one downloaded concert in which the intros are labeled as track #0. Same thing goes here.

I CAN see a problem with numbers < 0.

As I said, not urgent, but accepting these would make the log smaller and easier to navigate.

[simoncn]

(03-01-2013 01:00)Mike48 Wrote:  A minor request, not critical.

My Minim log has many entries for illegal disc #0. These come from podcasts.

Would it be possible to accept disc #0 by default? This would be no worse than the many computer languages in which one has 9 fingers.

I have one downloaded concert in which the intros are labeled as track #0. Same thing goes here.

I CAN see a problem with numbers < 0.

As I said, not urgent, but accepting these would make the log smaller and easier to navigate.

I could change MinimServer to ignore a 0 value for disc number or track number without producing a message. Is this what you'd like, or were you expecting 0 to be treated as a real value?

[Mike48]

(03-01-2013 09:47)simoncn Wrote:  I could change MinimServer to ignore a 0 value for disc number or track number without producing a message. Is this what you'd like, or were you expecting 0 to be treated as a real value?

Just to ignore it would be fine -- and helpful. Thanks!

P.S. Perhaps it interprets an empty field as zero?

[simoncn]

(03-01-2013 09:53)Mike48 Wrote:  

(03-01-2013 09:47)simoncn Wrote:  I could change MinimServer to ignore a 0 value for disc number or track number without producing a message. Is this what you'd like, or were you expecting 0 to be treated as a real value?

Just to ignore it would be fine -- and helpful. Thanks!

P.S. Perhaps it interprets an empty field as zero?

MinimServer interprets an empty field as empty (disc or track number not specified), not as zero. You're asking me to also interpret an explicit value of zero as if it were an empty field. This doesn't feel quite correct to me, but it shouldn't do any harm because it's the same as the current behaviour but without the warning message.

[Mike48]

Simon,

Sorry, I wasn't clear. I wasn't requesting that you interpret an empty field as zero. I was just asking if that was the default. I see not that (quite reasonably) it isn't.

It will be nice to have true zeroes ignored in this context.

Mike