Bitwig

Everglide · Post by **Everglide** » Tue Apr 04, 2017 11:28 am

I can't automate parts 2, 3 & 4 of Largo using Bitwig Studio 1.2 or 2.0

It works fine with Studio One, I'm able to automate all parts - please

Everglide · Post by **Everglide** » Sat Apr 08, 2017 5:08 pm

Time to email Waldorf and wait while everyones enjoying Musikmesse

Maybe Bitwig could visit Waldorf booth in Frankfurt.

"Ya, your parts 2, 3, & 4 don't work"

Everglide · Post by **Everglide** » Tue Apr 11, 2017 5:37 am

Dropdown.png

To answer my own thread and clarify fro anyone else who finds a similar issue with a multipart VST instrument.

Largo parts 2, 3 & 4 when changed in GUI while recording don't record automation.

The only way is to add then manually from the automation dropdown;

Everglide · Post by **Everglide** » Tue Apr 11, 2017 5:38 am

Look at the list of options

aMUSEd · Post by **aMUSEd** » Tue Apr 11, 2017 7:31 am

This may be related to the bug reported here:

http://www.kvraudio.com/forum/viewtopic ... 9&t=482036

stuff that can be mapped or automated fine from the plugin gui in most other hosts isn't being picked up by Bitwig - usually it does work from the generic params list (as it does in this case - I can move the cutoff knob for part 3 and record it fine from the generic device view, just not the plugin gui). I did report it on the beta forum so hopefully it will be fixed soon, there seem to be a number of serious issues with automation in Bitwig currently

Everglide · Post by **Everglide** » Tue Apr 11, 2017 9:19 am

Thank you aMUSEd, your response is much appreciated

Ingonator · Post by **Ingonator** » Sat Apr 15, 2017 11:38 am

Everglide wrote:
Dropdown.png
To answer my own thread and clarify fro anyone else who finds a similar issue with a multipart VST instrument.

Largo parts 2, 3 & 4 when changed in GUI while recording don't record automation.

The only way is to add then manually from the automation dropdown;

Hi,

as mentioned in the other Waldorf thread from time to time i work for Waldorf as a "Beta Forum Manager" where i do tests myslf and also receive results from other testers.

I just check with Largo v1.7.0 (latest version with the new serial based protection) at Windows 10 64-bit and in Bitwig Studio 1.3.16 (latest version for Bitwig v1.x).

I recorded moving te Cutoff and Resonance parameters in the GUI and when playing the track again this semed to play properly. If i open te recorded automation in also see the changes for those parameters there.

Maybe you already know it and this might not be related to your issue but In Largo usually one important thing to hear parts beyond the first one is to set "Output" to "Stereo". This parameter is found right of the part selection and switches.
If you use multiple outputs you could also use the "Multi" option.
If you want to hear all parts and not just the currently selected one you might also change "Multi" to "Layer" instead of "Part". This is foudn left of the part selection and switches.
The standard setting with multiple layers seems to be to set "Multi" to "Layer" and "Output" to "Stereo".

aMUSEd · Post by **aMUSEd** » Sat Apr 15, 2017 11:41 am

Ingonator wrote:
Everglide wrote:
Dropdown.png
To answer my own thread and clarify fro anyone else who finds a similar issue with a multipart VST instrument.

Largo parts 2, 3 & 4 when changed in GUI while recording don't record automation.

The only way is to add then manually from the automation dropdown;
Hi,

as mentioned in the other Waldorf thread from time to time i work for Waldorf as a "Beta Forum Manager" where i do tests myslf and also receive results from other testers.

I just check with Largo v1.7.0 (latest version with the new serial based protection) at Windows 10 64-bit and in Bitwig Studio 1.3.16 (latest version for Bitwig v1.x).

I recorded moving te Cutoff and Resonance parameters in the GUI and when playing the track again this semed to play properly.

Maybe you already know it and this might not be related to your issue but In Largo usually one important thing to hear parts beyond the first one is to set "Output" to "Stereo". This parameter is found right of the part selection and switches.
If you use multiple outputs you could also use the "Multi" option.
If you want to hear all parts and not just the currently selected one you might also change "Multi" to "Layer" instead of "Part". This is foudn left of the part selection and switches.
The standard setting with multiple layers seems to be to set "Multi" to "Layer" and "Output" to "Stereo".

