I'm still wrestling with that one BTW ... currently at version 20 ... I can't get it "right" ... maybe I should have stopped at version 8 _________________Jan
(yawning shifts perceived pitch, making things more interesting)

Am I the only one in which this 1.6.2 didn't fix the Editor disconnect issue? Curious, because I also experience this same bug in 1.4 as well--consistently.

To clarify, in 1.6.2, same for me as 1.6.0, same for me as 1.4, I can connect my G2 via USB, open the editor and the hard/soft connection is made and I can build/tweak, etc. If I quit the editor & then restart the editor--I can't get the software to recognize the hardware until I either power-cycle the G2 or disconnect the USB cable and re-connect it. This has been the case ever since I first got the G2 (only about 14 months ago), and so seeing it in 1.6.0 didn't surprise me, and I was more surprised to hear people noticing it for the first time. But the problem is definitely NOT fixed on my system in 1.6.2, so I am now fully curious what is up? anyone else with the same system as me experiencing same/different?

Am I the only one in which this 1.6.2 didn't fix the Editor disconnect issue? Curious, because I also experience this same bug in 1.4 as well--consistently.

To clarify, in 1.6.2, same for me as 1.6.0, same for me as 1.4, I can connect my G2 via USB, open the editor and the hard/soft connection is made and I can build/tweak, etc. If I quit the editor & then restart the editor--I can't get the software to recognize the hardware until I either power-cycle the G2 or disconnect the USB cable and re-connect it. This has been the case ever since I first got the G2 (only about 14 months ago), and so seeing it in 1.6.0 didn't surprise me, and I was more surprised to hear people noticing it for the first time. But the problem is definitely NOT fixed on my system in 1.6.2, so I am now fully curious what is up? anyone else with the same system as me experiencing same/different?

Am I the only one in which this 1.6.2 didn't fix the Editor disconnect issue? Curious, because I also experience this same bug in 1.4 as well--consistently.

To clarify, in 1.6.2, same for me as 1.6.0, same for me as 1.4, I can connect my G2 via USB, open the editor and the hard/soft connection is made and I can build/tweak, etc. If I quit the editor & then restart the editor--I can't get the software to recognize the hardware until I either power-cycle the G2 or disconnect the USB cable and re-connect it. This has been the case ever since I first got the G2 (only about 14 months ago), and so seeing it in 1.6.0 didn't surprise me, and I was more surprised to hear people noticing it for the first time. But the problem is definitely NOT fixed on my system in 1.6.2, so I am now fully curious what is up? anyone else with the same system as me experiencing same/different?

I just tested this and I am NOT having the same problem. Let's re-trace my steps:

1) Turn on G2
2) Start editor software
3) Created a new performance, added some oscillators that are connected to main left output of the out module. Sound is coming out of left speaker.
4) Quit the editor. Sound is still coming out of left speaker.
5) Started the editor software again. Patch loaded up. Connected the oscillators to the main right output of the out module. Sound is now coming out of both speakers.

Is this test sufficient? What does it do on your set-up?

I am using a black macbook (e.g. the 'blackbook') with the latest motherboard for that model ( 2.2 ghz processor and 800 mhz frontside bus, 667 for RAM). This was the last version of the model that they made before the new, all aluminum line of macbooks. My G2 is probably from one of the first runs, it is several years old. I'm thinking the macbook model itself might be at the heart of the issue for some reason.Last edited by zynthetix on Tue Feb 17, 2009 9:15 pm; edited 1 time in total

No it isn't, because if you're running the 1.60 driver, the 1.40 update program will not recognize the G2.

At least on Windows, what you have to do is go into Device Manager, right-click the driver (which you must do with the G2 connected, because otherwise the driver won't be visible in Device Manager), say you want to update it, then supply the 1.40 driver as the "update".

Once you've done that, the 1.40 driver will recognize the G2 even though it won't be able to talk to it. At that point, you can run the 1.40 update program and it will replace the system software in the G2 even though it is replacing it by an earlier version.

So it's not a particularly difficult process; but you have to do things in an order that may seem counterintuitive.

Much to my suprise I got some a couple of the dreaded lost connection errors at the weekend (having not had any since I first got my Nord) but I had recently attached my Nord to my very recently acquired USB hub rather than direct to my PC, so I switched it back to getting a direct line from the PC and have had no more errors since.

Not sure how relevant this is, just thought I would mention it. I have heard that some devices just don't get on with all external hubs and mine is a cheapy and others are quite happy. E.g. To date my iPhone has not had a problem with the external hub._________________iP (Ross)
- http://ipassenger.bandcamp.com
- http://soundcloud.com/ipassenger

Much to my suprise I got some a couple of the dreaded lost connection errors at the weekend (having not had any since I first got my Nord) but I had recently attached my Nord to my very recently acquired USB hub rather than direct to my PC, so I switched it back to getting a direct line from the PC and have had no more errors since.

Interesting.

I've been running my G2 on a hub since I got it, and never had any problems until I installed 1.62, at which point I started getting occasional problems. Going back to 1.40 made the problems go away.

So I suppose it's possible that 1.62 is more sensitive to hub issues (timing?) than 1.40.

I'm on 1.62 and only experienced the issue after quite heavy patching (presumably it is pretty intermittent), a good few hours in. However once it crashed, it did so quite soon afterwards, so I removed it from the hub and have not experienced a crash since.

That's not's to say it wont mnd.

My USB Wifi dongle wasn't keen on the hub either but as I mentioned my card reader and iphone are quite happy with it to date.

If you ask me this USB lark is pretty wonky. My iphone and ipod hate the port on the front of my pc (crashes regularly during data transfer) but my wifi dongle couldn't be happier. It could just be a snugness (!!!new word alert!!!) of plug to socket issue._________________iP (Ross)
- http://ipassenger.bandcamp.com
- http://soundcloud.com/ipassenger

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum

Please support our site. If you click through and buy from our affiliate partners, we earn a small commission.