rob papen - predator 3

[Weasel-Boy]

I mentioned in an earlier post that Rob has implemented both global and local modulation assignments in Pred3’s UI.

Global assignments are created through the Modulations window, where every possible parameter modulation assignment available can be made, while local assignments, made through the ENV/LFO/AF window, only appear within the individual ENV/LFO/AF modulator interfaces. When these assignments are made, they are not duplicated in the Modulations list.

Rob tells me he did it this way to keep from confusing the user.

However, it is possible to assign a modulation from the ENV/LFO/AF interface and enter the same exact assignment in the Modulation list…so the two exist simultaneously. What I’ve been able to tell is that when you do this, the two assignments are not cumulative as far as values are concerned. But the assignments are now existing in two places. Frankly, I don’t find this confusing.

It’s my contention that any modulation assignment made locally (via the ENV/LFO/AF interface) should automatically show up in the Modulation window, so the user has an easy to see “one stop shopping” modulation list in the logical place one might expect to see all assigned modulations.

As it stands now, you can interrogate any parameter by right clicking on it to see the source of the modulation assignment…and from there, you’d pick the appropriate interface to make an adjustment.

Here’s the thing though… I have a few presets that clearly show that the main Oscillator individual volume controls are being modulated, but no modulation source assignment can be identified either through the ENV/LFO/AF and Modulation interfaces or by right click interrogation.

Has anyone encountered this and have a solution, or is this a bug?

[codec_spurt]

khg

[EnGee]

Here’s the thing though… I have a few presets that clearly show that the main Oscillator individual volume controls are being modulated, but no modulation source assignment can be identified either through the ENV/LFO/AF and Modulation interfaces or by right click interrogation.

Has anyone encountered this and have a solution, or is this a bug?

Which presets are those? So, we can check them

[Weasel-Boy]

EnGee wrote:

Which presets are those? So, we can check them

Try this one:

Comp 1.fxp.zip

"we"?

[fmr]

Then report it to Rob Papen. It won't get addressed until the developer knows there are complaints.

I don't know what the problem is since all of Rob's stuff installs perfectly here on two different systems.

I don't know if you are addressing to me, but to make it clear, THERE IS NO PROBLEM with Rob Papen installers. The problem is generic, and resides on the fact that there isn't a consistent behavior in the installers, Some show the directory where things will be installed, some don't. Some create sub-folders (it's the case of Rob Papen's) some don't.

Heck, some (like for example the Roland installers) don't even prompt you to choose a directory, and install anywhere they want, and we have to manually pick the installed plug-ins and copy them to the proper folder afterwards.

[EnGee]

EnGee wrote:

Which presets are those? So, we can check them

Try this one:
Comp 1.fxp.zip

"we"?

Yes "we" the users here! What is strange about it?

Anyway, "I" think it is an animation bug! I couldn't hear the volume being changed by invisible modulator.

Oh I also noticed the VST3 version has empty space when enlarging it in my scaled Windows! I'll tell him directly in the video streaming next Friday as I already reported it to the support (Jon).

[Caine123]

So i just installed also Quad and used Raw again , latest versions now, if they are active, wo not gui hidden in fl20 it gets laggy. Can someone check maybe too? I had this with hive in the past and updated it and it was again ok then

[Teksonik]

Then report it to Rob Papen. It won't get addressed until the developer knows there are complaints.

I don't know what the problem is since all of Rob's stuff installs perfectly here on two different systems.

I don't know if you are addressing to me, but to make it clear, THERE IS NO PROBLEM with Rob Papen installers.

Yes I was addressing you and since my comment was right below yours I didn't feel the need to add a quote. I read your post to say that you have a problem with Rob's installer particularly. I was just saying if you did have a problem with Rob's installers to let him know. Rob and Jon are really nice guys and easy to work with they just apparently don't monitor KVR and again I can't really fault developers that don't.

