Giter Club home page Giter Club logo

Comments (4)

q3cpma avatar q3cpma commented on May 29, 2024

Another problem, how can I embed ':' in my tags? Tried 1 or 2 backslash but it did nothing.

from cyanrip.

q3cpma avatar q3cpma commented on May 29, 2024

Scratch 2), didn't see that the keys were case insensitive.

from cyanrip.

cyanreg avatar cyanreg commented on May 29, 2024

The quotes are definitely not passed on in tags. They don't even make it to cyanrip as the shell simply removes them. Is your terminal doing something weird and outputting non-ASCII quotes which aren't escaped? I know OSX handles quotes in a weird way where they're converted to Unicode quote start/end characters.
The quotes are only there to remind users its an easy way to escape spaces, so if your terminal does something weird, you can just use a backslash to escape it, like -a written\ letter. Hopefully, if at least backslashes are ASCII.

The tag keys are automatically translated and converted by FFmpeg to the format's native keys. So for Ogg they're uppercased and renamed, for MP4 some keys are renamed, and so on, and where possible, they're passed on as-is, otherwise they're dropped. FFmpeg's tag key convention thankfully matches what a lot of formats use and follows logic.

-a album_artist="some artist":album="SOME\:ALBUM" -t 1=artist="gibberish":title="other\:name" works for me.
There's a bug I found where the lazy way of -a "title":"artist" is problematic when the title contains a : which I don't think I can feasibly fix without scrapping the lazy syntax (which really saves me time).
As a workaround, for track or album titles that contain a :, specify some other tag before it, like -t date="2009-09-09":title="A\:SYS". Or just the same tag twice, as the second time the tag is mentioned it'll overwrite the first one's contents. -t 1=title="will not be recorded":title="actual title" or just -t 1="will not be recorded":title="actual title".

from cyanrip.

q3cpma avatar q3cpma commented on May 29, 2024

Yeah, confused the backticks with single quotes while looking at the readme in emacs; which obviously made the double quotes go through. I only tried using the lazy title syntax, good to know the "proper" way works, then.

from cyanrip.

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.