Free FM Synthesizer Dexed (VST Windows and Mac)

VST, AU, AAX, CLAP, etc. Plugin Virtual Instruments Discussion
Post Reply New Topic
RELATED
PRODUCTS
Dexed

Post

Thanks TT for making this utility available!
Just a tip I wanted to pass along ...

If you're running dxfixheader on a large number of files, like the collection BlackWinny created, try running it like so:

dxfixheader -r > error.txt

It will operate on the files and also pipe information into a text file you an scan for broken files more easily.

Here's a fragment:

Code: Select all

fixed: CLAV_2.SYX -> CLAV_2.SYX
fixed: CLAV_3.SYX -> CLAV_3.SYX
fixed: HARPS1.SYX -> HARPS1.SYX
fixed: harpsi_1.syx -> harpsi_1.syx
fixed: harpsi_2.syx -> harpsi_2.syx
Input file <Keybd01.syx> should be 4096 or 4104 bytes long
Input file <Keybd02.syx> should be 4096 or 4104 bytes long
fixed: KEYBDS01.SYX -> KEYBDS01.SYX
fixed: Keyboard.syx -> Keyboard.syx
Cheers.
“I'd far rather be happy than right any day.” ~ Arthur Dent, Hitchhikers Guide to the Galaxy

Post

section.png
I've been learning the Dexed vst and worked out most of it. However, I'm still not grokking this section. Would some kind soul take a moment and give me a short explanation?

Cheers and thanks.
You do not have the required permissions to view the files attached to this post.
“I'd far rather be happy than right any day.” ~ Arthur Dent, Hitchhikers Guide to the Galaxy

Post

The way I understand it it's a kind of Key Follow, except that it doesn't have to be linear. The keyboard has a definable "break point", and we can define a behaviour for the left part and another for the right part.

This way, we can, therefore go up until a certain note, and then go down from that note up (or the opposite. We also have the possibility ot have a line (linear) or a curve (exponential). If you want a linear key follow, as it's tradition in the analogue synths, you can define the break point to the first note or the last note, and just care with the relevant "curve" (the right or the left, depending if you defined the break point as the lowest note or the highest note). The depth is the modulation intensity of the "key follow".

You have these links which hopefully can clear thing more:
https://www.reddit.com/r/synthesizers/comments/4i8vcd
http://www.chipple.net/dx7/english/edit.mode.html

And here is a small PDF with a tutorial about programming the DX7: http://www.deepsonic.ch/deep/docs_manua ... thesis.pdf
Fernando (FMR)

Post

Ah, I see. Hey thanks fmr, your explanation and a bit of study from the links cleared it up. :)

Cheers.
“I'd far rather be happy than right any day.” ~ Arthur Dent, Hitchhikers Guide to the Galaxy

Post

long shot but hey... can i use Dexted with the Yamaha FB-01 ? I know it's only 4 OP but was wondering if i could use it to upload to it?

Post

Hello,
I have been unable to get Dexed to load on my Mac OS X 10.6.8.
I have tried 0.9.1 and 0.9.2
I am using Reaper.

The VSTi does not even show up in Reaper at all. The AUi shows up
but will not load. I am using Reaper 4.78 Dexed is the only plugin out of many that doesn't work.

I saw a post somewhere that Dexed 0.7.0 and earlier worked on 10.6.8 but I cannot find any Dexed earler than 0.9.1 anywhere on "the net".
Any help would be greatly appreciated.

Thanks,
Brian

Post

overdrainbow wrote:Hello,
I have been unable to get Dexed to load on my Mac OS X 10.6.8.
I have tried 0.9.1 and 0.9.2
I am using Reaper.

The VSTi does not even show up in Reaper at all. The AUi shows up
but will not load. I am using Reaper 4.78 Dexed is the only plugin out of many that doesn't work.

I saw a post somewhere that Dexed 0.7.0 and earlier worked on 10.6.8 but I cannot find any Dexed earler than 0.9.1 anywhere on "the net".
Any help would be greatly appreciated.

Thanks,
Brian
Hi,

Version 0.9.0 runs on OS X 10.6, get it here : http://le-son666.com/software/dexed/

Post

Got it...
You are a lifesaver... :)
You wouldn't believe how many hours I spent trying to dig up an older version with no luck.
And, I was not even sure if the newer versions had a compatibility issue with 10.6 and if the older versions even worked or not on 10.6.

Thank YOU ASB2M10 !!!
Very much!

All the best,
Brian

Post

The Traveler wrote:
section.png
I've been learning the Dexed vst and worked out most of it. However, I'm still not grokking this section. Would some kind soul take a moment and give me a short explanation?

