using a MIDI-recorder with controls and GUI (start recording, play and stop SysEx patches).
Good afternoon Pomax! While searching for solutions for upgrading old synthesizers, I noticed your project as an idea for upgrading the built-in hardware for storing patches inside a synthesizer that does not have internal elements for recording and playback, such as the Korg DW8000; DS8; or, by analogy of the RAM card containing a bank of new presets for Roland JD800; so I became interested and had questions for the author of the code:
- is it possible to organize recording to a MIDI/SysEx file by sending a message to receive DUMP data via the USB-MIDI interface of a PC? And not write all the MIDI sequence events that are not related to the preset patch.
- is it possible to bring out additional file controls and GUI, or control MIDI events for scrolling and loading favorites for autonomous reading as an upgrade inside similar synthesizers described above?
regards, Vladistone
Regarding point 1, I don't see why not: MIDI is MIDI so you just need to record "everything" rather than just the note on/off and marker information that this code captures.
Point 2 isn't really related to the MIDI pass through capture process, that's just general programming.
You did not understand me or correct me if I am wrong in the hope of using your code!
- I am interested in the possibility of code for receiving SysEx DUMP with subsequent launch of recording to a file with the same name. That is, nothing extra except F0 ... to F7 with the assignment of a file name according to certain rules.
- And also the organization of a certain library for viewing and launching in a standalone synthesizer with the help of either an additional interface or interception of events from the synthesizer interface itself
Yeah, so:
1: As long as you write the correct byte listener, you can record any midi messages/data you want. 2: That's sounds like something you absolutely don't want to do on an arduino but on something like a raspberry pi instead.
The final version of the project prototype with optional attachments, which implies that depending on the amount of free ROM and code (including global variables and the necessary reserve of RAM space for reading MIDI files - I plan to use only for SysEx patches) therefore it is still necessary to choose between the implementation of an additional EEROM and LCD (although I do not see the point of installing an additional LCD screen inside the synthesizer...
- at least with a 3-segment screen you need to think several times where to install it *I think as a case analogy with the Gotek FDD emulator, from which I took a 7-seg. LCD as a donor), not to mention an additional LCD (at least 1602 or 2002 size. It has already been tested for displaying incoming information...) although you can imagine an option with a miniature 0.96 inch OLED screen... but I do not see the point of such ergonomics...
to create an autonomous repository of SysEx patches inside such synths that do not have any devices for storing additional SysEx lib. (the same Korg DW8000 and JP-8000. Maybe for Roland Jx-10 and Yamaha DX7 it will be possible to transfer to receiving and saving via USB protocol? I don't know) For now I am collecting code based on several sketches from your MIDI recorder and Arduino space. plus
- SD player with a small code for displaying a list of files on a 7-seg display using a rotary coder + SW (or HID remote control via USB) I can't say that all ideas will be implemented, because I have a complicated relationship with coding on Cpp *if you share your thoughts about bugs and possible problems on the way to implementing the plan?.. I will be grateful to you!
the only thing that bothers me at the moment:
- this is the fear that the Arduino pro mini 328PB ROM will not be enough for reliable operation *including for processing and sending SysEx files from the SD card via MIDI interface, with such an extensive periphery of the project.