Notifications
Clear all

Blue Arp defaulting to Program 01 since update


Keys61
(@keys61)
New Member
Joined: 2 days ago
Posts: 4
Topic starter  

Blue Arp has defaulted every preset both Unify library and my User library to Program 01. Even when I re save a new preset,it default back to Program 01 when I reload it.

All this has happened since version 1.61 and 1.62


Quote
Robert.P
(@robert-p)
Estimable Member
Joined: 2 years ago
Posts: 143
 
Posted by: @keys61

Blue Arp has defaulted every preset both Unify library and my User library to Program 01. Even when I re save a new preset,it default back to Program 01 when I reload it.

All this has happened since version 1.61 and 1.62

No problem here. Opened my default preset (BlueArp prog. 1), changed to prog. 2, resaved and reopened - BlueArp recalled prog. 2 as expected (win10).


ReplyQuote
Keys61
(@keys61)
New Member
Joined: 2 days ago
Posts: 4
Topic starter  

@robert-p thanks for your reply,  doesn't solve any of my problems. Blue Arp doesn't seem to remember any settings from any library . All I get is 16th notes on every inserted Arp whichmakes for a lot of noise in the Bpm presets.


ReplyQuote
Robert.P
(@robert-p)
Estimable Member
Joined: 2 years ago
Posts: 143
 

@keys61 

Interesting, please check BlueArp prog.change settings (see attached) and set to ignore to see if it makes a difference. Also, make sure your midi controller / DAW is not sending any ProgChange Messages (You can use the built-in MIDI monitor to  find out).


ReplyQuote
Keys61
(@keys61)
New Member
Joined: 2 days ago
Posts: 4
Topic starter  

@robert-p Thank you happens in both, stand alone and vst. I don't have a midi controller. I'll try your suggestion tomorrow 


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 2788
 
Posted by: @keys61

Blue Arp has defaulted every preset both Unify library and my User library to Program 01. Even when I re save a new preset,it default back to Program 01 when I reload it.

All this has happened since version 1.61 and 1.62

You probably have an earlier version of BlueARP elsewhere on your system, and Unify is now loading that one instead of the one in Unify's own private VST folder. Look up BlueARP in Unify's Known Plug-Ins list; you will probably see more than one entry. Right-click each and choose "show folder containing plug-in". Remove all entries except the one for the one bundled with Unify, which will be in

  • /Applications/PlugInGuru/Unify/VST/BlueARP on Mac
  • C:\Program Files\PlugInGuru\Unify\VST\BlueARP on Windows

Unify v1.6.2 includes some changes which could change which of several identical plug-ins has been registered; that's why this is showing up now. The fact that it didn't happen before was basically luck.

For more about Unify's files and folders, see this manual page.


Robert.P liked
ReplyQuote
Robert.P
(@robert-p)
Estimable Member
Joined: 2 years ago
Posts: 143
 
Posted by: @getdunne

You probably have an earlier version of BlueARP elsewhere on your system, and Unify is now loading that one instead of the one in Unify's own private VST folder

It seems that I have a newer version of BlueARP in my common VST folder. To avoid conflicts, I changed the file extension of BlueARP in Unify's private VST folder to make it unavailable (I do it with each Unify update). This is probably not recommended, but works for me - never had a problem and the BlueARP is accessible to other programs as well.


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 2788
 
Posted by: @robert-p

It seems that I have a newer version of BlueARP in my common VST folder. To avoid conflicts, I changed the file extension of BlueARP in Unify's private VST folder to make it unavailable (I do it with each Unify update). This is probably not recommended, but works for me - never had a problem and the BlueARP is accessible to other programs as well.

Do as you wish, but I advise against it. Someday I hope Unify will provide better support for multiple versions of a given plug-in, but for now this is a limitation. Your work-around will be fine until Oleg decides to make another breaking change to BlueARP's state-data format; then it might fail.

If you are entirely comfortable with editing XML files, I can suggest a better approach; let me know.


Robert.P liked
ReplyQuote
Robert.P
(@robert-p)
Estimable Member
Joined: 2 years ago
Posts: 143
 
Posted by: @getdunne

Your work-around will be fine until Oleg decides to make another breaking change to BlueARP's state-data format; then it might fail.

 

True, I need to be very careful

 

"If you are entirely comfortable with editing XML files, I can suggest a better approach; let me know."

 

Yes, please!


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 2788
 
Posted by: @robert-p

"If you are entirely comfortable with editing XML files, I can suggest a better approach; let me know."

Yes, please!

First, make sure your Known Plug-Ins list entry for your newer version of BlueARP is up-to-date. If it does not indicate the correct version number, remove the entry from the list, locate the actual BlueARP DLL you're using, and drag/drop it into the Known Plug-Ins list. QUIT Unify.

For the next bit, study the Unify manual page about Unify's files and folders. You didn't specify whether you're on Mac or Windows, so I'll try to give a generic answer, and you can refer to that manual page to find the folder locations for your system.

Before editing any XML file, make a safe backup copy. Editing raw XML is notoriously difficult, and you will screw up your Unify installation royally if you get it even slightly wrong.

Locate the plugins.xml file in Unify's private VST folder. Open it in a real text editor, ideally a programmer's editor such as Notepad++ on Windows, and locate the tag for BlueARP; it should be right at the beginning. On my Windows 10 PC, it looks like this:

    <PLUGIN name="BlueARP" descriptiveName="BlueARP" format="VST" category="MidiEffects"
          manufacturer="graywolf2004" version="2.0.3.0" file="\BlueARP\BlueARP.x64.dll"
          uid="37645778" isInstrument="1" fileTime="171d07e0520" infoUpdateTime="17576c59352"
          numInputs="0" numOutputs="2" isShell="0"/>

DELETE this tag (exactly four lines), and save the file.

Now re-start Unify and check the Known Plug-Ins list. There should be only one entry for BlueARP, and if you right-click and choose "show in folder", it should take you to the correct location for your desired version of the plug-in.

Note this plugins.xml file will get overwritten every time you update to a new version of Unify by running the installer, so be prepared to repeat this.

Also note, this is simply some technical advice about a cleaner way to do something I don't recommend in the first place.


Robert.P liked
ReplyQuote
Robert.P
(@robert-p)
Estimable Member
Joined: 2 years ago
Posts: 143
 

Excellent, thank you! I'm on Windows and I use Notepad++ on regular basis. I'll sort it out this evening (I won't forget about backup). Thanks again!


ReplyQuote
Keys61
(@keys61)
New Member
Joined: 2 days ago
Posts: 4
Topic starter  

@getdunne Hey thanks for all your help,  all I did is remove the old version and install the latest version of BlueArp.

Seems to have fixed it for now.

Just one more question, I am getting a lot of cpu spikes when I use Orchestral Tools Sine player in Unify especially when I use the Sustain pedal.

Any suggestions what I can do about that?

Thanks again,  love your work 👍 


ReplyQuote
getdunne
(@getdunne)
Member Admin
Joined: 2 years ago
Posts: 2788
 
Posted by: @keys61

I am getting a lot of cpu spikes when I use Orchestral Tools Sine player in Unify especially when I use the Sustain pedal.

Sorry, I can't advise about Sine Player as I've never used it. If you're seeing CPU spikes when you hit the sustain pedal, this is more than likely an issue in the Sine Player plug-in itself. Unify doesn't do anything itself that would cause this.


ReplyQuote
Share: