Notifications
Clear all

Unify Macros and Diva


doncagen
(@doncagen)
Active Member
Joined: 6 days ago
Posts: 7
Topic starter  

I am a Unify beginner. My first tasks are to learn to use the Unify Macros to control plug-in synths with my wind-controller without using Midi Learn directly inside the plug-in. I want the control to be from the Unify Macro. I am starting with U-He Diva. I can do this successfully with a Macro knob 1, set-to CC2, mapped to Diva Volume. I see the Diva volume knob moving and I can hear the change. Success. But...

I have had trouble assigning the same Macro 1 to Diva Filter Cutoff Frequency and Resonance. I cannot make the Diva knobs move this way. I can do this inside Diva with Diva Midi learn, but I want to use the Unify Macros instead because of the greater low and high value control, and CC curve control. Thoughts? Also, using the huge Diva parameter list inside Unify is a quite a challenge on it's own. 

 

This topic was modified 6 days ago by doncagen

Quote
Topic Tags
terrybritton
(@terrybritton)
Member
Joined: 3 months ago
Posts: 64
 

I take it you already have downloaded the Unified Diva library from here?

https://forums.pluginguru.com/unify-patchbook/official-all-unified-libraries-w-links/#post-12021

Study on that one perhaps for ideas if you haven't already. Yes, there are a million parameters exposed by Diva to Unify!!!!

Don't forget that you can copy and paste knob settings and even entire knob banks, and save them as knob presets as well if you find some pre-existing ones that spark your fancy.

Terry

This post was modified 6 days ago by terrybritton

ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 3098
 

@doncagen

If you link a Unify knob to a Diva parameter, and you don't see the Diva knob moving when you move the Unify knob, there are three possible causes:

  1. You might have the parameter connected to MIDI already. Make sure you don't have any MIDI CC assigned directly to one of Diva's parameters (e.g. by MIDI-learn) at the same time as you're trying to control the parameter from a Unify macro. Otherwise the two types of control will "fight" each other.
  2. You might have selected the wrong parameter name. Diva's parameter names can be a bit misleading. I think the parameters you want are called 'VCF1: Frequency' and 'VCF1: Resonance' (the quotation marks are added because the parameter-names contain spaces), but the corresponding knobs on the Diva GUI are labeled "Cutoff" and "Emphasis".
  3. Your response curve might just not have enough range. If you add, say, the Resonance parameter using the default "zero to current value" curve shape (leftmost of the five icons at the top selected; see attached image), you might end up with a very flat response curve that just doesn't cover enough range.

See https://pluginguru.net/unify/manual/doku.php?id=realtime-params for all the details, and feel free to ask more questions here until you get comfortable with this.


RO-mix liked
ReplyQuote
doncagen
(@doncagen)
Active Member
Joined: 6 days ago
Posts: 7
Topic starter  

@terrybritton Thank you for the response. I did find the library link, after posting my question. It is helpful! Still having some challenges.


ReplyQuote
doncagen
(@doncagen)
Active Member
Joined: 6 days ago
Posts: 7
Topic starter  

@getdunne thanks so much. The problem is in the Diva "per instance control." Even though I have no midi learn items in the Midi Table, and nothing chosen at this point in the global Control A/B, CC02 is still showing up in the per instance control and is working in the patch. I don't know how to clear this. 

The parameters I need control over via Unify (in this example) are VCF1 FreqMod Depth and VCF1 Frequency. FreqMod Depth reacts better to CC02 than does VCF Frequency, for some reason I don't yet understand.

(I made some screenshots but when I click on "choose file" in this forum, nothing happens.)


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 3098
 

@doncagen I'm no Diva expert, but:

Click on the two input boxes in "Per Instance Control" and drag down until the box reads "None".

The FreqModDepth parameter is a multiplier applied to whatever is modulating the Frequency parameter, so how it responds may vary according to the setting of FreqModSrc. You may get better results by linking to the Frequency parameter and adjusting the shape of the curve until it responds the way you want.

The "Choose File" button should open a standard file-open dialog for your operating system, to allow you to select one or more files. (If it does not, I have no idea what the cause may be. Javascript settings in your browser, perhaps?) If you want to attach more than one file, or anything other than a single image file, zip the files first, and attach the zip.


