Analog Lab bugs summary

[aMUSEd]

You may want to look at what other products have been updated. These probably affect the operation of Analog Lab if they're out of date on your system.

Clicking on the PREF button (of Analog Lab) I see that I need to update the following:

Jupiter-8V 2.5.4 Latest
Oberheim SEM V 1.1.7 (Latest)
Wurltizer V 1.0.6 (Latest)

The good news is that these updates now exist on Arturia's Update Page (see my previous post here if you're interested).

I updated to Oberheim SEM V 1.1.7 the day it came out - that's the problem. It is updated but still says I should update (so won't load)

And with Modular V for many patches if I open the full plugin it is showing a different patchname (eg load 3Filterpad in Analog Lab then click on the full edit window and the patchname showing is Elfbass.ted, even though I'm pretty sure it is 3filterpad that's playing)

[Aloysius]

Well I definitely have everything updated now for the first time. Everything is showing 'ON' and 'DETECTED' in the PREF menu.

I've messed about with it for only a few moments but still think the CPU load is on the heavy side.

Some presets seem to be silent. Could be a loading time related issue.

The first time an Instrument is loaded under 'DATA FILTERS' Analog Lab seems to perform its initial scan for that particular Instrument. So, slow the first time. Much quicker after that.

I'm a bit tired of it now so I'll take a break from it. If you notice anything interesting, do let us know.

[aMUSEd]

Well I definitely have everything updated now for the first time. Everything is showing 'ON' and 'DETECTED' in the PREF menu.

I've messed about with it for only a few moments but still think the CPU load is on the heavy side.

Some presets seem to be silent.

Is that Jupiter presets? I have found that they often go silent as prelude to a crash if you keep trying to play them. I'm going to see if running the SEM updater again after updating A Lab forces it to recognise it.

[aMUSEd]

I'm wondering if they have sneakily updated the SEM installer actually - the date of the update was the 14th June and when I downloaded it then the dmg was just named "latest.dmg". Now it is called "oberheim SEMV 1.17.dmg" - maybe they made some changes but didn't tell anyone or change the version number?

edit crap no - still says SEM 1.1.7 - but with "must be updated" next to it

[Aloysius]

Well I definitely have everything updated now for the first time. Everything is showing 'ON' and 'DETECTED' in the PREF menu.

I've messed about with it for only a few moments but still think the CPU load is on the heavy side.

Some presets seem to be silent.

Is that Jupiter presets? I have found that they often go silent as prelude to a crash if you keep trying to play them. I'm going to see if running the SEM updater again after updating A Lab forces it to recognise it.

I'm not 100% sure. I only noticed the LOADING dialogue that's shown under the Preset Menu (right hand side) when a preset is slow to load. It's possible that I hadn't waited long enough for the 'silent' Presets to Load. It's possible that the Initial Instrument scan had not been completed, and that is why certain Presets were initially slow to Load. See the rest of my last post here for details on that scenario.

[Aloysius]

I'm wondering if they have sneakily updated the SEM installer actually - the date of the update was the 14th June and when I downloaded it then the dmg was just named "latest.dmg". Now it is called "oberheim SEMV 1.17.dmg" - maybe they made some changes but didn't tell anyone or change the version number?

That's possible.

[drewdav]

This thing is annoying as hell. The sounds are great and the idea is awesome but its the most poorly made plugin ive ever come across by far.
Its unusable on my computer.

Bugs:
1. Crashes a fair bit.
2. Sometimes doesnt aurthorize.

Big Bugs:
3. Patches last forever. After hitting a single note, the sound will just hang around almost as if the release time is set to infinity. Makes making a melody impossible. Only way to stop it is change patch (but the next patch usually has the same problem) or delete then re-add Analog Lab. Upon deleting it often causes a CRASH.
This happens on specific patches, but no point mentioning which ones as it happens to just about all of them.

4. Volume levels of sounds are all over the place. Ill hit a note with one sound, lets call it "Sound A", and itll be +6db, then ill change to "Sound B" and that sound will be barely audible hitting around -12db, then i will go back to "Sound A" and it will be barely audible now hitting -12db. It makes making music impossible mainly for the next bug.

5. So ive found a sound, its being weird but im persevering with it. I make a melody with one Analog Lab, i make a bassline with the other. I adjust the levels. Save my Liveset and exit.

