Notifications
Clear all

Changing patches with MIDI apparently no longer works since UNIFY 10.x.

6 Posts
2 Users
1 Reactions
317 Views
(@meinolf)
Active Member
Joined: 1 year ago
Posts: 5
Topic starter  

Hi Unify team,

I like to use UNIFY in my daw (Ableton) and I like to experiment with multiple patches while composing.

To switch the patches I use the UNIFY function "Changing patches with MIDI" and the Max for Live device <a href=" removed link " target="_blank" rel="noopener">KeySwitch & Expression Map for Ableton Live. This device provides the switching functionality for patches with one mouse click. 

This has worked fine until Unify 1.9.1. Since Unify 1.10.1 it seems that "changing patches with midi" does not work any more.

I tested it by using different Unify versions in the same track:
- Unify 1.9.1 = working, patches are switched
- Unify 1.10.1 removed link not working, patches are not switched

Can you please check this and hopefully fix the problem.

Many thanks,

Meinolf    


   
Quote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4500
 

@meinolf

Please go to Unify's Settings view, scroll down to "MIDI Functions", and make sure "Bank/Program Change" is checked. If not, check it, close all instances of Unify, and then retry.

If patch switching still does not work, please let me know whether you're on Windows or Mac, and whether you're using the VST or VST3 version of the Unify plug-in in Ableton Live.


   
ReplyQuote
(@meinolf)
Active Member
Joined: 1 year ago
Posts: 5
Topic starter  

@getdunne 

Many thanks for the fast reply.

On my system Unify has only one settings file located in C:\Users\xxxx\AppData\Roaming\PlugInGuru.
The settings file contains the following line: <VALUE name="midiProgramChangeEnable" val="1"/>

I assume that this settings file is used by all Unify instances.

For Unify 1.9.1 I use the VST version, for Unify 1.10.2 I use the VST3 version.
I have not installed the Unify 1.10.2 VST version.

I am using Windows 11, current version.

I use a mix of Unify versions in my Ableton tracks:
Ableton keeps former versions of a VST in the Lifeset to avoid compatibiliy problems.
The user has to change the VST/VST3 in the track when necessary or needed (e.g. to use the new plugins in MegaMagicc Guitars V3)

Used Versions:
- Unify 1.9.1 VST in older tracks stored in Ableton Life Sets, Bank/Program Change is working  
- Unify 1.10.2 VST3 in new tracks in the same Life Set, Bank/Program Change is not working

In both versions the MIDI function settings are
- not checked Interpret in Embedded Unify only ...
- activated: CC7 Main Volume
- activated: CC11 Expression
- activated: Bank/Program Change
- activated: Bank/Program error message 

I did not change the settings in Unify 1.10.2 manually after installation. I assume that version 1.10.2 has imported the settins from the settings file.

The Max for Life device in front of Unify generates the standard MIDI bank-select and program-change message based based on a keyswitches and sends the messages to Unify. This causes an immediate change of the selected patch in Unify. 

If I exchange the Unify 1.10.2 VST3 against the Unify 1.9.1 VST the Bank/Program Change is working as expected.

Is there any way to provide some pictures to make the explanation more understandable?  

Best regards,
Meinolf
  

 

 

 

 

 


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4500
 

@meinolf

Thank you for the details. I will check the code. It may be that something has changed so only the Unify stand-alone app is responding to MIDI program change, but the plug-ins are not.


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4500
 

@meinolf

Are you using the VST3 version of Unify v1.10.x in Ableton Live? If so, please try the VST version instead.

VST3 plug-ins don't receive raw MIDI, and hence don't receive MIDI program-change messages.


   
ReplyQuote
(@meinolf)
Active Member
Joined: 1 year ago
Posts: 5
Topic starter  

@getdunne 

Thank you for solving the problem. I have now installed the 1.10.x VST and it works perfectly.

Best regards,

Meinolf


   
getdunne reacted
ReplyQuote
Share: