Korg Legacy 64 bit is here!

[SixStringGeek]

And it's a Free update!

http://www.korguser.net

Oh YEAH! I do love da Korgses.

[MIDI Life Crisis]

What's interesting is that they are selling the M1, WS, and the useless MX thing separately now. I bought all three together for about $125, which is about the same thing price wise. I probably wouldn't have gotten the MXE or the M1 but the VI version of the M1 is so superior to the hardware version I'm really glad I have that. It's gotten some good use.

I didn't miss the WS as no projects called for it and I could bypass it with a different 64 bit plug. So now there's really no 32 bit plug I haven't updated...

...excuse me...? What's that?

I'm being told that MOTU still has to update the MX4... never mind.

[Prime Mover]

All the plug ins are working great here except "Legacy cell", it crashed on validation. It even crash my VEPro and my Jbridge.

The rest of the plug ins are working great at 64bit.

I'm using Mountain Lion with DO8.01.

That's concerning, I use Legacy Cell more than anything else.

[David Polich]

Happy to report that KLC (including Legacy Cell) is working fine in DP 7.24, 10.6.8, and in DP 8.01, 32-bit and 64-bit, on 10.6.8.

Boo-yah! Now I just need Sound Toys and Slate to go 64-bit, and all will
be well.

[delcosmos]

All the plug ins are working great here except "Legacy cell", it crashed on validation. It even crash my VEPro and my Jbridge.

The rest of the plug ins are working great at 64bit.

I'm using Mountain Lion with DO8.01.

That's concerning, I use Legacy Cell more than anything else.

I know! Same thing here, thats my favorite plug in

I'm using 10.8.2 and it fails in every plug in validation, I can't even open it as a Stand Alone Synth.

Weird thing is that all the other plug ins work perfectly.

I think it has something to do with Mountain Lion, I don't know.

[Prime Mover]

Anyone experiencing this?

I'm about to go on tour, so I'm not touching it with a 10 foot pole. My current version has a bad error though, it often doesn't load when starting up. Sometimes choosing a new patch will cause it to load, but sometimes I have to unload and reload the whole plugin. In Jambalaya, I often have to do this while on stage, and just make another band member talk for 10 seconds while I do it! Scary! Part of the reason I was so eager to upgrade was to see whether this fixed the problem, but if Legacy Cell isn't working on ML, then I'll live with the weirdness for a time, rather than risk loosing LC entirely. One of my main keyboard leads comes out of LC!

[Music4dw]

I had M1 -LE and received an upgrade offer for the suite for $99 so when I heard here it was 64bit I went ahead and made the purchase. I didn't have much time last night but I did install, authorize and launch each one as a plugin and most standalone (since they launched in the auth process).

I'm running ML 10.8.2 and had no problems with LC running as a plugin in Logic. I went through a lot of presets and had no issues. I'll try using it some more tonight in DP 8.01, and MainStage and see if I have any issues.

[Armageddon]

Anyone experiencing this?

I'm about to go on tour, so I'm not touching it with a 10 foot pole. My current version has a bad error though, it often doesn't load when starting up. Sometimes choosing a new patch will cause it to load, but sometimes I have to unload and reload the whole plugin. In Jambalaya, I often have to do this while on stage, and just make another band member talk for 10 seconds while I do it! Scary! Part of the reason I was so eager to upgrade was to see whether this fixed the problem, but if Legacy Cell isn't working on ML, then I'll live with the weirdness for a time, rather than risk loosing LC entirely. One of my main keyboard leads comes out of LC!

