Welcome, Guest
Username: Password: Remember me

TOPIC: Understanding Attenuation

Understanding Attenuation 3 years 4 months ago #7

  • Dan Eble
  • Dan Eble's Avatar
  • Offline
  • New Member
  • Posts: 9
Davy wrote:
For sure, the attenuations set in Polyphone are correct (I already tried to save with Polyphone and open with Swami for instance).

Now that Polyphone is known to be incorrect relative to the Creative/E-MU implementations, somebody should tell the Swami developers that their program is incorrect too. Would you prefer to do it or should I?
The administrator has disabled public write access.

Understanding Attenuation 3 years 4 months ago #8

  • S. Christian Collins
  • S. Christian Collins's Avatar
  • Offline
  • Senior Member
  • Posts: 62
  • Thank you received: 23
Swami uses FluidSynth under-the-hood, so it should already be handling this correctly.
The administrator has disabled public write access.

Understanding Attenuation 3 years 4 months ago #9

  • Dan Eble
  • Dan Eble's Avatar
  • Offline
  • New Member
  • Posts: 9
The synthesizer output is one way that a SoundFont is presented. Another way is as numeric values in an editor. Polyphone has the problem that when the editor says the attenuation is 10 dB, the synthesizers actually use 4 dB. The UI should be changed to say 4 dB in that case.

I understood from Davy that Swami shows the same attenuation value as Polyphone. If that is correct, Swami's UI should also be changed to show the actual attenuation that the synthesizer will use.
The administrator has disabled public write access.

Understanding Attenuation 3 years 4 months ago #10

  • S. Christian Collins
  • S. Christian Collins's Avatar
  • Offline
  • Senior Member
  • Posts: 62
  • Thank you received: 23
I see what you are saying now, sorry. Yes, to have the SoundFont editors reflect the *actual* attenuation that will occur rather than the numeric value stored in the SoundFont is a good idea.
The administrator has disabled public write access.

Understanding Attenuation 3 years 4 months ago #11

  • Davy
  • Davy's Avatar
  • Offline
  • Administrator
  • Organ enthusiast and creator of Polyphone
  • Posts: 343
  • Thank you received: 83
This is indeed a good idea for consistency between the unit and the value displayed. This can easily be done since this is just "cosmetic", at the ui level.

But this might be surprising for users. I know for example which amount I should add or remove to modify the intensity of the sound, and including the 0.4 factor will imply a new learning with these values. Moreover, all other parameters dealing with dB are impacted (modulators, envelops, ...).

My question would be: is this fix worth the effort to re-learn the handling of attenuations?
Being rather rigorous I would fix the interface. But for sure we will got a lot of questions and some users will like to see the same values between all other soundfont editors.

Davy
The administrator has disabled public write access.

Understanding Attenuation 3 years 4 months ago #12

  • S. Christian Collins
  • S. Christian Collins's Avatar
  • Offline
  • Senior Member
  • Posts: 62
  • Thank you received: 23
Davy wrote:
Moreover, all other parameters dealing with dB are impacted (modulators, envelops, ...).

What do you mean by this? As far as I know, the 0.4 dB factor only applies to instrument and preset level attenuation values. It shouldn't affect dB calculations for things like velocity curves, etc.

My question would be: is this fix worth the effort to re-learn the handling of attenuations?
Being rather rigorous I would fix the interface. But for sure we will got a lot of questions and some users will like to see the same values between all other soundfont editors.

I agree. Perhaps the editable value should remain as it is, but then the actual amount of dB attenuation could appear next to it in parentheses. This is the solution I would prefer as a SoundFont designer.
The administrator has disabled public write access.
Time to create page: 0.162 seconds
Cron Job Starts