I am in the process of updating all my patches including creating macros for them. I am creating some ALV collections with varying instruments and getting some inconsistent results when creating macros.
Using SEM V3 as an example, I can create the macros in the open instrument in ALV and these changes are reflected when using the respective knobs on my Keylab Mk2, the macro knob in the SEM and the macro knob in the ALV macro sidebar (although the parameters affected are not detailed). So that is all as I would expect i.e. the macros created in the instrument are recognised by ALV.
However, if I follow the same process in Jup 8v the new macros are not recognised by the physical keyboard knob or the macro knob in ALV but only by the macro knob in the instrument. This looks like a bug in the operation of Jup 8V in ALV to me. There may be other affected instruments.
I am running the latest ALV and all instruments are up to date. I get this problem in standalone and AU in Logic Pro 11.2.1 running on OSX Sequoia 15.5 on a Mac Mini M4.
EDIT: More info. All third party macros in Jup 8V work in ALV. So the problem seems to be confined to my creations. If I create a macro in standalone Jup 8V it is not working as above when the patch is opened in ALV.
EDIT: I deleted preferences for ALV and then Jup 8000V and uninstalled/reinstalled them. Still the same issue. I deleted the db3.db file for the hell of it - no change. Then I looked closer at the macro assignment in ALV and if I clicked “Learn” and then the macro knob in the instrument, it assign it and it works. So I have a fix but still dont understand why I have to do this in Jup 8V but not in SEM V3 for example? Having scrolled thru my Jup 8V patches I see a mixture where the macro in ALV is assigned and functioning and some where it is not and I have to assign it. I have no idea how the difference comes about.
This patch has macro 1 assigned to filter cutoff in Jup 8000V. This macro is not recognised in ALV until I manually “LEARN” it in the ALV macro sidebar.
When you open a preset in Analog Lab, then the Macros uses the Macro settings set in the original instrument.
Perhaps there is something in this settings that make it seem like it does’nt work?
When you delete the parameter in Analog Lab and add it again in Analog Lab, then there is no previous settings from the original instruments.
Can this explain what you experience?
It can be confusing to work with.
May i ask why you will add the Macros in Analog Lab and not in the original full instruments?
Ha! It’s a Jup-8000V preset, not Jup-8V.
Do you have the same issue with the Jup-8V4, or only the 8000V? Or any other V-Collection instrument? (especially new ones like Jup-8000V, for instance Pure LoFi)
Not sure how it’s possible to create a new user patch without any Macro assigned in Analog Lab, but this is indeed what happens when I load your Jup-8000V patch in Analog Lab.
It doesn’t seem to happen when I create my own Jup-8000V patches.
It would be useful to know your procedure when you create new patches.
I have not been through all my other patches to see if any other plug-ins are affected.
I create all Jup 8000V patches from a default within the plugin itself and that is where I create the macros for each patch.
The problem seems to appear when opening them in ALV.
Of all my Jup 8000V patches, some have the problem in ALV and some do not.
As you can see in the attached screenshot, even though Macro 1 is assigned to Filter in the plugin, there is no assignment in the ALV macro slot to the right. If I click on the LEARN button and then the Brightness knob, the assignment is made in the ALV macro sidebar and it works as expected.
In addition. If I open a Jup 8000V patch in ALV for editing and set another Macro up in the the Jup 8000V, that setting is not reflected in the ALV Macro sidebar and hence does not work.
I have no idea why some of my patches have the problem while others are ok as my creation process is consistent.
EDIT: I have now had time to try this in Pure LoFi. I created a Macro1 in a new default patch in standalone - all working. I then opened the patch in ALV and Macro1 was still working as expected using the ALV sidebar and physical knob on my Keylab. I then created Macro 2 in Pure Lofi and while working within Pure Lofi, it was not associated with the macro in the ALV sidebar and hence Keylab. I had to “LEARN” the macro to get it to work.
The Jup-8000 V factory default preset should work. If you have your own Default preset, then perhaps try to create another one, in case that’s corrupt.
If you have saved the preset and reloaded the preset in Analog Lab after creating Macro 2 in PureLofi, then it’s very strange indeed. I’ve just tried to create a test preset using PureLofi’s factory Default preset as start point. It work for me as long i reload the preset in Analog Lab.
I dont use my own custom default presets - just the Factory default.
How can I recreate a new default?
The problem with Pure Lofi is I can create a working macro outside of AL that then works in AL but cannot create an additional working macro in Pure LoFi when opened in AL.
If you are not experiencing the same problem as me when following the same steps then I need t raise a ticket with Arturia.
Seem to work here. I’m on Windows.
Yes try to contact Arturia support. Perhaps i’ve missed something, or perhaps something odd is going on.
Perhaps Sean have been able to reproduce your issue.
I just meant, if you have a preset that you use instead. We unfortunately can’t change the Default preset that we get, when we select New Preset in the main menu.
Hi, I’m trying to figure out why you’re getting this problem.
This is what I’m getting as a Default in Jup-8000, and when I “Save As” as a test preset, when I open it in Analog Lab V, the macros are well assigned.
Maybe try deleting your db.db3 file in /Library/Arturia/Presets or ProgramData/Arturia/Presets to clear the cache? Is this happening in the other VC11 instruments like Synthx?
I was about to reply on the back of @lily.arturia and say it looks like its my setup and not a bug. Now your replication of the issue seems to indicate a bug.
@lily.arturia - can you take this forward as a possible bug or should I log it with Arturia?
On my system (Windows 10), that “Demon Vault” patch opens without any Macro mapped in Analog Lab Pro, standalone.
Additionally, when I load the “Demon Vault” patch in Analog Lab, I can’t map AL’s Macro 1 to Jup-8000V’s Macro 1. But I can map AL’s Macros to any function of the Jup-8000V (say, Macro 1 to Filter Cutoff).
But any patch I create in Jup-8000V from the factory Default patch, adding my own Macros in Jup-8000V, opens in Analog Lab with the correct Macros 1-4 mapped to the Jup-8000V’s Macros 1-4 by default.
