|
|
|
|
|
1. Windows Vista and Windows 7 2. Apple Mac 4. Sending data to the Korg Z1 5. Overwriting data accidentally 6. Inserting/deleting/moving bank patches: tips 7. Showing patch names in multisets 8. Protecting patches in multisets 9.
“Missing remap text files”
message 10. “File may be non-Z1” message 11. “Unrecognised data” message 12. Replacing selected patches with import tool 15. Future upgrades Does the program work with Windows Vista
and Windows 7? Yes. The
latest version of the program uses a Windows installation package to enable
the program to run on most Windows platforms: Windows 98, Windows ME, Windows
2000, Windows XP (SP2 and SP3), Windows Vista and Windows 7 (32-bit mode). Is there an Apple Mac version of the program? Sorry, no.
Korg themselves did produce a Korg Z1 Editor for the Apple Mac (which may
still be available from the Korg web site). However, it does not contain many
of the Korg Z1 utilities which can be found in Korg Z1 Editor 2004. Does the program work with all MIDI
interfaces? The program should work well with all MIDI
interfaces. With earlier versions of the program some MIDI
setups have had difficulty when the program sends large bulk data (eg bank
data) to the Korg Z1. Some MIDI interfaces can only handle bulk data with
buffers of certain sizes and delays between the buffers to slow down the
transmission speed. Version 2.1 of the program, released in November
2009, now includes preset buffer sizes and delays which can be varied to suit
particular MIDI interfaces. Problems sending data to the Korg Z1. Failure to
send data to the Korg Z1, or error messages when sending data, are usually
caused by missing out one of the 3 settings on the Korg Z1 which should be in
place for sending any sysex data to the Korg Z1. The 3 standard
settings are:
This should
enable any data to be sent from the program to the Korg Z1. Is it possible for the program to overwrite patches on the Z1
accidentally, like some other programs. No. The
patch editor only sends patches to the Korg Z1's edit buffer. To overwrite a
particular patch on the Z1 you would need to use the Z1's own write utility
to copy the patch in the edit buffer to a specific location (eg A037). If you
select Send while using the bank editor, this will send the current
bank to the Korg Z1. This will overwrite all patches in a bank
(if the Z1's memory protection is switched off), but the program gives a
warning message first and you are asked to confirm before this happens. The Auto Send (Sound Show) feature
enables you to quickly try out any or all of the patches in a bank in turn
without overwriting the bank in the Korg Z1. Inserting/deleting/moving patches in banks:
tips To
insert a patch To insert a
patch within a bank (eg to put A043 Pipe Organ Full between A007 Male Ahhs
and A008 Syndicate Lead) you should select all the patches between A008 and
A043 by clicking on A008 and pressing SHIFT
and clicking A043. Then right click and select the Rotate (+) option (or press CTRL
+). This will move A043 into position A008. A008 Syndicate Lead will become A009, A009
will become A010 and so on. To
delete a patch To delete
a patch (eg to delete A040 Rockin Bee! in the group A039 Jazz Organ, A040
Rockin Bee! And A041 Full Organ) you should click A040 to select it, and then
right click and select Insert Last
from the drop-down menu. A039 Jazz Organ will now be followed by A040 Full
Organ. Any number
of patches can be deleted in this way. It is only necessary to click on Insert Last once. Patches
are not actually deleted from a bank by doing this, as this would leave a
bank with less than 128 patches, but the effect is much the same. Patches are
moved to the end of a bank. They can be left there and ignored, or easily
replaced by better patches. To swap
2 patches Click on
the 2 patches and select any of the 4 rotate options in the (right
button) popup menu (or simply press CTRL
+ or CTRL -). To undo
the swap just select the same rotate option again or select Undo or
press Ctrl Z. To move
a number of patches around Click on
the patches and select rotate+ in the (right button) popup menu (or
press CTRL +). If you want to undo
the last move just select rotate- or select Undo or press Ctrl
Z (or press CTRL -). When each
patch is in the position you want just click that patch to deselect it. Carry
on until each patch is in the position you want. If you
want to move the patches by more than one position at a time then you can use
rotate++ in the (right button) pop up menu. This moves patches forward
by 50%. For example, if you have selected 8 patches it will move them forward
by 4 positions. To undo you should select Undo or press Ctrl Z. To move
a number of patches around in an ordered way Click on
those patches and select one of the sort options in the (right button)
popup menu. To undo you should select Undo or press Ctrl Z. To
reverse the order of a number of patches Click on
the patches and select rotate-- in the (right button) popup menu. To
put the patches in their original order just select the same rotate option
again or select Undo or press Ctrl Z. All the
options shown above (apart from Insert Last) only affect the patches you
select (highlight). You can use the 4 rotate options and the 6 sort options
in any combination to put patches in the positions you want. All other
patches remain unaltered. To move
a number of patches to the start of the bank If you
want to move only the patches you select and the patches at the start of the
bank which they replace, select Swap First in the (right button) popup
menu. To undo the swap just select Swap First again or select Undo
or press Ctrl Z. The new Swap First and Swap Last tools
simply swap the patches you select and the corresponding patches at the
start or end of the bank. All other patches remain unaltered. With this
option the start or end patches which you have just swapped are highlighted
in their new positions to make it easy to identify them. The
options Insert First and Insert Last (the same as Put First
and Put Last in earlier versions of the program) are rather more powerful.
Insert First will put the patches you select at the beginning of the bank and
move all other patches back, which changes all patch numbers in a single
operation. The patches you selected will be highlighted in their new start or
end positions. Insert First and Insert Last can be very useful if you
have a bank which you are free to add to and change as much as you like. If
you are not sure whether you want to use Insert First or Swap First you can
try them out and select Undo or press Ctrl Z if you change your
mind. I loaded a multiset into the
program but it only showed patch numbers. How can I show multiset patch names
as well? Korg Z1
multisets contain only bank letters and patch numbers. On the Korg Z1 these
numbers are converted into patch names using the currently loaded banks.
Similarly in the Korg Z1 Editor program these numbers are converted into
patch names used in banks A and B if these banks are loaded. There is a
way to show multiset patch names in the program even if banks A and B are not
loaded. When you load bank A or bank B into the program you can select Bank
> Map New when each bank is displayed. You only need to do this
once. This stores a list of bank numbers and corresponding names in the
program's data folder. After that multisets and multibanks loaded in the
program will show the names of patches as well as the bank letters and patch
numbers, even if banks A or B are not loaded. Not only
can you display the patch names of each multiset on screen. You can also use
the print or save list facilities in the program to print out or save lists
of each multibank, showing all the patches in each multiset in each
multibank. I use multisets with my sequencer, and
don't want to change or delete any of the patches which the multisets use.
Any suggestions? You could
print a list of all the patches used by the multisets in each multibank and
then scan this list before deleting any patch. You need to enable your
multisets to show patch names (as explained in showing
patch names in multisets above). Then you just load a multibank and
select File > Print. However,
to save having to refer to the list each time you move or replace a patch it
may be worth doing a one-off reorganisation. You could put all the patches
used by multisets at the beginning of bank A or B, sort them alphabetically
for ease of reference and then use the remap tools including the new Show
Remap utility. For
convenience, the 77 patch names used in the original Korg Z1 multisets
(factory presets) have been grouped together here, showing their original
bank and patch numbers. You can download the list by right clicking one of
the links below (and selecting Save
Target As...) Alphabetical list of multiset patches (1K) Numerical list of multiset patches (1K) You can
even download (below) the Korg Z1 factory banks A and B with these 77 patches
changed from User Group 1 to User Group 2. You can then use Bank > Find
Patches > User Group = GROUP2. All the multiset patches will be
highlighted. Also, if you send these banks to the Korg Z1 all these patches
will show User Group 2 instead of User Group 1. (You could, if you wish,
change the name of User Group 2 on your Korg Z1 to a more meaningful name eg
Multiset Patch) Bank A with multiset patches changed to User
Group 2
(83K) Bank B with multiset patches changed to User
Group 2
(83K) Ian Clark
adds: On my own Korg Z1 I then moved all these patches to the beginning of
bank B, using Put First, Export/Import (bank) and Sort by
Name in the bank popup menu. After moving the patches I used the Bank
> Create Remap and Multi > Remap Multibank tools to remap
both multibanks. All the original Korg Z1 multisets in multibanks A and B
work correctly using their original patches, even though all the patches are
located in bank B (at locations B000 - B076). By doing this I can now add,
delete and move patches in bank A as much as I like without any risk of
affecting any of the multisets. I get a “Missing remap text files” message
when using the Create Remap function The Create Remap function uses 4 text files
showing lists of patch names and bank numbers for the original banks
(oldA.txt and oldB.txt) and lists of patch names and bank numbers for the
current banks (newA.txt and newB.txt). These text files can be quite useful
on their own. These files can be produced by the Bank >
Map Old and Bank > Map New functions. Where they don’t exist,
they should be created when using the Create Remap function. In
earlier versions of the program one of the files might not be created, and the
above error message appeared. This has been corrected in version 2.1.221 of
the program (Feb 2010). The Create Remap function links these 4
lists together into a conversion list (the remap). This can be seen on
screen, with different display options, and all or part of the remap can be
copied into sequencer programs that use lists of patch names and numbers and
remapping functions. The remap can also be quickly and easily used by
Korg Z1 Editor to change all or any multisets so that they continue to use
the same patches as before. Korg Z1 Editor 2004 gave me a "File may be non-Z1"
message when I tried to load a bank file created with a Korg Z1 Sysex merge
utility. The file loads OK into a sysex dump program. Is it safe to send it
to the Korg Z1 with that program? If the
merged file was created by Pete Kvitek's merge utility then it is probably
safe to send it to the Korg Z1 using a sysex dump program. Pete is well
respected in Korg Z1 circles and his utility has been around for quite some
time. The file
created using the merge utility is not actually a Korg Z1 bank file, using
the Korg specification for such files. That is why the file will not load
into Korg Z1 Editor 2004. The merged file is made up of individual patch
files joined together. When sent to the Korg Z1 it treats it as a succession
of requests to overwrite individual patches - not as a bank file. Sysex dump
programs and sequencers will happily load files which vary in size and
content from the Korg Z1 specification, as they do not check the integrity of
the data. This can sometimes cause problems. It is always safest to check the
file in an editor program first. If any
Korg Z1 file cannot be loaded into Korg Z1 Editor 2004, and you are doubtful
about sending it to the Korg Z1, you are welcome to send it to the IAX Software
helpline to
check it to see if it can be converted into a useable file (or files). By the
way, the new Bulk Import (to Bank) utility provides a fully flexible and controllable
tool for merging patch files to form new banks. The Extract to File tool
already provides a fully flexible and controllable tool for splitting banks
into component patch files. All files created with these utilities conform to
the Korg Z1 specification. I sometimes receive "unrecognised
data" messages when sending banks from the Korg Z1 to the program. This
does not happen when sending single patches. Why is this? Single
patch files are small, and sending and receiving them is handled easily. One
of the Korg Z1 Editor 2004 beta testers sent 256 patches from the Z1 to the
program one after the other, and checked them, with 100% success. This is
typical performance for the program. Larger
data places more demands on the Z1, MIDI connections, MIDI interfaces, the
various MIDI software components and the PC operating system. Occasionally
there may be a problem where one or two bytes are "lost". The
program will show this as "unrecognised data", rather than try to
load and display corrupted data. This reflects the program's checking system,
which is a feature of good editor programs. Sequencer programs which handle
sysex dumps, or general purpose sysex dump programs, will happily load the
data without checking. If the
"unrecognised data" message appears, data can simply be
retransmitted from the Z1. In the experience of the author and the
beta-testers it is rarely necessary to retransmit data more than once. Technical
note:
Although there could be a number of reasons for "losing" data
bytes, the most likely - and consistent - explanation is a one-off resizing
of the computer's MIDI input buffer during MIDI transmission which interrupts
the processing of the incoming MIDI message. If the
"unrecognised data" message appears often you should refer to Help
> Contents > Troubleshooting > Check List > Problems
receiving from the Korg Z1 or contact the helpline here. It looks as if the Bulk Import tool can only replace a
continuous sequence of patches in a bank. Can it also replace selected
patches dotted around a bank without affecting any other patches? Yes. The File > Import to Bank tool on its
own was designed to directly replace a sequence of patches starting with the
bank patch you select (eg 013, 014, 015, 016, 017, 018, 019 ...). However, it
is possible to directly replace a number of separate bank patches (eg 003,
017, 045, 068, 088, 089, 102, 116 ... ) if you use the File > Import to Bank tool in conjunction with the existing Export/Import
(bank) tool (which swaps patches between banks). Suppose
you have 8 separate patches in bank A that you don't like and want to replace
them directly with 8 new patches that you have just downloaded. Here is what
to do: 1. load
bank A and then select Bank > Swap Banks [to create a temporary
Bank B] 2. load
bank A again [this will be the active bank A] 3. select File
> Import to Bank and select the 8 patch files you wish to import in
the file list. Select bank B, select patch no B120 in the Select start patch
to overwrite box and click Import [The
8 new patches are then imported as B120 - 127, the last 8 patches in bank B.
If you wanted to import 48 patches you would select patch no B080 rather than
B120. B080 - B127 = 48 patches] 4. click Done 5. in bank
A, click on the 8 patches that you want to replace 6. right
click and select Export/Import (bank) in the popup menu. [You will
be asked to confirm that you wish to replace these 8 patches with the last 8
patches in bank B] 7. click Yes
and that's it! You can
now send your new bank A to the Korg Z1 (and save it on the PC as well). You
might also like to print out a copy of your latest bank A patch list (File
> Print). There are 10
sort options, which can be applied to a group of patches or an entire bank. Sorting
a group of patches Firstly
select the patches you want by: a. using
the Bank > Find Patches menu option; or b.
clicking the first patch and pressing SHIFT and clicking the last patch to
make a continuous selection; or c.
clicking each patch directly. Then click
the right mouse button and select one of the 10 Sort [...] options in
the popup menu. Sorting
an entire bank There are
times when you will wish to sort an entire bank. You may want to do a
reorganisation of your banks, or to produce different versions of your banks
to keep on a memory card with all the patches sorted for ease of reference.
To sort an entire bank you should go to the main menu and select Bank >
Sort by ... and one of the 10 sort options. Sort
and Undo The new Undo
feature opens up additional possibilities for using the sort options. For
example, you can now do a quick, reversible bank sort to check for duplicate
or similar patches. If you have used another editor program that moves
patches by using "drag and drop" it is possible that you may have
duplicate patches. Getting rid of these patches makes it easier to fit new
patches into a bank. Duplicate
patches:
you can sort alphabetically using Bank > Sort by Name to check if
you have any duplicate patches. Duplicate patch names will appear together.
After you've checked, simply select Undo... at the top of the Bank
menu or popup menu (or Ctrl Z) to put the bank back to its original
order. Similar
patches:
you could do a multiple sort (eg OSC1, OSC2 etc) to identify patches that may
be the same or similar, even though the names are different. When done,
select Undo... (or Ctrl Z) the appropriate number of times to
put the bank back to its original order. Sorting
patches by OSC1, OSC2, FX1, FX2, Filt1 and Filt2 will put the same patches
next to each other and will tend to put similar patches next to each other.
If you select these sort options in reverse order you will have a bank
sorted by OSC1, then sorted by OSC2 within each OSC1 block, and so on. You could
send these sorted patches to your Z1, and listen out for any that sound like
duplicates or candidates for removal. To do this you should select the
patches you want to send and then select Auto Send (Sound Show) in the
right popup menu. If you
want to do an exact check on 2 (or more patches) that seem like duplicates
you can put them into the patch editor (Put in Patch Editor in popup
menu) and then select System > Compare Last. This will tell you if
the last 2 patches loaded in the patch editor were identical. If it is only
parameters 1 to 16 that are different, the patches are identical apart from
name. Exploring the Korg Z1 MOSS: tips The Korg
Z1's Multi Oscillator Synthesis System (MOSS) has amazing capabilities. Many
synthesisers use just 1 oscillator type to generate sounds. The Korg Z1 has
13 different oscillator types, many of which can be combined. This makes it a
very powerful, but also rather complex, synthesiser. The best
way of understanding each oscillator type is to select and compare patches
produced using each of the oscillator settings. The Super Find and Auto Send
(Sound Show) tools make this particularly easy: 1. load
bank A or B (or both) into the program 2. select Bank
> Find Patches ( or Ctrl F) 3. in the Find
by Type box select OSC1 4. select
one of the 13 oscillator types in the drop-down list 5. click Find
and then Done. All the patches which use this oscillator type as the
primary oscillator (OSC1) will be highlighted in the selected bank. 6. right
click on any of the highlighted patches, and then select Auto Send in
the pop-up menu. When you select Start on the Auto Send screen the
patches will be sent to the Korg Z1 in turn. You can play them as they are
sent, or hear them play automatically using the Sound Show option. As well as
the preset Korg Z1 banks A and B, you may have other Korg Z1 banks. In order
to check all of your patches which use any given oscillator you would need to
check each bank separately. To avoid this, you could first set up a library
folder with all your patches sorted by oscillator type. You would only need
to do this once, and then you can add to it as necessary: 1. select Settings
> File Names and check that the Patch name format box is set to
oxx patch name. (This will automatically save patch files with the primary
oscillator number followed by the patch name) 2. load a
Z1 bank into the program, and select all 128 patches by clicking on the first
patch and pressing SHIFT and clicking on the last patch 3. click
the right mouse button and select Extract to Files in the popup menu 4. select
(or create) the folder you wish to use as your library folder, and then click
Save. The 128 patches will be saved as 128 patch files in just a few
seconds 5. when
you have done this for each of your banks, you will have a folder containing
all your patches sorted by primary oscillator type: o00
Standard OSC o01 Comb
Filter OSC o02
Variable Phase Modulation OSC o03
Resonance OSC o04 Ring
Modulation OSC o05 Cross
Modulation OSC o06 Sync
Modulation OSC o07 Organ
Model o08
Electric Piano Model o09 Brass
Model o10 Reed
Model o11
Plucked String Model o12 Bowed String
Model The
author's patch library, containing 772 patches sorted by oscillator type and
then alphabetically can be downloaded here: Korg Z1 patch library: 772 patches (0.35 MB) Having
created a patch library folder you can then use the File > Import to
Bank and Auto Send (Sound Show)
tools whenever you wish to check out a group of patches with the same
oscillator type: 1. load
any bank into the program (as a temporary bank) 2. select File
> Import to Bank to put the patches you want from your library folder
into the bank 3.
highlight these patches, by clicking on the first patch and pressing SHIFT and clicking on the last patch 4. right
click on any of the patches, and select Auto Send in the popup menu. Do you have any plans for future upgrades? With the release of version 2.1 of the program,
there are no plans for any early upgrades. This very much depends on comments received
about current features and suggestions about new or enhanced features. All
feedback is very welcome. |
Please send any questions, comments and
suggestions to iax software Program versions: Version 2.1.221 released 15 Feb 2010 Version
2.1.217 released 12 Nov 2009 Version 1.6.213 on request 12 June
2009 Version 1.6.205 on request 14 May
2007 Version 1.5.191 released February
6 2005 Version 1.5.184 released June 15
2004 Version 1.4.154 released January 7
2004 |
|
|||
|
||||||
|
||||||
|
||||||
|
||||||
|
|
|
|