Cheers and thanks.
Breakpoint is not 0-99 on the DX7. I don't understand why this parameter is not matching up when everything else does.
Intel Core2 Quad CPU + 4 GIG RAM

Post

The Traveler wrote: ...
It will operate on the files and also pipe information into a text file you an scan for broken files more easily.
...
or just sort files by modified date/time :party:

@asb2m10
Speaking of the breakpoints, are you sure they break at the right place? According to my math (based on dx7 manual) 17 in

Code: Select all

int offset = midinote - break_pt - 17
should be changed to 21. But I have no idea how the real thing works.
BP=39 should break at C3 => 60-39-21==0

EDIT:

dirty fix to see things better:

Code: Select all

String CtrlDX::getValueDisplay() {
    String ret;
    if ( label.endsWith( "BREAK POINT" ) )
    {
        char *breakNames[] = {"A", "A#", "B", "C", "C#", "D", "D#", "E", "F", "F#", "G", "G#"};
        int breakNumber = getValue();
        ret << breakNames[breakNumber%12] << (breakNumber+9) / 12 - 1;
    }
    else
        ret << ( getValue() + displayValue );
    return ret;
}

Post

Got newsletter from Music Society about freebie soundsets for Dexed (and other DX7 compatible plugs)

http://music-society.de/index.php?topic=5566.0

(Note, need to log in at the site to download)

Post

tico-tico wrote: @asb2m10
Speaking of the breakpoints, are you sure they break at the right place? According to my math (based on dx7 manual) 17 in

Code: Select all

int offset = midinote - break_pt - 17
should be changed to 21. But I have no idea how the real thing works.
BP=39 should break at C3 => 60-39-21==0

EDIT:

dirty fix to see things better:

Code: Select all

String CtrlDX::getValueDisplay() {
    String ret;
    if ( label.endsWith( "BREAK POINT" ) )
    {
        char *breakNames[] = {"A", "A#", "B", "C", "C#", "D", "D#", "E", "F", "F#", "G", "G#"};
        int breakNumber = getValue();
        ret << breakNames[breakNumber%12] << (breakNumber+9) / 12 - 1;
    }
    else
        ret << ( getValue() + displayValue );
    return ret;
}
Thanks, that will probably do the job. I'll include it in the next commit with the credits.

As for the break, I didn't code that part... so I cannot tell. Did you test it yourself (I am telling this since testing right now with the real DX7 is somewhat complicated for me). If it is really 21, I'll put 21 cause it makes sens.

Post

asb2m10 wrote:
tico-tico wrote: @asb2m10
Speaking of the breakpoints, are you sure they break at the right place? According to my math (based on dx7 manual) 17 in

Code: Select all

int offset = midinote - break_pt - 17
should be changed to 21. But I have no idea how the real thing works.
BP=39 should break at C3 => 60-39-21==0

EDIT:

dirty fix to see things better:

Code: Select all

String CtrlDX::getValueDisplay() {
    String ret;
    if ( label.endsWith( "BREAK POINT" ) )
    {
        char *breakNames[] = {"A", "A#", "B", "C", "C#", "D", "D#", "E", "F", "F#", "G", "G#"};
        int breakNumber = getValue();
        ret << breakNames[breakNumber%12] << (breakNumber+9) / 12 - 1;
    }
    else
        ret << ( getValue() + displayValue );
    return ret;
}
Thanks, that will probably do the job. I'll include it in the next commit with the credits.

As for the break, I didn't code that part... so I cannot tell. Did you test it yourself (I am telling this since testing right now with my DX7 access is somewhat complicated for me). If it is really 21, I'll put 21 cause it makes sens.

Post

asb2m10 wrote:As for the break, I didn't code that part... so I cannot tell. Did you test it yourself (I am telling this since testing right now with the real DX7 is somewhat complicated for me). If it is really 21, I'll put 21 cause it makes sens.
dexed_brk.gif
Well, as you can see, now the osc has maximum output around C, without the fix it was somewhere around A. Maybe it's not 21 but 20 or 22, only dx7 owner with an oscilloscope could say for sure.
Thanks, that will probably do the job. I'll include it in the next commit with the credits.
Maybe something like this https://github.com/tico-tico/dexed/comm ... b29a82af17 will work better.
You do not have the required permissions to view the files attached to this post.

Post

There's four DX7 patches from Brian Eno in this Keyboard magazine article from 1987. I was going to try and enter them into Dexed, but then I found this syx file. Alas, there's some junk data at the beginning and end that prevents it from loading in Dexed (FM8 is able to read it).

After checking the DX7 sysex format I was able to tidy it up and now it loads fine. I've attached the fixed sysex file.
You do not have the required permissions to view the files attached to this post.

Post Reply

Return to “Instruments”