Unfortunately OS 3.2 has a bug with the parameter sequencer, so I rolled back to 3.01
Whatās the bug?
Iāve noticed with my Core and 3.2 that if I save a program/patch AND I save it with parameter sequencer as the last āopenā sequencer, then the next time I load the program, or after reboot or something that loads from the saved state, it outputs a low-rumble on the first step.
If I save the same program/patch, but with a different sequencer page as the last āopenā sequencer (step/arp/etc), the first step doesnāt have a rumble associated with it.
Just curious if the bug is that, or something else. If itās that, just save as above. If itās something else, Iād definitely like to know.
The bug is that the parameter sequencer just wonāt start with 3.2.
it is not running at all.
I know the pads on the Iridium get a lot of hate, but I donāt mind them, and use them to improvise quite a bit.
Has anyone managed to get the midi note data sent from the pads working in Bitwig?
I can see midi data sent from the pads being received with the amazing ShowMIDI, and have tried configuring in the controllers section using generic keyboard/controller scripts and also Driven by Moss Generic Flexi device, but Iāve not had a breakthrough yet.
Iridium price just dropped 500⬠@ Thomann. (1999 ⬠now instead of 2499 ā¬).
Maybe they want to boost sales before christmas or itās a sell-off and a new synth is on the horizon.
Changing the 12v Plug on an Iridium
I mentioned awhile back a temporary fix I made on the power cable when Iridium got stuck in itās boot-cycle.
I made a more permanent fix today as my cable failed me.
New plug and some layers of heat-shrink has made it feel a bit more reliable.
If anyone wants to know the plug-type and wiring config (the 4 pins are only connected to two wires) let me know and Iāll add that in.
You suggested that fix in response to me. When I got mine back from the distributor, working seemingly without intervention, other than a bench test, I decided to take your advice on this anyway, as Iād previously just used some Velcro to strap it to my Jaspers stand to relieve the strain.
I used Sugru to fashion a support piece around the plug/cable junction.
My Iridium has never had any further issues since it was returned, Iām still not sure what caused, or resolved my boot loop issue.
Yeah, Having now cut through the original plugās plastic layers (to see exactly what wires went where as continuity was clearly failing) I can say itās pretty weak in terms of support.
I just got a cheap 4-pin down the road as I didnāt want to wait for delivery but, once I finish this project, I may decide to lose another few cm of flex and go for something even more solid like this which has a crimping cable support.
Quite why Waldorf opted for this sort of connection is beyond me!
Looking very closely at the image, especially the arc of the black keys, and comparing that to several keyboards of my own. There is a resemblance to the shape of the Medeli Polytouch keybed in the Hydrasynth. Thatās the closest match of my keyboards.
I canāt be too certain of this, but the Medeli keybed certainly could be an option for Waldorf.
ADDED : And it turns out the poly-aftertouch keybed Waldorf uses is from Fatar.
I predict- existing synth but in keyboard form.
Iād guess itās going to be a keyād version of the M.
Ever since my experience with the Iridium Iāve been a lotā¦less excited about new Waldorf gear
What was your experience with the Iridium?
A QuandiriuM?
Under pressure ? I predict a beer machine !
I predict the Waldorf Mercury.
Im looking up James Bond characters to figure out a synth name
It is a coffee machine⦠the Waldorf Bialetti!