Analog Lab bugs summary

[voxx_man]

I can confirm that the pads only play chords in standalone mode too. When used as a plugin they just play single notes.

I also still have an issue with one of my ALab plugin sounds never being remembered, the other 8 ALab plugins sounds I am using are fine, but I have to constantly reselect the correct patch when opening my project on this one particular plugin (weird but not a show stopper I guess).

Parameter and value knobs don't scroll when using ALab as a plugin. They work fine when in standalone mode.

[SoundGoddess]

I can confirm that the pads only play chords in standalone mode too. When used as a plugin they just play single notes.

Try explicitly setting the port dropdown to "10", for some reason the VST seems hard-coded to listening on port 10 for the pads.

[voxx_man]

Hi Kati Maya,

When you say to set the port dropdown to 10, where are you referring to. I can't find an option for this on the hardware, VST plugin or Arturia midi mapper (which incidentally takes at least 5 attempts of loading to pick up the keylab61, very annoying).

[SoundGoddess]

I'm referring to the drop-down menu that selects the active midi channel. It defaults to "ALL" but I have to explicitly set it to "10" to get the vst to map properly to the pad controls. I realize that midi ports and midi channels aren't the same thing but sometimes I find myself confusing the terminology.

[voxx_man]

Thanks for the super quick response. I will check it out again tomorrow, Ive got fed up with the constant crashing, so have decided to watch something on TV instead (very uncreative I know). I've been using hardware samplers (akai etc) for years, but the band have decided to move on now. I'm lovin all the plugin stuff (it beat taking my juno106 out), and Analog Lab is pretty awesome, but some of the software anomalies are so blooming annoying. I just want it to work

Cheers again

[voxx_man]

I'm referring to the drop-down menu that selects the active midi channel. It defaults to "ALL" but I have to explicitly set it to "10" to get the vst to map properly to the pad controls. I realize that midi ports and midi channels aren't the same thing but sometimes I find myself confusing the terminology.

Hi, I tried that, but all that happens is the nothing on the keyboard responds, including the pads

[SoundGoddess]

I'm referring to the drop-down menu that selects the active midi channel. It defaults to "ALL" but I have to explicitly set it to "10" to get the vst to map properly to the pad controls. I realize that midi ports and midi channels aren't the same thing but sometimes I find myself confusing the terminology.

Hi, I tried that, but all that happens is the nothing on the keyboard responds, including the pads

Are you using a MiniLab or a different keyboard? I only have experience with the MiniLab.

[aMUSEd]

Jeez, just installed the latest update and many of the the bugs are still there. When you open an edit window for a full version plugin it still appears behind the Analog Lab window so you can't get at its controls, and opening a Modular V patch still opens the wrong preset in the full version. They are obviously not paying any attention to the bug reports.

Oh and still no Prophet Hybrid patches.

In NI Kore 2 32 bit now I can't even modify any params with the mouse, the gui is totally unresponsive. Plus I'm getting exit crashes in Kore and Studio One if I close them with Analog Lab loaded.

[murnau]

what a lame company arturia became just like stei... ahh forget it!

[rasmusklump]

Still insane loud distorting patches next to quiet ones. Doing three clicks in the pligin cilled my cubase instance. Didn't have this for years...