Fixed the Waldorf non-starting issues by installing 2005, 2008 and 2010 Visual C++ runtimes packages from Microsoft.
http://www.microsoft.com/en-us/download/details.aspx?id=5555

And also make sure you get DUNE that Irion linked to above guys. We're spoiled for choice now; Waldorf PPG and DUNE, sweet!

Both PPG and especially DUNE sound great.

Limitations are:

DUNE: No effects section.

Waldorf PPG 2.V LE: 1 MIDI Channel and 8 voices

Peanuts really...

Also note: it appears Dune comes with both a Windows and a Mac version. (And seems to work perfectly on the Reaper/Linux/Wine setup - hooray!)

That's really good, more reasons to put it on.

There are a few banks included in the installation and they all have names, so there's that at least. But what didn't you like about the synth? Tiny GUI? Sound? Editing? In my opinion it compares very favorably to lots of freeware synths sound-wise, and I've seen many worse UI's too.

I've owned the Waldorf collection since it originally came out and cost $99. Love the PPG. Attack isn't bad but totally out gunned now a-days (though it still has a fairly unique sound). They definitely take some work to get the hang of them.

I tried loading those banks in Sonar X1 x64. I'm not getting any error messages, but the bank doesn't really load, and the factory bank stays in effect. I tried the same thing with Reaper, and the banks load properly. More motivation for me to learn Reaper I guess

The rules right now say about one month for construction of track for OSC. I have a proposal to give one additional month for testing. So when VSTi is chosen, first month is for testing, second month for composition. So every month we have one VSTi 'in testing' status, second VSTi we have 'in composition' status.

My reason is, right now I have about 3-4 tracks unfinished for previous OSC (except track for Minimoog where the reason is quite different).

As far as I know, every proposed synth has been previously tested by V'ger and Irion. Maybe we could think about extending the pool of testers (i.e. extending the range of OS and hosts, in order to avoid major issues during the contest), but I still prefer to maintain the current monthly frequency for the contest.

I agree with the above proposal too.

If we expand the testers pool then I would also propose that we set some guidelines and rules for testing as well. It should already be there and V'ger/Irion might be following it, just needs to be published. The reason being, everyone will have their own perspective of testing a plugin and in the process we may leave some parts untested so it will be good if we have some minimum set of testing and then it's up to the testers if they wanna do additional testing.

I always start with the presets when I load a new plugin and to be very honest the sound of this synth didn't impress me at all. I mean there are other free plugins that outshines this. Secondly, I was already pissed off during the installation, with the stuck notes, registration process, etc. so that anger also played a major role too . No prob with GUI or anything else, those are trivial to me. I would take Voyager (even though it's GUI with million buttons staring at me all the time is overwhelming) than PPG any day. I may or may not install it if we select it for the contest, depends on how much time I would have that month. also the mood

Trouble with public testing is that it will reveal what synths are coming and might lead to some songs having been worked on for months while latecomers only getting the one month which is quite unfair.

And even with mass testing it's clear from the competitions that there will always be some issues with some systems/DAWs regardless. I admit that some synths have been above average troublesome, but then sometimes a synth just sound too good or is in a class that it really ought to be put on even if it's going to be frustrating for some. Point is that a synth's stability/compatibility shouldn't always be the main factor in my opinion, but this could be voted on in an upcoming poll of course.

Example is next month's DUNE BE. We already know it causes issues in FL Studio, but would you rather we pass it up for one that works perfectly but not in the same leauge sound-wise? Like with previous competitions, the argument is still the same that it will work fine in other DAWs, so the DAW bugs can't be said to be a deal-breaker in my opinion as some DAWs are free to use and others are very cheap, have working demos etc.

I totally missed this point. Yes, it would be unfair unless we forbid the testers to take part in the contest

So next month it's going to be Dune BE?

It is unfair unless everybody knows exacly what is actually under test, right?
If everybody knows what is tested, the issue is that someone may spend more time for composition whan one month BUT he will miss minimum one deadline instead. Is it still unfair?

Is the period one month for composition so importand (why?) or the issue is to get dead line for one synth every month?

As there will not be a sticky thread for the testing (we are max allowed 2), the topic of testing will have to be inserted in the submissions or voting thread or in this general one which I think will lead to it being missed by many.

But even if it was known by all which synth will come next month, there will undoubtedly be (like it was before) that some will skip the current one and focus 2 full months while others who participate in both will only have 1.

Just find it fairer on all levels that it's 1 month for all without exceptions, although I think many will have guessed now that PPG V2 will be on sooner or later..

Also, I recently put forward a few synths to test and not many did to be honest, and not all DAWs were represented.

@V'ger

Hi mate,

Iv'e just been speaking to Bulent at KV331 Audio about your KVR Osc challenge and i asked about a free copy to give away plus my 4 expansions (400 presets) he went one even better as to donate 1 copy to you guys every month plus all current expansions.
Hope this is ok with you guys
All you have to do after the result of every KVR OSC challenge is contact Bulent here via PM and you'll have your full copy of Synthmaster 2.5 plus all expansions delivered promptly.

PS

All the best for this months challenge guys.

Rob