Bug reports + FRs for Waldorf plugins (e.g. Largo, PPG Wave 3.V, Waldorf Edition, Lector)

[izonin]

The only bug I see with Largo is that presets sound different @ different sample rates. The amount of brilliance of the oscillators varies with the sample rate, and the LFO rates get shifted.

[Ingonator]

The only bug I see with Largo is that presets sound different @ different sample rates. The amount of brilliance of the oscillators varies with the sample rate, and the LFO rates get shifted.

Hi,

Interesting. I never recognized this as i never really tried to compare Largo at different sample rates. AFAIK there is no report of this bug in the database so far. Could you please write a more detailed report like mentioned in the OP of this thread?

This kind of report is one reason why this kind of thread could make sense.


Ingo

[Kriminal]

Waldorf dont have a user forum for this kind of thing?

[Ingonator]

Waldorf dont have a user forum for this kind of thing?

They got a email list here:
http://www.waldorf-forum.com/cgi-bin/ma ... user-forum

http://www.waldorf-forum.com/pipermail/user-forum/

Most of the posts there are about hardware synth like e.g. Blofeld, Q or MicroQ.

Anyway i would like to collect both known bugs and unkown bugs here so i could either enetr new bugs to the database or could do additions to know entries in the database.
The official bug tracker database and the beta forums (beta forums are an email list) could only be accessed by registered beta testers.
Of course anyone could apply to become a beta tester by sending an email to Waldorf support: support@waldorfmusic.de


Ingo

[Igro]

Ok, lets start. FR's for Largo:

1. Linear envelope for Attack. For now it's really hard to get nicely rising pads, exponential attack is not good for such tasks.

2. Make the GUI to look like Lector. It's more serious looking and better for eyes.

3. To have a negative Brilliance value. The brilliance function is cool, I like it, especially for a bright supersaw, but sometimes I need less than normal.

4. Make LFO Amount working more gradually with increase. Now till 30-40% the changes are to subtle and then we have substantial increase.

[Ingonator]

Ok, lets start. FR's for Largo:

1. Linear envelope for Attack. For now it's really hard to get nicely rising pads, exponential attack is not good for such tasks.

2. Make the GUI to look like Lector. It's more serious looking and better for eyes.

3. To have a negative Brilliance value. The brilliance function is cool, I like it, especially for a bright supersaw, but sometimes I need less than normal.

4. Make LFO Amount working more gradually with increase. Now till 30-40% the changes are to subtle and then we have substantial increase.

Thanks for those. I'll collect them in a text file and add to the database ASAP.


Ingo

[EvilDragon]

FR for Largo:


1. Drawable waveform oscillator

2. Import wavetables from Komplexer

[izonin]

- Plugin name: Largo

- Task type: bug report

- Operating System: Windows XP SP3 32-bit

- Severity: Low

- Plugin version: v1.5.1

- Summary/headline of the bug description :

Changes of LFO rate at different sample rates in Largo v1.5.1

- Details:

The LFO rate doubles with doubling the sample rate, making patches with modulation sound different.

____________________________________________

I left out the bit about the brilliance, as it most likely has to do with the way BLIT is implemented, and is part of the oscillator design.

[Ingonator]

Thanks for those reports. I'll collect for a little time and then start to check the database and enter the first requests and/or bugs.


Ingo

[Ruddy]

Largo

Bug report

Mac - 10.6 - 10.7 (at least, did not it on 10.5)

Logic

Crashes the project after a while. Any project with Largo WILL crash after a while. I did try to tell them years ago, but they said it was prob something else as theirs didi not do it. I am running a Mac Pro 8x2.8 with 10 G ram.

Also has issues with slow GUi and XS CPU usage, but I could live with that. I had to remove it from all projects in order to continue work due to the crashes. Pity because I actually really liked it.


+1 on hating the ide of the mailing list btw.

-------------

On a side note, I think making this thread was a good idea, perhaps they will finally start to pay attention.

But pls be careful to not just dis Waldorf here or the thread will become unusable very quickly.

[PietW.]

FR for Largo:


1. Drawable waveform oscillator

2. Import wavetables from Komplexer

The Wavetables from Komplexer have 33 Waves. I think thats a Problem to konvert for Largo but the Idea is great.

[mikefix]

I'm having problems with the LE version of the PPG in Cubase 6.5, OS X 10.6.8.

The PPG is not recalling the presets correctly when songs are reloaded.

ie: If i use the synth in a song, save the song, then later reload the song, the PPG doesn't recall the correct patch and won't make any sound.

I've emailed Waldorf, but have yet to hear anything back.

[mikefix]

I'm having problems with the LE version of the PPG in Cubase 6.5, OS X 10.6.8.

The PPG is not recalling the presets correctly when songs are reloaded.

ie: If i use the synth in a song, save the song, then later reload the song, the PPG doesn't recall the correct patch and won't make any sound.

I've emailed Waldorf, but have yet to hear anything back.

Just heard back from Waldorf. It's a known issue with Cubase that started with v6.

[Chalisque]

This is over ten years ago. Is there a current method to file bug reports. In particular:

Product: Largo 2 (Windows)
Type: Bug Report
Host: Reaper
OS: Windows 11 Pro

Issue:
Create a stereo track.
Put Largo 2 on the track.
Change number of tracks to 8 (for the additional outputs).
Largo2 crashes Reaper.

If you create the stereo track, then set the number of outputs to 8 before adding Largo 2,
things work fine. So this is likely a bug in how Largo 2 handles a change in the number of input
channels.

[chk071]

This is over ten years ago. Is there a current method to file bug reports. In particular:

Product: Largo 2 (Windows)
Type: Bug Report
Host: Reaper
OS: Windows 11 Pro

Issue:
Create a stereo track.
Put Largo 2 on the track.
Change number of tracks to 8 (for the additional outputs).
Largo2 crashes Reaper.

If you create the stereo track, then set the number of outputs to 8 before adding Largo 2,
things work fine. So this is likely a bug in how Largo 2 handles a change in the number of input
channels.

DId you report it here, as I suggested in the Largo 2 thread? https://waldorfmusic.com/support-request/