Changed Behavior In Character Mapping

[Spoon]

Re: Changed Behavior In Character Mapping

Try restarting Windows in safe mode (with networking):

https://support.avira.com/hc/en-us/articles/360002870214-How-do-I-start-Windows-10-in-Safe-Mode-

Then see if filename and DSP effect works.

[husker]

Re: Changed Behavior In Character Mapping

Try restarting Windows in safe mode (with networking):

https://support.avira.com/hc/en-us/articles/360002870214-How-do-I-start-Windows-10-in-Safe-Mode-

Then see if filename and DSP effect works.

Safe mode had no effect.

[Spoon]

Re: Changed Behavior In Character Mapping

If you look in dBpoweramp Control Center it says Release R17.2 and further down Registration Status: Reference Registered?

[husker]

Re: Changed Behavior In Character Mapping

If you look in dBpoweramp Control Center it says Release R17.2 and further down Registration Status: Reference Registered?

Screenshot below. "Fully Registered, No Restrictions"

[Spoon]

Re: Changed Behavior In Character Mapping

Which Windows version do you have?

[husker]

Re: Changed Behavior In Character Mapping

Which Windows version do you have?

Windows 10 Enterprise 20H2

[Spoon]

Re: Changed Behavior In Character Mapping

Do you have access to any other computer you can test on?

[husker]

Re: Changed Behavior In Character Mapping

Do you have access to any other computer you can test on?

OK. I did some addional testing. The issue happens whenever I create a new profile.

1. The default profile shows the filename correctly.
2. As soon as I create a new profile, even copying settings from the default profile, the filename column blanks out, and will not process the DSP.
3. This happens on two computers, both Windows 10 Enterprise 20H2.

[Spoon]

Re: Changed Behavior In Character Mapping

Which encoder are you using? if using Multi-encoder then it would not show filename there.

[husker]

Re: Changed Behavior In Character Mapping

Which encoder are you using? if using Multi-encoder then it would not show filename there.

Yes, I am using multiencoder.

[husker]

Re: Changed Behavior In Character Mapping

OK, narrowing this down a bit more - it is the multiencoder that creates the problem.

1. Create new blank profile, select MP3, add the DSP effect to replace ':' with ' - '

That works perfectly. However, if I do this:

2. Create new blank profile, select multiencoder, add MP3, add the DSP effect to replace ':' with ' - '

That will NOT work, and the DSP is not processed.

[husker]

Re: Changed Behavior In Character Mapping

Spoon - can you reproduce the above?

[husker]

Re: Changed Behavior In Character Mapping

OK Spoon, I can reproduce the error 100% of the time using multiencoder.

I can set different profiles for single encoders (Flac and MP3) with all the DSP effects, and they all work correctly.
If I set a multiencoder using the exact same (saved then load) DSP effects, they fail.

I have to rip CDs twice now (one each profile), so it would be helpful to have this fixed.

[Spoon]

Re: Changed Behavior In Character Mapping

We will look at this when next updating dbpoweramp, the dap effect is not being used for naming when within multi encoder.

[husker]

Re: Changed Behavior In Character Mapping

We will look at this when next updating dbpoweramp, the dap effect is not being used for naming when within multi encoder.

Can you reproduce the issue? Do you know why it is happening? It seemed fine on R16.