Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: QAAC tagging error in dBpoweramp CLI Encoder (Read 8037 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

QAAC tagging error in dBpoweramp CLI Encoder

http://i.imgur.com/U24kx8i.png <--- the error

http://i.imgur.com/q17wGbX.png <--- the setup

http://i.imgur.com/9i3cIDT.png <--- where I got the "--ignorelength -s --no-optimize -v 320 -o %d -" from (foobar2000)

I think this is mostly a problem because I don't know how to make QAAC tag files automatically.

Also, when it finishes and shows the error, not only is the .m4a file not tagged, but it is 0 bytes in size...

I've tried closing programs and unchecking the "dB Write ID Tags", as if that would help (and obviously it didn't).

Yes, I'm new to dBpoweramp (first day using it).

QAAC tagging error in dBpoweramp CLI Encoder

Reply #3 –
Quote from: bigjoegamer on
http://i.imgur.com/U24kx8i.png <--- the error

It's not qaac but dBpa that writes tags in this setup. Strictly speaking qaac writes a few tags such as tool tag and iTunSMPB, but not others.
This "Unable to tag file" message is coming from dBpa.

Can you run qaac directly from command prompt? Is it working?

QAAC tagging error in dBpoweramp CLI Encoder

Reply #4 –
Quote
http://i.imgur.com/q17wGbX.png <--- the setup


to me, it looks like copying that foobar preset is the problem

Code: [Select]
-o %d


should be

Code: [Select]
-o [outfile]


and presumably DBPA supports stdin so [infile] needs to be removed??

QAAC tagging error in dBpoweramp CLI Encoder

Reply #5 –
Quote from: nu774 on
Quote from: bigjoegamer on
http://i.imgur.com/U24kx8i.png <--- the error

It's not qaac but dBpa that writes tags in this setup. Strictly speaking qaac writes a few tags such as tool tag and iTunSMPB, but not others.
This "Unable to tag file" message is coming from dBpa.

Can you run qaac directly from command prompt? Is it working?


Yes, qaac works just fine in the command prompt, just like LAME and other encoders.
I guess you need a "frontend" like foobar2000 or dBpa in order for qaac to copy tags for you , like you said.






Quote from: marc2003 on
Quote
http://i.imgur.com/q17wGbX.png <--- the setup


to me, it looks like copying that foobar preset is the problem

Code: [Select]
-o %d


should be

Code: [Select]
-o [outfile]


and presumably DBPA supports stdin so [infile] needs to be removed??



It works now. The tags and attached pictures of the resulting m4a file are the same as the original FLAC file. Needless to say, the file size and bitrate are also the same as the m4a file I converted in fb2k.





I should mention that removing [infile] brings up this error when I try to convert the file...
http://i.imgur.com/aXvKr4J.png

...but if I leave it there, it works perfectly...so, it's all good (I think...?).
http://i.imgur.com/pnQRAMb.png






QAAC tagging error in dBpoweramp CLI Encoder

Reply #6 –
it looks like you removed the hyphen at the end after [outfile]. if you put it back, removing [infile] should work.

Code: [Select]
-o [outfile] -

QAAC tagging error in dBpoweramp CLI Encoder

Reply #8 –
i don't normally use dbpoweramp but i did download the trial and what i said does work as expected.... but then i noticed you have pass wave header unticked. if you enable that, it does work with this command line...

Code: [Select]
--ignorelength -s --no-optimize -v 320 -o [outfile] -
 

QAAC tagging error in dBpoweramp CLI Encoder

Reply #9 –
Quote from: marc2003 on
i don't normally use dbpoweramp but i did download the trial and what i said does work as expected.... but then i noticed you have pass wave header unticked. if you enable that, it does work with this command line...

Code: [Select]
--ignorelength -s --no-optimize -v 320 -o [outfile] -



Ok, now it works. Thank you very much. Sorry about that.