Korg Forums

Has anybody tried emulating the types of sounds made by a SID chip like the ones in old C64 computers? hehe oh yes I have :) in fact I am (still) working on some kind of "tracker" with special radias support (well, it's progressing slowly TBH) special support means that, besides other retro-like ...

- a program switch that makes controllers (e.g. targeting filter cutoff) modify only the last triggered voice (instead of all voices of a timbre!) - as a deluxe version of this feature, the switch could cause ctl. changes to modify all voices that have been started in a given time window (e.g. a ...

meatballfulton: You are right, of course. The factory kits work fine (and so do a whole lot of other drum patches I programmed myself), it rather seems to be a problem with these specific patches. The bassdrum uses an extreme pitch modulation via EG3, by the way. tonyman: No effects used. Could ...

G'day, I am currently having trouble with some very annoying Radias sound anomalies which result in random blips and bleeps. I have created a bassdrum (triangle) and a hihat (noise) sound and put them both in a drumkit (along with a DrumPCM snaredrum to be exact but that could be left out). As long ...

1.) I'd really like to have a synth-mode that decouples (most of) the knobs/switches from the synth engine so they become general purpose midi controllers. It should be possible to enable/disable the "controller-mode" via MIDI SysEx and on the Radias itself. 2.) I am missing SysEx messages to up ...

these are used to select the MIDI controllers for the MIDI1..5 sources you can assign to V.PATCH 1 through 6 (when editing a timbre).

I found the timbre system a bit awkward at first but started loving it after a short time. One really cool thing about the Radias is that you can change the timbre data really fast (if you connect it via USB MIDI). While you are of course still "limited" to 4*2 FX units and certain timbre parameters ...

klangsulfat: I second that.. Why on earth didn't Korg make send FXs instead of inserts.. would be much cooler that way and it really wouldn't require much more DSP time.. I believe that it is still possible to fix this in a future OS upgrade: There are some unused bytes in the timbre data-- one of ...

yes, it is a standard A<->B connector like it is used for many usb printers or external harddrives for example.

-deleted-

F0 42 3n 72 oo F7

where "n" is the device id (global midi channel)
and "oo" is 10 for the current program and 01 for the current drumkit.

well, you can't argue about taste. If it doesn't fit your (hackjacks) idea of sound then get other gear.. I for one tip my hat to the Korg engineers who created this machine. It's one of the most exciting synths I ever laid my hands on! I have it since 2 days and I am just excited as I was 15 years ...

so good so far.. the "incremental timbre update" works so far (as described above)..takes 405 midi bytes to change from "init timbre" to the v1.02 VeloSyncLead timbre :) (w/o insertfx, modsequence data, though) I stumbled over a few minor issues regarding parameter updates via CCs; couldn't persuade ...

Hmm it seems that the Korg devs forgot to implement the following sysex functions: "CURRENT TIMBRE PARAMETER DUMP REQUEST" (receive) "CURRENT TIMBRE PARAMETER DUMP" (send+receive) "CURRENT TIMBRE PROGRAM DATA DUMP REQUEST" "CURRENT TIMBRE PROGRAM DATA DUMP" (send+receive) + several others to ...

:) :) Got my Radias today and guess what.. one of the first things I tried is to answer my question. I have modified my tracker/sequencer (which I am currently working on but that's another story) to send 80 parameter change sysex requests to the Radias every 4 ticks (125 bpm, 96 ppq) i.e. ~50 times ...