Roland JD-990 Super Editor

  • Version 2.7.1
  • 5/03/2020


Download JD990 Super Editor

JD-990 Super Editor

  • Menu access to SR-JV80-04 external card patches and waveforms if installed.
  • Rename any remote patch name for Internal Patches I-11 – I-88 (64 x patches).
  • Save Temporary Patch data on Ctrlr panel to any Internal Patch location I-11 – I-88 (64 x patches).
  • Palette mode. Quick adjustment of each Tone ABCD using mouse wheel or click & drag.
  • Loaded patch data can be saved as a sysex file to computer.
  • Bulk Sysex dumps of patches I-11 – I-88 (64 x patches) or use JD-990 Sysex Dump Utility.
  • Emulation of most graphic elements on the JD-990 display.
  • Separate ”mixer’ area allowing simultaneous adjustment of each Tone Level & Pan.
  • Sync button ~ synchronising panel with JD-990..
  • Please use Ctrlr version 5.3.201 on Windows.
  • Please use Ctrlr version 5.3.201 on Linux (tested Ubuntu 18.04).
  • Please use Ctrlr version 5.3.198 on Mac (not tested).
  • Works only in ※ PATCH mode. ※ PerformanceRhythm 
  • ※ New Features in Version 2.7.1:
    • CC mapping to panel from (keyboard) controller
    • Mouse dragable graphs
    • All expansion card series waveform names can be loaded.*
      * [ Only  SR-JV80-04 patch data can be loaded. ]
    • Visit SourceForge for archived version 2.6.6
Known Issues:
    •  MacOS ※ If images are not visible/loading — delete folder Library/Preferences/JD-990 Super Editor/ and restart program.
    • WINDOWS ※ If old images are loading, but not new: — delete folder C:Users%USERNAME%AppDataRoamingJD-990 Super Editor and restart program.
      @RD /S /Q “C:Users%USERNAME%AppDataRoamingJD-990 Super Editor”
    • When saving custom ccmapping to file under Linux and MacOS be sure to add extension .jd990 to end of filename.
Version History and Change-log:
    • Version 2.7.1 (05/03/2020)
      Fixed MIDI Buffer Full error on patch change/reload + bug fixes
    • Version 2.7.0 (04/30/2020)
    • CC mapping to panel from (keyboard) controller
      Mouse dragable graphs
      Support for expansion card waveform names
    • Version 2.6.6 (05/03/2020)
      Fixed MIDI Buffer Full error on patch change/reload + bug fixes
      Version 2.6.5 (04/29/2020)
    • FIX:: Delay Tap Modulators not updating when resyncing
    • Version 2.6.4 (04/29/2020)
      FIX:: save sysex error for Delay Tap in FX
      Causes checksum error on upload of sysex back into JD-990 / possible buffer overflow
      Improved save as (rename) window.
      Changed font patch name window to reflect case.
    • Version 2.6.3 (11/07/2019)
      “Patch Pan” Button stopped at R49 – should be R50 
    • Version 2.6.2 (10/03/2019)
       Re-ordered Graph controls to follow JD-800 layout
      Make “y” axis visible at zero on all graphs 
      Thanks to u-man for suggestions
    •  Version 2.6.1 (07/31/2019)
      Resolves MacOS booting errors with VST/AU
      Thanks to taoyoyo for suggestions
    • Version 2.6.0 (07/26/2019)
      LFO Graphs show correct fade Amplitude values.
      minor code optimization – removed custom modulo function
      With many thanks to AndrewWerdna for comprehensive testing and advice
    • Version 2.5.2 (06/13/2019)
      Palette menu was not working for modulators in the LFO tab.
      Version 2.5.1 (04/17/2019)
    • Fixed frozen phaser controls (thanks to AW for spotting this).
    • Version 2.5.0 (04/12/2019)
      Palette Mode working.
      New Wave selection interface.
      Many code changes.
    • Version 2.4.3 (03/23/2019)
      Tone Select sysex was not updating for modulators when syncing with JD-990.
      MultiTone (on change Tone) selection was changing all modulator values.
      With thanks to user AW for spotting these problems.
    • Version 2.4.2 (03/22/2019)
      Fx Ctrl Combos (drop downs) were not working/Incorrect titles.
    • Version 2.4.1 (03/18/2019)
      Fixes DEL TAP buttons not sending sysex.
    • Version 2.4.0 (03/14/2019)
      VST indexes re-generated and re-ordered.New Copy Tones function.
      Many fixes.
      New design.
    • Version 2.3 (02/28/2019)
      VST indexes re-generated and re-ordered.
    • Version 2.2 (02/27/2019)
      Leftover debug code removed.
    • Version 2.1 (02/27/2019)
      Minor Standalone bug fix and graphics update.
    • Version 2.0 (02/26/2019)
      Complete re-write.Please upgrade  from previous versions
    • Version 1.7.0 (01/18/2019)
      minor design change – small bug fix – zoom function
    • Version 1.5f (01/12/2019)
      sys dump Area button fix
    • Version 1.5e (01/04/2019)
      Voice Priority and SoloSync were not displaying
    • Version 1.5d (11/11/2018)
      Fixed incorrect sysex formulae for Spectrum.
    • Version 1.5c (10/30/2018)
      Waveform Load Function was crashing on startup.
    • Version 1.5b (10/09/2018)
      Waveform Source button now working
    • Version 1.5a (10/07/2018)
      Fixed missing images in VST.dll
    • Version 1.5 (10/06/2018)
      Many code fixes
      Load time should be greatly reduced.
      Addressed Ctrlr Bug: sends all combo sysex/cc to machine on panel load.
      Fixed Midi Buffer Full Errors and Checksum Errors.
    • Version 1.2 -1.4  (from 09/28/2018)
      Please upgrade to version 2.5
    • Version 1.1 (08/18/2018)
       Fixed panel size (24px Ctrlr Bug)
    • Version 1.0 (07/10/2018)
      Changed Checksum function
    • Version 0.99 (07/04/2018)
       Checksum error fix
    • Version 0.98.5 (12/15/2017)
       Minor code fixes
    • Version 0.98 (10/13/2017)
      First release
