Conversion of presets from the GNX 4 to the GNX 3000
Does anyone know if you are able to change a preset for the GNX4 and make it compatible with the GNX 3000. For example - in the Guitar World Magazine, I am able to download presets from the digitech website but they don't have some of them available for the GNX 3000 which is what I have. I have tried changing the file extensions and that didn't work either. Does anyone have any suggestions that may help? Thanks.
Comments
I don't believe anyone has written a conversion program to do it automatically for you. I have the GNX4, not the GNX3000. I don't think that the CPU chips are the same and therefore a direct conversion would not be possible. If you knew the manual settings on the GNX4, you could probably manually make a similiar preset to the GNX3000. But making presets is not my forte. But you should be able to create your own presets if you knew the settings on the GNX4.
Or, you can check out the following site I just heard about. They claim that they have over 1500 GNX3000 presets for free download. http://tons-of-tone.tripod.com/patch1.html. Best wishes.
You cannot transfer patches, but you can manually edit them in XEdit and save them in the G3K. You need to be able to read the GNX4 patch, 'translate' the different amps/cabs/effects etc from the GNX4 names to the G3K equivalent. (download a copy of the GNX4 manual). The parameters aren't exactly the same, but are close enough to create a very similar sound. Below is a link to the XML patch reader that you can open the GNX4 patches with. Save the GNX 4 patches you want into a folder on your pc. Save a copy of the xml reader into the same folder. To read the GNX4 patch just 'drag' the patch and 'drop' over the reader file, then press run. It lists all the settings.
Also, if the patch uses 'custom' amp/cab settings, then you may not be able to get the sound you want, as these are settings specifically created by the originator.
Hope this helps.
Regards
Tony
http://emlconseil.free.fr/fichiers/patchReader.exe
Open the GNX4 patch in Notepad. At the top, change the first-level tag from Gnx4Preset to Gnx3kPreset.
Scroll down to param ID 8263. Copy everything through and including that parameter tag. It helps to view the file in Excel, since it's an XML file. Discard the footswitch assignments.
Next is the tricky part. You need two GNX3000-compatible amp model. You can get this from another GNX3000 patch. You cannot use the one on GNX4.
However, you can reuse the cabinet data. Be sure to change this part:
<GenetxModel>
<Version>Version1</Version>
Need to read:
<GenetxModel>
<Version>Version2</Version>
Don't forget to change the last line from </Gnx4Preset> to </Gnx3kPreset>.
Best of luck!
I now wonder if it is that simple, why have DT not made an official convertor ?
It would immensely increase the acceptance of any new MFX product if all the older MFX patch files could be translated to the new format.
I have often been hankering for a PDF \"Patch distribution format\" that all manufacturers can adhere to so that any patch from any hardware can translate (as close as possible) on to any other hardware.
If intervendor interoperability is a dream, lets atleast have interoperability of patches within the hardware pool of each individual vendor.
1) MIDI (and the General MIDI patch instrument map)
2) IEEE 1149.1 BSDL standard for being able to test highly complex digital ICs
\"patch information\" is an ideal candidate for such an effort. There is almost universal commonality for all the information and data to describe this stuff, like:
For AMPs;
Volume, Treble, Bass, Mid, Gain, Tremolo
For Effects;
Reverb - Type, Depth, etc.
Chorus (and all the parameters)
Distortion (and all the parameters)
Delay (and all the parameter)
and on and on....
For Modelling;
AMP type, Cabinet Type, Speaker.
This is a perfect realm for adopting standards by which data for patch information could be adopted.
Of course this would be starting over for everybody (all the manufacturers) with a design process that could implement this kind of a standard, but I believe that it would eventually catch on.
..and there could be a facility within the standard to accommodate \"special\" stuff that isn't common, similar to the \"System Exclusive\" stuff in MIDI.
Good food for thought (if nothing else).
Actually I see a PDF patch distribution format as fairly easy to implement.
All the different vendors need to do is ---
HARD PART : Agree to cooperate and agree on the format of the PDF. This needs user pressure to convince them of the long term benefits to all.
EASY PART : Dont touch any existing H/W or S/W. Just write a new software that can translate their proprietary patch formats to/from the PDF.
Did you see the Line6 to VAmp convertor that someone wrote using SYSEX as the common language ? Suddenly the VAMP gets 4000 patches.
Actually I see DT's effort to make human readable, not encrypted XML patches as a step in the right direction !!!
All MFX are just collections of Amp emulators, Compressors, Fuzz, other effects etc
All Amp emulators have very similar parameters
All Compressors have very similar parameters etc etc
It is very possible ( as chuck notes above ) to have a PDF for patch distribution amongst different units from the same manufacturer or even different units from different suppliers. All it needs if for them to realise that it helps the industry and helps acheive common goals.
If the manufacturers dont do it, there is a chance of a 3rd party to cash in. When Microsoft, Lotus, Apple could not agree on formats, Adobe stepped up and made a PDF format that could read/be read on all platforms. Soon they became the defacto standard !!