Hello,
I´m using the TAK encoder 1.03 with EAC and Wapet (to write the Tags), and it works very good. Additionally I have bought the dbpoweramp Reference Version 12.4, because the secure ripping of my Plextor 760 are much faster with this program.
I use the CLI-Encoder for dbpoweramp to encode with TAK - and it works. I tried to use Wapet by using the same command-line options, posting here "How to Tak". But no tagging took place.
Has anybody here an idea, how I can write tags within dbpoweramp´s CLI-Encoder?
thank you
Full Version: Writing Tags within dbpoweramp for TAk encoder
QUOTE(UweM @ Mar 11 2008, 17:09) 
Hello,
I´m using the TAK encoder 1.03 with EAC and Wapet (to write the Tags), and it works very good. Additionally I have bought the dbpoweramp Reference Version 12.4, because the secure ripping of my Plextor 760 are much faster with this program.
I use the CLI-Encoder for dbpoweramp to encode with TAK - and it works. I tried to use Wapet by using the same command-line options, posting here "How to Tak". But no tagging took place.
Has anybody here an idea, how I can write tags within dbpoweramp´s CLI-Encoder?
thank you
in the CLI help file you will find this list of dynamic values:
you'll need to replace the EAC (ie %a) ones with the ones dbPoweramp uses
i tried to configure it my self too, but i couldn't get tak to work at all. would you mind sharing the line you use if you get it to work please?
CODE
Dynamic Command Line Items
The following items will be dynamically replaced on usage:
[infile] Input filename, if not present stdin is used
[outfile] Output filename, this is required for every conversion
[artist] Artist
[album] Album title
[title] Track title
[genre] Music genre
[year] Year of recording
[track] Track number
[track_total] Total tracks on CD
[disc] Compilation disc number
[disc_total] Compilation disc total
[tag]<element>[] Embed user defined tag element
[unique] Unique number (not padded)
[extension] Audio format extension
[date] Current date
[time] Current time
[day_of_week] Current day of week
[now_year] Current year
[frequency] Frequency ie 44100
[channels] Channels ie 2
[channels_subone] Channels-1 ie 0 for mono
[bits_per_sample] Bits ie 16
[bytes_per_sample] Bytes (bits / 8) ie 2
QUOTE(UweM @ Mar 11 2008, 08:09)
secure ripping of my Plextor 760 are much faster with this program.
Apologies for being somewhat off-topic, but it would seem that you haven't optimally configured EAC with this drive.
You will get the best results (speed and accuracy) using the -usefua switch and C2 pointers with cache flushing disabled. If you do this, your ripping speed will be much more comprable to dBpowerAMP without sacrificing security (not taking into account that dBpa uses C2 pointers during re-reads for improved accuracy during re-reads).
I am not trying to detract from your decision to go with dBpa; I simply don't want people getting the wrong impression about the potential performance with this drive and EAC.
EAC is slower as it does not use AccurateRip in a smart way, example:
1 Disc all tracks are ok (disc in in AccurateRip) except track 3 & 5, both can be recovered by re-reading.
In dBpoweramp all tracks would rip in 1 pass, track 3 + 5 would automatically go into secure re-rip mode, bad frames are recovered.
In EAC you can configure to burst rip, look at AccurateRip then switch to secure mode, unselect the other tracks, and rip track 3 + 5 again (there is extra time taken for these tracks to be re-read).
If secure mode is used for the whole disc in EAC then is it 2x slower on the all tracks except 3 + 5, and possibly slower on 3 + 5 depending on the damage.
1 Disc all tracks are ok (disc in in AccurateRip) except track 3 & 5, both can be recovered by re-reading.
In dBpoweramp all tracks would rip in 1 pass, track 3 + 5 would automatically go into secure re-rip mode, bad frames are recovered.
In EAC you can configure to burst rip, look at AccurateRip then switch to secure mode, unselect the other tracks, and rip track 3 + 5 again (there is extra time taken for these tracks to be re-read).
If secure mode is used for the whole disc in EAC then is it 2x slower on the all tracks except 3 + 5, and possibly slower on 3 + 5 depending on the damage.
There is absolutely nothing stopping someone from selecting all tracks, pressing F5, looking at the AR results and then pressing F8 for the tracks it can't verify.
People are often unaware that they may be using a configuration or ripping method that is less than optimal. This was my primary concern here; not nitpicking the differences which cannot account for dBpoweramp being "much faster" than EAC with a PX-760.
People are often unaware that they may be using a configuration or ripping method that is less than optimal. This was my primary concern here; not nitpicking the differences which cannot account for dBpoweramp being "much faster" than EAC with a PX-760.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.