M3 Editor - Imported PCG uploads straight into the hardware?

[dswtan]

PCGs in the M3 Editor are confusing me.

I thought the Editor and hardware were independent in that you could make changes in the Editor and then had to manually write those changes to the hardware -- the Editor and hardware are not "auto-synced" together.

However, when I Import a PCG into the Editor, the PCG settings are immediately sent to the hardware automatically.

I expected the PCG to just load into the Editor only; allow me inspect the programs/combis in there (and be selective and make changes if I want); and then I manually send over the Editor's copy of the current PCG settings (which would then be a program/combi load in the Editor and not a PCG as such) to the M3.

Instead, I can never use the M3 Editor to pre-inspect a PCG before loading it into the hardware -- which is really what I want to do. I have to have it load (and potentially overwrite) the hardware.

Am I just missing a "auto sync to hardware" option somewhere? I want to turn it off. Thanks for any assistance!

[Shakil]

I am not sure about the software editor, but on the hardware M3, you can preview a single program from any PCG. Instead of Pressing Load, you press open, and then it opens banks included in PCG, then opening a bank will show the included programs, and clicking those programs load into temporary buffer to preview.

May be there is a similar function on M3 editor....

[alland]

Yes, this is strange behavior of my M3 editor too. Whenever I choose import PCG then M3 Editor starts transmitting alld data back to M3. Why?

Usually any sync operations are manually done when I invoke this operatin from Utility menu.

Because of that auditioning should be rather done from USB - this allows listen programs and combis without loading into banks.

[dswtan]

Thanks both, Shakil & alland -- the USB auditioning/preview is a fair workaround. I was not aware of that. Cool.

I note that if I use Utility/Load in the Editor to load a .M3all file, the same behavior happens as Utility/Import -- everything is sent over to the M3 straightaway. Again, this is not what I would expect. I'd prefer the Editor as a separate buffer and I'd like to choose when to sync. It is far too "keen"!

BTW -- does your Auto Load File work in the Editor? Mine doesn't seem to do anything these days. I'm wondering if it used to work and is now broken, or if I just dreamed it used to work -- when I start up the Editor, I just see InitProgA000, etc. for all my Progs and similar for Combis.

[Thunderchief]

Hi

I've just had this same thing, the autoload file stopped working.

make sure you have selected the check box for the autoload, (mine had become unchecked somehow) which is in the global section, then you have to save the changes. you do this by clicking on utility and then; "save as default"

Hope this helps

Simon.

edited to clarify the instructions.

[KorgyRadias]

Hi

If you enable the 'memory write protect' on the M3, does it still overwrite to the M3? If it doesn't then disable the memory write to Prog & Combi on the M3.

[BasariStudios]

It is not a bug or a problem, its just the way it should be. The M3 editor has no sound
Engine of its own that's why you can't prelisten...all it does is sends and recieves Sys
Commands and MIDI messages, a Sound has nothing to do with those, it has to be
Coming from some kind of sounds engine, as in the case of VSTi which the M3 is not.

[mocando]

It is not a but or a problem, its just the way it should be. The M3 editor has no sound
Engibe of its own that's why you can't prelisten...all it dows is send and recieves Sys
Commands and MI0I messages, a Sound has nothing to do with those, it has to be
Coming from somekind of sounds engine, as in the case of VSTi which the M3 is not.

Are you typing with your gloves on Nedim? Sorry bud. Couldn't help it

[BasariStudios]

Lolz...kinda, from my BB9700 thats why.