Notifications
Clear all

Gforce SEM - trouble with Macro Knobs and cc assignments with plugin

11 Posts
4 Users
1 Likes
1,458 Views
(@glenjdiamond)
Estimable Member
Joined: 3 years ago
Posts: 106
Topic starter  

Hi,  I have installed the VST3 version of Gforce SEM and installed the unified patches. I don't know for sure if this is a VST3 issue... but I'm getting unresponsive macro knobs.  Sometimes I can get them to work by clicking the nipple and selecting parameter links.  I think it is a "focus" problem... either Unify or SEM loses focus somehow.  On one occasion unify closed itself.  Also,  when I try and use the SEM plugin "cc" button to assign the Mod Wheel (cc1) the SEM plugin annoyingly keeps assigning the VCO1 Saw/Pulse control rather than the Vibrato Amount control that I double click on.   Apart from that, really enjoying SEM and Unify is fantastic!!  The other reason I think it's a focus issue is because when I manually assign using the SEM cc button, I can see that the cc value stays for each unify patch, but the modwheel does nothing until I double click into the SEM plugin then the modwheel works.

Another focus issue I've noticed (just for SEM) is that when I twiddle the knobs on my controller keyboard, Unify shows the values spinning around the macro knob but the SEM software doesn't react.  Whereas if I use my mouse on the same macro knobs the SEM software mostly reacts.


   
Quote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4410
 
Posted by: @glenjdiamond

... I'm getting unresponsive macro knobs.  Sometimes I can get them to work by clicking the nipple and selecting parameter links.  I think it is a "focus" problem... either Unify or SEM loses focus somehow.

...

The other reason I think it's a focus issue is because when I manually assign using the SEM cc button, I can see that the cc value stays for each unify patch, but the modwheel does nothing until I double click into the SEM plugin then the modwheel works.

Can you provide more details? I don't quite understand.

On one occasion unify closed itself.

Did it crash, or did the GUI just close? Please specify which operating system you use, and how you're using Unify, i.e., stand-alone or as a VST/VST3/AU/AAX plug-in in a DAW).

Also,  when I try and use the SEM plugin "cc" button to assign the Mod Wheel (cc1) the SEM plugin annoyingly keeps assigning the VCO1 Saw/Pulse control rather than the Vibrato Amount control that I double click on.

This sounds like both SEM and Unify might both be configured to respond directly to the CC#1 messages. Again, more details please.

Another focus issue I've noticed (just for SEM) is that when I twiddle the knobs on my controller keyboard, Unify shows the values spinning around the macro knob but the SEM software doesn't react.  Whereas if I use my mouse on the same macro knobs the SEM software mostly reacts.

This sounds very strange. The SEM plug-in is very new, and I suspect it may have a few bugs.

It may take a bit of time and patience to disentangle the multiple issues you're reporting here. Would it be possible for you to make short video illustrating what's happening? You won't be able to attach videos here, but you should be able to link to a video elsewhere, e.g. a private video on YouTube, or a file on Dropbox, etc.


   
ReplyQuote
(@glenjdiamond)
Estimable Member
Joined: 3 years ago
Posts: 106
Topic starter  

hi... I tried, but frustratingly none of the video capture programs would capture audio (with standalone unify running), and OBS failed completely to see anything to capture at all!!    Looks like I have a very unique DELL Laptop that OBS for some reason doesn't like the video.  I tried alternative audio routing programs but nothing doing for some reason.

Edition Windows 10 Pro
Version 21H2
Installed on ‎16/‎04/‎2021
OS build 19044.1766
Experience Windows Feature Experience Pack 120.2212.4180.0

1.8.0 for standalone Unify.

I can tell you that the macro knob 8 on cc28 on my controller works fine  -  I think that's because it is linked to the filter within the unify layer.

The other macro knobs 2 to 7, my controller cc22 to cc27 spins the macro knobs in Unify but the SEM VSTi doesn't respond.

If I use my mouse to spin knobs 2-7, the Gforce SEM does respond.

the VSTi cc button issues within Gforce SEM may well be a bug within their VST3.

Gforce does have a VST2 version of SEM, maybe I should try that one to see if it is just a VST3 issue?

 


   
ReplyQuote
(@glenjdiamond)
Estimable Member
Joined: 3 years ago
Posts: 106
Topic starter  

OK, so I've tried the VST2.

The macro knobs work with my controller.  Yey!   So we now know the macro knobs have a VST3 issue  (on my Win10 laptop).

But... to get the ModWheel to work by using the "cc" button in the VST, still has the annoying issue with SEM VST2 and VST3, the extra parameter gets activated, so as well as getting Vibrato Amount, I am also getting VCO1 Saw/Pulse being activated!!

 

 

 

 


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4410
 
Posted by: @glenjdiamond

But... to get the ModWheel to work by using the "cc" button in the VST, still has the annoying issue with SEM VST2 and VST3, the extra parameter gets activated, so as well as getting Vibrato Amount, I am also getting VCO1 Saw/Pulse being activated!!

