So... now when N2O is out, what do you think of it? I've got some major GUI-stealing-loads-of-processors-power issues but works fine if closing the GUI.

Well I'm sure the Bakers are going to take a little time off for the Holidays!! But a Proper MANUAL would be a nice little detail !!!!!


The routing section has a page that seems to be for crossing channels and flipping phase .......... But there are 8 boxes and I'm not sure how they relate in the scheme of things .


I'm also curious as to if there is a way to listen to the side chain ( which option shows up in the envelope follower) so that you can check the routing in your DAW is set up properly .

Jensa - do you experience this GUI-related CPU peaks all the time, or only when plot animation (modulation preview in MTRX tab) is on?

Flatfinger - the routing subsection you're talking about allows you to invert the phase and middle/side encode/decode (prior to operator and after it - that's why you have two switches for each op). It allows you to run the entire processing in middle/side, too by encoding prior to first operator and decoding after the last one (assuming your operators are in series).

There's a way to listen to sidechain signal, but you can't do it directly in enveloper follower settings. You have to use SIDEMIX operator (or compressor/expander, which has sidechain monitoring switch)

Hi. Thanks for asking.

About the GUI slugisshness - Everything, mouse movements, VU's etc in Reaper, animations in N2O etc gets a framerate about 5-10 fsp but the sound is working as it should. And the CPU use don't go down if I click off the "power"-button in the plugin fron-end. Also, when closing the plugin front-end window while running Reaper I get a crash, every time. I've made a animated screen capture with LiceCap (included in Reaper installation) so you can see what happens. Check it out here:

http://masarin.info/PSP-N2O-Crash-1.gif

My system spec is:

Windows XP 32-bit
4 GB RAM
Reaper 3.75pre2 (pre2 is not the problem)

I'll try a reinstall of N2O and see if that solves the problem.

Thanks!

Is it me being blind or is there no immediate easy way (if at all) to disable operators individually?


Just for the record - NO crashes or other problems with N2O on Mac with Logic in 64-bit mode so far on my setup. Can't comment about other situations.

I can reproduce the reaper sluggishness issue. It happens anytime the N2O GUI is visible.

If you set an operator to the 'gain' tool, leave the attenuation value a 0.00 db, and do not allow an operator to modulate any parameter for the gain operator, it is essentially the same thing as bypassing that operator.

It took me a little while to figure that out. Basically, I set all 4 operators as described above and listened to the processed signal. It sounded identical to the signal when N2O was not in the chain at all (I suppose you could call this the ultimate bypass).

Hope that helps.

Thanks for sharing your workaround.

However, I am in disbelief that a plugin such as N2O doesn't have individual operator bypass functionality as a fundamental part of the feature set??!!!

What is going on PSP?? This is just basic.

Overall, I feel you guys (PSP) are starting to lose it....

Starting? It's soon been 6 months. And almost no signs of life.

It is also actually possible to 'bypass' an operator using the routing matrix. This is a bit tedious though. It would be kind of cool to be able to select 'Bypass' in the operator selection menu and have that automatically make the changes to the matrix.

I am not giving up on PSP yet.