Git Product home page Git Product logo

Comments (5)

JonnyJD avatar JonnyJD commented on July 24, 2024

I know lots of releases with "bonus DVDs", but people always added them as the second medium.

With a case like this, it basically means we can't guess the offset at all, because it could always be a blu-ray as the first disc (without a discID).

Your proposed solution is in this case not much about setting the offset beforehand, but telling isrcsubmit it shouldn't guess the offset. (and additionally providing an offset)

from musicbrainz-isrcsubmit.

JonnyJD avatar JonnyJD commented on July 24, 2024

Anyways, we have two solutions to the problem.

  1. Never guess offsets, even for single disc releases. Which would make isrcsubmit 1 nearly unusable, of course.
    (edit: actually, we can just remove the code you quoted, that would be fine)
  2. Provide an option to "not guess" the option:
    a) only --no-guess
    b) set an explicit offset (your patch)

See #47 on why I don't think providing the offset on the command line (before actually knowing how many discIDs are in the DB) might not be a good idea.

from musicbrainz-isrcsubmit.

JonnyJD avatar JonnyJD commented on July 24, 2024

Ad-hoc I would like the --no-guess solution best (apart from getting isrcsubmit 2 ready).

We can only hope, of course, that the blu-ray and cd have different numbers of tracks and isrsubmit fails, so the user sets the --no-guess option afterwards.
We should mention the --no-guess option at the breakage, of course.

from musicbrainz-isrcsubmit.

JonnyJD avatar JonnyJD commented on July 24, 2024

Actually: I'm wrong. Solution 1 might be "too strict".

We can also just remove the code you quoted. Single disc releases still have a guessed offset of 0 and it would ask for an offset in your case.

So that might be the "best solution" in this case.

If you do that, I can merge it. Include a reference to this ticket and tell why your blu-ray case makes that guess wrong.

from musicbrainz-isrcsubmit.

Freso avatar Freso commented on July 24, 2024

My pull request on #47 wasn't meant to "fix" this issue report. Even with this issue fix, #47 is still valid on the grounds of being able to feed the program the proper offsets from the initiation, thus leading to a (slightly) less interactive experience, when you have, say, a 4-disc release and you know the track offset for all of them. I do agree that it's a bit hackish though, and I'm looking forward to isrcsubmit v2. ;)

That said, I'll try out removing the block I quoted earlier... at some point. Right now I'm trying to head to bed, and my --offset has alleviated my immediate issue. :) (Now I just need someone to vote yes to removing all those ISRCs added in the first run... >_>)

from musicbrainz-isrcsubmit.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.