I'm unable to reproduce this with the SEM VST2 on my Win10 PC. Are you 100% sure you didn't also assign CC#1 to the VCO1 Saw/Pulse knob inside SEM?


   
ReplyQuote
(@glenjdiamond)
Estimable Member
Joined: 3 years ago
Posts: 106
Topic starter  

@getdunne I've had another go... after clearing the cc's in the SEM VST, I am now able to assign CC1 to the Vibrato Amount and it sticks to just that one parameter.   Something that I was unable to achieve with the VST3 earlier on!    

So it looks as though VST2 saves the day!

Any chance the Unified patches can be VST2'ified!!!???


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4410
 
Posted by: @glenjdiamond

Any chance the Unified patches can be VST2'ified!!!???

I'll look into it. Please note I'm preparing for a major move, so it may take a while.


   
glenjdiamond reacted
ReplyQuote
(@thsve)
MR
Joined: 4 years ago
Posts: 341
 

@glenjdiamond 

I can't reproduce the problems you have neither in VST 2 or VST3.

Anyway, I recreated a VST 2.4 version of the library. You can download it here: https://www.dropbox.com/s/l5gsxchkn17nklc/Unified%20-%20GForce%20SEM%20%28VST%29.guru?dl=0.

The library is named "Unified - GForce SEM (VST)".

All patches except a couple of the z-patches are converted to VST2. The patches I haven't done are so complex so I wasn't sure how to set them up 😒.

EDIT:
After uploading the library, I found some irregularities with some of the macros in the VST3 versions: OSC 1 Tune, OSC 2 Tune and OSC 3 Tune all are mapped to VCO 1 Frequency. That "error" is propagated to the converted patches also. I will se how I can correct them in an easy way.

EDIT 2:
Macro mapping mentioned under EDIT above fixed. New library uplodaded, same link as above.. 

Win 10 and 11/Cubase Pro 12/Unify/Wavelab 8/Vienna Pro 7/Spectrasonics all/NI 13 Ultimate/Izotope MPS2/Serum/Cthulhu/Scaler 2.5/MusicLab guitar vsts/BIAB 2022/TouchOSC/Metagrid Pro etc


   
ReplyQuote
(@glenjdiamond)
Estimable Member
Joined: 3 years ago
Posts: 106
Topic starter  

@thsve thanks - it all works beautifully now.  The macro knobs work with my controller keyboard.   But... and I think this is a "Gforce" issue.. I'm still having issues mapping cc01 to the modwheel (keeps selecting some other parameter) so I guess I'll have to wait for an update to their software... or perhaps I may have to replace this laptop for Win11 or Mac at some time in the future!


   
ReplyQuote
(@craigr68)
Member
Joined: 3 years ago
Posts: 210
 

It's cool that we can use polybox to turn mono SEM patches into polyphonic ones.  But it gets a little tedious with the repetitive mouse clicking.

So I made a little autohotkey script called "Make 8 Voice SA.ahk" that will take a single layer Unify patch and automate the mouse clicking to turn it into an 8 layer Polybox patch.  Some of the coordinates and the sleep times may need adjusting.  Coordinates should match for anyone running 1920x1080.  At the end, it also sets the macro knob links provided you have a saved Macro Definitions file saved prior.  With the SEM patches, I just saved Johns Macro knobs.  Macro knobs are assumed to be showing before running script.

I have comments thru out the script showing what stage it's at for troubleshooting.  At line 41 "doubleclick on your personal Macro Definition file"  the coordinates for the particular Macro Definition file would need to be changed.

In order to fire this thing off repeatedly, I created a "Shortcut.ahk" script which makes "Alt-5" execute the script.  Best to load it first so it's setting in the tray.  It can be closed from the tray afterward.  The location of "Make 8 Voice SA.ahk" needs to be edited in the Shortcut script.

This post was modified 2 years ago by craigr68

   
ReplyQuote
(@thsve)
MR
Joined: 4 years ago
Posts: 341
 

@craigr68 

Hi,

A bit of the initial topic, but just a short comment on you script. We can continue discussing scriptinh in another thread or by mail after this if you like.

I have several diffrent scripts for unifiying macros. The problem with the macro handling is that you must add the parameter link from an "empty" macro definition in order to get the corresponding value from the vsti in question. In your script the macro nob will always be set to the value in the Macro Definition file not at the value in the actual SEM patch. This is not specific for SEM, but general. For som libraries I have used a AHK script to actually loop through every macro and set the macro feinitions from scratch. It takes a while if there are several macros involved 😎 .

In the Unified library from John, the macro values doesn't correspond to the values in SEM and isnt't in my VST2 version either at the moment. I am planning to update the unify patchfiles using Python and retrieve the values from the SEM patchfiles directly (xml-files). Just haven't come around to it yet.

Win 10 and 11/Cubase Pro 12/Unify/Wavelab 8/Vienna Pro 7/Spectrasonics all/NI 13 Ultimate/Izotope MPS2/Serum/Cthulhu/Scaler 2.5/MusicLab guitar vsts/BIAB 2022/TouchOSC/Metagrid Pro etc


   
ReplyQuote
Share: