# Roland JV2080 presets - any way to sell presets?

**URL:** <https://forum.electra.one/t/roland-jv2080-presets-any-way-to-sell-presets/4675>\
**Category:** Instruments\
**Created:** [October 25, 2026, 9:58pm UTC](https://forum.electra.one/t/roland-jv2080-presets-any-way-to-sell-presets/4675 "2026-10-25T21:58:31Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Moize](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.electra.one/moize/32/4716_2.png) [@Moize](https://forum.electra.one/u/Moize)\
**Post date:** [October 25, 2026, 9:58pm UTC](https://forum.electra.one/t/roland-jv2080-presets-any-way-to-sell-presets/4675/1 "2026-10-25T21:58:31Z")

</div>

Hello.  
I have finally finished my presets for the Roland JV2080 on the Electra One Mini. It was hard work that took eight months of writing, testing, learning the architecture of both the Electra One and the Roland, and thinking about how to bring it to the professional level I wanted.

I had been preparing for it for a few months beforehand. I bought the Roland JV2080 because I wanted equipment that would meet my requirements: I needed deep ethnic sounds and full control over them for live performances. But as a newbie, I didn’t know much about the limitations of controlling it via an external controller.  
It was a long journey: learning about them, trying Ctrlr plugins, trying to map them via Control Change messages, reading about CoffeeShop and MIDI Quest, and thinking they might work for me and my requirements. They didn’t. Nothing worked the way I wanted.

So I ended up here. I needed to build it from the basics, and I did. I don’t know how many hours I spent on it, but certainly a few hundred. I made two presets: one for Performance & Rhythm Mode and one for Patch Mode, which includes Performance part patch editing. Almost every parameter in the device can be controlled from the Electra One and an external controller via Control Change. Both presets work in the same way and can be pinned and used underneath/under the surface. Both are built on a Single Source of Truth architecture; before use, they just need data from the Roland. When the Roland sends information about the banks actually in use, everything is 100% synchronized - even if you change parameters from the front panel, the Electra updates the values automatically. There is no way to desynchronize it unless you change the bank.

Both presets have an advanced outgoing buffer to the Roland, so that it is not flooded with too many messages at once. Both presets monitor whether the buffer has accidentally created micro-desynchronization and update values on an ongoing basis, so no value drift can occur. When editing individual tones in Patch mode, we can edit up to 4 tones simultaneously, which causes a large increase in messages arriving at the Roland; here too the buffer has been dynamically adjusted depending on the number of tones being edited, so there is no possibility of flooding the old processor with messages, provided we do not frantically change values repeatedly from 0 to 127.

Both presets accept both full data dumps triggered from the Roland front panel and those triggered by dedicated buttons on the Electra or an external controller. They also accept single changes from the Roland front panel. All data is saved on an ongoing basis in the device’s RAM; even after changing the edited mode, the values are retained in the background at all times and can be returned to on an ongoing basis without re-querying the device for current data.

Both presets dynamically adapt to the declared expansion boards that can be installed in the Roland JV2080. It is enough to declare them in Lua code; the preset knows how to interpret these boards and how to adjust the relevant controls.

Each parameter can be assigned to Control Change mapping in relative Two’s Complement mode; in total, this is split across 4 editable MIDI channels, since we can assign up to 350 parameters to CC messages in total. When movement from an external controller is detected, the pages containing the edited parameters are automatically invoked, so we immediately have a preview of the values. Any collisions caused by several movements at once from an external controller have been safeguarded against.

The entire interface dynamically adapts to the currently selected edit modes.  
For example, it is enough to map the parameters for the LFO once, and with a separate control we define whether we are editing LFO 1 or LFO 2; with yet another control we define whether we are editing LFO 1 or 2 in Patch mode or in Performance mode; and with yet other controls we set which tones the change should apply to (the tones update in the background in a relative manner), so practically every parameter in the preset can have multiple interpretations depending on the operating mode we are currently in.  
This is built in a simple and intuitive way.  
All parameters present the actual ranges and text definitions exactly as in the Roland JV2080; values often change dynamically through many formatting functions adapted 1:1.

Frankly speaking, there are plenty of dependencies in both presets; I tried to include the most important ones, although most parameters have their own nuances and dependencies that improve use of the device.

It is possible that when I find more time, I will want to record a video explaining how the script works and more of the dependencies hidden in it; there is really a lot of it, I tried to use the maximum of the possibilities that Electra One offers - and there are an enormous number of them, and looking at it today, it was worth going that deep.

A simple introductory tutorial on using the presets:

> **A working preset supporting the Common Patch and Patch Tone sections for the Roland JV2080.**
> 
> Sound editing is supported both in Patch mode and at the level of individual parts in Performance mode.
> 
> To use the program correctly, and to support an external controller, the Roland JV2080 must:
> 
> - Have the default Device ID number 17 set
> 
> - RX Sys.Excl ON
> 
> - RX Control Change OFF _ **!!!** _
> 
> If you have EXP expansion boards for the Roland JV2080, you must declare them in the table
> 
> # **detectedCards = { }**
> 
> To do this correctly, we must declare the appropriate EXP board recognition byte used by the script. A table listing the recognizable boards and their corresponding byte values is located at the very bottom of this description.  
> The bytes must be separated by commas if there is more than one, for example:
> 
> # **detectedCards = { 0x01, 0x02, 0x03, 0x04, 0x05 }**
> 
> The script supports a maximum of 8 expansion boards, i.e. as many as the Roland JV2080. The order in which the boards and slots are declared does not matter to the script or to the Roland, but the correct order is recommended for your own convenience when reading parameters on the Electra One device.
> 
> …
> 
> # **The script supports CC mapping from an external controller.**
> 
> By default, the channel for the Common Patch section is MIDI channel 1, and for the Patch Tone section it is MIDI channel 2.
> 
> The channels can be changed; find:
> 
> # **REMOTE\_MIDI\_CHANNEL\_COMMON = 1**
> 
> # **REMOTE\_MIDI\_CHANNEL\_Tone = 2**
> 
> Then declare the appropriate target channel.
> 
> Each parameter and CC number can be defined.
> 
> To do this and to check the default mapping, find the following table in the script:
> 
> # **REMOTE\_CC\_MAP\_COMMON**
> 
> and
> 
> # **REMOTE\_CC\_MAP\_TONE**
> 
> and define in brackets the appropriate CC number that we want to assign to individual parameters.
> 
> Currently, only the relative Two’s Complement mode is supported.
> 
> …
> 
> # _ **To start using the Electra One device, we must dump the memory values of all parameters for both the Patch and Performance sections.** _
> 
> The request for this data should be initiated by pressing button ID 22.  
> Control ID 1900 is responsible for selecting the operating mode: Patch, or the selection of the edited Part 1-16 in Performance mode. The logic of the data dump for button ID 22 depends on the selected mode.  
> If we are working in Patch mode, the request will fill in only the data for Patch mode. If we are in Performance mode, the request will fill in only the data for all parts in Performance mode. To fill in the data for both modes, we must first press button ID 22 while in Patch mode, then switch the mode to Performance (regardless of the edited part) and press the control again.  
> From then on, all data and modes will be fully synchronized between the devices.
> 
> Remember that every time the overall bank for Performance or for Patch is changed, you must query the Roland again for the current parameter states, depending on the operating mode and the changed bank.
> 
> If we change the Bank for the Patch section, it is enough to query the Roland for the Patch section parameters.  
> If we change the Bank for the Performance section, it is enough to query the Roland for the Performance section parameters.
> 
> After data synchronization, changes on both devices are monitored on an ongoing basis, regardless of whether the changes are generated by an external controller, by the Roland JV2080, or by the Electra One device itself.
> 
> …
> 
> # **For the Common Patch section:**
> 
> Parameter ID 22 requests that the Roland JV2080 provide the Common Patch and Patch Tone section data; both sections are updated simultaneously, depending on the Patch/Performance operating mode.
> 
> Parameter ID 1900 selects the current operating mode: Patch, or Performance per selected Part.
> 
> Support for all parameters related to the general Patch section and the send mixer for individual Tones.
> 
> Full support for the Reverb, Chorus and EFX sections depending on the operating mode. According to the Roland JV2080 architecture, in Patch mode 1 EFX block is available for editing, whereas in Performance mode we can handle 3 EFX blocks: A, B and C.  
> The ability to select the appropriate Source for each EFX block in Performance mode. Which part uses which EFX block is defined separately in the script supporting Performance & Rhythm mode on page 1.
> 
> Since the Roland JV2080 does not provide Source settings for Chorus and Reverb, the only possible way to copy these parameters to Performance mode, to the general effect block, is via Utility → Copy → Effect from the front panel of the Roland JV2080.
> 
> Support for CC messages in relative mode, by default on MIDI channel 1.
> 
> …
> 
> # **For the Patch Tone section:**
> 
> Buttons ID 151-154 allow selecting the Tone currently visible on the screen. This is not equivalent to editing the visible layer; it is only for preview.
> 
> Buttons ID 101-104 allow selecting the Tones currently being edited. It is possible to select several edited Tones at once, regardless of which one is currently visible on the screen. We can edit 4 layers simultaneously. If no layer is selected, no parameter can be edited; this prevents value desynchronization between the devices.
> 
> Support for CC messages in relative mode, by default on MIDI channel 2.
> 
> …
> 
> **Addresses of Individual EXP Expansion Boards:**
> 
> **0x01** : Pop — Adds 145 sound banks and 224 WaveForms
> 
> **0x02** : Orchestral — Adds 255 sound banks and 174 WaveForms
> 
> **0x03** : Piano — Adds 111 sound banks and 73 WaveForms
> 
> **0x04** : Vintage Synth — Adds 255 sound banks and 255 WaveForms
> 
> **0x05** : World — Adds 255 sound banks and 255 WaveForms
> 
> **0x06** : Dance — Adds 255 sound banks
> 
> **0x07** : Super Sound Set — Adds 220 sound banks and 255 WaveForms
> 
> **0x08** : Keyboards of 60s/70s — Adds 255 sound banks and 255 WaveForms
> 
> **0x09** : Session — Adds 255 sound banks and 206 WaveForms
> 
> **0x0A** : Bass & Drums — Adds 204 sound banks and 241 WaveForms
> 
> **0x0B** : Techno Collection — Adds 255 sound banks and 255 WaveForms
> 
> **0x0C** : Hip Hop Collection — Adds 255 sound banks and 255 WaveForms
> 
> **0x0D** : Vocal Collection — Adds 128 sound banks and 94 WaveForms
> 
> **0x0E** : World Collection ASIA — Adds 168 sound banks and 148 WaveForms
> 
> **0x0F** : Special EFX — Adds 204 sound banks and 100 WaveForms
> 
> **0x10** : Orchestral II — Adds 255 sound banks and 100 WaveForms
> 
> **0x11** : Country — Adds 255 sound banks and 247 WaveForms
> 
> **0x12** : Latin Collection — Adds 255 sound banks and 141 WaveForms
> 
> **0x13** : House Collection — Adds 255 sound banks and 255 WaveForms
> 
> _Minor discrepancies may occur between the number of added banks and WaveForms and reality; if so, simply decrease or increase the limits in the EXP\_CARD\_PATCH\_LIMITS or WAVE\_LIMIT\_TABLE arrays_

> **A working preset supporting the Performance and Rhythm sections for the Roland JV2080.**
> 
> To use the program correctly, and to support an external controller, the Roland JV2080 must:
> 
> - Have the default Device ID number 17 set
> 
> - RX Sys.Excl ON
> 
> - RX Control Change OFF _ **!!!** _
> 
> If you have EXP expansion boards for the Roland JV2080, you must declare them in the table
> 
> # **detectedCards = { }**
> 
> To do this correctly, we must declare the appropriate byte by which the script recognizes the EXP board. A table listing the recognizable boards and their corresponding byte values is located at the very bottom of this description.  
> The bytes must be separated by commas if there is more than one, for example:
> 
> # **detectedCards = { 0x01, 0x02, 0x03, 0x04, 0x05 }**
> 
> The script supports a maximum of 8 expansion boards, i.e. as many as the Roland JV2080. The order in which the boards and slots are declared does not matter to the script or to the Roland, but the correct order is recommended for your own convenience when reading parameters on the Electra One device.
> 
> …
> 
> # **The script supports CC mapping from an external controller.**
> 
> By default, the channel for the Performance section is MIDI channel 3, and for the Rhythm section it is MIDI channel 10.
> 
> The channels can be changed; find:
> 
> # **RHYTHM\_MIDI\_CHANNEL = 10**
> 
> # **PERFORMANCE\_MIDI\_CHANNEL = 3**
> 
> Then declare the appropriate target channel.
> 
> Each parameter and CC number can be defined.
> 
> To do this and to check the default mapping, find the following table in the script:
> 
> # **REMOTE\_CC\_MAP\_PERFORMANCE**
> 
> and
> 
> # **REMOTE\_CC\_MAP\_RHYTHM**
> 
> and define in brackets the appropriate CC number that we want to assign to individual parameters.
> 
> Currently, only the relative Two’s Complement mode is supported.
> 
> …
> 
> # _ **To start using the Electra One device, we must dump the memory values of all parameters for both the Performance and Rhythm sections.** _
> 
> The request for this data should be initiated by pressing button ID 23 for the Performance section and button ID 24 for the Rhythm section.  
> Remember that every time the overall bank for Performance is changed, you must query the Roland again for the current parameter states of both sections.
> 
> If you change the Bank for the Rhythm section, it is enough to query the Roland for the Rhythm section parameters.
> 
> After data synchronization, changes on both devices are monitored on an ongoing basis, regardless of whether the changes are generated by an external controller, by the Roland JV2080, or by the Electra One device itself.
> 
> …
> 
> # **For the Performance section:**
> 
> Parameter ID 23 requests that the Roland JV2080 provide the Performance section data
> 
> Parameter ID 10 selects the currently edited Part for pages 1 and 2.
> 
> Mixer support for all 16 parts.
> 
> Support for CC messages in relative mode, by default on MIDI channel 3.
> 
> …
> 
> # **For the Rhythm section:**
> 
> Parameter ID 24 requests that the Roland JV2080 provide the Rhythm section data
> 
> Parameter ID 27 determines the currently edited Key Note
> 
> Editing of every possible parameter for the currently selected key.
> 
> Support for CC messages in relative mode, by default on MIDI channel 10.
> 
> …
> 
> **Addresses of Individual EXP Expansion Boards:**
> 
> **0x01** : Pop — Adds 0 banks
> 
> **0x02** : Orchestral — Adds 0 banks
> 
> **0x03** : Piano — Adds 0 banks
> 
> **0x04** : Vintage Synth — Adds 0 banks
> 
> **0x05** : World — Adds 1 bank
> 
> **0x06** : Dance — Adds 2 banks
> 
> **0x07** : Super Sound Set — Adds 4 banks
> 
> **0x08** : Keyboards of 60s/70s — Adds 0 banks
> 
> **0x09** : Session — Adds 8 banks
> 
> **0x0A** : Bass & Drums — Adds 4 banks
> 
> **0x0B** : Techno Collection — Adds 8 banks
> 
> **0x0C** : Hip Hop Collection — Adds 8 banks
> 
> **0x0D** : Vocal Collection — Adds 0 banks
> 
> **0x0E** : World Collection ASIA — Adds 4 banks
> 
> **0x0F** : Special EFX — Adds 4 banks
> 
> **0x10** : Orchestral II — Adds 0 banks
> 
> **0x11** : Country — Adds 5 banks
> 
> **0x12** : Latin Collection — Adds 5 banks
> 
> **0x13** : House Collection — Adds 8 banks
> 
> _Minor discrepancies may occur between the number of added banks and reality; if so, simply decrease or increase the limits in the WAVE\_LIMIT\_TABLE array_

Nevertheless, I would like to raise a less pleasant issue, which I included in the title of the post.  
I know that this goes beyond the standards of the community here, I respect that people share their work with others, thanks to which this device can be quickly adapted to one’s own needs without additional costs; for most people interested in synthesizers and music equipment, it is obvious that we treat this as a hobby, not paid work, and often it even consumes financial resources and never pays back.  
By nature, I am not a fan of so-called micropayments, but from the perspective of time, sacrifices and nerves it cost me, I am not able to simply share this for free.  
I was aware that for more professional programs for controlling the Roland I would have to pay quite a lot anyway (by my living standards), but they would not provide me with what I expected 100%, so I decided to create it myself.  
Speaking selfishly, I did it primarily for myself, and although I would very much like to share it with others, I am not able to give my work away for free. Everything I have achieved in my life I had to work hard for, and my life has never been easy; it has always been a lonely struggle with my own ambitions and with an environment that was unable to meet them. It would probably have been easier for me to create this if I were a programmer; it might ultimately look neater and much more professional, but it fulfills its purpose, which I am extremely happy about, and I would like to share it.

And here is my question. Is there any future possibility of sharing paid presets? In such a way that copyright could be retained and they would not suddenly be shared for free without authorization? How much money would users be willing to spend for the ability to use such a preset? I am not able to determine the level of advancement of other presets available on this site, because I do not have the devices to test them in practice, but from what I have seen so far while reading Lua scripts, they do not seem very advanced.  
I guess that coming out with such a proposal may meet with criticism; so be it, but this was not an escape for me after hours spent at work. My obsessive personality comes down to the fact that I spent a huge amount of time on this, often in total isolation, at the cost of taking a normal job, which ended in large debts. I do not know whether I will not end up back living in a garage, which I have already gotten used to, because things have never gone too well for me, and often wrongly set priorities, such as music, have brought me to the very bottom more than once, which has actually become my everyday reality.  
For this simple reason, I decided to ask whether there is such a possibility to benefit from the work I have done by sharing what I have achieved using the capabilities of the Electra One device.

Best regards and thank you for your understanding.

---

<div class="post-metadata">

**Author:** ![oldgearguy](https://avatars.discourse-cdn.com/v4/letter/o/f4b2a3/32.png) [@oldgearguy](https://forum.electra.one/u/oldgearguy)\
**Post date:** [October 26, 2026, 10:17am UTC](https://forum.electra.one/t/roland-jv2080-presets-any-way-to-sell-presets/4675/2 "2026-10-26T10:17:00Z")

</div>

Here is my opinion after building editors/apps for various hw platforms like the Lemur and Electra One and also creating computer editors that require purchasing.

People are reluctant to pay for editors these days. In the past, I had a few hundred Lemur apps downloaded, all with a ‘freeware/donateware’ model. Total income = $0.

There have been a few people here that have voluntarily sent me some money for my work.

Total sales of the 2 editors I made for the computer: less than 25.

My suggestion - take the Electra One work as a learning platform and convert it into a computer-based editor and see if you can monetize it that way. Given the amount of AI assistance and the rapid advancements, I don’t see a future in creating paid-for editors on any platform.

You might be better off keeping your work private and creating banks of new presets and selling those. People seem to want to buy presets but not the tools used to make their own.

Creating apps here was done from the beginning knowing they would be public. I spent a couple years creating the PCM 80 and 81 editor here. It’s here for anyone to use and RE and create it on other platforms.

I probably have more to say, but this may help spur additional discussion from people that have created a lot of Electra One tools.

---

<div class="post-metadata">

**Author:** ![oldgearguy](https://avatars.discourse-cdn.com/v4/letter/o/f4b2a3/32.png) [@oldgearguy](https://forum.electra.one/u/oldgearguy)\
**Post date:** [October 26, 2026, 11:20am UTC](https://forum.electra.one/t/roland-jv2080-presets-any-way-to-sell-presets/4675/3 "2026-10-26T11:20:31Z")

</div>

I read your post again and I believe you are not correct when you say most presets here are not complicated.

Some (like mine) involved reverse engineering the sysex dumps that are not documented anywhere. I know @kiwigrass , @NewIgnis and others have invested a lot of time and energy into their presets.

The presets that interact with the computer apps and DAWs are amazing engineering feats and the authors keep them updated.

That is also another area of concern. When you charge for a product, they’re is an understanding that you will make some effort to fix bugs and continue to support it across hardware and OS updates. Just more to consider.

Obviously you can decide what to do, but @martin has been clear that the Electra One is an open platform and will continue that way.

---

<div class="post-metadata">

**Author:** ![kiwigrass](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.electra.one/kiwigrass/32/4983_2.png) [@kiwigrass](https://forum.electra.one/u/kiwigrass)\
**Post date:** [October 26, 2026, 11:55am UTC](https://forum.electra.one/t/roland-jv2080-presets-any-way-to-sell-presets/4675/4 "2026-10-26T11:55:16Z")

</div>

I spent this weekend building a couple of sequencers. Their complexity are beyond anything I could have imagined tackling before @martin 's new AI assistant feature of the offline editor. It allowed me to spend my time thinking about design rather than how to wire it up. In short, AI will make building complex presets much easier for E1 preset developers going forward. I’m happy to pay for that ability. I don’t expect renumeration.

---

<div class="post-metadata">

**Author:** ![martin](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.electra.one/martin/32/145_2.png) [@martin](https://forum.electra.one/u/martin)\
**Post date:** [October 26, 2026, 12:19pm UTC](https://forum.electra.one/t/roland-jv2080-presets-any-way-to-sell-presets/4675/5 "2026-10-26T12:19:46Z")

</div>

even though I totally understand your points and where you are coming from, I think that the E1 is not a good platform for that. there are several reasons:

1. it was really designed as an open platform. Not only to encourage to share work but designed that way. It is easy to get preset files out of the website as well as to download them from the controller. There is no mechanism that would prevent that. Not only that users can share the presets, but there are other projects that use public presets from E1 for their own purposes. The E1 project started with my personal frustration of not having a chance to control my gear using one and ideally non-computer device - something like you mentioned. The idea of sharing everything was to change that for like-minded people and possibly help other projects or products go that way.
2. The total number of controllers sold is getting close to 3000 now. Given the 6 years of production, it is not a significant number. The audience for paid presets is small (a potential buyer needs to have both, the controller and the MIDI device in question, and they must be willing to pay).
3. Given the AI developments, especially recently, suggests that the hardwork on the presets will be reduced. This does not necessarily mean that you will not be able to potentially sell presets, but the support, workflow, etc will become more important aspect. Not talking about E1only now, web-based editors, computer applications, hacked/repurposed existing hardware have impact here. I would say that this again reduces the audience, as @oldgearguy @kiwigrass said.

On the other hand, I was many times asked to help with customizations, making presets tailored to specific setups and integrations, and even hardware mods. We, as the company, did not charge money for that, but I know other users who do this for others too and get paid. But of course, it is different type of business.

---

<div class="post-metadata">

**Author:** ![Moize](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.electra.one/moize/32/4716_2.png) [@Moize](https://forum.electra.one/u/Moize)\
**Post date:** [October 26, 2026, 5:02pm UTC](https://forum.electra.one/t/roland-jv2080-presets-any-way-to-sell-presets/4675/6 "2026-10-26T17:02:15Z")

</div>

(post deleted by author)

---

<div class="post-metadata">

**Author:** ![Moize](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.electra.one/moize/32/4716_2.png) [@Moize](https://forum.electra.one/u/Moize)\
**Post date:** [October 26, 2026, 5:02pm UTC](https://forum.electra.one/t/roland-jv2080-presets-any-way-to-sell-presets/4675/7 "2026-10-26T17:02:51Z")

</div>

I understand and respect that, as words from more experienced users and programmers. I know the current reality of AI programming, and I don’t want to go too deep into that; I don’t have time for it, and I don’t have more devices right now to make other presets. Maybe I will make one more in the future, but it’s not truly important to me right now. I’m not trying to find a way to earn a profit every day. Anyway, when I said I don’t think the presets here are too advanced, I didn’t mean that users spend little time on them or make them without finesse. I just think that, mostly, they are not offered as much as they could be, compared to the possibilities of the Electra One - which only shows how advanced that controller is. I think that, because I’ve made something much more practical, just as I wanted, it would be nice to share it. But after years of making things for people and expecting nothing in return, that taught me not to give myself away.

Thanks for your response. Either way, I’ve made what I wanted; sorry I can’t share it. Maybe in the future, if life shows me I’m wrong in my thinking, but I don’t believe in miracles.

Greetings and have good day, we can close that topic.