Unfiltered Audio Sandman Pro: Available Now

[Jeeez]

@thelizard: Would you consider an option to save the sleep buffer data together with a preset? I use the sleep buffer as a sound source for drones and would like to come back later and refine the loop. As it is right now, the content of the sleep buffer is empty every time I reopen my project (Reaper).

Thank you!

[xx JPRacer xx]

About the upcoming January updates.. Will this fix the high CPU load when the GUI is open?

Also, is the special bundle price time limited?

Thanks, awesome job!

[gaf_thit]

Also, is the special upgrade price time limited?

From the email:
"Limited time $29 upgrade offer:
Through Oct 31st you can upgrade to Sandman Pro"

[xx JPRacer xx]

Ok, thanks!

But sorry, I should mention that I was talking about the bundle. I've edited my original post.

[thelizard]

@thelizard: Would you consider an option to save the sleep buffer data together with a preset? I use the sleep buffer as a sound source for drones and would like to come back later and refine the loop. As it is right now, the content of the sleep buffer is empty every time I reopen my project (Reaper).

Thank you!

Sure! We'll look into how feasible this is, but it sounds like a good option to include.

[thelizard]

About the upcoming January updates.. Will this fix the high CPU load when the GUI is open?

Also, is the special bundle price time limited?

Thanks, awesome job!

Which GUI is giving you trouble, Sandman Pro? Does disabling the waveform display (in the gear options menu) help? Are you on Mac or Windows? What sort of graphics card do you have?

We're not experiencing large CPU spikes when the GUI is open, but if anyone is, please send Plugin Alliance support an e-mail with the above questions answered. They'll file each computer into a bug report tracker for us, making it easier for us to identify which general platforms are having issues. We'll try to make as many optimizations as possible for the January updates.

I'll talk to PA about the bundle pricing. So far, I've given at least one user bad information on deal lengths, so I'll try not to do that again

[zerocrossing]

Hm, looks like a nice bundle to pick up this Christmas!

[xx JPRacer xx]

About the upcoming January updates.. Will this fix the high CPU load when the GUI is open?

Also, is the special bundle price time limited?

Thanks, awesome job!

Which GUI is giving you trouble, Sandman Pro? Does disabling the waveform display (in the gear options menu) help? Are you on Mac or Windows? What sort of graphics card do you have?

Fault, Dent and Indent. With a clean project, no audio and host stopped, with GUI close I have ~2% CPU (with all 3 loaded on a track). When I open a GUI the CPU go to about 28%. If I open all 3 GUIs my CPU is ~72%. I can even hear the CPU fan speeding up. This is with no audio and host stopped.

Windows 10, i5-3450, 16 GB RAM, host is Reaper x64 and my GPU is nVidia GTX 970 with latest drivers.

Am I really the first to mention this?

[thelizard]

About the upcoming January updates.. Will this fix the high CPU load when the GUI is open?

Also, is the special bundle price time limited?

Thanks, awesome job!

Which GUI is giving you trouble, Sandman Pro? Does disabling the waveform display (in the gear options menu) help? Are you on Mac or Windows? What sort of graphics card do you have?

Fault, Dent and Indent. With a clean project, no audio and host stopped, with GUI close I have ~2% CPU (with all 3 loaded on a track). When I open a GUI the CPU go to about 28%. If I open all 3 GUIs my CPU is ~72%. I can even hear the CPU fan speeding up. This is with no audio and host stopped.

Windows 10, i5-3450, 16 GB RAM, host is Reaper x64 and my GPU is nVidia GTX 970 with latest drivers.

Am I really the first to mention this?

Yep, it's the first official report.

On my computer (extremely similar setup: W10, i5, GTX 960, 16 GB RAM), each Fault (debug build, so much slower) is showing 7.2% CPU, Dent (debug build) is showing 2.9%. I'm seeing a CPU uptick of about 1% when opening the GUIs vs using REAPER's generic GUI view.

I'm testing with VST3 builds in REAPER 5.26. 5.26 fixed some graphics issues with our plug-ins vs 5.24 and 5.25. Are you using VST2s or an older build of REAPER by chance?

[Hez]

Well done Michael & co, this thing sounds bonkers already.

Getting the same issue with automated delay times on the Glitch/Pitch modes (sadface, they are the ones I wanted to abuse the most!), but other than that it seems like a monster.

Any chance of adding specific Attack/Release times to the Envelope Follower instead of just slew? For sound design I like to do stuff like e.g. bury the delay time at 0 until the input sound has finished playing (with a really fast attack on the follower) then gradually let it off with slow release once the input has disappeared.

Along those lines, a longer slew time for the S&H would be much appreciated to sort of emulate a sample & glide instead. Works at short modulation times but once you're up to half a second cycle+ it starts to feel stepped again with maxed slew.