The problem is generic, and resides on the fact that there isn't a consistent behavior in the installers, Some show the directory where things will be installed, some don't. Some create sub-folders (it's the case of Rob Papen's) some don't.

Heck, some (like for example the Roland installers) don't even prompt you to choose a directory, and install anywhere they want, and we have to manually pick the installed plug-ins and copy them to the proper folder afterwards.

Ok I can agree it would be nice to have some standard with all installers but I doubt that will ever happen. Some spew content all over your hard drive in multiple locations (I'm looking at you Melda).

Some use the Program Data folders, some the Documents folder, some App Data Local or Roaming and so on.

An installer that doesn't allow you to pick your custom VST location is particularly egregious. Ideally installers should look for the Registry key for your VST location and read from there but many do not. (Obviously I'm only referring to Windows. I have no idea how it works on a Mac)

That's why I just manually choose my VST folder location if the installer doesn't pick it up and let installers do what they want then organize my plugins from within my DAW's plugin managers.

I think trying to do your organization from within the plugin folder itself would be far more work and problematic but to each their own.

[Teksonik]

EnGee wrote:

Which presets are those? So, we can check them

Try this one:
Comp 1.fxp.zip
"we"?

What is it we're listening to with this patch ? I think there is a perceived volume modulation due to morphing between the wavs on both Osc1 and 2.

Is that what you're talking about ?

[Teksonik]

So i just installed also Quad and used Raw again , latest versions now, if they are active, wo not gui hidden in fl20 it gets laggy. Can someone check maybe too? I had this with hive in the past and updated it and it was again ok then

I have the Quad demo. I'm not sure I understand "wo not gui hidden". Do you mean the gui is open and not hidden?

What parts are laggy for you ? The XY balls are a little laggy here. Knobs and sliders not too bad. It definitely doesn't feel perfectly smooth in FL Studio but I don't think which DAW will matter much.

This system has onboard graphics so lag issues should be worse on it. On my studio system the lag in Predator 3 is much less due to the dedicated graphics card.

Anyway in Rob's latest video he says there will be a new version next week and it will have a 120% gui for those of us on 1920x1080 (I'm not sure if he meant to say 125% which is what Quad has and it's perfect).

It will also have the ability to tun off the wave display altogether and some other optimizations. Some more patches will be added as well.

So let's see how that version performs and we'll take it from there...

[SLiC]

I tried the demo. GUI is very laggy for me (Win 10, i7 GTX980) tried in Bitwig and Live.

VST3 version seem to not size properly in Bitwig (maybe a Bitwig bug I guess, the Bitwig plugin window is a lot bigger than the VST)

The sound was pretty good but I am not sure it does anything my existing synths such as ICARUS 2 don't do already, but deleted for now until the laggy GUI issue is resolved, will maybe try it again at some time as I like NKS synths!

[Weasel-Boy]

What is it we're listening to with this patch ? I think there is a perceived volume modulation due to morphing between the wavs on both Osc1 and 2.

Is that what you're talking about ?

Look at the individual volume controls associated with each Oscillator while playing some notes. They show modulation being introduced, but the source of the modulation is completely unidentifiable.

[Teksonik]

Look at the individual volume controls associated with each Oscillator while playing some notes. They show modulation being introduced, but the source of the modulation is completely unidentifiable.

Oh ok I had the dial animations turned off. It's due to the Spread knobs. If you turn them off you'll see the animations stop.

Start with the Default preset and apply Spread and the animations are there. Notice how the value decreases with note on. Maybe it's automatic gain compensation when using Spread. They don't modulate after the initial note on even with the patch at full sustain.

[Weasel-Boy]

Ha! I would have never guessed. Thanks for finding the source. The implementation seems a bit arbitrarily inconsistent though, doesn’t it?

[gaggle of hermits]

though teksonik is right in how spread seems to affect the volume animation, I’ve seen the behaviour on a bunch of presets and the relationship with the spread position seems to be pretty arbitrary, so I think there’s a bug lurking there. You can set spread to zero and it still animates in some presets.