Clear Audio Extraction Log

[Dansync]

Re: Clear Audio Extraction Log

Yesterday I replied to all your questions and advice, but that reply needed approval by moderation. I still don't see my post here so I'll type it out again, a bit shorter this time:

Did about 4 rips after the reset:
1 with default settings (no log)
1 with my secure ripping settings put back (log for that rip, so it went good)
1 with that same CD, but deleted the previous rip, didnt change settings, still only the log for that CD
1 with all my old settings back (made backup screenshots before the reset tool), and now the massive log was back again

Running Windows 10 Home, didn't change anything to my system, other then buying a license for R16.3. Used R16.2 as a trial earlier this year, finally got the time to continue on with ripping so I decided to buy.

I'll run a new CD for the big log, ill update this post with a pastebin link of it.

EDIT: Big log file: https://pastebin.com/VXz6X3eQ

[Dansync]

Re: Clear Audio Extraction Log

To clean slate dBpoweramp run:

https://forum.dbpoweramp.com/showthread.php?13285-Totally-Clearing-dBpoweramp-from-the-System

Then try with the default settings.

Rip 1:
Tried one rip with default settings. By default apparently no log is written to file.

Rip 2:
I made screenshots before running the reset tool, so for the second rip I have only put back the Secure Ripping settings. Log file was written, only the log for this rip is in there, which is good (but also obvious because all settings are reset).

Rip 3:
I deleted the second rip (including the log file, deleted the whole directory). Everything still same settings as rip 2, so only the Secure Ripping settings are set. Again, the log file only shows the current rip, which is good.

Rip 4:
I have put back all my settings for rip number 4. And the big log file is back.

When did this issue begin and has anything changed on your system, recently? What Windows version? Where are you ripping CDs to?

I purchased and updated dbPoweramp today from R16.2 to R16.3. I used a trial of R16.2 earlier this year (I think in April) to test out if I liked it or not. Been very busy rest of the year, finally got some time to get back into ripping my collection so decided to buy the license today and update the tool.
Not sure since when this problem started to occur, as I didn't write log to a file earlier this year, but I decided today I wanted to keep them around.

Running Windows 10 Home. I'm ripping to a second internal harddisk (not a partition, just an extra physical disk) with 2TB of free space.

can you post the contents of one of these odd log files here. maybe there's a clue somewhere inside?

Latest log file: https://pastebin.com/p7jWcTZ4

Thanks for all your help so far. Nice community here

[garym]

Re: Clear Audio Extraction Log

When did this issue begin and has anything changed on your system, recently? What Windows version? Where are you ripping CDs to?

can you post the contents of one of these odd log files here. maybe there's a clue somewhere inside?

[mville]

Re: Clear Audio Extraction Log

It's getting even stranger. I just started to rip a different CD, and the log file written to that [rippedtopath] also contains log information of the other CD I ripped earlier.

When did this issue begin and has anything changed on your system, recently? What Windows version? Where are you ripping CDs to?

[Spoon]

Re: Clear Audio Extraction Log

To clean slate dBpoweramp run:

https://forum.dbpoweramp.com/showthread.php?13285-Totally-Clearing-dBpoweramp-from-the-System

Then try with the default settings.

[garym]

Re: Clear Audio Extraction Log

I'm out of ideas. Good luck.

[Dansync]

Re: Clear Audio Extraction Log

Tried again with "Rip to '._' files, rename album at end" but too but also same results. So it's not related to that setting.

[garym]

Re: Clear Audio Extraction Log

Yes I do have a naming string, that is correct. Each album goes into its own directory, if an album has multiple discs, those share the same directory, with separate log files inside it.

That makes me think, I do have a setting called "When Ripping" set to "Rip to temporary folder, move album after ripping". Could this be related? I think this is default, could you check what your setting says there? The Setting can be found under CD Ripper Options > Tags & Filenames.

EDIT:
Other possible options here are:
- Rip to '._' files, rename album at end
- Rip direct to final filenames

mine is set to:
- Rip to '._' files, rename album at end

[Dansync]

Re: Clear Audio Extraction Log

Yes I do have a naming string, that is correct. Each album goes into its own directory, if an album has multiple discs, those share the same directory, with separate log files inside it.

That makes me think, I do have a setting called "When Ripping" set to "Rip to temporary folder, move album after ripping". Could this be related? I think this is default, could you check what your setting says there? The Setting can be found under CD Ripper Options > Tags & Filenames.

EDIT:
Other possible options here are:
- Rip to '._' files, rename album at end
- Rip direct to final filenames

EDIT2:
Tried with "Rip direct to final filenames" but didn't help either.

[garym]

Re: Clear Audio Extraction Log

As the log file is getting bigger and bigger I decided to uninstall dbPoweramp > reboot machine > install dbPoweramp with the new installer I got today for registering R16.3 > reboot machine. Somehow dBPoweramp saved all my settings, which is neat.

Did another rip, new CD, still same problem. Old log info is still being shown. A log file for 1 rip should usually be around 15-20 KB, but its over 200 KB now...

Hopefully Spoon will have an answer!

Very odd. I went back and looked at some rips over the last few months just be be sure. In every case, the log file that's in the subdirectory with the album tracks only reports the ripping info for that particular CD.

A thought (probably not useful). I assume you are ripping the CDs using some sort of naming string that places the tracks within and "ARTIST/ALBUM/tracks" folder structure. That is, you're not ripping tracks from all CDs to a single subdirectory (and then maybe moving them later to their own directory)??? If you were doing this, I suppose it thinks every new attempt at ripping a CD is the same CD (all in same folder) and it just adds log info to the file that's already there. But that makes no sense to me either, as you have tried deleting the old log file before ripping. A real mystery...

[Dansync]

Re: Clear Audio Extraction Log

As the log file is getting bigger and bigger I decided to uninstall dbPoweramp > reboot machine > install dbPoweramp with the new installer I got today for registering R16.3 > reboot machine. Somehow dBPoweramp saved all my settings, which is neat.

Did another rip, new CD, still same problem. Old log info is still being shown. A log file for 1 rip should usually be around 15-20 KB, but its over 200 KB now...

Hopefully Spoon will have an answer!

[Dansync]

Re: Clear Audio Extraction Log

Just rebooted the machine dbpa is running on, didn't help either. Rather not reinstall dbpa as I will probably lose all my settings and there is no export settings feature, asked about that earlier already in another topic some time ago.

[garym]

Re: Clear Audio Extraction Log

First I closed dbPoweramp. Next I deleted this file as you suggested. Did a rip of yet another CD (not ripped before), and again it contains logs from older CD rips.

Any other suggestions?

First, exit dbpa, delete the bin file, then reboot the entire machine dbpa is running on. If that doesn't work, my next step would be reinstall of the program.

[Dansync]

Re: Clear Audio Extraction Log

Please try this.

Delete this file for having a clear state


C:\Users\YOUR NAME\AppData\Roaming\dBpoweramp\CDRipperCache.bin

A new file will be generated after your first rip.

First I closed dbPoweramp. Next I deleted this file as you suggested. Did a rip of yet another CD (not ripped before), and again it contains logs from older CD rips.

Any other suggestions?

[garym]

Re: Clear Audio Extraction Log

My goal here is to have a simple log file only containing the results of the actual rip that just happened, written to the same directory as the FLAC files are written to.

That is what should happen and what has happened with 1000s of my own rips. So something is very odd.