Open musikBear opened 6 years ago
Tested
Actually, when two Higher Quality Pitch Scaler are active, they will produce strage sounds even if played alone.
So this looks like Higher Quality Pitch Scaler relies on some fixed memory locations that both instances try to use.
its source should be this https://github.com/swh/ladspa/blob/master/pitch_scale_1194.xml
I guess it's not really our bug...
SWH plugin's pitch_scale
function uses static buffers and FFT plans. It means sharing the library instance between plugin instances means they'll share those static variables.
However, LMMS processes effects using multiple worker threads. Due to sharing static variables, it's thread unsafe.
@PhysSong I have some questions:
High Quality Pitch Scaler
plugin?wontfix
with a proper explanation?Is this our bug?
SWH's pitch_scale
implementation doesn't take care of multiple instances and thread safety, so I'd say no.
Is this our bug?
SWH's
pitch_scale
implementation doesn't take care of multiple instances and thread safety, so I'd say no.
Thanks. Is it easy and possible to patch the static buffers upstream?
It is possible, but I'm not sure whether it's easy. I'm pretty sure if won't be difficult, though.
D.Ipsum reports this on forum:
Here with 3oc: issue_HardLimiterPitchScaler.txt