The computers I'll be using it with will be:
Mac Pro and White Macbook,
will not be plugging into any Hubs.

Yup, until the 1.62 editor is updated (and 100% working), that the way to go.
The 1.62 editor is working fine with the 1.40 OS here, on an Intel-Mac OSX 10.4.11.
But I asume this works fine for 10.5 also...

Did anyone ever say what mods might have actually been made to the G2 firmware with 1.62? I'm intrigued...

Well ... actually someone did say something

Clavia's Magnus Kjellander said that nothing was changed on the synth OS. I didn't pay too much attention when he said that, as everything works fine for me with the last OS, but my folow up question, in retrospect, should have been: only the version number was changed?_________________Jan

In the OS update utility there is a large resource of 512 kB that I assume to be the synth OS. I extracted that resource for both the 1.62 and the 1.40 version and then did a file comapre on the resuls, they are equal ... so I'm not sure where the version info is kept

Edit : oops .. I did something wrong ... I copied one over the other, no wonder they were the same ... will redo this test later when at home ..._________________Jan

Ok, that was nonsense what I wrote before ... the dumps are wildly different ... didn't check though if its a shift or that maybe it is encrypted, but a linear comparison indicated that almost no bytes matched._________________Jan

Having said that, I have managed to lock-up my unit by sending relatively rapid program change messages over MIDI (I had MIDI out on my NL3 hooked to MIDI in on my G2).

I'm wondering if G2 can get swamped / overloaded by certain types of message - possibly either over USB or MIDI. If it were to lock up half-way through writing a patch, perhaps that would cause effective corruption?

Mind, I've so far not had any issues. I'm now using the latest nord driver - he one they've posted up for nord wave.

Can you try the following experiment:

1) Connect your G2 to your computer.
2) Launch the G2 editor.
3) Turn the knob to select a random patch, hit "Load patch"
4) Repeat 50 times, each time loading a new patch as soon as the old one finishes.

to Roland :
i experienced same thing some times ago,
i could not save some patch on the machine, it caused a hang.
i sent an email to clavia and a gentleman from there replied me that the OS 1.6 has probably revealed some memory corruption on my G2.
here is the fix :

"1. Use the Editor to make a total backup of all patches and performance in your unit. You need to save everything on your computer hard drive. And do not forget to verify that these backups can actually be loaded back to the G2 after you have saved them.

2. When you are certain that you have backups and copies of all your important files, we want you to erase all the content of the G2 flash memory. Here is how to do this:

a. Shut down the G2 and then hold the Performance Mode, Display Mode and Store buttons while you power the unit up. Keep holding until the G2 Testprg is visible in the display.

b. The lower line in the display will show: MNB - PNL - EXP and SYS. Press the Keyboard Assign D button to enter the SYS tests .

c. Use the right arrow navigator button to scroll to the ERASE FFS action. This is an eraser for the flash memory, and when activated will format the entire flash. Every program, patch and performance will be erased in the G2.

d. Press the A button to "run" the eraser.
or (it depend on your g2 hardware version)
You start the process by pressing: Shift, Patch Load, Store and Patch Settings, 4 buttons at the same time.

e. When this is completed, turn off the G2 and then back on. Reload your programs and try saving again.

If this was not successful, do it again but select the ERASE ALL which is found after the ERASE FFS option. This will force you to reload the OS, I would go for the 1.6 first. If this still produces errors, downgrade to 1.4. "

This fix was ok for me. i just had a problem to re-import the perfs in the machine, i had to load each one by one, could not load by bank...

I suspect some patch from the NM->G2 conversion to be bad formed and have corrupted the memory (?), because the problem happened again just after i played with the NMG2 archive... but i'm not sure..maybe it's a clue..i don't want to blame anyone.

For what it's worth, I just tried loading 1.62 into my G2 with the 2.16 USB driver.

NO problems so far! In particular, I tried loading a bunch of patches into the G2 in a way that caused it to crash with the 2.14 driver, and I could not get it to crash.

Of course it may be that this memory corruption problem is widespread; but I am hoping it is not.

Why do I care, you may ask? Because if I cannot get 1.62 working in a satisfactory way, I intend to buy a netbook running Windows XP while I still can, to be sure I have a computer that I can use to edit G2 patches as long as possible. But if, on the other hand, I can be confident of using Vista and (presumably) Windows 7, I expect I'll be able to continue using my G2 for at least 5 years more than I would otherwise, and that's a big deal.

hi ark and revelin,
i have 2 g2 engines not with perf knobs.
like the beta software, the 1.6 software can't save pch/perfs.
the 'save in synth' (in synth dropdown menu) is not high lighted
(grey instead of black).
so how should i clean my g2's?
one progress in comparison to the beta version is:
when i startup the editor, it makes direct contact with the g2's.
with the beta software i had to double click a pch/perf, then the editor
opened with contact to the g2's. i use vista btw.

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.