Automating parameters not in machine view.

[Spud Sabre]

How can I automate a trigger/parameter that doesn't appear in machine view? For example, Jeskola Noise Generator in machine view has the parameters Attack, Sustain, Release, Color, and Volume. But in sequence view there's also an On/Off trigger. How can I assign that trigger to one of the controls on my midi keyboard?

[polac]

You could try to use PeerCtrl or load the Jeskola Noise Generator in PVST, here you can control all buzz parameters, also the pattern-only parameters.

[Spud Sabre]

I can see the trigger in the parameter list when I load the Jeskola Noise Generator in PVST, but I don't have the 'Bind To Midi Controller' option any more. So, how do I accomplish that? Also, for some reason I can't get PeerCtrl to work. I click on 'Assignment Settings' and nothing happens.

[polac]

Peerctrl:

First download v1.5 from here:
http://www.buzzmachines.com/machineinfo.php?id=805

Then copy this one here over:
viewtopic.php?f=2&t=1252#p7994

Lastly you have to register the envelope.ocx from your Buzz folder via cmd.exe(run as admin):
Regsvr32 /s "c:\your buzz folder\envelope.ocx"

PVST:

You have to learn the trigger to a track parameter at first, then you can go to the buzz parameter list and bind the proper "param val" to a midi controller for example.

[Spud Sabre]

Peerctrl:

First download v1.5 from here:
http://www.buzzmachines.com/machineinfo.php?id=805

Then copy this one here over:
viewtopic.php?f=2&t=1252#p7994

I'm a bit confused. Am I supposed to replace the PeerCtrl.dll from the v1.5 with the 'x86 dll only, static MFC' one?

Lastly you have to register the envelope.ocx from your Buzz folder via cmd.exe(run as admin):
Regsvr32 /s "c:\your buzz folder\envelope.ocx"

Should I expect to see anything in cmd.exe after I enter the command?

PVST:

You have to learn the trigger to a track parameter at first, then you can go to the buzz parameter list and bind the proper "param val" to a midi controller for example.

I got this almost figured out, except that whether I adjust the trigger via midi controller or changing the track parameter value, I don't know how to turn it off. Since in the standalone machine the trigger has 1=on & 0=off, I thought that with the noise generator in PVST it would be 0%=off & 100%=on, but any value I enter, even 0 turns the noise on.

Turning the midi controller, all the way up or all the way down turns the noise on. Reversing the midi controller does nothing, and the only way I can come up with to turn the noise off is to use Buzz's Play and Stop buttons.

[polac]

I'm a bit confused. Am I supposed to replace the PeerCtrl.dll from the v1.5 with the 'x86 dll only, static MFC' one?

Yes just replace the peerctrl.dll.

Should I expect to see anything in cmd.exe after I enter the command?

There shouldn't be any output after entering the command.

I got this almost figured out, except that whether I adjust the trigger via midi controller or changing the track parameter value, I don't know how to turn it off. Since in the standalone machine the trigger has 1=on & 0=off, I thought that with the noise generator in PVST it would be 0%=off & 100%=on, but any value I enter, even 0 turns the noise on.

Turning the midi controller, all the way up or all the way down turns the noise on. Reversing the midi controller does nothing, and the only way I can come up with to turn the noise off is to use Buzz's Play and Stop buttons.

Yes also the off triggers as it seems. What you could try is this:

1. open editor
1. learn the trigger to track parameter 0
2. and switch to settings view
3. select track 0
4. there is a bind button, click it bind the parameter to "key toggle"

This way you can trigger the parameter via a midi note.

edit: an easier way to do a similar thing:

1. open editor
2. rightclick the trigger, click assign
3. select all notes or a specific one

[Spud Sabre]

I got the parameter to turn on via midi note, but pressing the note again causes the parameter to re-trigger instead of turning it off.