BTW noticed a load of your posts on the Temps Utile thread on Wiggler the other day... how do you find so many hours in a day!?

[ericzang]

REAPER 5.26, x64, win7.
i7 960 3.2ghz, GTX 285M, 1920x1200

Both vst2 and vst3, blank project.
no audio running, high CPU use - ASIO buffer 512

when GUI open -
Total CPU: 25%
RT CPU: <1%

GUI closed
Total CPU: 1.2%
RT: <1%

6 instances, one GUI open :
Total CPU: 30%
RT: <1%

Switch to generic parameter GUI in Reaper, cpu use same as closed.

Tooltips only flash on in both vst3 and vst 2 version.

Thanks for your efforts!

[xx JPRacer xx]

About the upcoming January updates.. Will this fix the high CPU load when the GUI is open?

Also, is the special bundle price time limited?

Thanks, awesome job!

Which GUI is giving you trouble, Sandman Pro? Does disabling the waveform display (in the gear options menu) help? Are you on Mac or Windows? What sort of graphics card do you have?

Fault, Dent and Indent. With a clean project, no audio and host stopped, with GUI close I have ~2% CPU (with all 3 loaded on a track). When I open a GUI the CPU go to about 28%. If I open all 3 GUIs my CPU is ~72%. I can even hear the CPU fan speeding up. This is with no audio and host stopped.

Windows 10, i5-3450, 16 GB RAM, host is Reaper x64 and my GPU is nVidia GTX 970 with latest drivers.

Am I really the first to mention this?

Yep, it's the first official report.

On my computer (extremely similar setup: W10, i5, GTX 960, 16 GB RAM), each Fault (debug build, so much slower) is showing 7.2% CPU, Dent (debug build) is showing 2.9%. I'm seeing a CPU uptick of about 1% when opening the GUIs vs using REAPER's generic GUI view.

I'm testing with VST3 builds in REAPER 5.26. 5.26 fixed some graphics issues with our plug-ins vs 5.24 and 5.25. Are you using VST2s or an older build of REAPER by chance?

Reaper 5.26 with vst2.

[thelizard]

Well done Michael & co, this thing sounds bonkers already.

Getting the same issue with automated delay times on the Glitch/Pitch modes (sadface, they are the ones I wanted to abuse the most!), but other than that it seems like a monster.

Any chance of adding specific Attack/Release times to the Envelope Follower instead of just slew? For sound design I like to do stuff like e.g. bury the delay time at 0 until the input sound has finished playing (with a really fast attack on the follower) then gradually let it off with slow release once the input has disappeared.

Along those lines, a longer slew time for the S&H would be much appreciated to sort of emulate a sample & glide instead. Works at short modulation times but once you're up to half a second cycle+ it starts to feel stepped again with maxed slew.

BTW noticed a load of your posts on the Temps Utile thread on Wiggler the other day... how do you find so many hours in a day!?

Thanks! The glitch/pitch modulation appears to now be fixed on our end. We need to do some intensive testing to make sure that we haven't broken any projects, presets, or other behaviors, but the initial feeling is that it works. Once we test it, we'll release a hotfix. That must've broken late in the process, and I apologize that it made it into 1.0.

The bidirectional slew (a la Maths, right?) would be awesome, but it would break existing presets. It could work as a separate mode, though. (Also, hah, it would almost be possible to build a mini-G8 with our modulation system and a gain control).

Regarding S+H, the current max slew time is equal to the generation frequency. So, if it samples every 1 second, it should take 1 full second to get to each new "voltage" at 100% slew. Is it behaving otherwise for you?

I love Temps Utile and O+C. I'm working on an O+C app that is similar to a JAG in that it converts X-Y CV inputs into coordinate CV outputs. If you have Reaktor, I also have a big batch of Blocks available for that: https://www.native-instruments.com/en/r ... show/9093/

[GaryG]

Think I've experienced a (site specific?) bug...

If I reduce the number of taps in multi-tap mode then the CPU goes up dramatically. In fact as I got down to two, Reaper actually crashed.

This was on an old i3 laptop (Win10 32bit) so not a powerhouse but generally holds it's own.

Besides that, totally awesome.

[thelizard]

Think I've experienced a (site specific?) bug...

If I reduce the number of taps in multi-tap mode then the CPU goes up dramatically. In fact as I got down to two, Reaper actually crashed.

This was on an old i3 laptop (Win10 32bit) so not a powerhouse but generally holds it's own.

Besides that, totally awesome.

Wow, just tested in Live. Yeah, I can't crash it, but I am seeing a definite spike. That's one of the most counter-intuitive bugs I've ever seen. Surely I did something stupid with the optimization there.

Hopefully this is something we can get into the hotfix as well. Thanks for the report!