Pfm2 : unison discussion

[vurt]

@matrix12x
volume often full (2.0), but it really depends since some patches can be very quiet otherwise, i've spent a long time making every patch the same level.. if i turn down the internal volume its fine. but yeah it probably shouldn't change the patches in such a way that suddenly they distort.

[Xavier]

volume often full (2.0), but it really depends since some patches can be very quiet otherwise, i've spent a long time making every patch the same level.. if i turn down the internal volume its fine. but yeah it probably shouldn't change the patches in such a way that suddenly they distort.

Thanks again for the presets you sent me.

Full volume is 1.0 not 2.0.
The preenfm2 adjust the volume per voice depending on the number of instrument enable (voices > 0) and number of voices.

I tried your patches, the 3 of them have volume > 1.0.

I did not notice any difference between 2.20 and 2.20u (unison) firmwares. And I don't see in the code any reason for that.
When they distort in 2.20u they also distort in 2.20 with the tests i've done.

A possibility is that when you played them in 2.20 you had another instrument enabled (with voices > 0). So the volume was divded by 2.
And when trying them in 2.20u instrument you don't have other instrument enabled, so they use the full DAC resolution and because of volume > 1.0, the DAC buffer saturates.

Do you think that can be the reason ?
If not, please let me know how you tested.

[vurt]

max volume (gain, in filter section) says 2.0, that's what i meant. at least it does for me, and that's where the volume is for at least 2 of the patches i sent you.
i've not changed voices or instruments enabled..

but it's no biggie to me, i'll just lower the gain and re-save. if its just me who's affected i guess it's on my end anyways.

[matrix12x]

@vurt I didn't realize you meant the gain in the filter section. I thought you had meant the volume knob.

I always set gain to less than 1.0 (usually at 0.85 or so), as I had interpreted 1.0 as full gain to avoid any overdrive that I did not intend.

[vurt]

i go to 2.0 for the quieter patches so that i can have all patches at pretty much the same volume, it's very irritating to browse for sounds and suddenly something is extremely quiet (or loud).. in fact i wouldn't mind if it went to 3... i still have sounds that are too low in volume, though not too many.

[Xavier]

Just compiled a new version this morning 2.20w
https://drive.google.com/file/d/134BZ5ynOieO-ALGhXGHc_6dFoDJ3eTh3/view?usp=sharing
. Midi CC 13 for Unison Detune (only use at note on event cannot do real time modificaiton during a note).
. Midi CC 14 for Unison Spread
. Fix a display problem (preset name all over the screen) when receiving a patch from the editor

[matrix12x]

I checked 2.20w out. CC13 and CC14 work as described.

I checked out the display after sending presets from the editor and that seems to work as well. (no weird names all over the display)

Good work.

[Xavier]

I checked 2.20w out. CC13 and CC14 work as described.
I checked out the display after sending presets from the editor and that seems to work as well. (no weird names all over the display)

Thanks a lot ! 

[matrix12x]

I just noticed a bug (when using 2.20w and the current version of the editor)... when I push a patch from the editor, it "zeros" out the voices in the PFM2. regardless of the voice setting in the editor.


If I turn the voice knob in the editor the number of voices is correct, its just when I press "push."

Not sure if its an editor bug, or a PFM2 bug. However, this behavior does not exist at PFM2 2.20u.

[hitachii]

This often happens with me too. I'm using 2.20, haven't installed the Unison firmware.

[Xavier]

I'm trying to see what's wrong.
I don't see any difference between 2.20v and 2.20w that could explain that.
And it should not happen with 2.20 in with editor in "pfm2" mode.

1. Do you use editor 3.1.3 ?
2. Do you use the editor in "pfm3" mode ?

[matrix12x]

Ahh, I was using 3.1.2 in PFM2 mode. I just updated to 3.1.3 based on your post and it fixed my issue.
Thanks. Accordingly, there is no bug. It was operator (me) error.

[Xavier]

Cool thanks for the update 

[hitachii]

Wanted to add that I went to see if there were any special circumstances that caused this to happen for me, and couldn't find any. It still makes 0 voices on the PFM2 when pressing the "push" button, regardless of how many are set in the VST. Also want to mention that this is never a problem for me, as adding voices after pressing "push" either in VST or on the physical instrument works just fine.

Always thought that it was a way to ensure that you weren't exceeding the number of voices the hardware can handle.

[Xavier]

Always thought that it was a way to ensure that you weren't exceeding the number of voices the hardware can handle.

When the number of voices pushed is greater than what is available the max possible is used (no 0).


I released a 2.21 firmware with a small video 
Difference from 2.20w: stop playing when changing play mode (poly/unison) to make sure next played note us the correct number of voices.