What started as an offhand remark from a friend about the DL8000R (and initially dismissed by me because the sysex looked challenging), turned into something that came together relatively quickly.
It got easier to finish once I actually bought a DL (but that’s another story).
These delays are known for their deep menus, encoders that get completely flakey to use, and their amazing sound when programmed.
So here is a working version that does everything but save the edited patch (that will come).
For now, I didn’t embed the factory or default user names because I’m trying to keep it small enough to run on the Mk I as well as the Mk II.
OK, I think I added the patch naming change and saving a preset.
Still some random cleanups here and there, but it seems fine (at least from my 10 minutes testing).
now back to my personal Sisyphean task known as the PCM 80
Some tweaks to the main, but, also added a Mk II only version. DL 8000R mk II only
What happens now is - when you first choose a preset to edit, I download all presets and the utility info.
This way, I can display all the preset (factory and user) names plus give you access to the utility config info and the ability to change between Tap Tempo and regular millisecond time.
The Tap Tempo stuff is currently out on Page 10, still making sure it’s stable, but it is there and seems to be working.
I will need to rearrange the Config, Utility, and Tempo controls to be less cluttered and more useful, but for now, I think this version is useful, so it’s out there for you.
There’s no documented way I’ve found to just grab the utility info, so I can’t do most of these extras on the mk I just yet.
It is still private, but for initial playing around, here you go: AM8000R
Some random caveats that I’ll be addressing – renaming a preset before saving kind of works, but the AM is stuck in the rename screen, so save doesn’t save the new name. Need a remote way to exit that screen.
For some reason, some AM8000R patches (mainly with Saturator as FX 2) will lock things up. I think the Korg MIDI documentation is not 100% correct (already fixed a few errors in it).
So if a particular patch locks up the Electra One, reboot and try a different patch.
Let me know if you like the way I decided to implement the FX 1/2 and Dly/Rvb algorithm selections
fixed the lockup and fixed the rename/save (ugly - still needs work).
Also added a FX 1 on/off button as a test.
still private - next week it’ll be cleaned up and finalized and made public.
As with the DL8000R preset, the very first patch you recall pulls back all the user patch names so that scrolling through stuff makes more sense. You need to wait a bit until the Electra screen shows the patch name and the fx1/2/rvb names then you’re good to go.
Note that you can pull back just 1 patch after that and in the Utility page you can set the option to just grab 1 preset, but there’s a downside to that because then there’s no way to grab all the utility parameters on the Utility page and you’ll have to set the FX 1/2/Rvb CC numbers manually to use the section on/off buttons.
There’s ways I can probably work this stuff, but I need time to think and that won’t be until the weekend.
How’s it going OGG? Saw you pushed an update to the DL8000R (V7), but wasnt sure what changed exactly. I saw the patch name/selector is in a new location on bottom left. Anything else notable? Thanks for working on this for all of us!
The latest version of the DL8000R is now here: DL 8000R v8
Any/all earlier links to the mkII version are no longer valid. I have not thought about porting changes to the mkI mainly because I’m overwhelmed with things that need to be done in the next few weeks.
The description has the changes. Give it a whirl and let me know. I did some consolidation of the pages. Hope it helps you navigate things a bit easier. There’s still a lot of parameters in this unit and I tried to more closely follow the general flow of the DL menus and block diagram.
The Mixer page is first and the tap delay times and modulations are on the Left Mod and Right Mod pages.
hey there - just playing around with this now. the new arrangement of pages is great!
I noticed something that seems like a bug. rather than use the left side buttons on my E1 to jog through the rows, I prefer to just touch the parameter directly to select it.
However, touching any parameter directly on this preset always shoots me back to the Config/Save page.
In the attached video, I am trying to select the BPM parameter on the Utility page. When I make contact, it shoots me back to Config/Save and opens the parameter in that same position (Pedal Mode > Down).
I’m not sure why it would behave like this, but noticed it in the last version too. Let me know if you have any ideas!
I’ll take a look. Probably some leftover code that I had pulled from another project in the event handling section. I will update this reply with what I find and/or update the preset.
Thanks much for giving it a spin and the feedback on the layout changes.
EDIT #1 - there’s nothing in the code that is specifically handling screen touches. No custom controls or anything. What OS are you running on the Electra? I have been developing/testing mainly with 3.7.0f (I think that’s the one - Electra is at home and I am not, but that’s close to the number). I have sometimes booted up 3.6.1, but I think all recent DL8k and AM8k changes/testing has been again a 3.7.x variant.
you guys - of course it’s all in good fun and I’ve implemented touch actions in the past (Waldorf XT Wave envelope, touches for short-cuts on various controls, etc).
That is why I was not sure if old/dead code was causing this problem. I see nothing in my code that would react to a screen touch. @martin - are there any new configuration parameters that would trigger events on a touch?
My code for events in this preset is very minimal:
-- event handling
--
-- NOTE: jumpPage() called first, then onPageChange()
events.subscribe(PAGES | POTS)
function events.onPotTouch(potId, controlId, touched)
if (touched == false) then return end
end
function events.onPageChange(newPageId, oldPageId)
curPage = newPageId
-- if (oldPageId == 10) then
-- pages.setActiveControlSet (CONTROL_SET_1)
-- end
end
so I’m a bit confused.
HOWEVER, I did rearrange a number of controls and the pages in the cfg/save, utility 1, and utility 2 pages, so it is possible I am trying to do something on a page/control that no longer exists. As long as all the other controls/pages are behaving properly, my best guess (pre-testing) is that the toggle between time and tempo is causing the issue.
shoot, my bad. i just realized I did load up the latest beta firmware, and I bet that has something to do with it. I will revert back to 3.7 asap and see if the issue persists.
tagging @martin as it seems likely to be a factor.
No worries. That’s part of the help @martin needs for stabilizing the release. To assist, - here’s the formatter() and function() code associated with the Time/Tempo toggle button (the button is on Page 8):
function dispMode(valueObject,value)
if (value == 0) then
return("Time")
else
return("Tempo")
end
end
-- flip between time and tempo mode
function timeTempoCC(valueObject,value)
local isVis = true
if (value == 1) then
bpmMode = true
isVis = false
else
bpmMode = false
isVis = true
end
for i=0,3 do
local left = controls.get(7+i)
local right = controls.get(59+i)
left:setVisible(isVis)
right:setVisible(isVis)
end
if (curPage == 8) then
-- control that sets the CC for the time/tempo panel button
local ctl = controls.get(292)
local timeCC = ctl:getValue("value"):getMessage():getValue()
midi.sendControlChange(portNum, midiChan+1, timeCC, (value * 127))
end
end
