Replies: 7 comments 20 replies
-
|
Great list! Some of these should be fairly easy to do I think. One that might be tricky is the pitched samples. It is possible to some extent, but the pitch control would be somewhat coarse and non-linear. But it would be interesting to try, just to see how it can be used. It might also be possible to do this by resampling the audio before transferring to the NESizer. When you mention rate of Env Mod, isn't that really just a question of changing the attack and decay parameters, or am I missing something? |
Beta Was this translation helpful? Give feedback.
-
|
After adding the checks for device ID, I'm still having intermittent issues loading samples via SysEx, but I think it may be MIDI-OX problem. I have made some changes in a local branch to the way NESizer parses SysEx messages which makes patch changing via SysEx work perfectly, but it is still screwy with sample loading. Tonight I'm going test loading samples using ALSA amidi on my Linux machine and see if that helps. Might also try clearing all my NESizer settings and RAM because I have been pumping it full of garbage. I'm still trying to rule out buffer overload / race condition. I also fixed a bug in the way the 7seg display function displays error messages, by adding a function which can display arbitrary combinations of LEDs with a comment block that shows how to use it. When I have unborked my SysEx sample loading I'm going to implement: |
Beta Was this translation helpful? Give feedback.
-
|
Looking for some feedback on ProgramChange patch select feature: I just noticed that in FL Studio the program change drop down menu is labeled 1-128, but program 1 sends 0x00, program 2 sends 0x01, program 3 sends 0x02 and so on. In Cakewalk they aren't numbered at all, just labeled with the General MIDI instrument set. My keyboard pads are configurable to send PC# 0-127 so that's how I programmed it. I have mapped them to 0-99. Is that how y'all want it? Or do you have a 1-99 preference, where 0 is just left a default patch or something? |
Beta Was this translation helpful? Give feedback.
-
|
I'm a big ol' dummy and just now realizing that documentation says nothing about patch/bank exporting/importing. Is this possible? I'm not too confident my patches will survive an extended period of time. If there's no current way to do this, I'll have to add this to the top of my wishlist, along with pitched sample playback, for as janky as it may be. :) |
Beta Was this translation helpful? Give feedback.
-
|
@jeff464 On the midi CC side you will need to change the value by increments of 14, I believe, but I haven't tested this. Looking at the code it has a possible 9 values and these will be broken out over the range of 128 for midi CC. Could you test the Octave shift on the actual device, page 5 in the manual? That will help track down the issue. |
Beta Was this translation helpful? Give feedback.
-
|
Added "tables" to the wishlist. Not sure how feasible this is, though! |
Beta Was this translation helpful? Give feedback.
-
|
Added "sample channel offset" to the wishlist. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
After (finally!) being able to play with this for a few hours, I had a few ideas come to me. I'm not sure how feasible any of this is, so take these suggestions for what they're worth.
Idea: Ability to save MIDI channel voice assignment per patch, instead of globally.
Why: Some patches require stacked voices, but there doesn't seem to be a way to un-group the assignment if I need those voices separate later in the song.
Idea: Ability to hear parameter adjustments in real time when editing on the unit itself.
Why: Currently the user has to make adjustments blindly and it's not until one clicks "ok" that they're able to hear the change. MIDI CC adjustments are real time - it would be a quality of life improvement to have that on hardware as well.
Idea: Ability to create arps per voice/patch.
Why: Currently the user has to create the arp manually in the sequencer, and this may not always be an option. Famimimidi allows arp creation per patch, and it would be great to see that here.
Idea: Table for pitch, etc on an instrument level - think LSDJ or c64
Why: Famimimidi has this baked into some of the presets and it allows for modern sound design, interesting percussion, and delays. This might require a massive rewrite, so not sure how possible this is.
Idea: Noise loop mode placed at higher octave, opposed to having a separate mode.
Why: LSDJ/mGB has the different noise modes available as different octaves as standard and it allows for seamless switching during the song, instead of entering a different mode during playback. This way allows a greater variety of possible rhythms.
Idea: Pitched samples
Why: Most of the charm of sample playback is what it does to higher/lower pitches. It would be nice to either set the playback pitch of the sample on the NESizer, or set the ability to allow for key ranges where the user can place samples at different pitches.
Idea: Sample channel offset
Why: It looks like MIDINES had MIDI CCs implemented for sample offsets, etc. This allows for interesting effects like time stretching and wave scanning. I'd love to see the sample channel receive more attention. MIDINES info can be found here: https://wayfar.net/0xf00000_midi_chart.php
Idea: S/H & Noise shapes for LFO
Why: Because it's fun.
I'm certain I'll have more ideas pop up as time goes on. Also, it's very possible that some of these might already be possible and that I may have missed something in the posts here/manual. In that case, my apologies. ;)
Completed/implemented features since the original post:
Program change over MIDISeparate LFO shapes per slotBeta Was this translation helpful? Give feedback.
All reactions