Jerethi
May 24 2004, 11:36
Hi, folks.
Is there a way to use the new auToV encoder with dbpoweramp? I've been experimenting with trying to change the default vorbis encoder, but I haven't really had much. I tried to make a new CLI encoder, but I'm not really familiar with the options.txt file.
Anyway, if anyone who has had any luck with this or knows how to accomplish could steer me in the right direction, I'd be most grateful. Thanks! (and cheers to vorbis for making one helluva showing on the latest multiformat test)
The way I did this was to
download the CLI Converter and run it.
There is no need to edit the options.txt. Under the dbpoweramp music converter program menu will be a new setting called Create Generic CLI. Select this. When it runs enter;
- the name you want to give to the encoder
- browse and select the encoder
- enter .ogg
- enter a version number like auToV beta 2
Then when you right click or use the CD Inout you can enter the command line. Based on the multiformat test I entered:
-q 4.35 -a "%a" -t "%t" -l "%g" -d "%y" -N "%n" [InFile]
Just create your own argument and away you go! Works fine for me
Jerethi
May 24 2004, 13:51
Well good night! That sounds pretty darn easy!
... and here I was trying to make my own CLI encoder. I love making problems harder than they actually are.
Thanks for the help!
Jerethi
May 25 2004, 01:23
Quick question -- is your media player showing the correct header information (i.e. that this is a third party tuned version?) I'm looking at files I've encoded through dbpoweramp using this method, and the vendor tag displays this as using the standard ogg vorbis encoding libraries.
I got suspicious, so I uninstalled the ogg vorbis codec I downloaded from dbpoweramp.com, re-encoded, and sure enough, the vendor tags now display that it is aoTuV B2.
Of course, now the tags don't transfer.
Are you experiencing something similar?
Yes now you've mentioned it. With the "normal" vorbis codec installed I get all the tags but wrong version information and when it's uninstalled vice versa!
I tried it in Audiograbber and it works fine, displaying correct header and tag information.
I will raise it on dbpoweramp forum unless Spoon sees it here!
It is how the tagging it done, the audio file will be encoded with the autov encoder, then the tags are applied using dBpowerAMPs ogg tag writer after encoding, which must be setting the version number (? overwriting the tool number ?).
Can you be sure autov is writing tags - remove dBpowerAMPs ogg codec - encode a file and see if the tags were written.
Nope no tags were written once the "standard" Ogg codec is uninstalled. Just the aruguments are present i.e a, n etc. However the version number is correct.
Try:
q 4.35 -a "[IDArtist]" -t "[IDTrack]" -l "[IDAlbum]" -d "[IDYear]" -N "[IDComment]" [InFile]
plus add [IDGenre] for genre with the correct switch
Jerethi
May 25 2004, 11:31
I'm away from my home computer at the moment, but I will try that new command line as soon as I can.
If dbpoweramp is using the default ogg vorbis codec just to write the tags, would this really affect the quality of the encoded file? Afterall, it is using the aoTuV b2 encoder to make the file.
Then again, I really have no idea!
QUOTE(spoon @ May 25 2004, 01:26 PM)
Try:
q 4.35 -a "[IDArtist]" -t "[IDTrack]" -l "[IDAlbum]" -d "[IDYear]" -N "[IDComment]" [InFile]
plus add [IDGenre] for genre with the correct switch
That did not work for me. I tried a couple of times. It worked on naming the file but did not write any tags. I will try and amend the arguments and test later.
Jerethi
May 26 2004, 01:10
QUOTE(Tomb @ May 25 2004, 09:51 AM)
That did not work for me. I tried a couple of times. It worked on naming the file but did not write any tags. I will try and amend the arguments and test later.
Hmmm... I guess it would be futile for me to try that new string then.
I doubt my limited knowledge will provide much insight to this problem, but I'll try my hand at experimenting to see what I can come up with.
If you look into the help for the Generic CLI there is a debug switch you can set in the registry, this will show the exact command line being passed.
Jerethi
May 29 2004, 18:01
For no particular reason, I decided to have one more go at convering to an auToV b2 vorbis file, and lo and behold, it works (with proper vendor tag and all!)
Here's the argument I used
q 4.35 -a "[IDArtist]" -t "[IDTrack]" -l "[IDAlbum]" -d "[IDYear]" -G "[IDGenre]" -N "[IDComment]" [InFile]
I used the MSVC 7 compile provided here at HA.
kenjima
Jun 10 2004, 05:04
I was able to use the auToV oggenc by using the P4 optimised vorbis cli plugin on the dbpoweramp website, but just selecting the auToV oggenc as the executable file. That seems much easier to me.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.