Physical Audio P4 dual spring reverb

[v1o]

Edit:
forget about it

[cjwseven7]

Does anyone find it incovenient that PA products including this spring reverb function only in low sampling rates?

What?? No way! .... Oh. Yes way. Deal breaker.


Screen Shot 2018-11-13 at 4.18.38 PM.png


I harp on the issues of not all devs support all sample rates and get flak from some people who think my concerns are unfounded - this is yet another example of it. Bad form when it comes to audio tools. I push my work into 96k whenever I can. But I often get hampered by plugins that prevent this. I try work-arounds, or asking the dev to fix it. Sometimes I have no choice because there are no options other than 44.1k.

Yet another trap for young players. The mine field of audio software!

Thanks filulilu for the warning! I was about to buy it!

Hey, thanks for bringing this up. PA1 and PA4 can only operate at 44.1 or 48 because they are very demanding on the CPU, making it possible, though probably inconvenient to work at higher sample rates. This is something we discussed in early beta tests, and our choice was to find a tradeoff between quality and usability. So far we haven't had a lot of complaints in this respect, but we are always very open to feedback.

[plexuss]

Hey, thanks for bringing this up. PA1 and PA4 can only operate at 44.1 or 48 because they are very demanding on the CPU, making it possible, though probably inconvenient to work at higher sample rates. This is something we discussed in early beta tests, and our choice was to find a tradeoff between quality and usability. So far we haven't had a lot of complaints in this respect, but we are always very open to feedback.

There is a best practise in usability "Give the user control and freedom". Hampering user control is bad usability. Just let the user know what the implications are. By doing what you are doing, you prevent the user from controlling their project sample rate. For example, I mix in 44 and then when ready to bounce a master I switch to 96 - I dont care at this point if I can play in real time - as long as I can render and the plugins work the same in 96 as 44 I'm good. I will get a good true 96k mix that I can then proceed to mastering.

This is one of the benefits of working ITB - the ability to get higher quality renders from lower quality real time work.

The way you've implemented it, you prevent me from doing this. This is the same gripe I have with Acustica with Nebula where they disable the ability to turn off their plugin and save CPU even when freezing tracks!!

There is no good reason to do this. The user should have control and freedom. They should understand the implications. If you plugin can only work if you take this control and freedom away then you need to come clean and explain this and not come up with a spin that it is to create usability. Good usability is giving the user control and freedom. Preventing DAW features from working (eg. changing the project rate) is a huge usability error.

[filulilu]

You could have an optional high quality setting. Also, just for convenience, when in high sample rate projects, the "standard quality" setting could downsample the signal before processing and upsample it again at the output. Rendering could be done always in the project's actual sample rate.

[cjwseven7]

You could have an optional high quality setting. Also, just for convenience, when in high sample rate projects, the "standard quality" setting could downsample the signal before processing and upsample it again at the output. Rendering could be done always in the project's actual sample rate.

Noted.

[cjwseven7]

Does anyone find it incovenient that PA products including this spring reverb function only in low sampling rates?

Hey, our reverbs now support sample rates up to 96kHz. The update is free for all our users.