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

[Ingonator]

Hi everyone,

as i am about reading several complaints and/or bugs about Waldorf plugins like e.g. Largo, PPG Wave 3.V and Waldorf Edition here since a while i thought it would be a good idea to collect those bugs somehow so i could compare it with the current bugs database of Waldorf and either enter new bugs there or mention known bugs in the Beta forum and/or directly at the developers again.

You could also add feature requests.

It would be nice if you could present a bug report like in the bug tracker of Waldorf which consists of:

- Plugin name: e.g. Largo or PPG Wave 3.V

- Task type: e.g. bug report or feature request

- Operating System: e.g. Windows 7 64-bit or OS-X 10.5

- Severity: e.g. Low, Medium, High

- Plugin version: e.g. v1.5.1

- Summary/headline of the bug description :

e.g. "High memory usage of the Largo plugin v1.5.1" (an entry i made at the 10th of January)

- Details:

detailed description of the problem/bug/feature request

example (for the summary in the example above):
"This is what i found in Windows 7 32-bit (could not select from the tab at the left).
Host used is Ableton Live 8.2.2.

When adding Largo v1.5.1 to a fresh project in Ableton Live 8.2.2 the memory usage jumps to additional 320 MB. With another instance additional 220 MB are used
and another 230-250 MB with a third instance. This problem is mostly when the GUi is open. If you load a project without the GUI open there is much less problems.
Once the GUI was opened this could not be solved by closing it again.

This problem was also reported for the Mac version at KVR recently but i could not check that myself."

- Attachments: you could add links for e.g. pictures, audio files or videos


You could post this either here at this thread or send it to me as a PM.
I'll then compare it with the existing bugs database and try to either enter new bugs or add additional info to already reported bugs. I'll also try to add informations to the Beta forum and also directly to the developers then.

Of course i could also check all threads here at KVR myself but this would take a bit longer then or it would miss some informations which i would have to ask about by a PM.


Just a small general comment about the sense of this thread:
This is not thought for bashing or flame wars about Waldorf, this is a serious attempt of myself to contribute to the solution of obviously existing problems/bugs.
Of course i could not fix the problems myself, i could only collect reports and enter it to the right places.



Best wishes,
Ingo

[rob_lee]

Hello Ingo,

No place to post bugs mate that's what the private beta forum is for on (FS)
Just saying

Rob

[Ingonator]

Hello Ingo,

No place to post bugs mate that's what the private beta forum is for on (FS)
Just saying

Rob

Hi Rob,

this is for collecting bugs which users here at KVR find or found and by posting it in the way i mentioned it would be easier for me to compare and/or enter it into the Waldorf bug tracker. I could also check all threads at KVr myself but first this takes a lot of time and second it would miss some info like e.g. OS maybe.
I don't see a problem about a dedicated thread for bug reporting here at KVr or what do you think?
Of course i'll try if i could reproduce a specific bug (if it's not already known) before i enter it at FS. I could als oadd information at the Beta forum before adding it to FS.
If it's a known one maybe there will come some additional informations.

I think that Waldorf should really seriously start working on bug fixes as soon as possible as complaints seem to get more now. That memory leak bug in Largo (when opening the GUi or more than one GUI) is a bit annoying i agree.


Ingo

[rob_lee]

Hello Ingo,

No place to post bugs mate that's what the private beta forum is for on (FS)
Just saying

Rob

Hi Rob,

this is for collecting bugs which users here at KVR find or found and by posting it in the way i mentioned it would be easier for me to compare and/or enter it into the Waldorf bug tracker. I could also check all threads at KVr myself but first this takes a lot of time and second it would miss some info like e.g. OS maybe.
I don't see a problem about a dedicated thread for bug reporting here at KVr or what do you think?
Of course i'll try if i could reproduce a specific bug (if it's not already known) before i enter it at FS. I could als oadd information at the Beta forum before adding it to FS.
If it's a known one maybe there will come some additional informations.

I think that Waldorf should really seriously start working on bug fixes as soon as possible as complaints seem to get more now. That memory leak bug in Largo (when opening the GUi or more than one GUI) is a bit annoying i agree.


Ingo

Can of worms springs to mind mate but this is KVR after all.. users of Waldorf synths are better finding and posting here after registering and checking the archives:

http://www.waldorf-forum.com/cgi-bin/ma ... user-forum


cheers

Rob

[Ingonator]

Can of worms springs to mind mate but this is KVR after all.. users of Waldorf synths are better finding and posting here after registering and checking the archives:

