BlueARP VST Arpeggiator development - let's discuss! (Apple M1 ready, 4K)

[e-musician]

Also pls double-check that you have the updated vst3, it should show version 2.8.7b on the top panel.

Yes, I thought that I had updated the VST3 version, but now I have seen it still says 2.8.7 at the top. Checked again and updated again - same thing. So it seems that the download - although it says 2.8.7b - still contains the old 2.8.7 vst3 file (VST2 is fine).

[graywolf2004]

...
Yes, I thought that I had updated the VST3 version, but now I have seen it still says 2.8.7 at the top. Checked again and updated again - same thing. So it seems that the download - although it says 2.8.7b - still contains the old 2.8.7 vst3 file (VST2 is fine).

Checked it, I'm seeing the right 2.8.7b file in my archive, maybe you still mixed up something, but never mind, this is a minor issue and I think I found something more important with Unify. I updated my Unify to version 2 and checked BlueARP with it - sometimes it works, sometimes goes weird like not sending the output notes sometimes seems that noteOffs come too late and the notes get longer... I didn't yet find a robust pattern to it, only see that it happens more with SampleAccurate=On, and only when I'm creating my own patches, the factory ones work fine with v2.8.7b. Strange, but I'll try to look further next weekend.
PS. Right after writing this message checked this again - and it works. New Unify2 patch - add Guru Sampler with the default sound, add BlueARP as MIDI FX - initial BlueARP program plays fine, but just before that I did the same and it sounded like there's no NoteOffs. If you find any pattern to it. pls let me know. But maybe it is just my system, have no idea yet but will try to debug it more.
PPS. Maybe this happened because I selected BlueARP not from the internal Unify2 VST folder, bit from 3rd party and in the moment I had a broken version, will take some time to debug...

[e-musician]

Got it working now! My bad – I did mix up the versions and forgot to trigger a rescan in Unify.
Sorry for the false alarm and all the confusion, and thanks a bunch for jumping in so quickly to help!

[robert_p]

Change log (...)

Recent updates have resulted in the loss of backward compatibility with Unify because the parameters names have changed (again!) and Unify macros don't recognize them ("CurProgram" changed to "Current Program", "Cur_Chain" changed to "Current chain" etc.). These types of changes prevent Unify developers from updating embedded BlueArp to newer versions and force users to use the old version.
---

Parameters.jpg

[graywolf2004]

Change log (...)

Recent updates have resulted in the loss of backward compatibility with Unify because the parameters names have changed (again!) and Unify macros don't recognize them ("CurProgram" changed to "Current Program", "Cur_Chain" changed to "Current chain" etc.). These types of changes prevent Unify developers from updating embedded BlueArp to newer versions and force users to use the old version.
---
Parameters.jpg

I was absolutely sure Unify, as the other hosts, takes care only about the parameter IDs (which did not change) and the parameter names are only a display name for the user, but thx for mentioning. I wrote Shane (hope he is still the main dev behind Unify) about this issue and hopefully he will fix it in the next Unify2 release.
PS. Just double-checked in FL - and yes, it doesn't care about parameter display name change, as long as ID stays the same, and all the saved automation is picked up correctly.

[mabian]

Change log (...)

Recent updates have resulted in the loss of backward compatibility with Unify because the parameters names have changed (again!) and Unify macros don't recognize them ("CurProgram" changed to "Current Program", "Cur_Chain" changed to "Current chain" etc.). These types of changes prevent Unify developers from updating embedded BlueArp to newer versions and force users to use the old version.
---
Parameters.jpg

I was absolutely sure Unify, as the other hosts, takes care only about the parameter IDs (which did not change) and the parameter names are only a display name for the user, but thx for mentioning, I hope Shane it still the main dev behind Unify, I will write him and ask if he can fix it.

Shane is no longer the main dev of Unify, I think you should contact the info or support instead. Even though Shane should be able himself to give you the proper directions...

- Mario

[robert_p]

Change log (...)

Recent updates have resulted in the loss of backward compatibility with Unify because the parameters names have changed (again!) and Unify macros don't recognize them ("CurProgram" changed to "Current Program", "Cur_Chain" changed to "Current chain" etc.). These types of changes prevent Unify developers from updating embedded BlueArp to newer versions and force users to use the old version.
---
Parameters.jpg

I was absolutely sure Unify, as the other hosts, takes care only about the parameter IDs (which did not change) and the parameter names are only a display name for the user, but thx for mentioning, I hope Shane it still the main dev behind Unify, I will write him and ask if he can fix it.

Shane is no longer the main dev of Unify, I think you should contact the info or support instead. Even though Shane should be able himself to give you the proper directions...

- Mario

That's right - Paul Carter (aka "Wavesequencer") is currently responsible for the development of Unify.

[graywolf2004]

...
That's right - Paul Carter (aka "Wavesequencer") is currently responsible for the development of Unify.

