Artur D'Assumpção

Makes sense complete sense, I though it would be something in those lines. Thanks for the clarification and your availability. :) PS: you can close this issue :) Cheers, Artur

Hi Urs, That makes sense :) Indeed I was led falsely by the short help, because you have the T = Tag numbers "1" | "2" | "3" | "12" | ... Also i saw somewhere in the documentation there was also the "all" shortcut possible for referring all tags. My workaround was exaclty like you said, I am doing several removes in sequence. I was wondering if this is somewhat related with another "issue" I have found but I didn't reported because it was a little weird and I found a work around. It is the following:...

kid3-cli not removing RIFF INFO tags when using "remove all" or "remove 123" commands.

Hi Urs, That's awesome that you figured out the issued! Thanks. :) Just curious, although ID3 requires a list separated with '| how does ID3 defines if you have a only a single involvee set? Should it always be set with a '|' in the end (e.g. involvee 1|) Also, what does the ID3 defines as involvement vs involvee ? Care to give an example? Cheers, Artur

Hi Urs, Thanks for the quick reply! :) Well I must confess that I though it was strange to find a kidrc file insteand of the Kid3.conf, which was the file that I have found referenced in the discussions (alongside with the windows kid3.ini version). I am using Ubuntu 18.04 bionic with Gnome (not KDE). First of all i noticed I had the kid3 KDE version installed and not the kid3-qt. I have now removed all kid3 packages and reinstalled from scratch again, now with the correct versions (just to mention...

Hi Urs, Thanks! :) Yes, I am aware of the dbus option. I also noticed this JSON request was already mentioned in the discussion forum by other user. I think although dbus is a very good option and more powerful integration overall, but at the same time not as trivial and seamless. Also, this option is only available for Linux users, so a more universal "interface" would be more appealing I guess?! The JSON output is not perfect either I confess, since in the form I suggested it only accounts for...

ID3v2.4.0 config option isn't being honored by kid3-cli for WAV files

UPDATE: I created a feature request with this topic (https://sourceforge.net/p/kid3/feature-requests/97/) Hi, I've been using a lot kid3-cli integrating it into an automatic processing workflow of audio files and I think it would be interesting to have an option to have kid3-cli output formated in JSON data format. This would help greatly the integration with other systems and giving some confidence that the output format wouldn't break in future versions. Currently I'm using regular expressions...