Thanks, but the Matrix 6 isn’t one of mine, but I’ll take all the credit of course. lol
1 Like
With the PCM70 the display is changing which helps (at least in the beginning) if the correct parameter is changing according to the value at the .1
Do you know it the parameter on the PCM81 will be changing if it is showing at the display of the PCM81 and it is changed using the .1?
Yes - I believe that you will see the change if you have it dialed up on the PCM screen.
It’s been a while since I had the 70 around, so my memory is always a bit suspect. The PCM 80/81 MIDI documentation specifically mentions the display does not keep up with the remote edits.
On the flip side, the Korg DL 8000R and AM 8000R do jump around and so does the Waldorf XT, so it varies. You should be able to hear the immediate change on the 81 though.
As mentioned I was giving the preset another try today and besides the odd “Cannot store data as requested” message everything works fine and as desigend (as far as I can tell).
Thanks again for the great support 
OK, you still have a MIDI loop that needs to be fixed. Until that is correct, nothing will be working 100%.
So, do this:
unplug the Electra One from the computer.
Use a USB power adapter and connect it to the Electra One.
Verify you only have the PCM 81 connected (in/out) to the Electra One port 1 (out/in).
Power up the PCM 81.
Power up the Electra One.
Now you should be able to Sync, select patches, and edit and never see the “Unable to save” message.
Once that is working, try the same thing with the PCM70. Something on your computer is causing a MIDI loop, especially if you unchecked all the routing boxes on the Electra One.
I double checked all settings as mentioned by you.
-USB Power supply for .1 no connection to PC
-Direct MIDI connection between .1 on PCM81
-First power up PCM81 then .1
Unfortunately still getting message “Cannot store data as requested”
Not sure what else to test…
So there is something in the E1 that is sending the message back to the PCM 81.
When the E1 is hooked to the computer, and you bring up the web UI, in the Controller section, make sure there is only the single PCM 80 preset in the slot. If there are any other presets in any other banks/slots, remove them. I know this is a long shot, but we have to look at everything.
In the Router section, make sure it looks like the attached picture (Electra OS 3.6.1).
You have to understand - this preset (and all others) have been tested by the developers before being made public. Unless there is something fundamentally wrong/changed with the preset, basic operation should be working as designed. The only way you are getting that message on the PCM 81 is because the program you downloaded is from the register (factory presets) area and the E1 is trying to send it back to save it.
Maybe try re-downloading the PCM 80 1.04 preset and load that into your E1. I am on travel until Monday night, but I did load that preset and connect my PCM 81 to it and it worked as designed before I left.
Sorry for the delay of my reply.
I checked the routing page several times in the past and every time it looked like the pic you posted.
I went ahead and deleted all presets and installed them again fresh from the preset library.
With the empty .1 I checked the routing page again just for kicks and guess what suddenly the MIDI IO Port 1 was forwarded to MIDI OUT 1 !!!
Of course, I changed the setting and redeployed the PCM80 preset and the “Cannot store data as requested” message disappeared and the preset worked flawlessly.
As I mentioned in earlier posts the router page of the .1 looked always correct . What beats me is why it changed (or showed as changed) when I deleted all the presets.
I tried to recreate the behavior and installed and deleted presets again and again to see why it happened but to no avail.
I was not able to recreate it and the routing page shows the MIDI 1 OUT/IN “un-routed” and the PCM80 preset worked every time during the test.
I wonder if there is something wrong with my .1 since I also observe hang-ups/freezing during using presets when buttons stop responding and I need to unplug it from USB power or the fonts starting to getting dimmer and dimmer until they barley readable and I’ve to perform a “soft reset”.
Thanks again for your awesome support and let’s continue on the PCM70 thread…
See below for the lockups. The fonts getting dimmer is a problem I have never seen, so maybe there is a hardware problem with your Electra. Contact @martin about it to see if it is a known issue.
Thank you for tracking down the issues on your end. There is something about the Electra Configuration and presets and OS versions. I do see that sometimes my configuration changes unexpectedly, but I thought it was due to changing between multiple OSes and multiple web URLs (app.electra.one, app.electra.dev, the beta site).
If you are editing a patch and the Electra locks up and needs to be rebooted – it could be due to a problem in the PCM 80 preset editor. If you can remember or repeat the steps that caused it to lock up, that will help me diagnose the problem.
In general, a lock-up/freeze should never happen and it is usually due to a coding error. So, having the OS version and the steps that you were doing before the freeze would be great. Even if you said “I was editing PCM 80 program 3.4 DoubleTap and changing reverb parameters and it froze” that is still helpful.
It is very difficult for any developer to test every parameter and every combination of edits, so feedback from users is a great way to make the preset work better for everyone.
Just wanted to chime in that this in its current state works flawlessly on my E1. It really is a great preset, I’m having tons of fun.
One question: why are most controls “greyed out” until one touches the corresponding encoder (usually, afaik, all parameters within the row selected by the three left buttons light up)? I thought it might be because not all parameters are in use in all the PCM presets, but they all seem to spring into their colored state, and stay that way, whenever the parameter is adjusted. Until switching page again.
Best,
Magnus
Magnus - my E1 does not behave that way. I am running OS 3.7.0f and this is my UI settings for the controller
Well, to be fair, my e1 locked up a few times right after posting my previous message 
while displaying other visual artifacts.
I thought I did a factory reset just recently when I downgraded the V4 beta back to stock. So haven’t time to use it much yet, but it only done that using the pcm preset. I believe it might’ve locked when tweaking Patcher settings on the pcm; those settings might’ve still not be ready? Believe I read something about that here.
Anyways, awesome preset despite any hiccup; having a control like this changes the machine completely for me 
That’s high on my list to work on when I get a chunk of free time in mid-March. The patch system is fragile trying to mimic what happens inside the PCM 80. Hopefully, my time away from it plus Martin’s improvements will help get it up and stable.
2 Likes
I’ve started looking at the patch matrix stuff. Some of it actually works as designed, but a lot of it is very shaky. I know why folks can have issues, especially when changing patch destinations and when (accidentally) changing the number of data points from some number to 0 and then back.
I’ll continue looking at it and will post a ‘it is updated, give it a try’ message when I stabilize this section.
4 Likes
I’d say that unless one’s able to make it work reliably, I’d rather be without it… But good luck! From what I’ve read about the patcher in the manual it seems like a kinda outdated, complicated way to treat modulation. Maybe I haven’t understood the potential
I cleaned up a lot of it and it is working much better.
What I hesitated on (was going to post this afternoon before heading out of town) is that when you change the Target, the PCM somehow reassigns values based on what was there before.
I need to tweak to adjust that, and handle when a user creates data points and then changes their mind and doesn’t want to save them.
What’s up there is much more solid than before with the caveat that changing the Target of a patch can lead to weirdness/errors.
When it’s actually fully ready and tested, I’ll speak up again.
1 Like
Great stuff! Looking forward to it..
Made a lot of progress. Last thing (I think) is adjusting the max range of params as the algorithms change (needed to re-scale the patch values for each point).
Made a lot of changes to the patch area - hopefully adding some better visual clues and definitely more correct coding. lol
I’ll need to add some screen shots and text info to get new folks oriented to how that area works.
If you’re really bored and/or just need to take a look, you can grab the 1.05 version that is up there now.
but – it’s not quite 100% (close but not there)
2 Likes
I decided to make it private for a while. I’m making too many changes/explorations for it to be stable for the moment.
As an aside, I know why no one has ever made a full editor for the PCM 80/81 before…
3 Likes
OK, after a lot of cleanup, I think it is working much better.
I listed it as version 1.10 and it has been initially tested under beta Electra OS 4.0.0.p
Special notes for the Mod Patch page:
- When you edit a patch and change anything (patch source, destination, number of data point, source position, target value for that point), the main Patch button across the top will start to flash.
- If you want to keep your changes, press that same button and it will turn red and save the changes.
- If you want to discard the edits, press any other patch button.
- When changes are made to a patch, the label area above the patch button will invert to indicate that you have local changes that have not been sent to the PCM 80. You must select that patch and press the Send button (or save the entire patch as usual) to update the PCM 80 with your changes.
- To edit the data points of a patch, press a data point button and adjust the source position and target value.
Oh, I also added a feature that lets you tap on the ‘Preset Selection’ control (on the screen, don’t tap the pot) to jump between banks. So if you’re on P0.3 and tap, you’ll jump to P1.4, P2.4, etc.
NOTE - I’ve done some testing on this and there are things I’d love to eventually add like an undo, better reverb page organization, and more robust handling of the ‘patch changed’, ‘patch not sent’ indicators.
Have a play with it and let me know what you think.
5 Likes