http://www.waldorf-forum.com/cgi-bin/ma ... user-forum


cheers

Rob

Possible but it could not be a bad thing to start such a thread at KVR. At least we could say we tried. At the end it doesn't matter at which place this is reported.

Of course it would be a good idea for Waldorf customers to also join the official forum but using an email list is maybe not for everyone.

Anyway Waldorf should seriously consider doing updates/fixes in the near future. I know that some bugs are Mac specific so i could not test those with my own machine.


Ingo

[EvilDragon]

I think that Waldorf's first priority should be fixing bugs on the Blofeld, and only after that handle their plugin software bugs.


Also, as a feature request, Waldorf should just open a real forum, none of this mailing list crap. We're in 21st century goddamit. Mailing lists are unwieldy. Forums are a lot more convenient, easier to follow, etc.

[musikmachine]

Also, as a feature request, Waldorf should just open a real forum, none of this mailing list crap. We're in 21st century goddamit. Mailing lists are unwieldy. Forums are a lot more convenient, easier to follow, etc.

+1! I would like an updated browser for Attack like the PPG/Largo and of course 64bit versions but i don't think we'll ever see them.

[Ingonator]

I think that Waldorf's first priority should be fixing bugs on the Blofeld, and only after that handle their plugin software bugs.


Also, as a feature request, Waldorf should just open a real forum, none of this mailing list crap. We're in 21st century goddamit. Mailing lists are unwieldy. Forums are a lot more convenient, easier to follow, etc.

Comments/reports about Blofeld are also welcome here.

I agree that the mailing list forum is also not really my favorite kind of forum.
Besides managing the eamils important stuff seems to easily get lost in this kind of forum.

An official Waldorf forum here at KVR would be maybe a good idea.


Ingo

[Ingonator]

Just a small general comment about the sense of this thread:
This is not thought for bashing or flame wars about Waldorf, this is a serious attempt of myself to contribute to the solution of obviously existing problems/bugs.
Of course i could not fix the problems myself, i could only collect reports and enter it to the right places.


Ingo

[Igro]

Waldorf mailing list is a joke.

[Igro]

Just a small general comment about the sense of this thread:
This is not thought for bashing or flame wars about Waldorf, this is a serious attempt of myself to contribute to the solution of obviously existing problems/bugs.
Of course i could not fix the problems myself, i could only collect reports and enter it to the right places.


Ingo

So no feature requests here?

[EvilDragon]

Well, I think that Waldorf should really solve that bug on the Blofeld with low update rate of tempo synced LFOs. That one is really hideous. After that, they should get their tempo syncing of the delay effect without glitches working (it's possible to have it without glitches!).

I didn't have the time to try the latest beta OS for Blofeld at my friend's place, but I sincerely hope that when scrolling category search and reaching the end of the filtered list, the list wraps from the start when you pass the end. This is such a logical behavior it hurts if it's not there!

[PietW.]

Just a small general comment about the sense of this thread:
This is not thought for bashing or flame wars about Waldorf, this is a serious attempt of myself to contribute to the solution of obviously existing problems/bugs.
Of course i could not fix the problems myself, i could only collect reports and enter it to the right places.


Ingo

So no feature requests here?

What for? Feature requests have been around for years. Nothing is happening.

[Ingonator]

Just a small general comment about the sense of this thread:
This is not thought for bashing or flame wars about Waldorf, this is a serious attempt of myself to contribute to the solution of obviously existing problems/bugs.
Of course i could not fix the problems myself, i could only collect reports and enter it to the right places.


Ingo

So no feature requests here?

Hi,

sure you could do feature requests. It's mentioned around 3 times in the OP of this thread (and in the title as "FRs").
Feature requests are one task type of the Waldorf bug tracker.


Ingo

[Ingonator]

Just a small general comment about the sense of this thread:
This is not thought for bashing or flame wars about Waldorf, this is a serious attempt of myself to contribute to the solution of obviously existing problems/bugs.
Of course i could not fix the problems myself, i could only collect reports and enter it to the right places.


Ingo

So no feature requests here?

What for? Feature requests have been around for years. Nothing is happening.

As already mentioned this thread is thought as a starting point for improvements. Of course the final solution could only be done by the developers of Waldorf.

A proper bug report with all informations listed in the OP is a first step to this.

Like mentioned i know that some problems are known but first maybe there are unknown or not so well known bugs or second additions to known bugs or feature requests.



Ingo