Waldorf LARGO SLOW GUI Problems, vote please !

VST, AU, AAX, CLAP, etc. Plugin Virtual Instruments Discussion
Post Reply New Topic

Waldorf Largo Slow GUI problems

I have problems ( Windows XP x86 - 32bit )
15
17%
I have problems ( Windows XP x64 - 64bit )
1
1%
I have problems ( Windows Vista x86 - 32bit )
0
No votes
I have problems ( Windows Vista x64 - 64bit )
2
2%
I have problems ( Windows 7 x86 - 32bit )
15
17%
I have problems ( Windows 7 x64 - 64bit )
27
31%
I have NOT problems ( Windows XP x86 - 32bit )
10
11%
I have NOT problems ( Windows XP x64 - 64bit )
0
No votes
I have NOT problems ( Windows Vista x86 - 32bit )
4
5%
I have NOT problems ( Windows Vista x64 - 64bit )
3
3%
I have NOT problems ( Windows 7 x86 - 32bit )
4
5%
I have NOT problems ( Windows 7 x64 - 64bit )
7
8%
 
Total votes: 88

RELATED
PRODUCTS
Largo

Post

Sorry for my english :)

Lot of people has problems with Waldorf Largo GUI. When GUI is opened and If you tweak or If you have automated some parameters GUI is realy slow and it slow down DAW GUI.
I just want to know which version of Windows you use ? and have or NOT problems.

PLEASE post your PC specifications here.




Its based on this topic : http://www.kvraudio.com/forum/viewtopic ... 44#3957144[/b]
Last edited by ekeaze on Fri Jan 29, 2010 6:30 pm, edited 2 times in total.

Post

Also, when you tweaking parameters during the playback, check task manager for CPU loading and you will see it strikes hugely. For example, from 12% to 50-60%.

Dual Core Duo T2300, 1.66Ghz. x86. Mobile Intel 945 Express Chipset Family . RAM 2Gb(DDR2 PC2-5300(DDR2 667)).DAW: Energy XT2.
Last edited by Igro on Tue Feb 09, 2010 5:06 pm, edited 2 times in total.

Post

My problems spec. with Largo :
W7 x64, 8gb RAM, Asus Maximus formula II, Q6700, Nvidia GT220 + Nvidia 8600, RME Fireface 400
CUBASE 5, Ableton , Reaper ...

Post

Bump

Post

Largo is at this moment being tested and worked on regarding this Igro.

Cheers


Rob

Post

rob_lee wrote:Largo is at this moment being tested and worked on regarding this Igro.

Cheers


Rob
Yeah, there are some lucky folk who haven't this issue. :D

Post

So what we have for now: 8 vs 1.
8 persons have problems with GUI.

Post

If their GUI is as slow as their response to a sales inquiry, I feel your pain. It's been a month and I've not heard a word from them (and, yes, I check my junk folder). Hope they solve your problem!

KEv
Missiles Kill Militants / Avionik / Neutronaut
Cubase Pro/Wavelab Pro/SSL UF1, UF8, UC1/Binaural & 7.1
https://missileskillmilitants.bandcamp.com/

Post

Igro wrote:So what we have for now: 8 vs 1.
8 persons have problems with GUI.
Who's the 1? I never voted so i can't see :D I have issues with the Browser but that's about it..
Sometimes i have graphics issues sometimes i don't.
I'll email Wolfram now and see what's happening best i can do.

Rob

Post

Its start to be interesting here :)


Please post yours PC specifications specilaly who vote for NOT problems... may be we will find what is wrong
:hihi:

Post

Hi

Wolfram Franke asked me to post this message i just recieved back from him..
As a Waldof Blofeld and Largo beta tester im not able to discuss hardware/software or the workings of the above mentioned but below you will find a fair answer to the issues you users and i/us beta testers also have.
I'll also post this message on the Waldorf boards as asked.
Please read the email below :)
Hi Rob,

(please forward this text to the KVR forum and maybe to our user-forum, if you like)

It's not a bug so there is no "fix". It's a performance problem obviously depending on some components of the PC in question.

The reason is that I chose a Windows functionality Microsoft developed a couple of years ago and introduced in Windows XP called GDI+. This GDI+ was supposed to replace GDI, which was good since GDI is really outdated and misses a great lot of functionality Largo needs to display its GUI.

