Korg Forums

chorg · Joined: 25 Jan 2006 Posts: 28

When I first heard about the M1 emulation in KLC, I made a wish list for T1 emulation, consisting of these four features:

(1) the internal PCM sounds of the T1, in the right "locations" to enable existing T1 programs to work without having to edit them to get the right waves for the two oscillators

(2) the ability to import T1 Programs & Combinations stored in computer files, both as individual sounds and as banks, and/or to receive such files via SysEx (eg from inside Cubase or over MIDI). (The combinations could refer to any of the 200 programs in banks A & B.)

(3) the ability to use data (preferably transferred to hard disk) from T1 PCM diskettes - ie those containing samples, not just patch data - I have many PCM diskettes, some being commercial Korg products, some copied free at Korg, and some from third-party suppliers. I know it's possible for a PC floppy disk drive to read T1 diskettes, because many years ago I bought a PC program (DOS, not Windows) that read T1 diskettes and copied the contents to hard disk. (I suppose this feature amounts to creating your own "PCM Cards" like the ones used in the M1 emulation?)

(4) instrumental response to SysEx in order to play back edits made to sounds during recording at the keyboard, such as from Button-A-H clicks and data-slider movements on the T1. I occasionally recorded (into Atari Cubase) with numerous edits made in this way, mainly changing the samples used in the two oscillators: on playback, the recorded SysEx recreated the edits correctly amongst the other MIDI events; I'd like to be able to replay these sequences using T1 emulation.

Now that the T1 sounds have been made available for use with the M1 emulation, are features 1 & 2 already available?

What about 4?

For me, the most important use of T1 emulation would be to recreate some sequenced pieces (recorded from my T1 into Atari Cubase). Without feature 3, it would be impossible to recreate my sequenced pieces that used third-party PCM data (eg jazz cymbals, various percussion, other instruments, sound effects), and this would seriously limit the value of the T1 emulation.

Any thoughts/comments/feedback?

chorg · Joined: 25 Jan 2006 Posts: 28

Francois and Jaz - questions mainly addressed to you, but if anyone else can answer, ...

Under the topic "The ultimate collection of M1 sounds for Korg Legacy Edition", at

http://www.korgforums.com/forum/phpBB2/viewtopic.php?t=14522

Francois has replied to questions from me about importing SysEx data, and this partly deals with my queries concerning my points (1) & (2) above. However, just to clarify whether I'm interpreting Francois's answers correctly, I've got three supplementary questions. They are more appropriately put here rather than continue under the other topic:

(1) When it's said that the M1 emulator will import SysEx, does this mean that the imported file must contain precisely the bytes that the hardware synths would have sent to the computer, with (for instance) no additional header information, OR will the import feature read and ignore any such header info until it recognises the start of the SysEx part (and similarly ignore any data following the SysEx part)?

(2) Is it unambiguously the case that no files in the popular Steinberg Synthworks formats can be directly imported (ie with no preliminary editing)?

(3) Will the emulator import not only M1 but also T1 bank SysEx files, and will it properly interpret files in T1 format, ensuring that the appropriate multisounds are used when the T1 "sound card" multisound data are in use?

Clive

Daz · Retired Joined: 01 Jan 2002 Posts: 10829

hayashi · Korg Japan Joined: 09 Sep 2005 Posts: 259 Location: Japan

I have a question/suggestion...

The software version of M1 and WAVESTATION do not allow to import SysEx which has multiple chunks. (I mean the chunk is a block of F0 to F7)

It is not planed to change this specification, but I (or someone) probably be able to make a simple utility which "chops" multiple chunked SysEx file to single chunk files with useful file name. I assume that the utility won't care for the input file type, just deal with it as a binary file. So any files can be chopped to be imported into M1/WS.

I just want to know whether it will help you or not.

I'm very happy that you love our synths, so I want to help your cool sounds which created by spending your precious days.

Best regards,
Masanao Hayashi
Cheap Software Engineer Shocked

From sweet living room

Daz · Retired Joined: 01 Jan 2002 Posts: 10829

hayashi · Korg Japan Joined: 09 Sep 2005 Posts: 259 Location: Japan

Daz · Retired Joined: 01 Jan 2002 Posts: 10829

Hi Masa,

Great minds think alike Wink

At the moment my application works only with WaveStation Sysex. It essentially does as you suggested and extracts the blocks of data between 0xF0 and 0xF7 in a generic way. However because it understands the WaveStation Sysex format it is able to store the chopped up sysex in file names that are appropriate to the contents of each block (i.e. the data type and the BANK if relevant)

e.g.

aquila2_AllPatches_Bank1.syx
aquila2_AllPerformances_Bank1.syx
aquila2_AllWaveSequences_Bank1.syx

I could easily adapt my application to understand the M1 sysex too, as per your idea, if people were interested.

Thank you for your kind offer though !

Daz.

hayashi · Korg Japan Joined: 09 Sep 2005 Posts: 259 Location: Japan

Hi Daz,

Francois · Posted: Mon Jan 30, 2006 1:34 am Post subject:

Francois · Posted: Mon Jan 30, 2006 1:42 am Post subject:

Q1 - Yes, the file needs to be exact. Even adding something after F7 at the end of the file will mean the sysex won't import. It has to start with F0 and ends at F7.

Q2 - No, Synthworks cannot be imported as is without editing the files.

Q3 - Yes, T1 sysex work, I've tried and succeeded importing two Voice Crystal banks I have. Of course, I have other files that won't work because they refer to other samples from Korg floppies (2 series of 10 disks altogether, we have 5 so far).

Daz · Retired Joined: 01 Jan 2002 Posts: 10829

Francois · Posted: Mon Jan 30, 2006 2:37 am Post subject:

No worries. You can still adapt your WS proggy when you have time, I have other banks Wink

Daz · Retired Joined: 01 Jan 2002 Posts: 10829

This one is for Francois Smile

http://daz.korgforums.com/M1SyxSplit.zip

... a quick and dirty tweak of my WaveStation program ... it splits up files that contain multiple M1 sysex dumps and copies each sysex dump into a separate file with an appropriate name. There is no header stripping functionality ... let me know if you need that (send me an example file with header if poss)

For example if I drop the file m1best.syx (from Francois' collection) on the application it creates 3 files :

m1best_AllCombis_Int100.syx
m1best_AllPrograms_Int100.syx
m1best_GlobalSetup.syx

Note the suffix on the Combi and Program files ... it indicates whether the syx came from the Internal memory or the Card and the number of Programs/Combis contained in the file (50 or 100 according to the M1's config).

Daz.

Francois · Posted: Mon Jan 30, 2006 9:54 pm Post subject:

Many thanks. I'll try it later.

hayashi · Korg Japan Joined: 09 Sep 2005 Posts: 259 Location: Japan

Wow! Thanks Daz!! Very Happy