Giter VIP home page Giter VIP logo

Comments (5)

sandreas avatar sandreas commented on May 30, 2024 1

Thanks for reporting... There is not explicetely an option for this, since i thought, ffmpeg would skip it automatically. As you might know, ffmpeg is used for merging files and --audio-codec parameter is more or less directly converted to ffmpegs -acodec parameter, so you could try to use:

--audio-codec="copy"

This might fail, i'm not sure, if this has side-effects - especially because ffmpeg should detect, wether encoding is needed. I'm also not 100% sure, if there IS a merging capability in ffmpeg without re-encoding and whats the result, if you just copy the codec.

BUT: I'll treat this issue as a feature request and will check the docs, so that you won't have to provide any parameter for just merging files as they are in the next version of m4b-tool - default option should be to copy the codec and not to transcode / encode again, when it is not neccessary.

from m4b-tool.

kristofferR avatar kristofferR commented on May 30, 2024

The workaround I ended up using was CTRL-C after the first file was transcoded, then I just added the source files with the same file name structure (number-filename-finished.m4b) to the tmp folder.

When I ran m4b-tool again it merged them into a single m4b without any transcoding or issues.

from m4b-tool.

sandreas avatar sandreas commented on May 30, 2024

Haha this is a nice one ;) But good that you mentioned it, perhaps i can provde a quickfix that way... i'll override the target files with the existing files and it should work...

thx

from m4b-tool.

sandreas avatar sandreas commented on May 30, 2024

Fixed by adding --no-conversion flag... feedback welcome, here is a build :-)
m4b-tool.zip

from m4b-tool.

gennaios avatar gennaios commented on May 30, 2024

Is it worth creating a new issue to track causes of failures when using --no-conversion? ffmpeg notes there could be multiple causes though I haven't looked into it. Using the latest version, plus AtomicParsley to first remove covers (somewhere someone mentioned that as a cause), I was able to get merging as such to properly work with correct chapters, though in one case metadata wasn't preserved and chapters were named by number. I haven't tried to track down what made it work. Should m4b-tool perform some steps such as removing covers or other metadata before attempting a merge as such?

from m4b-tool.

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.