Notifications
Clear all

[Solved] Program change via text file

10 Posts
4 Users
1 Reactions
1,051 Views
(@padster13)
Eminent Member
Joined: 4 years ago
Posts: 26
Topic starter  

Has anyone had any luck using the midi.txt Program Change system in Unify using Studio One Pro? The only time I can get any response from Unify is when it is instanced in Komplete Kontrol (I tried this just because KK can respond to Program Change msgs as a parameter event). However with this method Unify is then unable to access the location of the midi.txt files, presumably because it’s instanced in KK and it throws up an error with it’s “path not found message”. When Unify is simply instanced on a track in S1 there is no response whatsoever from it. S1’s own midi monitor shows the MSB, LSB and Program change msg being sent by my midi keyboard as I adjust the rotary knobs on my keyboard but Unify’s midi monitor doesn’t show any response (Unify does respond to keyboard notes). I’ve carefully checked my file syntax. I’ve also set “Bank/Program Change” in Unify. I’ve spent ages trying to get this working. What am I not doing? Any thoughts welcome.


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

I just spent over half an hour trying to figure this out, and it seems the main issue is that you must use the VST version of Unify, not the VST3. When using VST plug-ins, a "Program" section appears in the S1 Inspector, and MIDI bank/program change messages are passed through to the plug-in. It seems this is not the case for VST3 plug-ins.

Refer to the manual page https://pluginguru.net/unify/manual/doku.php?id=midi-patch-select  for details about how to set up MIDI program change in Unify. To make sure Unify is even receiving MIDI program change messages, switch OFF "Bank/Program Change" in Settings, put a MIDI Monitor instance on the first layer, and do whatever you have to do to get your controller device to send MIDI bank/program change messages. If you don't see them in the MIDI Monitor, Unify isn't getting them. Once you get that working, switch "Bank/Program Change" on (provided you have set up your bank file(s) correctly), Unify should respond to those messages by changing patches.


   
ReplyQuote
(@padster13)
Eminent Member
Joined: 4 years ago
Posts: 26
Topic starter  

@getdunne  Many thanks for the swift reply Shane. I didn't even realise I had the VST3 version loaded. I've many the change necessary to solve that issue. Unify now shows the prg msg in the midi monitor (and S1) but pops up the txt file not found msg. I have double checked the file is named correct and configure correctly. I've read the manual instructions. I'm not infallible but I've done my best to check. I used the example file too just be sure it isn't me. The Unify path to the midi text is this-  F:\Studio One 3 and KORG and DX7\PlugInGuru\Unify\Unify-MIDI_Bank_Files\MIDI Bank Files. Dont know if this is the issue but Unify runs fine with this setup. I've included a few screen shots via PDF to show the problem. I'll keep at it in case I solve it in the mean time. Thanks once again. 


   
ReplyQuote
(@padster13)
Eminent Member
Joined: 4 years ago
Posts: 26
Topic starter  

Just after replying I realised that the path wasn't correct. I had copied the file path exactly as it was on the web site but this meant that the path was F:\Studio One 3 and KORG and DX7\PlugInGuru\Unify\Unify-MIDI_Bank_Files\MIDI Bank Files but should be F:\Studio One 3 and KORG and DX7\PlugInGuru\Unify\MIDI Bank Files. Phew! So glad to finally sorted this, I hate being beaten! My first experience of midi was a DAW called Midi Orchestrator Plus by Voyetra in 1994 running on an Amiga 500. Quite advanced for the time. I seem to remember having a lot of "fun" with that too😆 


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

@padster13

I'm glad you got this working. The error-prone nature of text-based software interfaces is what drove the change to graphical interfaces, which are great but take 20 to 200 times the programming effort. I'll freely admit this first implementation of MIDI bank files is a cheat to avoid all that extra effort. I hope to add a graphical editor someday...


   
ReplyQuote
(@padster13)
Eminent Member
Joined: 4 years ago
Posts: 26
Topic starter  

This is great for now Shane!


   
ReplyQuote
(@pottz)
Trusted Member
Joined: 4 years ago
Posts: 38
 

Hey Shane,  just logged on with the intention of asking how this was going, and I find it's already available!!!  Awesome.  I'll have a go at setting it up now in my live set-up...thanks for rolling this out.

 


   
ReplyQuote
pjsvis
(@pjsvis)
Estimable Member
Joined: 4 years ago
Posts: 77
 

Hi there, Just a quick note about the MIDI Bank files:

1. If the library/patch name contains a # then the remainder of the name is treated as a a comment and the library/patch name is not recognized

2. This is the case for some lines in BELL, PAD, and WIND

3. EG In BELL.txt "10 Unify Standard Library / BELL - Kalimba #2 Dry" throws Library/patch name error Unable to match...

 

Regards,  

 

Peter


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

@pjsvis

Well spotted, thank you!

This is happening because the code to isolate the file/patch name only works up to the first "#", which is assumed to be the start of an end-of-line comment.

The next release will require two spaces before the # symbol for end-of-line comments.


   
ReplyQuote
pjsvis
(@pjsvis)
Estimable Member
Joined: 4 years ago
Posts: 77
 

@getdunne I should also have mentioned that the change between the built in patches is lightning fast.


   
getdunne reacted
ReplyQuote
Share: