- #The glue vst offline authorization install
- #The glue vst offline authorization 64 Bit
- #The glue vst offline authorization 32 bit
- #The glue vst offline authorization upgrade
I used to think while I was building my new machine that I could not live without all the 32 bit stuff I had going on my older machine.
#The glue vst offline authorization 64 Bit
I feel you might be better off just running the 64 bit version of V3 on a true full 64 bit machine and leave it at that. I would not use any 32 bit versions either.
#The glue vst offline authorization install
Sounds like maybe the 64 bit install did not know where the M1 plug-in DLL was. The checks/cheques are going out in the mail first thing Monday. That's not such a problem anymore, obviously.Īnyway, thanks to all who replied. I started doing that when v2 was first released and not all plugins had a 64 bit version yet. On a side note, I'll stay with the 64 bit version of S1 V3 to break out of my habit of using 32 bit version on a 64 bit machine. It's also worth noting that this problem existed before I updated M1 to v1.70. I think the blue screen and subsequent windows repair process may be more relevant to solving this than my having added the Korg folder path to the mix-no pun intended. Well, now M1 is working fine on BOTH 64 & 32 bit versions of Studio One and without a hitch. Did the Windows fix (whatever it does, I don't know cause I'm used to Disk Warrior on Mac and various other familiar fixers.)Īnyway, once the computer started up again, I also added the Korg folder to the VST paths, just in case. I started up my computer and got a blue screen (yay). That's why I'm posting here, otherwise I would not have had any concerns. In my original post you'll see that I DID reauthorize M1 and that the problem persisted. You may need to install both the 32 bit and the 64 bit versions of the M1 on your system for them to work in both versions. Just go ahead and re-authorise the M1 on the 64 bit partition. It will bridge to 64 bit in Reaper but not S1. I'm forced to because one piece of software that I REALLY like is still 32 bit. I have found it is better to run the 64 bit version of V3 on a 64 bit OS computer. Not sure why you are running a 32 bit version alongside the 64 bit version. My M1 works perfectly, as it always did, on a 32bit version of Studio One 2.6.5 in my 64bit system. I built a separate 64 bit computer and had to get a new licence code from Korg to make the Wavestation work again. It may have something to do with the 64 bit system you are running. Jemusic wroteI have had a few little issues with my Wavestation plug-in too similar to yours.
#The glue vst offline authorization upgrade
However, I paid my money for the upgrade and expect a functioning DAW. After being banned for a week, I no longer feel welcome here. And yes, I used a version saved in v3 format. How can I work on songs if I can't count on my VSTis to work? What I think of the new GUI is besides the point if I'm struggling to use my old projects. Version 3 is breaking my Korg Legacy Collection M1 Licensing. just to prove it, and sure enough.M1 works fine.
(Didn't I just do that?)Īnyway, I already knew M1 would work in my old DAWs. Do you want to authorize anyway?" HUH? WHAT? Then, I removed the instance of M1 from the old song project and tried loading up a new instance in a track. First message was (paraphrased) "This computer is already authorized. alert advised), reauthorized my computer. Well, I had done that long ago and M1 has always worked perfectly before, until I tried using it in Studio One V3. No crap.Īnyway, when I try to load the VST, I get a message that I need to register my software. 64 bit partition using a 32bit version of Studio One, v3. Today, it is my Korg M1 License authorization code.
It is a struggle to get to like this version when I keep encountering new usage problems.