Clear Audio Extraction Log

[garym]

Re: Clear Audio Extraction Log

I doubt it. I haven't seen @spoon chime in on this thread to even confirm that this is a bug or whether there is already a setting you can change to solve the problem. You might want to create a new post with the subject "Possible Bug in writing log in multi-encoder" and link back to this thread. That might get more views (and maybe views from multi-encoder users....that would likely provide the most help and/or confirmation). There are plenty of multi-encoder users and I've never seen anyone else raise your issue. Thus my thoughts that maybe there is a setting that would help you.

[Dansync]

Re: Clear Audio Extraction Log

Is this bug fixed in R16.4?

[Dansync]

Re: Clear Audio Extraction Log

There may be a way to indicate different logs for both the flac and mp3 rips. I've never looked into it as I've never setup multi-encoder. I hope someone who uses this or @spoon can chime in with a suggestion/solution.

I think encoding doesn't write logs, just ripping. MP3 is encoded based on the FLAC rip. So no logs exist of that.

[Dansync]

Re: Clear Audio Extraction Log

After more trial and error I figured out that this bug is related to the combination of multi-encoder with the log file tag [rippedtopath]. When I replaced [rippedtopath] with the hardcoded path as set in the multi-encoder, the big log file didn't get written anymore, and just the log for that one rip is made. Would be nice if this could be fixed in a next version.

[garym]

Re: Clear Audio Extraction Log

So another reply got deleted from me, odd. Anyway, for now I decided to not use the logs anymore. It is too buggy. I hope it will be fixed in the next version. I rather use multi-encoder without logs over no multi-encoder with logs.

I figured out the issue. Don't have a solution yet though..

When using the Multi-Encoder, the path the logfile is written to by default starts with the tag "[rippedtopath]". This tag gives problems with Multi-Encoder and I do consider this a bug. When I replace this tag with the same path, but hardcoded (of the path of the FLAC version, as I rip both FLAC and MP3 to different directory structures and the [rippedtopath] only wrote to FLAC directory anyway) it somehow works magically.

There may be a way to indicate different logs for both the flac and mp3 rips. I've never looked into it as I've never setup multi-encoder. I hope someone who uses this or @spoon can chime in with a suggestion/solution.

[Dansync]

Re: Clear Audio Extraction Log

So another reply got deleted from me, odd. Anyway, for now I decided to not use the logs anymore. It is too buggy. I hope it will be fixed in the next version. I rather use multi-encoder without logs over no multi-encoder with logs.

I figured out the issue. Don't have a solution yet though..

When using the Multi-Encoder, the path the logfile is written to by default starts with the tag "[rippedtopath]". This tag gives problems with Multi-Encoder and I do consider this a bug. When I replace this tag with the same path, but hardcoded (of the path of the FLAC version, as I rip both FLAC and MP3 to different directory structures and the [rippedtopath] only wrote to FLAC directory anyway) it somehow works magically.

[Dansync]

Re: Clear Audio Extraction Log

Yes, there are many users of multi-encoder I believe. What about my question related to the name/location settings you've given to the "write log to" settings. Was that your naming string or the default? My best guess is that if that is not default, there is something about your naming string for writing the logs that is creating the problem.

p.s. I also rip to FLAC and then later create mp3 copies for on the go. But I don't do this all at one step. I setup the dbpa converter to do this for me, with a couple of mouse clicks. It can create my mp3 library and it is smart enough to only add new FLAC file mp3 copies, it doesn't recreate all the already existing mp3 files. There's also the new TuneFusion illustrate product (in beta), which can automate creating copies, converting from one codec to another, etc., all in an automated manner. See:

https://forum.dbpoweramp.com/showthread.php?39617

Thanks for the info. I really appreciate the help.

My multi encoder settings are in the google doc they are:

FLAC
Output To: [IFEQUALS][encoder],(FLAC 1.3.2),FLAC[]\[IFEQUALS][album artist],Various Artists,Various Artists\[album] ([year])[][IF!EQUALS][album artist],Various Artists,Artists\[album artist]\[year] - [album][]\[IFMULTI][disc]-[][track]. [artist] - [title]

MP3
Output To: [IFEQUALS][encoder],Lame 3.100.0,MP3[]\[IFEQUALS][album artist],Various Artists,Various Artists\[album] ([year])[][IF!EQUALS][album artist],Various Artists,Artists\[album artist]\[year] - [album][]\[IFMULTI][disc]-[][track]. [artist] - [title]

They are not default.

I will look into how dpba converter works, maybe use that instead of multi-encoder. Still in my opinion, setting an "Output To" different from default with some of the nice coding magic dpba offers, shouldn't break the log writing functionality. So I'd still like to see an answer to the issue.

[garym]

Re: Clear Audio Extraction Log

It indeed is related to the multi-encoder somehow. When I put the Profile back to default, it writes just the log file for that rip... Now to find out what is wrong here... I can't be the only one using the multi-encoder, right? This is the part I like about dBpoweramp in which it makes the FLAC versions for archival and MP3 for on the go..