Connect to JD-990 – PANEL AS VST To create a VST or AU file:
  • Load the Ctrlr.dll (Ctrlr VST/AU) into your DAW
  • Load this panel into Ctrlr VST/AU instance.
  • Then go to File -> Export -> Export Restricted Instance. 
    This will build a VST dll or AU (.component) file.
  • You can now load this panel independently of Ctrlr.
  • Or download pre built files from Download JD990 Super Editor

Running as VST under Cubase
  1. In Cubase, Disable †Midi-in **Midi-out ports to the JD990.
  2. Open JD-990 VST in an instrument track IN=(All Midi Inputs)
  3. Create Midi track IN=(All Midi Inputs) OUT=(JD-990 Midi-in) (I record midi notes & data to this track).
  4. In the VST Ctrlr panel connect to the †Midi-in and **Midi-out ~ connected to JD-990 (you disabled them in Cubase ( See step #1)).
  5. I found the only Midi-thru setting that needs to be checked was
    MIDI→Midi Thru→”Plugin-host->Output Device”
    (The 5th option down in the fold out menu)
  6. Engage Monitor on Both tracks. 
Running as VST under Reaper

(Thanks to user AW for these instructions)
(This is the JD990’s audio output)

  1. Insert – Track
  2. Record Arm
  3. Monitor Input (right-click record button)
  4. Track Input:Stereo Input

(Ctrlr VST settings)

  1. Insert – Virtual Instrument on New Track – Panel
  2. Routing – MIDI Hardware Output – JD990
  3. Ctrlr MIDI – MIDI Thru – Deselect “Input Device -> Output Device”
  4. Ctrlr MIDI – MIDI Thru – Select “Plugin Host -> Output Device”
  5. Ctrlr MIDI – “Input from host to comparator”
  6. Ctrlr MIDI – “Output to Plugin Host”
  7. SYNC with JD990

And make sure in your Preferences, Audio – MIDI Devices, you have it set so that your MIDI Device which connects to the JD990 is enabled for input, output, and control messages (right-click).



Comments or suggestions  welcome.

87 thoughts on “Roland JD-990 Super Editor”

  1. Awesome ! just created my account at Ctrlr looking for a editor for my Kurzweil K2500 and find this – which I also have.

    I look forward to getting my head around Ctrlr and your user pannel. Have you seen the one on mididesigner ?

  2. It’s great to get some feedback – Once you understand Ctrlr as a user, it works well. I hope to improve this panel’s vst functionality in the future, so please check back for updates!

    I don’t have an iPad, but that mididesigner panel for the JD-990 looks excellent. Didn’t know about that. You can see from the screenshots just how many features are locked away in the JD-990, which makes designing access to all of that a challenge!

  3. may be, would be nice that when a parameter is changed on the JD990 then it is reflected in the editor ( like the on off switch for the ABCD operators, or the part select or the ability to use the value button to adjust filter freq …). Well great work anyway ( sorry if my english is a bit erratic , I’m french )

  4. Bonjour Robx21, well your English is excellent, but I think what you say is not possible on the JD990 – maybe I’m missing something, but you can update your changes you make on the JD990 by clicking the “Sync with JD990” button. It’s the next best thing I suppose.

  5. Hello dnaldoog, thanks for your quick answer, indeed the sync button is fine, no need to complicate things. Well if I can think of one thing that would be to me very valuable in your editor, it would be the ability to save and load entire banks. I know we can use midiox for this but i’ve tried it today, it was very slow, i’ve tried too the JD990 patch organiser. It was faster than midiox, I could manage to receive banks from the JD990, but not to send them. If you can add this to your editor then we would have everything we need to create and manage sounds for the JD in the same soft. It would be great.

    • I can look at that – I t should be possible, but it’s great to hear about anything like this, because this is really stage 1, version 1 and I hope to improve the interface (it’s not the most beautiful) and maybe have graphs in there too.


      • Hi Robx21!

        A few months later and I have created a bulk sysexdump utility for the JD-990. I am working on incorporating it into the editor, but that’s more of a task than creating a panel dedicated to bulk dumps.

        I intend to also add extensive saving and editing capabilities to this panel.

        Right now as you know, on this JD-990 Super Editor panel you can only save the temporary patch to a sysex file and then read it back to the temporary memory area if you don’t manually save it on the machine, but soon the editor will be able to save directly to any of the JD-990 Internal Patch Memory Banks.

        Kind regards,

  6. Hello dnaldoog , keep on the good work , what you’ve done already is VERY useful ! I found that it can work with a DAW open at the same time, if I open the DAW first ( Studio One 3 here) I just select a midi track in Studio One and then I open your editor, it sends a few messages like some midi is missing BUT then it works very fine . Most of editors I’ve tried ( I’ve got one for a VS prophet) can’t work with a DAW open a the same time.
    So when synth editing is needed you have to quit your DAW and the reload it.
    For sure don’t change this beautiful feature. Thanks again for your work. Regards

  7. Thanks Rob. It’s very encouraging to hear this. I haven’t received any feedback apart from yours, so I am guessing “no news is good news” but I have no idea if it is working on any other system apart from mine (and yours).

    Again, thank you for the compliments and I am very happy to hear it is useful for you. My JD990 has a very dim display, so I had avoided using it until I developed this and accessing the SR-JV card expansion patches was also difficult. Not so much now. I’m also working on a panel for the JV1010.

  8. Works really nicely here. like the poster above said this really allows you to modify a patch in in your daw in the mix. I have it with the vintage synths card and accessing its patches is really super convenient as well.
    what would be nice to have though is some way to automatically recall a preset in the daw. right now you either save it seperately on the jd or manually as a .syx file.

    • Thanks Frankie13,

      I think I hit a wall with that. I had trouble running the program in Cubase as a VST (that’s what you mean, right?). So that opened up a whole new can for me when developing the panel. So I released it as standalone only because I thought it was working as a panel.

      But I intend to go into that in the next version. When I do it would be great to get some input from you as to whether it is working. I’ll need some time as I am a bit tied up right now, but thanks for writing!

  9. Hello dnaldoog, glad that you feel less isolated, you’ve heard maybe of Solaris, he’s made some banks for the JD990, he seems to be a great fan of the JD, I’m sure he would appreciate your work. For the bulk dump the user memory is the only one needed . I also forget to tell you the access you managed to the SR-JV ( I got the 04 recently) is a real relief from the painful standart Roland procedure.

    • Hi Robx21,

      Yes, I got the sysex information for the SR-JV-04 from Don Solaris’s website and was able to modify the code to load into the temporary patch on the JD-990. Glad to hear you and frankie13 are able to access the SR-JV-04. I almost never used to use it because it was such a pain to access.

      So I’ll need some time right now, but when I can I will put that bulk dump capability into a new panel.


  10. Just bought the 990 (nice to have it back again after 15 years) and am checking out your Panel.

    Seems to be working well so far, great job. 🙂

    A couple of comments/questions:

    The Waveform menus only show Internal WFs until a Vintage Board preset is loaded (and then they only show the Vintage WFs)… is it possible to add some sort of INT/EXP button that would allow to switch lists without loading and EXP board first (or am I missing something?)

    • Hi taoyoyo,

      I am glad to hear the program is working for you. I have been away from all this recently and set up the JD-990 to check your question and as always amazed by the sound!

      I read through your message several times and I think what you want is already implemented. Please correct me if I am wrong or misunderstood the question.

      There’s a combo-box drop down labelled ‘source’ under Tone Delay Time in the WG-(Wave Generator) section. If I select a normal patch from the JD-990 (not the card) or load the program and then select EXP, I think the waveforms from the card will then be listed in the ‘wavefrom’ combo-box above.

  11. Thanks for the JD-990 panel. Your panel was one of the reasons I got the JD-990. It wasn’t working for me until I restored the JD-990 to its factory settings. Now it works fantastically in standalone mode. The panel doesn’t work within Logic but that’s as advertised, no? Just want to make sure I’m not missing anything in terms of getting it to work in the DAW. Thanks again!

  12. Hi dubscura,

    I’m glad to hear this panel was one of the reasons you got the JD-990.

    I use Cubase and I never could get this panel to work with Cubase satisfactorily if at all, so I presume it doesn’t work in Logic. I want to get back to working on a new version, perhaps with a view to getting VST working, so no you’re not missing anything!

    When I finally get around to doing that, it would be great to hear how it works in Logic.


  13. Hi dnaldoog,

    It doesn’t seem to work in Logic Pro 9. Unless I don’t know how to use it?
    In “Modulation” tag, the parameters are all the same, whatever tone is selected. Pressing “SYNC with JD990” button doesn’t change anything.


    • Hi Pevets,

      I wouldn’t know about Eprom versions and whether they would affect things. Would doubt it. As long as the Midi sysex is the same, which it would be – there shouldn’t be an issue.

      Unfortunately, I don’t have Logic.

      I had trouble running this version under Cubase LE 9.5 as VST too, but it does work (to a certain degree).

      Can you load it as a VST instance at all? Is it just connecting to the JD-990 that’s a problem?

      Can you supply more detail? For example you have to mess around with the Midi Thru routing options in Ctrlr of the VST instance to get it working and connecting to the JD990 (in Cubase), but I couldn’t get values to be recalled on reload – that – I hope , will be fixed in the latest version.


  14. Hi dnaldoog,

    Yes, I can load it as a VST instance in Cubase LE, as I can load it as an AU instance in Logic Pro, both 9 and X, under Mavericks (but not under Snow Leopard).

    About the MIDI Thru routing options, it’s in the panel’s MIDI tab?


  15. Hi Pevets,

    Everything is working for me, so it’s difficult to troubleshoot the problem.

    If you want to change patches make sure …
    Rx. Program Change in the SYSTEM AREA is set to on.

    How to connect the JD-990 (VST) to Cubase: (※ I don’t think any Modulator settings are saved though)

    1. In Cubase, Disable †Midi-in **Midi-out ports to the JD990.
    2. Open JD-990 VST in an instrument track IN=(All Midi Inputs)
    3. Create Midi track IN=(All Midi Inputs) OUT=(JD-990 Midi-in) (I record midi notes & data to this track)
    4. In the VST Ctrlr panel connect to the †Midi-in and **Midi-out connected to JD-990 (you disabled them in Cubase ( See step #1))
    5. I found the only Midi-thru setting that needs to be checked was
      MIDI→Midi Thru→”Plugin-host->Output Device”
      (The 5th option down in the fold out menu).

    Hope this works for you and I guess this is not the only way to do this and maybe not even the best way.

  16. Hi dnaldoog,

    Everything works fine in Logic! I’m so happy! I didn’t try again in Cubase.
    Your previous answer helped me. It made me think. The problem was very simple to solve: I did not choose ‘Roland JD-990’ in the MIDI settings… I’m so ashamed.
    Thanks again for your help.

    Does it exist a function to extract the name of the patches? And do you think that a librarian function will be possible in the future?

    Best regards.

    • Hi Pevets,

      So glad it’s working for you, as well as is the bulk dump utility.

      The next version will have that feature, where it will transfer custom patch names to the panel (menu) as well as being able to save individual patches to any of the 64 memory locations on the JD-990 as well as incorporating the bulk dump functionality.

      I must be about half way through as I write. When I do release it, it would be great to get your feedback on how it works with your setup, which I don’t have.

      Kind regards,

    • I think very soon Bobcat. The coding is finished; just working on the interface and barring any bugs found during testing, I will upload soon. Let me know what you think when it is uploaded if you can.

  17. Thank you so much for this. I bought my JD990 a handful of years ago with the intention of mapping the parameters to a MIDI controller and spent countless hours trying to get it to work, but I could not for the life of me get it to recognize CC messages at all, but this Super Editor does exactly that right out of the gate (and I’m happy to report it seems to work as well with Reaper as it does stand-alone).

    One issue I do have is when trying to select patches from the panel it will say “Midi buffer full” and then “Exclusive Checksum Error” on my JD990. This happens whether with the VST in Reaper or stand-alone. I’ve tried increasing the buffer time in the “Misc” section of the panel but that doesn’t seem to help. Not a big deal though for me at this point, would be nice to be able to organize everything from within the editor but far from necessary, I’m still just stoked I can finally affect the parameters of this synth from my DAW. I’m excited to see how the saving and loading function in the next version.

    Thanks again, this work is much appreciated.

    • Hi Andrew – it’s so great to read messages like these! Thank you!

      Before I wrote this program I was just using the JD-990 as a Rompler basically, but in testing I find it does amazing things! The weirdest sounds just with random knob twiddling. I tend to save them all! I am thinking of writing a random patch generator for it. But, I have come to learn that the interface is actually not so bad; still a little tedious and saps creativity. And the display is rather dim on mine and on most units I believe.

      The next version allows for renaming and or saving to all 64 patches. I am very close to releasing it. Going from 99.9% to 100% is difficult – When it is released, it would be great to get any feedback from you and suggestions for better design etc.

      I have just reloaded version 1.7 and I don’t seem to be getting those Midi Buffer Full errors or checksum errors.

      I connect Ctrlr 5.3.201 -> Edirol FA66 -> Roland A-880 -> JD-990

      One thing that may fix the error is to reset the JD-990 back to the Factory Settings [Exit + Utility + Execute] – I think this has fixed the problem for me on several occasions and other weirdness that sometimes suddenly manifests. Try that perhaps, after backing up your patches of course.

      Let me know if that fixed it?


      • Yeah, I was surprised after I had attempted to get it to interact with my MIDI controller and failed, I then just started programming patches normally and found it to be surprisingly intuitive considering the limitations of the interface. But that said, having all the parameters at your fingertips is always going to be better than having to navigate through a menu.

        I tried reverting to factory settings but no luck there. The SR-JV80-04 patches seem to load perfectly fine though. I realize now that it’s a simple matter of selecting the patch on my JD and then just pressing the “Sync with JD990” button on the panel and I’m good to go, so it’s not too important for me to be able to change programs through the editor. I use a Roland UM-ONE MIDI-USB cable direct from the JD to my Windows 10 PC btw.

        I have run into another problem however, which I suspect is related and will be more problematic. If I select a waveform through the editor, or one is set via syncing, whenever I make a change to any other parameter the waveform jumps to “Syn Saw 1” on the JD, followed by “(no selection)” on the editor. If there is no waveform selected on the editor and I change the waveform manually on the JD then it stays on the waveform when I change other parameters. On the editor it shows the waveform going from whatever was set to “(no selection),” and this occurs even when no MIDI device is connected so it seems to be a software issue. For example, if I select the waveform “[5] Syn Pulse 1,” then I change the FXM Depth from 1 to 2, the waveform will change to “[1] Syn Saw,” and if I continue to change the FXM Depth from 2 to 3, the waveform will change to “(no selection).” This occurs with the VST, stand-alone, and loading the panel through Ctrlr.

  18. Hello Dnaldoog ! ( a few month later !…)

    I had left my JD990 for a few months.
    I came back to it today and unfortunatly now I can’t have my DAW Studio One and CNTRL running at the same time .
    It’s one or the other that takes control of the midi.
    Before as I told you , if I launched Studio One before CNTRL,
    I received some warning messages from CNTRL but still they worked together, communicating by midi. But now it doesn’t. I don’t use the same midi interface. That’s maybe why.
    So I tried to load it in my DAW as a VST and then appeared just a bit of it, all stuck in the right corner of the plug DUY…..
    That was the VST2 … I spent some time trying to find a solution .. fumbling in the prefs’ …
    And then I realized there was a VST3 version too, that had to be put in the right place ( common files etc )
    and then IT WORKED ! with full sizable screen !
    How beautiful ! How handy ! I didn’t know you had made a VST version
    Well done again !
    My two pence question:
    for the panel I use an old one from the V5 version.. Would it be better to have one from the V6 ?
    maybe it doesn’t matter at all ..

    Thank you very much for your help

    Roberto Basarte

    Windows7 Studio One 3.5.2.

    • Hi Rox21!

      Well it’s great to hear you are able to use the VST version. Thank you for your comments.

      I think the new version of Ctrlr is pretty stable. It seems most developers stick to 5.3.201 version, which is what I am doing, but I think it works in version 6.x.

      Unfortunately I have discovered (with the help of another user) a few problems with the panel you are using. Let us say it is 95% working, but there are a few issues, especially with the waveform logic.

      I am working on a new version that addresses these problems. I hope to be able to sort everything out soon – so please check back for a new version or interim version soon.

      Great to hear from you!


    • Hi jd800user – I looked into this, but the sysex code for the JD-800 is completely different. It would be a big job – I would do it if I had a JD800, but without one it would be too difficult to test. I don’t know of any other editor unfortunately. If you want to modify this panel I can help you, but you would have to know coding and it will keep you busy for the next several months! 🙂

  19. Hello! I seem to have a problem with the new version on standalone mode as well as on vst. It seems as the letters are somehow merged to each other on many areas. Also the colors seem not normal, for example there are buttons that I can barely see. I’m not sure how I can describe what is happening correctly, but for example what I see on my computer is very different from the screenshots here…the previous version didn’t have those problems.

  20. Hi projectwoofer, this is very surprising to me, because I have the exact same setup (Win 10 Cubase) and I have had someone else checking it with no problems like that. The only thing I can think of is the panel is using cached versions of the previous version’s images (Version 1.7).

    Try deleting the folder:
    C:\Users\%USERNAME%\AppData\Roaming\JD-990 Super Editor.

    Also the panel Ctrlr folder that belongs to the panel

    – Mine is named 8.jqXBaZZBknB, but make backups first!

    Let me know how it goes.
    PS I added a note about this at the top of this page

  21. Hello

    I just donwloaded the editor, but I can’t open the .dll-file. Do I need a separate program to open it? Sorry, if this is a stupid question but I’m a noob with this stuff.

    • Hi FinnUser,

      Thank you for trying out this panel. There are a few updates coming, so please check back soon.

      It is confusing, but the .bpanez file needs to be opened in the Ctrlr executable you download and install separately (Version 5.3.201 for windows). (1) Open the Ctrlr program (2) open the JD-990 panel from within the program.

      If you downloaded the dll (VST) version from SourceForge, (1) unzip the file (2) copy the dll file to your VST directory on your DAW. (3) Open your DAW and you should be able to access the panel as a VST file in an instrument track (if on Cubase).

      There is also a standalone version, which is a separate windows executable that doesn’t need the Ctrlr program. The VST (dll) files don’t need Ctrlr either when run in your DAW.

      Hope this helps.

  22. Hello,
    thank you so much for sharing this amazing panel – It made me rediscover my JD990… I have being using it with the vintage synth board in most of my tracks since I found your panel, couple years ago…
    Now I am using the world expansion and it would be great if I could change the expansion waveform list to the world waveforms…
    I tried to replace the combo contents with the world waveform names in an older version of the panel and it works but when I change the source to int and back to exp, it comes back to the vintage synth wav names…
    Is there a way to access the waveform list and change the waveform names so I can save a panel to use with my world expansion?
    I don’t need to access the world presets for now, only the waveform
    thanks again

    • Hi Claudio,

      I am happy to hear this panel has helped you rediscover the JD-990!

      If you go into the lua editor and open the file _waveform under category tables then replace the data in _waveForm2={} with wave names from the world list, then that should take care of the waves as seen on the menu.

      Of course make sure you compile ※ File->Save and compile.

      If you need to eventually add all preset information let me know.


  23. Hey
    Thanks for the fast answer – It helped me a lot – I have just finished replacing the names and it is working great…
    Yes – if it is easy like this last fix, I would like to know how to add the presets

  24. Hi Dnaldoog,

    Congrats on the new version. Looking good as a VST on OSX so far.

    I’m having issues with saving the panel as a (Restricted version) AU though:

    I’ll open the panel in the, everything renders fine but after saving as an au a lot of the elements are missing, replaced by ‘Invalid Resources’ warnings [ see image saved as link below ]

    I’m on OSX 10.14.4, using Ctrlr-5.3.198 and JD-990-Super-Editor_2_5_2.

    I’ve tried creating the AU from Ctrlr both in Logic 10.4.6 and Live 10.1 but get the same results with both. I’m mainly wanting to use your panel in Logic, otherwise the VST would do just fine.

    Any help you could offer would be greatly appreciated.



  25. Hi taoyoyo,

    Glad the VST is working.

    I can’t see that image you posted on dropbox. Can you resend it or change the permissions? Would really like to see it.
    UPDATE:: I managed to see it by removing the ?dl=0 from the end of the URL you provided.

    Your build is not locating the images folder: Did you click on Export->Export Restricted Instance? If you save as .panel then re-load that file back into any DAW, the images will be missing.

    I was able to build an AU file using Reaper. Can you try it out?

  26. Hi dnaldoog,

    Many thanks for your reply.

    I did originally create the AU build with Export > Restricted Instance.

    Just tried the AU file in the source forge link above… am still seeing the missing images here. [ Also tried another AU build with Export > Instance and had the same thing ]

    I had a quick look at Package Contents of both the VST and AU and did not see any difference in existing files / file size between the two… where would/should the missing images be located? [ Assuming the location is included in one of the files… possibly one of the Resources files? ]

    Again, many thanks for your time.


  27. Hello!!

    Thank you very much for creating this editor! it’s the closest thing to a VST editor for the JD990 which I recently purchased and it works pretty good! I was even able to import the JD800 factory presets to it with your dump utility!

    I had a question if that was okay: being able to tweak the factory presets is great, but is there a way to “Init” and create a custom patch from scratch with the editor? I’ve only just started to use it, so I might have missed it!

  28. Thanks gabecastro for writing and I am happy to hear it is working as a VST.

    There is no way to initialize the JD-990 to some default patch. But you could switch off every tone save one, then change the waveform to some preferred waveform; also switch off all A/B effects- this basic tone can then be copied over to the other muted/switched off tones if desired on the sys page (see copy button). Oh and save as sysex to computer for future use as a template. I think that’s about the closest you could get to doing what you want to do.

    Good luck!

  29. Thank you dnaldoog! I’ll try to give it a shot. If I’m able to create my own custom patches from scratch, then it’ll be like a real soft-synth or at least as close as it can get!

  30. What a awesome panel. Excellent job done here. Only thing i am missing is, to be able to control the panel via CC Knobs and Sliders from my Remote SL, that would be so heaven 🙂 .
    I know that this must be possible, because Kiwi did that, with their patch editor.

  31. I can only repeat myself, how wonderful your panel is. Your link is exactly what i asked for in my previous post. I even have a Roland JD-800 as a programmer for the JD-990, but there is the same problem: i cant record movements of the sliders in CC-Style etc.
    Now if i could control and record slider changes done with my Novation Remote SL Master-Keyboard, i would be in heaven.
    If you mind, i might have some suggestions:
    The points in each section (WG, TVF, TVA) should have the names of their corresponding sliders. If that is not possible, then maybe include graphics like it is on a JD-800 panel. Example:
    The points are also dissappearing (they are below bottom) with a value of zero. The points should always be visible imho. If you need graphics artwork or a new skin, i can really help.
    I have even more ideas, but i dont want to act like douchebag here. You did a excellent job here.

  32. If you carefully observe the graphics, how Roland did that with the JD-800, you will see that the arrangement of the sliders in your panel is different. For someone who is using the Roland schematic, your panel is not intuitive. This is i think just a cosmetic change, with way more value, because it makes it intuitive and it combines the logic behind the points and the representing curve.

  33. Hello,
    I am new on this site, new with a new JD 990, new in midi practicing and very interesting to your productions !
    i wabt to use it in stand alone first.
    I install the Ctrlr 6.0.1 in my w10 pro, I had put a midi/usb cable in the back of my JD990, restart computer and JD…
    The JD is on a separate hardware amplificator for earing the sounds.
    But when I start the Ctrlr, there is no control at all, I modifie the midi device in Ctrlr/MIDI, i choose “USB2MIDI” for midi IN and the same for midi out, I choose my keyboard (SL studio in USB) for controler, and I can ear the sound when I play on keyboard, but there is no change in the panel, it stay on the fisrt patch : I 11 Deep Seamphony…
    I had make a factory reset, it’s the same, no access, I can’t modifie a patch.
    My version of the JD990 is 1.01, I had command a EPROM with V1.05….
    Anyone can help me ? Thank’s you before.

    • Hi Gregorax,

      Thank you for writing!

      Before you do anything uninstall version 6.* of Ctrlr. It may be the latest version, but it has many problems, especially with VST and probably the Standalone instance.

      You need exactly version 5.3.201.

      It should then work!

      Please let me know if you still have problems.

      Also if you are using one of those cheap USB midi cables (I have one) they don’t work for sysex.

  34. Hi Genious Dnaldoog,
    I had uninstall the 6, and install rhe 5.3.201, but it does not allow me to install on my C; HD, may be my antivirus ?
    No way, so I insist and try to install on a other HD (I have 4 of that…) and I take normal midi cables directly on the sound card, and….Miracle, it’s working perfectly, I have the sound and when I had click on the synchro button, I saw my JD 990, and it seems to be connect, I will try now to create sounds…
    I am so glag, so happy, it is a old dream to manipulate the JD with a PC….
    I go direct make some big noises in my house, and try in vst to in Ableton live 10….I ‘ll be back tomorow to thank’s you again !

  35. Hello Dnagoog,
    Yes you are rignt, I had no problems to installed as administrator on W10.
    May be it’s me but on Ableton live 10, I had tried tu use the JD like a vst, I had find a Ctrlr-VST-Win32.dll and a Ctrlr-VST-x64.dll in my 64 bits-vst2 folder for Ableton. When I’had tried to open it like a vst in Ableton live, it’s ok a window appeared but impossible to synchro with the JD990 like in standalone mode and impossible to change the settings, I had a error message….It is possible tu use it in Ableton, someone had tried it ?

    • Ah I don’t have Ableton and was wondering how it runs in Ableton, but you say you can run the program, but can’t connect to the JD-990?

      Maybe try another Ctrlr panel and look at its settings if you have another synth and you can connect to it.

      If the program runs, it must be possible, surely?

  36. Running JD990 Supereditor v2.7.1 under OSX 10.14 with Ctrlr-5.3.198 both standalone and as a VST in Ableton Live 10.1.18

    It’s so amazingly good. Can’t thank you enough.

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.