I think this is very much a Bitwig 2 issue, as I said it seems to be ignoring some automation data, not just from Largo but many other plugins.

Ingonator · Post by **Ingonator** » Sat Apr 15, 2017 11:43 am

aMUSEd wrote: I think this is very much a Bitwig 2 issue, as I said it seems to be ignoring some automation data, not just from Largo but many other plugins.

Will also check in Bitwig 2.0 demo soon. The latest demo seems to work also if v1 is installed at the same time. Soon i will hopefully also have the full version of v2.0.

Ingonator · Post by **Ingonator** » Sat Apr 15, 2017 11:51 am

Ingonator wrote:
aMUSEd wrote: I think this is very much a Bitwig 2 issue, as I said it seems to be ignoring some automation data, not just from Largo but many other plugins.
Will also check in Bitwig 2.0 demo soon. The latest demo seems to work also if v1 is installed at the same time. Soon i will hopefully also have the full version of v2.0.

In the Bitwig 2.0 demo i get the same results as posted above with v1.3.16.
The changes in Part 2 concerning the Cutoff and Resonance (i changed those in the GUI while playing) seem to be recorded and played back. When selecting the coresponding automation lanes i could also see the changes there.

I am using the latest official Largo version v1.7.0 in Windows 10 64-bit. It is still possible that there are issues related to Bitwig 2.0 in OSX which do not happen in Windows in a similar way.

I might ask Waldorf about this ASAP and if they could confirm it in OSX or not. Next week it is planned that i talk with them again anyway.

aMUSEd · Post by **aMUSEd** » Sat Apr 15, 2017 12:24 pm

Interesting, yes maybe that narrows it down to something more OS specific.

Everglide · Post by **Everglide** » Sat Apr 15, 2017 4:15 pm

Go Ingo, it would be great to have this finally sorted!

There's another bug that I reported regarding the voices and stereo spread.
Not Bitwig related, anyway I'm going to make an animated gif to get the point across.

aMUSEd · Post by **aMUSEd** » Sat Apr 15, 2017 4:27 pm

Everglide wrote:Go Ingo, it would be great to have this finally sorted!

So are you on Mac too?

Everglide · Post by **Everglide** » Sat Apr 15, 2017 4:30 pm

Yes I'm on a Mac also so it seems to be an OSX issue

Ingo, just to be clear with the automation bug mentioned in this thread. While recording and moving the GUI in Largo parts 2-4, Bitwig does not detect the changes via the GUI, nor does Bitwig record or create automations for those parts 2-4.

Bitwig does detect GUI adjustments and record automation for Largo primary part or part #1.

BTW, I'm using Largo 1.6 and I tested 1.5 also but I'm yet to upgrade to 1.7

Ingonator · Post by **Ingonator** » Sat Apr 15, 2017 4:57 pm

Everglide wrote:Yes I'm on a Mac also so it seems to be an OSX issue

Ingo, just to be clear with the automation bug mentioned in this thread. While recording and moving the GUI in Largo parts 2-4, Bitwig does not detect the changes via the GUI, nor does Bitwig record or create automations for those parts 2-4.

Bitwig does detect GUI adjustments and record automation for Largo primary part or part #1.

BTW, I'm using Largo 1.6 and I tested 1.5 also but I'm yet to upgrade to 1.7

Yes as mentioned above i tested with part 2 and it worked here in Windows 10.

If you expect a bug fix you should indeed move to v1.7.0 with the new serial based protection. The eLicenser versins will no longer be updated and the download links for them are also no longer availavble at the official website.

The most simple way to get the new serail is to use your "MYWaldorf" account and in the "eLicenser conversion" page there use the original eLicneser code (not the license at an USB eLicenser...) to add Largo to "My software" in your account (both the serial and downoad link shown there). You will also receive a confirmation e-mail.

If using the feature in the account does not work you would have to contact official support. I could not help in that case.

If you already installed the demo of Largo 1.7.0 you should be able to enter the serial there to "unlock" the plugin. Be sure to press the enter key after adding teh username (= e-mail) and serial and then re-start the plugin to remove the "Demo" label.

Another note: Opposing to what some people mentioned at KVR the new protection does not involve a C/R system. it is indeed just a serial number protection. Independent of that the EULA allows you to use this license at 3 computers at the same time. Of course they could not allow an endless amount of installations of the same license at the same time...

Bitwig

KVR Audio

Largo Automation