Windows 7 migration

kmmcdonald · Joined: Oct 08, 2005 Posts: 22 Location: USA Audio files: 1

What should I expect when I attempt to migrate to Windows 7 late this year for the following:

1) my NM G2 (USB control)
2) my original Nord Modular (MIDI control)

thanks

Keith

dorremifasol · Posted: Wed Aug 12, 2009 9:21 am Post subject:

The G2 and its editor works wonderfully under Windows 7, 32 or 64 bit. I tried both versions.

kmmcdonald · Joined: Oct 08, 2005 Posts: 22 Location: USA Audio files: 1

Which USB driver did you use? The XP one, or the Vista one?

thanks

Keith

dorremifasol · Posted: Wed Aug 12, 2009 11:16 pm Post subject:

There are no Vista or XS versions, just 32 or 64 bit.

http://www.nordkeyboards.com/main.asp?tm=oldproducts&clpm=Nord_Modular_G2&clnlm=Software_Updates

ark · Posted: Thu Aug 13, 2009 11:40 am Post subject:

Are you not having the problems that other people have reported with 1.62?

dorremifasol · Posted: Fri Aug 14, 2009 6:56 am Post subject:

What kind of problems?

I have not tested the editor extensively in Windows 7, but it seemed to work very well. My main operating system still is XP.

maybe you are referring to occasional disconnections between the G2 and the editor? have those on XP, but are rare.

blue hell · Posted: Fri Aug 14, 2009 7:52 am Post subject:

Some people report patch corruption with the 1.62 software ... I've got no such problems with 1.62 though.

ark · Posted: Fri Aug 14, 2009 1:36 pm Post subject:

What I found was that with 1.62 under Windows XP, if I connected the G2 to the computer and then loaded a bunch of patches in succession (by repeatedly twiddling the knob and pressing the "Load Patch" button), it was only a matter of time before the G2 would stop loading patches.

I never did try it with the G2 not connected to the computer; but I would appreciate if you would try something similar with 1.62 connected to your Windows 7 machine.

ark · Posted: Fri Aug 14, 2009 1:36 pm Post subject:

Oh yeah, one more question: Are you using the 2.12 driver or the 2.16 driver?

dorremifasol · Posted: Fri Aug 14, 2009 1:59 pm Post subject:

The last driver I downloaded (I still have the zip file in my hard drive) was v2.14 64 bit.

Unfortunately I don't have a Windows 7 OS anymore, as it doesn't work. I don't know why but from one day to another it can't be started, and it can't be fixed either (or so I'm told in the the windows safe mode). I can't even install a new Windows 7 version on top of it! the installer hangs when I try. Weird!

So, no more Windows 7 for me, at least until I get a new machine (probably an i5).

ark · Posted: Fri Aug 14, 2009 2:48 pm Post subject:

Are you still running OS 1.62 in your G2? If so, can you try the experiment of loading a few dozen patches in succession to see if it hangs?

dorremifasol · Posted: Fri Aug 14, 2009 4:23 pm Post subject:

Yes, the editor disconnects from the G2 once in a while, and I have to turn the G2 Off and On, or unplug / plug the USB again to make it work. I'm used to it Razz

ark · Posted: Fri Aug 14, 2009 7:07 pm Post subject:

Derek Cook · Posted: Tue Aug 18, 2009 5:04 am Post subject:

blue hell · Posted: Tue Aug 18, 2009 6:23 am Post subject:

ark · Posted: Fri Aug 21, 2009 9:27 am Post subject:

I am running Windows XP and 1.40 in my G2.

When I updated the G2 to 1.62 and installed the driver that came with it, I started getting the following problem: If I loaded a bunch of patches in the G2 (by repeatedly spinning the dial and pushing the "load patch" button), I would eventually get the G2 into a state where it would stop loading patches. At that point I would have to power-cycle it to reestablish communication.

After that, Nord released a new USB driver that they claimed fixed a timing problem with the Stage. I am wondering whether that USB driver will fix the G2 timing problem as well.

So can I ask someone with a G2 running 1.62 to try the following?

1) With the G2 connected to your computer and the editor running, try loading a few dozen patches in succession to see whether it eventually hangs.

2) With the G2 not connected to the computer, try the same thing.

3) If you dare, install the latest USB driver on your machine and repeat the experiment.

I am trying to figure out whether it is worth upgrading to 1.62 again, or whether I should wait until I decide to retire my XP machine (or until Nord fixes the problem, which they might still do).

blue hell · Posted: Fri Aug 21, 2009 9:52 am Post subject:

ark · Posted: Fri Aug 21, 2009 9:58 am Post subject:

blue hell · Posted: Fri Aug 21, 2009 10:17 am Post subject:

It is my perception as well that chance processes are involved - in case this was not clear from what I wrote before.

ark · Posted: Fri Aug 21, 2009 10:22 am Post subject:

purusha · Joined: Mar 13, 2008 Posts: 131 Location: Ilkley

Ark - I got that problem when I used my NL3 as master keyboard and tried to select a patch using the dial (which sends program change for each patch you end up dialling through).

It's almost like there's a MIDI buffer over-run - like it backs up the program change data and only processes the next program change when one's been actioned. Too many backed up and it refuses to take in any more.

The obvious course of action is: don't send it rapid program change messages. In fact, I now don't send it any program change messages. The worry is though, that a lot of cc messages could also have a similar effect.

On the corruption issue: I've so far not had a problem with any of the driver versions which came after 1.62. I wonder if it's down to individual's working methods? I've tended to: configure patches, do all the tweaking on the host PC etc. and then, with no MIDI data being sent to or from the G2, store the patch on the G2 using the G2's panel.

ark · Posted: Fri Sep 04, 2009 6:31 am Post subject:

purusha · Joined: Mar 13, 2008 Posts: 131 Location: Ilkley

...but, the driver didn't enter into the equation when I was sending program changes into the MIDI port. I'm not even sure I had the editor open and the USB cable connected at the time.

Smile

purusha · Joined: Mar 13, 2008 Posts: 131 Location: Ilkley

Actually, I've just double-checked my driver version.

I was on 2.14. I've just updated to 2.16.

Anyone know what the version history (if one exists) says for the difference between the 2 (apart from Ark's info above)?

ark · Posted: Fri Sep 04, 2009 6:56 pm Post subject:

As far as I know, 2.16 was released for the purpose of fixing an intermittent hang on the Stage.

When I used 2.14 with G2 OS 1.62, I would occasionally get hangs when loading a new patch into the G2 while it was connected via USB to my (Windows XP) computer. I reverted to 1.40 and the problem completely vanished.

I am reluctant to install 1.62/2.16 again because there's no upside at the moment--both my computers run XP and 1.62 has no new functionality. Moreover, Nord says that they have reproduced my problem on their end, so there is at least the possibility that they will fix it, and there is also the possibility that if I install a new OS on my G2, something will go wrong and I will be left with a very expensive doorstop. So I'm waiting a decent interval to see if Nord releases a new G2 OS.