I got these error and mentioned it in the webeditor thread already. Maybe you will find any solution for that. 
1 Like
Unfortunately the USB on my Blofeld is not reacting anymore, so I’m left without device to test. I’ve contacted Waldorf support. We’ll see what happens
Did you get this resolved? My version of @NewIgnis Blofeld preset seems to work OK with latest firmware. I can’t recall if I made changes but when I tested it today and it loaded fine. Here it is Electra One App
1 Like
@nemesis2049 Do check if you’re helped with my preset as published by @Kiwigrass. That could keep you going. I started making a new version last year, so I’ll be publishing an improved version in future, when my Blofeld’s USB gets fixed. I probably will have to send it in for support…
2 Likes
It works great! Thanks so much! 
But: Its MIDI Channel 8, not 9. 
Lovely to hear you’re helped out. I got my Blofeld working again last Thursday and now started to create an improved UI for Mk2
I am sorry @nemesis2049 for slow responses on the - duplicate references- issue. I actually identified the problem and the fix is included in the upcoming web editor update. I just had troubles to find a moment to communicate that.
1 Like
New version V4 for the Blofeld with UI enhancements.
I haven’t throughly tested it yet, but most changes are visual ones, so the logic should have remained the same. I find this version muuch faster to understand what the Blofeld can do, is doing ànd is not doing.
Please provide feedback, good or bad.
4 things on this 4 year old preset that still need doing:
- improve handling those different envelope variants
- clocked vs unclocked LFO speeds
- FX2 only in 2 rows instead of 3
- faster patch parsing
3 Likes
FYI
I use a standard color scheme in my presets, which I now adopted to this preset
- oscillators are orangish-brownish
- common oscillator controls: red
- filters: yellow (also the Filter EG)
- level controls : white or grey (also the AMP EG)
- glide : green
- effects : purple
- LFO’s: blueish
- patch control: purple
2 Likes
@NewIgnis Love the look of the new preset.
1 Like
@kiwigrass and @nemesis2049 ,
can you guys try out this version 5 ? please be careful though; it’s in beta.
It seems to suffer from unwillingness to parse, and it sends out strange midi when changing EG modes. So if you try it do this at a low volume to protect ear and gear.
What I want to know:
- does it still parse if you use it?
- what do you think about the new envelope visuals ? The graph are read only, but the controls now change dynamically. Any EG stage that appears in blue represents a part of the sustain/repeat part.
There 's one last part to do: show/set the patch name.
Quick test. It loaded fine. Parsed patches successfully. No squeals when changing ENV modes. The color changes going through modes and across EGs makes sense to me and appears to be consistent. E.g., if the Breakpoint is >= Sustain the ALDSDSR = ADSR. I hadn’t really played around with the modes much, but am loving setting breakpoint to 0 and using the decay time to adjust the speed of repeats in Loop S1 S2 mode.
1 Like
Wondering if it is feasible to add an option to sync the Amp Env and Filter Env settings? That is, have the option to make the Filter controls apply to the Amp CCs.
I can do that 
New public Version V5
It now
- parses the patch name
- provides a link between Filter EG and Amp EG. When enable, the link is still not mutual : after setting filter values, one can still change the amp EG values independently.
I had foreseen also to link the EG models between Filter and Amp, but this takes away some interesting possibilties so I decided against it.
If all that works out fine, I’ll do one last V6, which will make parsing much faster. I made the mistake of reading out the memory buffer, and that is rather slow because the memory is not immediately filled with new content when changing presets. Hence the built in waiting time.
What I will do is read out the chosen patch instead of the memory buffer, so we do no longer need to wait for the buffer memory. But all my parsing indicators must then be shifted, as the response header is not of correct length to make that work currently.
If you let me knwo all if well, I’ll start to work on it.
2 Likes
All is well. I see the patch name. The option to link Filter and Amp ENV shapes works. I did initially get a little confused because modes are not linked. For example, if Filter is ALDSDSR and Amp is ADSR then they both have a blue sustain fader, but it is actually the yellow Break point 1 fader on the ALDSDSR that will shift the sustain fader on the ADSR when linked. That is expected behavior, I just needed to stop and think about it. So, I’m pleased you didn’t link the modes as well. That is easy enough to do manually.
1 Like
Would it be possible to have the preset automatically parse whatever patch is loaded on the blofeld at start up? At start up the blofeld recalls the last patch used. Currently if, say, B 111 is loaded at start up I need to use the bank and patch controls to select B 111 to parse it. Maybe that would cause problems? Perhaps a “parse current patch” control? Just a thought and not important.
That is very easy to do manually: just press the upper right button. It just won’t show in the preset number, but you should get the right patch name anyway.
The name from now on will be a proof what patch you last parsed.
1 Like
I’ve now simplified the patch parsing, to speed up selecting patches:
- parsing is not automatic anymore. When you browse thourgh preset it goes very quickly because the controls are no longer updated. Also the patch name will revert to “PATCH NUMBER”, indicating the controls are no longer showing parsed info.
- then, by pressing the upper right button, the parsing is almost immediate.
I have a riddle however. The sysex manual says the following about request a dump of a particular patch:
2.11 SNDR
*****************************************************************************
SNDR 00h Sound Request
Upon reception of a valid sound request the Blofeld will dump the
selected Sound(s). The location is given in two bytes with the
following conventions:
BB NN Location
--------------------------------------------------
00 00 .. 00 7F Locations A001..A128
01 00 .. 01 7F Locations B001..B128
19 00 .. 19 7F Locations Z001..Z128 (*1)
40 00 All Sounds
7F 00 Sound Mode Edit Buffer
7F 00 .. 7F 0F Multi Instrument Edit Buffer 1..16
--------------------------------------------------
So the full format of a SNDR Dump is:
F0h, 3Eh, 13h, DEV, 00h, BB, NN, CHK, F7
where:
Index Label Value Description
-----------------------------------------------------------
0 EXC F0h Marks Start of SysEx
1 IDW 3Eh Waldorf Music ID
2 IDE 13h Blofeld ID
3 DEV Device ID
4 IDM 00h here SNDR (Sound request)
5 BB see above Location
6 NN see above Location
8 EOX F7h End of SysEx
-----------------------------------------------------------
Note that the checksum is omitted here.
*1: Note that the actual number of banks can be lower. Some
banks are reserved for future extension.
********************************************************************
When I sent
midi.sendSysex (devPort , { 0x3E, 0x13, 0x00, 0x00, 0x7F, 0x00})
the ‘Sound Mode Edit Buffer’ is nicely being sent back.
But when I sent
midi.sendSysex (devPort , { 0x3E, 0x13, 0x00, 0x00, bankNum, progNum})
nothing happens.
Any ideas?
One small thing I noticed on a patch I just loaded. The Filter MODE of the patch is ADSR but the displayed shape of the Filter EG is ALDSDSR. But it switches to ADSR shape when I move the Sustain fader. Not sure if that is a general or specific issue. Perhaps the shape picture is not updating correctly with the patch parse?
1 Like