Hi, more LADPSA stuff I'm afraid. I've a few plugins that can't be marked as HARD_RT_CAPABLE because thier cycle consumption varies too much when you change parameters (ie. they use parameter watching and only rebuild tables if they need to) otherwise they would be too slow with small chunk sizes. But this means that they can't be flagged as RT_CAPABLE, even though they don't use malloc or anything nasty like that. Is thier any advantage to allowing them to flag that they have unpredictable CPU consumption, but are otherwise safe? I'm not sure if that helps the host. - Steve
- Re: [linux-audio-dev] LADSPA hard_rt_capable Steve Harris
- Re: [linux-audio-dev] LADSPA hard_rt_capable Benno Senoner
- Re: [linux-audio-dev] LADSPA hard_rt_capable Steve Harris
- Re: [linux-audio-dev] LADSPA hard_rt_capabl... Paul Barton-Davis
- Re: [linux-audio-dev] LADSPA hard_rt_ca... Steve Harris
- Re: [linux-audio-dev] LADSPA hard_rt_capabl... Kai Vehmanen
- Re: [linux-audio-dev] LADSPA hard_rt_ca... Steve Harris
- Re: [linux-audio-dev] LADSPA hard_rt_capable Jack O'Quin
- Re: [linux-audio-dev] LADSPA hard_rt_capabl... Paul Barton-Davis
- Re: [linux-audio-dev] LADSPA hard_rt_capabl... David Olofson