Once you find a program to load, use the Electra One “Get Patch” button to load the Patch into the Electra.
The get patch button is the upper right soft black button to the right of the touch screen.
I try to use the standard Electra things when possible.
I know the instructions are a bit sparse. Basic sequence - press Sync, wait for the PCM to sync and display the patch select control, scroll through the factory and user patches and when there’s one you want to edit, press the Get Patch button. If everything is working, in the blue bar in the upper left, you should see the patch name. Once you’re done editing, go to save and try saving.
Note that I’m on travel, so I have the E1 with me, but not the PCM 80
Get patch button - brilliant! This just keeps getting more and more fun…
oldgearguy - you asked for bugs/issues reports: in the “Save to: R x.x” section, It’ll only let me save to R 0.0 thru 0.9; anything above that (R 1.0 thru 4.9) results in the PCM81 displaying “Operation Failed”. Not a huge problem for my workflow, but you did ask…
Thanks for that report. I may have a couple moments to look at that. Might be simple
Glad the explanation made sense to you and that it worked. I do need to put basic usage guides together since a lot of my presets have a similar approach to displaying and editing and syncing gear.
It’s still a work in progress and there’s a lot I’d like to tweak, but I’m quite burned out with this particular preset. Hopefully what is there is enough to help make the PCM editing process easier.
Since I still have a pair of 81’s and an 80, I am going to get back on it eventually.
One of the early big challenges was parsing both the 882 byte packed format and the 1421 new format in such a way that the result could be used easily. The patching matrix part is still rough and I’m sure there’s some other parameters that need work.
That and a lot of non-existent documentation about the sysex layouts for each algorithm beyond the original 10.
(To be fair, Italo did provide additional documentation after I had most of it reverse engineered, so it did help to correct a few things and fill in some gaps)
OK - finally got a bit of time to install this preset and have a go.
I’ve got USB connected to my Mac and two midi cables connected to the E1 (Midi 1 out/in) and PCM81 In/Out.
When I press the Algorithm Sync button basically nothing happens. Interestingly I also don’t see any activity on the E1 port labels (USB Device, USB Host, Midi1 Out, Midi 1 In, Midi 2 Out and Midi 2 In).
I’ve done a Midi Reset on the PCM. If I do a 3.8 Dump Current Program on the PCM In see the Midi In show activity on E1 but no patch is displayed. I do however see 1421 bytes of Sysex transferred (in the web app Midi Console)
I’m new to the E1 to if I’m doing something stupid forgive me!
Sorry - I’ve been off line most of the day.
First - you are using an Electra One Mk II, right?
Next - you are using the PCM 80 preset version 0.99a ?
Link: Electra One App
Lastly, in the PCM 81 menuing, press the Control button, then use the up/down arrow buttons to go to the MIDI section (3.x).
Make sure 3.3 Pgm Change is ON, 3.4 Automation is OFF, and 3.7 Sysex Receive is ON, press the Load/* to make sure device ID is 0, and I have dump speed 3.9 to Medium.
I just pulled down that version and connected up a PCM 81 and it syneced and was ready tograba and edit a preset.
Having worked through the thread I noted a post with some troubleshooting content.
I cleared down all of the presets in E1, pushed the preset 0.99a to E1 and then repeated with the debug screen open.
About 10% of the time I would get a blank screen on E1 i.e. no preset. The balance of attempts would (say 5%) give the following LUA error;
06:14:06.026 loadLuaModule: error loading file: filename=ctrlv2/slots/p000.lua, error=ctrlv2/slots/p000.lua:66: unexpected symbol near ‘,’
I then deleted the preset again and pushed it directly from the preset link above. Copied the preset to my library, opened the debug screen and pressed the send button. First try gave the error above again and then second gave;
Pressing Sync then worked and I got the following in the debugger;
06:29:14.574 lua: we received a heartbeat response
06:29:14.674 lua: sending heartbeat
06:29:14.794 lua: Device ID: 0.0
06:29:14.796 lua: Version: 1.00
06:29:14.796 lua: # RAM pages: 16
06:29:14.797 lua: program banks = 6, register banks = 1
06:29:14.797 lua: Number of algorithms: 17.0
06:29:14.797 lua: Card present? No
Selecting a patch and pressing the Patch request button now works and I think we’re good to go!
Others have said it but this preset is amazing and I can only imagine the amount of work that went into to getting it to this point. The code itself tells a story… thanks so much!
Thanks for being tenacious and working through things.
Yes - I have seen the error message 06:14:06.026 loadLuaModule: error loading file: filename=ctrlv2/slots/p000.lua, error=ctrlv2/slots/p000.lua:66: unexpected symbol near ‘,’
before and have never been able to track it down. It appears that the preset Lua code is such that either some stack is getting overflowed during the initial parsing/load or something being initialized in the beginning is getting some unexpected value.
I have not tried running this (or any of my) presets against the 3.7 beta yet. I am constantly fighting my own bugs on the current stable production OS and am reluctant to introduce yet another variable. If I get some time this week, I may put the beta OS on one of my E1’s and see what happens.
I am always happy to hear back from people actually using the preset and welcome suggestions/bug reports on what is there.
My current focus has been wrestling with the Eventide H3000 and trying to determine the best way to represent all the possible parameters across the algorithms. But I always can make some time to look into specific issues that folks find with other presets.
No problem at all and thanks for the support on getting me up and running.
The motivation for me was massive given that I’ve had this thing for over 20 years and always knew there was so much it could do if only I can get beyond the pain of the interface
I’ll report back the good and the not so good (if I find it) over the next couple of weeks as I intend to dig deep!
I was in the same boat. I had a PCM 80 (or two) many years ago and sold them out of frustration. I knew they were very capable boxes, but I didn’t want to just tweak a param or two for each preset, so I sold them off.
I would really love to know what is causing the sporadic issue. I do have a debug-equipped E1, but it would require some significant time to get the environment spun up and everything in place to test it out, so I keep putting it off until I have more dedicated time (realistically early 2025) or until something obvious and repeatable crops up in the logging or on screen.
There’s still a chunk to be done on the preset, mainly in the Patch matrix area, but the bulk of the “normal” parameters and such should be solid.
As always - use and feedback encourages (re-)engagement.
I’m having fun with the preset already and have probably dug deeper in the morning I’ve had with the E1 and PCM than in all of the years as it’s just so easy to tweak now. It’s game changing for me.
In terms of feedback and things I find that you may (or may not) know already do you want me just to post in this thread or through some other method? I’m happy to do it any way you want as I’m keeping the debugger open as I mess and spotting a few things along the way. I don’t want to become a pain and I’m certainly not expecting you to do anything but you might want to know
As a heads up I loaded all of the factory patches this morning and there are a couple that throw LUA exceptions onload. I’ve attached a file as a heads up but as I say, this is more for your insight than action!
Best tactic at this point is to just keep a log with the basic info like:
Algorithm 7 (or Factory Preset # x.y), mid RT value wrong
patch 4.9, delay times cause error display
Algorithm 49 parameters x,y,z are missing
Also - any/all UI/use feedback would be appreciated like:
On Page x, I always want to start editing in the middle, so place the current position on row 2 to save a button press
or - I always edit these params in this order -A/B/C and you have them in different rows/different pages.
Once you have accumulated a chunk of stuff, you can either send me direct email or respond in this thread.
When I post an update, I’ll try to document what was fixed; probably in the response msg and in the preset description section.
I will say that at one point, I was convinced that the MID Rt calculations Lexicon posted in their documentation was not actually what they are using inside the PCM 80/81. That still may be the case, so keep that one particular value/param in mind.
on the current stable production OS and am reluctant to introduce yet another variable. If I get some time this week, I may put the beta OS on one of my E1’s and see what happens.