Yes, there are many users of multi-encoder I believe. What about my question related to the name/location settings you've given to the "write log to" settings. Was that your naming string or the default? My best guess is that if that is not default, there is something about your naming string for writing the logs that is creating the problem.

p.s. I also rip to FLAC and then later create mp3 copies for on the go. But I don't do this all at one step. I setup the dbpa converter to do this for me, with a couple of mouse clicks. It can create my mp3 library and it is smart enough to only add new FLAC file mp3 copies, it doesn't recreate all the already existing mp3 files. There's also the new TuneFusion illustrate product (in beta), which can automate creating copies, converting from one codec to another, etc., all in an automated manner. See:

https://forum.dbpoweramp.com/showthread.php?39617

[Dansync]

Re: Clear Audio Extraction Log

Hmmm. It appears you are using the multiencoder. I've not seen your log issue mentioned with that either, but I don't personally use multiencoder so can't attest to how it behaves. Can you try some rips directly to FLAC or mp3 (not using multiencoder) and see if the problem still exists. If not, that would at least point to something in your multiencoder settings.

The log you posted certainly seems to have included multiple rips in a single log. I'm not at home so can't check, but is the "write to" log name you show in your google docs document the default name/location for the log? Or is it a name/location you specifically gave it. If so, I'd look closely at that as if something is odd about that location, it would keep the log file open forever.

It indeed is related to the multi-encoder somehow. When I put the Profile back to default, it writes just the log file for that rip... Now to find out what is wrong here... I can't be the only one using the multi-encoder, right? This is the part I like about dBpoweramp in which it makes the FLAC versions for archival and MP3 for on the go..

[garym]

Re: Clear Audio Extraction Log

Hmmm. It appears you are using the multiencoder. I've not seen your log issue mentioned with that either, but I don't personally use multiencoder so can't attest to how it behaves. Can you try some rips directly to FLAC or mp3 (not using multiencoder) and see if the problem still exists. If not, that would at least point to something in your multiencoder settings.

The log you posted certainly seems to have included multiple rips in a single log. I'm not at home so can't check, but is the "write to" log name you show in your google docs document the default name/location for the log? Or is it a name/location you specifically gave it. If so, I'd look closely at that as if something is odd about that location, it would keep the log file open forever.

[Dansync]

Re: Clear Audio Extraction Log

Can you try to post your log from pastebin again. (NEVERMIND: I connected to it. I'll take a look now). The one above doesn't work. copy the URL you want to post, then click on the "post link" icon above the text box for replying to this email. It is 6 icons from the right (looks like a planet eart with a little "link" emblem at the bottom of the earth).

Anything is possible, but it is unlikely a bug. I've never seen this problem reported in years of hanging out at this forum. And I've not seen this happen in my own ripping over the last 10 years, across thousands of CDs and many different versions and windows machines.

Just replace "DOT" with a "." in the URL.

[garym]

Re: Clear Audio Extraction Log

Log: pastebinDOTcom/VXz6X3eQ

Hope this helps. At this point im starting to think its just a bug in dbpa...

Meanwhile I've also been starting to type out all the settings I could find how I have currently set them see that below:
docs.googleDOTcom/document/d/1DeZdp5OIte6RJl_OlO5WCVIlHVu6iP6uzQFWV0l8sPY/edit?usp=sharing

Can you try to post your log from pastebin again. (NEVERMIND: I connected to it. I'll take a look now). The one above doesn't work. copy the URL you want to post, then click on the "post link" icon above the text box for replying to this email. It is 6 icons from the right (looks like a planet eart with a little "link" emblem at the bottom of the earth).

Anything is possible, but it is unlikely a bug. I've never seen this problem reported in years of hanging out at this forum. And I've not seen this happen in my own ripping over the last 10 years, across thousands of CDs and many different versions and windows machines.

[Dansync]

Re: Clear Audio Extraction Log

Log: pastebinDOTcom/VXz6X3eQ

Hope this helps. At this point im starting to think its just a bug in dbpa...

Meanwhile I've also been starting to type out all the settings I could find how I have currently set them see that below:
docs.googleDOTcom/document/d/1DeZdp5OIte6RJl_OlO5WCVIlHVu6iP6uzQFWV0l8sPY/edit?usp=sharing

[garym]

Re: Clear Audio Extraction Log

I already replied twice, why do my posts get deleted? Is it because I post a link to pastebin with the log? Anyway, reset didn't help. See my previous posts that got deleted twice for all details.

Sorry, I don't see any post with link to a log? But I did see the text of your post (below), when it was emailed to me as an update. Not sure why it disappeared.

[SIZE=2]=========================
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..:

Did about 4 rips:
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.
***************
[/SIZE]

[Dansync]

Re: Clear Audio Extraction Log

I already replied twice, why do my posts get deleted? Is it because I post a link to pastebin with the log? Anyway, reset didn't help. See my previous posts that got deleted twice for all details.