Pls try this quick fix v2.8.7d (make sure this version is shown on the top panel).
https://drive.google.com/file/d/1rVwJK6 ... ciE8vB292Q
What I did: I added the check - if the host is Unify of Unify2, it remaps the parameter names back to where it was in v2.8.1, which is the version that comes with Unify2. Pls check it with your saved projects and let me know if any unrecognized parameters left.
PS. I already wrote to John and Shane, but I think it won't hurt and John will re-direct the message. Anyway, the fix I just did will hopefully solve the issue.
If you are on Mac - let me know, I'll compile it for Mac too.

[robert_p]

...
That's right - Paul Carter (aka "Wavesequencer") is currently responsible for the development of Unify.

Pls try this quick fix v2.8.7d (make sure this version is shown on the top panel).
https://drive.google.com/file/d/1rVwJK6 ... ciE8vB292Q
What I did: I added the check - if the host is Unify of Unify2, it remaps the parameter names back to where it was in v2.8.1, which is the version that comes with Unify2. Pls check it with your saved projects and let me know if any unrecognized parameters left.
PS. I already wrote to John and Shane, but I think it won't hurt and John will re-direct the message. Anyway, the fix I just did will hopefully solve the issue.
If you are on Mac - let me know, I'll compile it for Mac too.

It seems to be more complicated than that: I have some patches saved using BlueARP 2.8.4 that won't work properly with the latest updates (including 2.8.7d), while my very old patches saved using 2.8.1 work fine with 2.8.7d.
---

Parameters.jpg

[robert_p]

(...)

UPDATE: The problematic patch shown above loads correctly in version 2.8.7d when I use standalone Unify (no broken macro assignment). However, the same patch loaded into Unify running in Studio One still shows unrecognized parameters.

[graywolf2004]

This is another half-blind fix: v2.8.7e
https://drive.google.com/file/d/1MaYPNJ ... Yej6f77KQD
I see that when Unify2 is loaded within a host, its reported host name is not 'unify2', but 'juce vst host', hopefully they can fix it in the future. For now I added a mapping 'juce vst host' -> 'unify2' to make my fixes work.

If 2.8.7e loads all your projects OK, pls try to save one of them with a new name and the load it. If it doesn't work, than try this one: v2.8.7f
https://drive.google.com/file/d/1MJVqSb ... e0fGL6nRih

The difference between them: 2.8.7e remaps param names to the older names only when the project was saved with the BlueARP version up to v2.8.6b (bank format 21), 2.8.7f - remaps param names regardless of the version. To clarify this, I need info from Unify2 developer which I don't have yet.

[robert_p]

I see that when Unify2 is loaded within a host, its reported host name is not 'unify2', but 'juce vst host'

Good find, thanks for investigating! Tomorrow I will test versions 2.8.7e and 2.8.7f and let you know the results.

[graywolf2004]

I see that when Unify2 is loaded within a host, its reported host name is not 'unify2', but 'juce vst host'

Good find, thanks for investigating! Tomorrow I will test versions 2.8.7e and 2.8.7f and let you know the results.

Thankfully it is Sunday, right after making my morning coffee I went to check myself, and 2.8.7f is your way to go:
https://drive.google.com/file/d/1MJVqSb ... e0fGL6nRih
(because on loading the plugin, looks like it scans and memorizes the param names and in 2.8.7e they come as 'new versions' from the factory back, because name re-mapper works with additional filter patchVer <= 21 (which means version up to 2.8.6b).
So to make it work I need to remap param names regardless the version.
Tested it in FL like this:
1. Created a dummy project with Unify2 and BlueARP 2.8.1 (factory one with Unify)
2. Added mapping for macro 1 -> Cur_Chain param
3. Checked if it loads OK and macro1 works - it does
4. Replaced BlueARP with 2.8.7f
5. Checked if it loads OK and macro1 works - it does

PS. Shane responded that he is no longer Unify2 main dev but he is still involved a bit and he will help Paul (new dev) to sort this out. No reply from John yet.

[robert_p]

Thankfully it is Sunday, right after making my morning coffee I went to check myself, and 2.8.7f is your way to go (...)

Thank you Oleg! I couldn't test it earlier because the KVR forum was in maintenance mode for a while and I didn't have access to the download links you posted. Paul is going to France and will return in May. He says he'll contact you when he gets back. I just downloaded version 2.8.7f and I'll start playing around with it - thanks again!

[graywolf2004]

There's v2.8.7g on my website
https://omg-instruments.com/wp/?page_id=46
Compared to v2.8.7f is has one more timing-related fix, looks like BlueARP swallows some notes in the guitar mode when randomize start > 0 or when restart on = key.
This is the tutorial on how to use BlueARP guitar mode in Unify2

And this is Unify2 patch to download and try
https://www.omg-instruments.com/bluearp ... _Split.zip
PS. Looks like some timing issues still left, I'm not sure if it is BlueARP bug or something in Unify, will need some more testing. But at least, after the fixes I made I got quite consistent behavior most of the time.