search

eclab / edisyn

Synthesizer Patch Editor
Apache License 2.0
551 stars 51 forks source link

Roland JV-2080 support #70

Open boonier opened 1 year ago

boonier commented 1 year ago

Hey there, just stumbled upon your editor. Thanks for making it!

I see that Is the editor for the JV-80. I have a 2080. Off the top of your head, do you happen to know whether they are similar in the spec? I'm a dev and willing to port/create an editor for the 2080; maybe I could use the JV-80 as a starting block?

Cheers

eclab commented 1 year ago

My understanding is that the JV-880 is roughly similar to related units such as the 2080. And Roland's sysex approach is pretty consistent. But I have never examined them for sure. I imagine it'd be a good place to start. Send me mail if you get stuck.

On Oct 12, 2023, at 6:19 PM, Si Mills @.***> wrote:

Hey there, just stumbled upon your editor. Thanks for making it!

I see that Is the editor for the JV-80. I have a 2080. Off the top of your head, do you happen to know whether they are similar in the spec? I'm a dev and willing to port/create an editor for the 2080; maybe I could use the JV-80 as a starting block?

Cheers

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.

02FD commented 1 year ago

I have a JV-1010 now which is internally a JV-2080, just without sub outputs and only having 1 EFX slot. If you need testing done on the JV-1010 I can definitely provide it!

Unlike 80s roland gear the JVs don't have any errors in the sysex charts in the manual to my knowledge, with the exception of the rack modules receiving (but not interpreting) the arpeggiator section.

boonier commented 1 year ago

Thanks I will give it a try when I can carve out some time! I seem to remember the Ctrlr panel for the JV range encompasses the range from 80/880 - 2080, so maybe it's fairly straightforward? I'll fork this repo and keep you posted if I get anywhere.

Cheers

boonier commented 1 year ago

Just looking at the 11.2 Setting Up the Development Environment section in the manual. Is this still relevant?

I've successfully built from the makefile, but what's the standard environment setup?

I'm on macOS. I've coded some Java (nice language actually), but I'm not too familiar with the setting up of a Java project. I already have JVM installed, but I changed some bits in the code and then run make all then make run to see the changes. Do I have to do this every time I want to test it?

I'm using VS Code as the IDE.

Thanks!

eclab commented 1 year ago

Edisyn is pretty bog-standard Java. The one gotcha is its binary files: edisyn/Manufacturers.txt, the various .init, .html, .png, .jpg, .txt.gz, and .txt files, which need to be in the .class directories corresponding to the .java directories. If you compile on the command line, that's not an issue as the .class files appear next the .java files. But most IDEs nowadays move the .class files to a separate target directory but don't realize that there are binaries that need to be moved with them. Yes, setting up the development environment section is still relevant, I checked.