Microsoft made the more or less wise decision to perform the GDI+ functions completely in software and ultimatively sending the resulting bitmap to the graphics accelerator. Wise in that that was what Apple always did with their QuickDraw and Quartz 2D and which served them well for more than 20 years.

However, as it looks, Microsoft were (and are) still not able to achieve even a good percentage of the performance Apple was able to get out of their routines. It sometimes feels as if some routines are written in Visual Basic or Java rather than well-optimized C or assembly code that might use features of the CPU to some extent. So, they extended GDI+ to use hardware acceleration in Vista SP2 and Windows 7, which was again wise (if you can compare graphic speeds between XP and Vista or W7 on your various systems, please tell me the results). Apple also switched to hardware acceleration of their drawing stuff starting in 10.4 with Quartz Extreme.

Now, for Windows 7, Microsoft developed a completely new set of functions to achieve faster graphics performance called Direct2D. This new package is also available for Vista but not for Windows XP. And, because it tries to be as performant as possible, its functionality is very different from GDI or GDI+. So, this would mean a major rewrite of the graphic stuff of Largo while still maintaining the GDI+ code to make sure it not only runs on W7 and properly updated Vista installations but also on XP, which is still one of the most popular "DAW operating systems".

So, my choices are:

* Switch back to GDI. Not good for Vista and Windows 7 since GDI is now routed to GDI+ internally and probably has the same performance problems there. Good for Windows XP, though.
* Switch to Direct2D. Lots of work and renders Largo incompatible to Windows XP. Would mean I have to maintain two completely different graphic engines to assure XP compatibility.
* Switch to OpenGL. Very performant for 3D graphics but quite unsuited for 2D graphics. I *could* find my way through it but it would probably be a very inefficient method of rendering a GUI like Largo's.
* Switch to a completely different graphic framework. There are a couple of interesting frameworks out there but since implementing one or the other of them into Largo just to make some benchmarks takes a lot of time, I couldn't start doing so yet. Those graphic frameworks very often also render the graphics purely in software, but it looks like their developers programmed a "bit" more optimized for speed than Microsoft.

All in all, I'm a bit stuck right now. I am aware of the graphic performance problem on some Windows machines but right now I don't have the time to work on a major rewrite of the graphic stuff. I can only tell you that it has the highest priority on my list and I will take care of it in the near future.

The poll is interesting but it would probably be more helpful to know the computer configurations as well, i.e. CPU and GPU type, and RAM. I developped and tested Largo on a MacBook Pro with ATI Radeon X1600. I did notice that graphics is considerably slower with Windows XP (booted natively with BootCamp) than with Mac OS X but no CPU spikes here. It might only happen with NVIDIA graphic accelerators, don't know, though.

But, as I said, I will work it out, but cannot do so right now. I hope you have patience and I apologize for the inconvenience.

If you have helpful comments that could help me making a decision which graphics framework to use, drop me a mail on wolfram/at/franke/dot/net or wmf/at/waldorfmusic/dot/de.

Best wishes,


Wolfram
Thanks

Rob

Post

Hmmm... uffff...

What we can do NOW ? Waiting when they have time for FIX :(
May be it will be better if they will sell it only fro MAC OS not for Windows !

Ok I will try it return back to shop. I absolutly uderstand why other VSTi works and Largo NOT. I think it is fatal error when they program it..

Post

ekeaze wrote:Hmmm... uffff...

What we can do NOW ? Waiting when they have time for FIX :(
May be it will be better if they will sell it only fro MAC OS not for Windows !

Ok I will try it return back to shop. I absolutly uderstand why other VSTi works and Largo NOT. I think it is fatal error when they program it..
Well it works mostly fine on my system and as Wolfram states if you email him your *exact* configuration he will be happy to help.
I asked the question and got an answer so there's nothing more i can do.

Not a fatal error when programming.. it's all stated in the message i recieved about how/why there is an issue with different OS.

Thanks

Rob

Post

I send my specifications yesterday...

Its strange why other plugins works on all diferent OS normaly...

Post

ekeaze wrote:I send my specifications yesterday...

Its strange why other plugins works on all diferent OS normaly...
Hi

Did you send it direct to Wolfram? His email is above at the end of that message.
Also did you sign up to here:
http://www.waldorf-forum.com/cgi-bin/ma ... user-forum

You will probably get more reply's about Largo or Waldorf gear there..

Cheers

Rob

Post Reply

Return to “Instruments”