ReplyQuote
terrybritton
(@terrybritton)
Member
Joined: 3 months ago
Posts: 64
 
Posted by: @doncagen

(I made some screenshots but when I click on "choose file" in this forum, nothing happens.)

Also, be aware that your filename must not include any space characters. Use underscores or dashes to separate elements.

Terry


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 3098
 

...be aware that your filename must not include any space characters. Use underscores or dashes...

Ah so that's the problem! Thank you.


ReplyQuote
doncagen
(@doncagen)
Active Member
Joined: 6 days ago
Posts: 7
Topic starter  
Posted by: @terrybritton
Posted by: @doncagen

(I made some screenshots but when I click on "choose file" in this forum, nothing happens.)

Also, be aware that your filename must not include any space characters. Use underscores or dashes to separate elements.

Terry

That is good to know. For me, the "Choose File" on Mac Mojave Safari does not open a dialog. I tried some security settings but did not help.  Works on my office Mac with Mojave no problem. So I'll use Firefox for this forum from my studio. 


ReplyQuote
doncagen
(@doncagen)
Active Member
Joined: 6 days ago
Posts: 7
Topic starter  
Posted by: @getdunne

@doncagen I'm no Diva expert, but:

Click on the two input boxes in "Per Instance Control" and drag down until the box reads "None".

The FreqModDepth parameter is a multiplier applied to whatever is modulating the Frequency parameter, so how it responds may vary according to the setting of FreqModSrc. You may get better results by linking to the Frequency parameter and adjusting the shape of the curve until it responds the way you want.

The "Choose File" button should open a standard file-open dialog for your operating system, to allow you to select one or more files. (If it does not, I have no idea what the cause may be. Javascript settings in your browser, perhaps?) If you want to attach more than one file, or anything other than a single image file, zip the files first, and attach the zip.

Wow, moving that per instance control to "none" is not intuitive. I had tried all sorts of clicks, option clicks etc!

The FreqModDepth works better with CC02 for some reason than just the Frequency. With Frequency the response is a little spotty and zippery. Perhaps there is some slew applied to the FreqModDepth inside Diva that smooths this out. 

Question on use of High Resolution Midi for Continuous Control. I use CC34 when possible rather than CC02. My controller (Berglund NuEVI) can send this when selected, and Diva accepts this. When I use it through Unify, the Unify macro graphics jump all over the place and response is uneven. 


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 3098
 
Posted by: @doncagen

Question on use of High Resolution Midi for Continuous Control. I use CC34 when possible rather than CC02. My controller (Berglund NuEVI) can send this when selected, and Diva accepts this. When I use it through Unify, the Unify macro graphics jump all over the place and response is uneven. 

High-resolution MIDI requires a specific sequence of two MIDI CC messages, first the "coarse" 7-bit value (in this case CC#2) and then the corresponding "fine" 7-bit value (in this case CC#34, because 2 + 32 = 34). If your controller is sending such a dual CC message sequence, Unify will see only the CC#34 value, and treat it as a full-range value (which is not what you want).

Make sure that you do not have both CC#2 and CC#34 assigned to anything in Diva, and also that you do not have CC#2 and CC#34 assigned to separate knobs in Unify. Either will result in multiple active control paths which will interfere with each other.

Wow, moving that per instance control to "none" is not intuitive.

I agree. I'd never even tried the per-instance controls in Diva; I just poked around and found this by accident.


ReplyQuote
doncagen
(@doncagen)
Active Member
Joined: 6 days ago
Posts: 7
Topic starter  
Posted by: @getdunne

High-resolution MIDI requires a specific sequence of two MIDI CC messages, first the "coarse" 7-bit value (in this case CC#2) and then the corresponding "fine" 7-bit value (in this case CC#34, because 2 + 32 = 34). If your controller is sending such a dual CC message sequence, Unify will see only the CC#34 value, and treat it as a full-range value (which is not what you want).

Make sure that you do not have both CC#2 and CC#34 assigned to anything in Diva, and also that you do not have CC#2 and CC#34 assigned to separate knobs in Unify. Either will result in multiple active control paths which will interfere with each other.

I'll look into this, thank you!


ReplyQuote
Share: