49 postsPage 1 of 3
1, 2, 3
Hi

This is probably best explained with a 1 minute video.
(Please note there is no issue with the stand alone version of Analog Lab V).

In summary, a controller looks like it's working visibly but it isn't if I use a dial on my controller. If I use a mouse it's fine. All my dials etc have this issue. Please have a look Thx...

phpBB [video]

Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb.
Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental).
Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths.
User avatar
by reggie1979beatz on Fri Sep 30, 2022 9:27 am
I think it's the same thing we discussed ad nauseum a while back? If so, it's a known bug, Jemusic says it's been fixed in 6, but it still doesn't work here.

Bye......:roll:
User avatar
by PreAl on Fri Sep 30, 2022 9:32 am
Ah bollocks!

Thanks for the response...
BTW I only just bought this plugin myself.

Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb.
Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental).
Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths.
User avatar
by PreAl on Fri Sep 30, 2022 10:20 am
Hmmm this works perfectly fine in Reaktor 6.
As stated standalone version works just fine.

I'm starting to think it's a specific issue with the Analog V plugin (5.5.1. 2692 x64) under Windows (at least). It may work in other DAWs but it may need adjusting for compatibility with Studio One.

I should log a ticket with Arturia tech support first.

Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb.
Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental).
Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths.
User avatar
by reggie1979beatz on Fri Sep 30, 2022 6:17 pm
They couldn't reproduce it. AND they deleted my thread I started asking if others experienced it.

Talk to Jemusic, he's far more plugged in with that. He says it works for him now in 6.

Bye......:roll:
User avatar
by Jemusic on Fri Sep 30, 2022 11:09 pm
It all works great under V6 now. I will make a video on it. I have to install OBS on this particular Win 10 laptop I am running Studio One 6 on. Also a little busy right now too but I will get onto it. It has changed a little in how it works. A window needs to be open though for real time control from controller encoders will take place. It does work and you can record the movements.

Specs i5-2500K 3.5 Ghz-8 Gb RAM-Win 7 64 bit - ATI Radeon HD6900 Series - RME HDSP9632 - Midex 8 Midi interface - Faderport 2/8 - Atom Pad/Atom SQ - HP Laptop Win 10 - Studio 24c interface -iMac 2.5Ghz Core i5 - High Sierra 10.13.6 - Focusrite Clarett 2 Pre & Scarlett 18i20. Studio One V5.5 (Mac and V6.5 Win 10 laptop), Notion 6.8, Ableton Live 11 Suite, LaunchPad Pro
User avatar
by PreAl on Sat Oct 01, 2022 3:27 am
Jemusic wroteA window needs to be open though for real time control from controller encoders will take place. It does work and you can record the movements.


In other words it doesn't work if the plugin is not visible, that's not exactly great but it's an improvement.

I still can't work out why other third party plugins work with Studio one 5, but not this one. This to me points to an issue with the plugin itself. Allegedly.

Yup OBS is the way to go, my video above used that.

Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb.
Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental).
Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths.
User avatar
by JohnBW on Sat Oct 01, 2022 11:14 am
As I recall, this seems to be an issue with "mapped" controllers in S1 v5.

S1 works fine using an Arturia KeyLab controller that has an internal CC map for Analog Lab V. No controller mapping in S1 is required for that to work. I realize that's not very helpful at the moment, but is some additional information.

Good luck!

Studio One Pro v5.5.2, Win10 Pro
User avatar
by PreAl on Sat Oct 01, 2022 11:41 am
JohnBW wroteAs I recall, this seems to be an issue with "mapped" controllers in S1 v5.

S1 works fine using an Arturia KeyLab controller that has an internal CC map for Analog Lab V. No controller mapping in S1 is required for that to work. I realize that's not very helpful at the moment, but is some additional information.

Good luck!


Anybody got a list of default CC codes for a Keylab 49? Their manuals aren't helpful.

A300 keyboard has custom built in maps. Maybe that's the way to go. Thx

Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb.
Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental).
Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths.
User avatar
by JohnBW on Sat Oct 01, 2022 1:57 pm
PreAl wrote
JohnBW wroteAs I recall, this seems to be an issue with "mapped" controllers in S1 v5.

S1 works fine using an Arturia KeyLab controller that has an internal CC map for Analog Lab V. No controller mapping in S1 is required for that to work. I realize that's not very helpful at the moment, but is some additional information.

Good luck!


Anybody got a list of default CC codes for a Keylab 49? Their manuals aren't helpful.

I pulled this from my keyboard using MIDI-OX, then ran the digits through a hex converter (been a long time since I could do it in my head). Then added notes based on this MIDI CC list: https://www.whippedcreamsounds.com/midi-cc-list/

Arturia KeyLab 61 MK II in Analog Lab mode

Note: KeyLab 61 MK II Analog Lab mode sends all control events over MIDI Port #1. DAW mode sends control surface events over MIDI Port #2 (MIDIIN2).

Captured with MIDI-OX (Hex), a mix of defined and general purpose MIDI CC numbers. These are hard coded in this keyboard mode.

Encoders (Hex/ MIDI CC):
1-4A/ 74 Filter Cutoff
2-47/ 71 Filter Resonance
3-4C/ 76 Sound Controller, general purpose
4-4D/ 77 Sound Controller, general purpose
5-5D/ 93 Effect Depth
6-12/ 18 general purpose
7-13/ 19 general purpose
8-10/ 16 general purpose
9-11/ 17 general purpose

Faders (Hex/CC):
1-49/ 73 Amp envelope attack
2-4B/ 75 Sound Controller, general purpose
3-4F/ 79 Sound Controller, general purpose
4-48/ 72 Amp envelope release
5-50/ 80 general purpose
6-51/ 81 general purpose
7-52/ 82 general purpose
8-53/ 83 general purpose
9-55/ 85 undefined

Studio One Pro v5.5.2, Win10 Pro
User avatar
by PreAl on Sat Oct 01, 2022 2:07 pm
Fantastic thank you so much!

Will try this next week....

Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb.
Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental).
Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths.
User avatar
by PreAl on Sun Oct 02, 2022 10:21 am
Hmmmmm....

I've set up a new Arturia map on my A300 keyboard. All those CC numbers as above are pumping right out.

In Studio One I can't seem to find a way to get the CC messages into the Analog Lab V instrument direct, it always goes through my current Studio One A300 mappings under "External devices" which I want to keep for other purposes.

How do I bypass Studio one CC mapping so the A300's CC's just squirt directly into the plugin?

In Analog V-settings->MIDI area I've just got it set to "generic 9 knobs and 9 faders"/Default right now).

I guess I'm expecting the CC's just to work like magic.

Thx.

Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb.
Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental).
Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths.
User avatar
by JohnBW on Sun Oct 02, 2022 12:23 pm
PreAl wroteHmmmmm....

I've set up a new Arturia map on my A300 keyboard. All those CC numbers as above are pumping right out.

In Studio One I can't seem to find a way to get the CC messages into the Analog Lab V instrument direct, it always goes through my current Studio One A300 mappings under "External devices" which I want to keep for other purposes.

How do I bypass Studio one CC mapping so the A300's CC's just squirt directly into the plugin?

In Analog V-settings->MIDI area I've just got it set to "generic 9 knobs and 9 faders"/Default right now).

I guess I'm expecting the CC's just to work like magic.

Thx.

If you run Analog Lab V standalone, do the CC messages from the A300 work correctly when Studio One is eliminated from the setup?

What other choices does AL V present to you as a MIDI controller option? Can you select a KeyLab mkII for example? That's what the MIDI messages I sent earlier were based on.

Studio One Pro v5.5.2, Win10 Pro
User avatar
by PreAl on Mon Oct 03, 2022 12:05 pm
OK I can kinda get it to work.

It will work provided the control isn't already mapped within Studio One device mapper for A300 (which I need up and running).
It won't if the CC number is already mapped in the studio one device mapper for A300.

The workaround is to perhaps assign different MIDI channels (say MIDI channel 2 for Analog Lab), so the A300 mapping within Studio One devices will twice as many dials and faders! - a mess - not much logic to it.

If only I could just switch off studio one device mapping totally for this A300 device.......

Or perhaps I need to create a new external device for the A300, but then it will come up with warning messages - like the midi ports are already assigned - etc...

I feel I've either hit a Studio One limitation or my knowledge is flawed (something I'm not understanding)...

Thx.

Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb.
Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental).
Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths.
User avatar
by JohnBW on Mon Oct 03, 2022 12:24 pm
It really sounds like the Studio One external device mapper is interfering with the MIDI messages that should be going straight to the plugin.

Studio One Pro v5.5.2, Win10 Pro
User avatar
by PreAl on Mon Oct 03, 2022 12:42 pm
JohnBW wroteIt really sounds like the Studio One external device mapper is interfering with the MIDI messages that should be going straight to the plugin.


Exactly right, and I can see that's by design. If only there was a bypassing mapping option...

Another workaround would be to remove in Studio One all the A300 device mapped controls, but I need them for the other plugins that don't have this issue.

Or just set up entirely different CC's for the A300 for plugins that work via mapping (away from Analog Lab).

I feel I'm missing something.

Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb.
Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental).
Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths.
User avatar
by PreAl on Mon Oct 03, 2022 12:53 pm
Looks like I'm covering old ground (see link)...
Doesn't look like any great solutions, but there is a solution if I tear apart my current A300 map.

viewtopic.php?f=151&t=5342

Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb.
Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental).
Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths.
User avatar
by JohnBW on Mon Oct 03, 2022 1:51 pm
PreAl wroteLooks like I'm covering old ground (see link)...
Doesn't look like any great solutions, but there is a solution if I tear apart my current A300 map.

Agree with that conclusion, unfortunately. Out of alternative ideas...

I'm not currently using any S1 control maps, so my Arturia controller messages are going straight through to the AL V plugin on the track.

Press a button on the KeyLab mkII to switch over to DAW mode, and the S1 Mackie Control external device kicks in and picks up all DAW control surface messages that go out over port #2, while the MIDI keys continue to be sent over port #1, so no conflict. In Analog Lab mode all messages use port #1 exclusively.

As I recall, the A300 used a similar 2-port setup with Cakewalk, but the DAW side setup was a bit more convoluted.

Studio One Pro v5.5.2, Win10 Pro
User avatar
by PreAl on Tue Oct 04, 2022 1:57 am
Thanks....

Well I've got it to work for A300 (it's no more than a workaround) and documented it here:
viewtopic.php?p=291277#p291277

Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb.
Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental).
Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths.
User avatar
by PreAl on Thu Oct 06, 2022 2:54 am
Just got a response from Arturia...

Thank you for using Analog Lab V, and sorry for this issue.
I have read your thread and seen your videos, you made your point very clear , thanks for that.

--> So this issue is known on our side and has been logged and your experienced added to the log.
Quality Assurance is aware of that as well as developers.

They are working on this issue to be addressed for the next major update of all current instruments, and of course for Analog Lab V.

Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb.
Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental).
Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths.

49 postsPage 1 of 3
1, 2, 3

Who is online

Users browsing this forum: Demious, kimyoonwoo1 and 74 guests