It used to happen (and may well still be capable of happening) to the standalone versions whenever I switched sample rates on my Konnekt 24D. It would default to 176 kHz, no controller and no output, and when I'd go in to set anything up, it would immediately crash. It didn't happen in the plug versions. I think I wound up Trashing Prefs, forcing the standalone to reset, and then, I could set things up again. It seems to me that the previous update to this one actually fixed the problem. Unfortunately, I don't have a 64-bit machine, so I'm not sure it would do any good for me to d/l this new update (but I'll probably do it, anyway).

What's interesting is that they are selling the M1, WS, and the useless MX thing separately now. I bought all three together for about $125, which is about the same thing price wise. I probably wouldn't have gotten the MXE or the M1 but the VI version of the M1 is so superior to the hardware version I'm really glad I have that. It's gotten some good use.

I didn't miss the WS as no projects called for it and I could bypass it with a different 64 bit plug. So now there's really no 32 bit plug I haven't updated...

I once scored a movie completely on a hardware M1 (circa 1992, rented for two weeks from a music store for the same amount of $125 I would later spend to get the VIs!), so the Digital Legacy Collection was pretty much the first bunch of soft synths I purchased. The software M1 is definitely miles above the hardware version, plus, you got all the sounds Korg made for it and finding third-party cards that users have converted for the plug is pretty easy. However, having never used WAVESTATION, I was completely blown away by the VI's sound quality. I've used it on a lot of music, whereas the soft M1 usually gathers dust, unless I feel nostalgic and bring in some of its signature sounds for something. I have so many bread-and-butter workstation VIs, not to mention specialty sounds, that I'm hard-pressed to try and use it as a workstation (though, if you'd told that to me back in 1992, my head would have exploded!), though, one of these days, I think I want to play around and see if I can score another movie using nothing but an M1 (or eight of them, there goes my 1992 head again!). I wish they'd actually been able to implement some of that stuff back on the original board, like having insert/master effects in Multi mode (instead of biting the bullet and picking "Hall" as your one of two main master effects or something), or not sweating having 16 or 32 notes of polyphony for the eight instruments you had loaded up for one song.

I like using the MDE-X as a keyboard 'verb send, gives you a nice, digital-y old-school reverb sound.

[wheever]

Well, I upgraded my KLC WS, then opened a tune that used WS, and DP8 said WS was missing. (In the missing VI dialog box.) After the tune loaded, I checked and, yes, there was the WS in the VI list, but for some reason DP is not making the connection that VI versions are the same instrument. I've never seen this happen before.

After messing around and trying to figure it out, I finally re-installed the older version.

I have no idea what that was all about. Has anyone else had this happen with a VI?

[mhschmieder]

I guess we're all having different issues.

Wavestation crashed DP at validation startup, so I had to quarrantine it. All others passed.

[MIDI Life Crisis]

Do you have the old plug installed? That happened to me and when I killed the old one and reinstalled the new WS passed.

[mhschmieder]

Nope; I deleted all the old ones first. But you know, there was some historical confusion because that one was originally included with the first KLC, before they split if off to the Analog and Digital Editions. So it's possible I might have a slightly differently named version of Wavestation from the original KLC installation.

[mhschmieder]

My Wavestation problem went away after I first launched it in standalone mode and fixed the default sample rate from 192 kHz to 48 khz. I did the same with the other standalone copies as well. Not sure why it defaults to that, and also why it's only available in 32-bit mode.

At any rate, after launching in standalone mode, I was able to load and validate the plug-in in DP. I seem to recall having a similar issue after an earlier update.

It remains a mystery, however, why Wavestation takes minutes to launch, whereas all the others (including Legacy Cell) launch instantly.

[Prime Mover]

Well, I upgraded my KLC WS, then opened a tune that used WS, and DP8 said WS was missing. (In the missing VI dialog box.) After the tune loaded, I checked and, yes, there was the WS in the VI list, but for some reason DP is not making the connection that VI versions are the same instrument. I've never seen this happen before.

After messing around and trying to figure it out, I finally re-installed the older version.

I have no idea what that was all about. Has anyone else had this happen with a VI?

Well, I had ALL SORTS of issues when going to jBridgeX, DP8 didn't make any connection between the original 32bit VIs and the jBridged ones... I had to go through all my projects and save all of my custom patches (a good idea, anyway). You might have to do the same. Thankfully, I'd only had KLC for about a year prior, so I hadn't used it TOO many times... if you've got it on dozens of projects, I feel for you man!

[midilance]

I probably wouldn't have gotten the MXE or the M1 but the VI version of the M1 is so superior to the hardware version I'm really glad I have that. It's gotten some good use.

That's because the Legacy version of the M1 is the M1EX version which contains all the sample rom from both the M1 and T1.

Also, give MXE effects a go. There are actually some useful effects in there.