- I open up the Liveset. Both Analog Labs change. My melody track sounds completely different to the way i saved it despite the exact same patch being selected. And by completely different i mean chalk and cheese. I have to change the patch then reselect the patch i had -> thats all well and good but if ive made changes to the original patch then im screwed.

- I had nice levels before, now i dont. My bass patch has done that thing where it was hitting 0db -> so i adjusted it to fit in the mix so it was hitting -5db.
But now that ive reopened the set, that sound has decided to become weak, and despite my fader being at -5db, the sound is no longer 'hitting 0db'. its dropped -12db. No point in me readjusting it and saving because upon working on the sound, it often decides that it wants to start redlining again.

So besides the very annoying forever lasting notes which i couldve made a work around by turning that channel off when needed, the thing is still unusable due to the fact that when you open up your saved project, the sounds you saved often sound completely different (like its some other sound completely) or the levels cant decide if they want to be normal, redlining 6db+, or barely audible.

Never had a problem with a VST that wasnt easily fixed (Ive never had a problem in general really with any plugin except those that use elicenser. All plugins that use elicenser are somewhat buggy). Ive tried to trouble shoot this for a couple weeks with Arturia and its still the same.
I dont know how this thing got released.
Its obviously not a system thing as ive read a lot of people having similar issues. My issues seem to be a little worse than the ones on this thread however.
Let me know if anyone is experiencing similar problems. Its VERY CLEAR its Analog Lab itself.
On Ableton 8.4.1, Snow Leopard, Macbook Pro 2011 16gig Ram.

Peace

[aMUSEd]

Still no update or fix for all these bugs!

[Echoes in the Attic]

Still no update or fix for all these bugs!

Don't worry, next year they'll release a new version with a new skin and call it "Analog L" or "Vintage Lab" and it won't fix any bugs but it will introduce lots of new ones. But it'll only cost 20 dollars to cross-grade!

[mikemusicked]

(question was answered at arturia forums)

[rasmusklump]

The problem with the varying volume and clipping patches was already in the very first analog factory. That we have to deal with the same problems in Analog lab shows, that they give a shit and it will never change.
In their survey I wrote that my most remembered thing about Arturia is the fact that they have the worst customersevice I have ever dealt with.

[aMUSEd]

Installed the 1.05 update - finally the SEM is detected and opens in edit mode! So one bug fixed. Bit annoying that they did this after the sale was over, it might have swung me in the direction of buying the suite to see some progress.

On the other hand the Modular still opens with the wrong preset showing in edit mode.

And still no hybrid presets for the VS.

[voxx_man]

I'm getting the exact same issues. I recently purchased a KeyLab61 with packaged Analog Lab software. I'm using with Ableton Live 8. There are a few issues with Analog Labs in standalone, but I'm not too fused about this, as I want to use it as a plugin. However, as a plugin there seems to be a lot of loss in functionality. The value and preset knobs are a waste of time, they only scroll up an down one increment, so I have to use mouse when using as a plugin. This is not my main issue though. The main issue is the sounds and volumes not being remembered after saving a song in Live. I am using Analog Lab as the only plugin on all my individual tracks, apart from a backing rhythm track. Everything is working perfectly and all saves fine. However, when I reopen the Live song, all the volumes of the Analog Lab Vst plugins have changed. I basically have to remix the track every time I open it. It makes Analog Lab as a Vst plugin unusable. I will be returning the KeyLab 61 controller if this isn't sorted soon, which is a shame, because the controller is a nice bit of kit.

[voxx_man]

Hi all,

Arturia support contacted me and advised that the 1.0.5 update would fix my issue. I purchased AL about 2 days before
this release, so assumed I already had the latest download. I guess this was unlucky timing on my part. Anyway, I can confirm that plugin volumes are now being saved in Live 8.

Thanks again for the quick response Arturia

voxx_man

[SoundGoddess]

I bought the minilab which came with analog lab. The standalone works okay but the VST won't map the preset selection knob nor the pad controls for the saved banks/chords. I bought minilab for automation control mapping for FL Studio but I'm very surprised that the VST they shipped with the minilab doesn't even map everything to minilab. Feels like they rushed it a bit.