It was.m a pain but I got midi working!!!
Requires JUCE7 not JUCE8.
1 Like
OK @wavejockey and @Handsonicsuki I have 0.1.18.1-Beta incoming…
big Midi work done here super simple works fast… just have midi connected… it will detect and I believe you dont need to leave the plugin.
Just choose your channel, choose your device, and choose if you want to receive midi clock… if receiving midi clock it will override any bus clocks incoming.
This is on a per pad basis… Pitch, gate, velocity – etc etc all connect withdoing anything.
Check this out. Video added to discord channel
ok here is 0.1.8-Beta
GRID 0.1.8.1-beta
- Fixed MIDI: switched to JUCE 7 for SSP ALSA compatibility
- MIDI pitch working: note 60 (C3) = no shift, each semitone up/down shifts pitch
- MIDI velocity scales pad volume per hit
- Start/End CV accepts 0V as valid (was incorrectly rejected)
- Left/Right arrows now switch tabs instead of navigating pads
- Right shift is pure mute mode — hold for mute, release exits, no page switching
- Choke and reverse symbols enlarged for readability
- Choke triangle with letter inside, semi-transparent white, bottom right of pad
- Reverse arrow enlarged to 22pt, matching style
- Filename display slightly larger (16pt) and semi-transparent
- Context bar no longer overlaps BPM pill
- MIDI clock only selectable when device is connected
- MIDI clock auto-disables on device disconnect
- Improved internal MIDI device filter (case-insensitive)
- Removed unused diagnostic display code
1 Like
feels much more logical, natural 
i think we are getting there (to a full release version)
this is not necessary, all my plugins use Juce 8 (8.0.6)
due to the use of shared memory within juce, Id be slightly concerned that having 2 versions in use may cause some issues.
(though in fairness, in the past we got away with it, so it maybe ok)
a few important notes:
- you’ll need to be using my unofficial synthor build, but I assume you are already if you are using my current plugins
- I’ll be updating my midi implementation in next release to handle reconnects and other minor issues.
- my plugins are released with juce 8.0.6, untested on later, see below
- due to new llvm release, I will be upgrading to the latest version of juce
edited: to clarify juce 8.0.6 is ‘released’,
Im testing / fixing 8.0.12 this morning, and hopefully updating my midi implementation.
given 8.0.12 was released very recently, it may be I need to push back if there are issues.
I do have a ‘patch’ to 8.0.6 in worst case scenario.
watch my release topic for release and details
2 Likes
ok, Ive noticed 8.0.12 is broken… see my post here for my plans
note: as I mentioned above, I cannot say I’m very surprised, this is pretty common esp with juce on linux (small % of devs / users using) , usually they fix after a few months.
Wait wait wait. Hold yer horses. What unofficial Synthor build!?!?
@wavejockey the Config Browser. We are almost to the point that we have all the 1.0.0 major release features. And now it’s just bug testing.
Can you please review let me know everything you’ve found. Performance issues. Bugs. Quirks. Etc?
We are almost there at the finish line.
I’ve found the clocking issues. Midi clock doesn’t calculate correctly. A few other small things.
So added choke and reverse (I thought it would be cool using reverse and time stretch to create risers or end of bar stuff for turn around very quickly.
Also. You probably noticed. I changed the navigation. I didn’t think we needed both arrows and encoders. So arrows now are navigating tabs.
That leaves the up and down arrows.
Maybe a shift plus arrows to lower octaves of all pads or selected pads might be a cool
Performance feature
1 Like
the one supplied with my plugins, did you not read the README when you installed my plugins ?!
Im pretty sure, you must be using it, since as far as I remember just bringing up the UI will cause my plugins to crash without it 
I got my SSP Percussa from jeffy of the Rack Pack (i traded him my N.U.S.S system I had collected), and it already came loaded wit hyour plugins – maybe he installed it
In other good news I fixed my ER-301 which I thought was DOA… the little micro sd card (internal) tray must be worn… so I added some electrical tape to the Micro SD Card and it clicked in and stayed snug.
It lives to see another day, besides it occured the day I received the SSP and never had the chance to compare then side by side
this makes me wary about plugin’ the SD card in & out of the SSP multiple times / day 
Hey <@1023200363765059654> I got an idea.
What if arrow up and down keys changed “kits”. So you instantly have access to change your kits.
And then we can have an option that says change kit on next bar.
So we could use the up and down key to browse a list of kits (preset kinda thing) and left shift to “enter” or activate. If no buttons or knobs pushed or dialed then after 3-5 seconds you are moved back to your current playing kit. If you push enter you either change to that kit instantly or in the next X amount of bars
1 Like
@wavejockey inunderstand man. I been doing it often for this development.
And I just got in my USB to Ethernet adapter.
I wonder now if I could just plug a USB to my computer and it would mount the sd card.
I am sorry man. We ar esp close know tho
If you want I can buy you an Ethernet little adapter so you can continue helping me.
beta 0181:
there’s a problem with files with a sample frequency other than the SSPs native frequency i think
when i load a loop that is 96Khz (my SSP is set at 48khz) it will play double as slow
also, the time reported is not totally correct
e.g. sample 24bit, 96Khz is shown as 4.1s but in fact it is 4.9s
Ahh. I been working on midi and external clocking.
Ok. Let me finish up this.
And then I will fix the sample playback in relation to the differing sample rates.
This is a really amazing find. Thank you.
1 Like
I tested version 0.1.8.1.
I wasn’t sure if this behavior was intentional, but in the plugin UI, I can adjust the pitch over ±48 st range, while via CV it only responds over a ±12 st range, so they don’t match.
Also, when I change the DEVICE setting from a MIDI controller to “None,” I get a message saying “failed to open 0.”
1 Like
Ok so the CV range is a really great find… that has not been caught up. And the Failed message you are seeing. I am glad you brought this up as well, I have bee diagnosing it. And I see it with the same behavior switching from a plugged in USB device to None… I see it not every time though… it takes me like 2-3 switches… Thank you by the way – definitely looking at this.
To fix:
- input Pitch CV does not match on board Pitch controls.
- Failed to open 0: JUCE message occurring when switching from assigned MIDI controller to None.
keep em coming!