Sure thing man, I‘m on version 3.0.1, panel version 0.04, keybed version 0.07
I can try to update later on and give the whole thing another try if that helps you, no problem.
Sure thing man, I‘m on version 3.0.1, panel version 0.04, keybed version 0.07
I can try to update later on and give the whole thing another try if that helps you, no problem.
Thanks, no rush! I’d just downgrade myself and test on that but I have no idea if that can cause problems when you’ve got presets saved with newer versions.
Hey guys, Thx for this.
I’ve just seen the NRPN mentions:
News to me, is there any documentation around (it didn’t pop up in a quick search)?
cheers!
Updated to v3.2.0
Lag is still there in Legacy mode (maybe even a bit more pronounced), but still no crashes regardless of what I do / combine (OSC1 + OSC2 + OSC3)
Trying this out I‘d say there‘s definite need for optimisation for the Legacy mode but what you’ve got going there with your device I would suppose includes some underlying hardware issue. (But I’m not an engineer so it’s a punter’s guess)
Do you still have the original box the Iridium Keyboard came in? It’s supposed to be kept & used for warranty claims (secure packaging etc), should be painfree to send it off if you still have that box
Thanks again, I’ll see what Waldorf say.
Yeah, I do have the box… Not that I put a huge amount of confidence in that flimsy foam they use though! The problem is, it was bought used (no clarity on warranty as yet) and although Waldorf are responding I’ve had radio silence from their UK service place for 3 weeks after the initial email exchange which is pretty disappointing. Tried a couple of gentle, polite requests for some kind of update in that time and nothing. It’s weird because I’d dealt with them before and had no issues at all.
Plus it sounds like someone else with similar issues was without theirs for a couple of months and even just insured postage is brutal these days. Fully covering it up to what I paid would be about £75 just in one direction.
Trying all I can to resolve it without resorting to starting a Paypal return because I don’t want that hassle but if it comes to it, that’s what I’ll have to do.
I see, sorry to read this. It’s such a nice and premium instrument, must be a real bummer to have spent all this money on it and then have it act up in some way. If I were you, I’d get on that PayPal Return ASAP, even if you end up not returning it I’d register the issue with Ebay/PayPal so that the seller can’t claim you caused the issue down the line. I myself have been too lenient with this sort of stuff in the past and it usually came back to bite me down the line.
Shame to hear about Waldorf’s UK customer service also!
It’s a downer for sure. Probably good advice on the return front, diagnosing it has dragged on despite my best efforts since there a lot of variables on this synth and some degree of instability widely reported, you’ve got to wait for responses from support etc. etc. I wanted to fully grasp the situation first (you’ve helped a lot there) because I don’t anticipate the seller being helpful based on my interaction with him so far.
I’ve been past the eBay 30 days for a while but Paypal give you much longer, I probably should do as you say but I’m dreading it really. Never had to do it before in all my years buying/selling and can’t shake the feeling I’ll somehow end up the one buyer who comes off worse in these things
Wanting to try the keybed was a lot of the motivation in buying it and I love that as expected but wasn’t sure how I’d get on with the synth side of things because I generally prefer more focused ‘do one thing and do it really well’ stuff. Kernels is mainly what I love but I’m also seeing the general usefulness of it as a bit of a Swiss army knife. Maybe the other stuff will still be more front and centre but anything else that needs doing, this will very likely do it!
Just to close the saga, Paypal today told me to return the item and I should get a full refund. Relieved that I have to send it back to an eBay address and not to the seller so there shouldn’t be any shenanigans.
Edit: Argh, I was wrong - it says eBay on the recipient but it’s his address. Oh well, fingers crossed it goes OK.
Appreciate the advice I got along the way
I’m not sure I’ll look for another Iridium since it sadly feels a bit tainted after all this stress… But at least I know I definitely want this keybed in something.
I said this way up in this thread (two years ago), but it bears repeating here: I bought an Iridium (Desktop) that had a serious hardware issue fresh out of the box (froze, wouldn’t fully boot up). I returned it (bought it at Guitar Center for this very reason–so I could return it). Lucky for me, they had another one in the warehouse, got it a few days later, and it has since been very, very solid, after two years of use and several firmware upgrades, and is still, without question, my favorite hardware synth. Now, I have an Osmose and can’t wait to hook them up together to see what they can do.
I for one will be very interested to hear about that, please keep us posted
I have in the past connected the Linnstrument and Push 3 to the Iridium for modulated sounds using their MPE capabilities. Very easy to set up and use, especially with Iridium’s delightful and very accessible modulation UI.
Just purchased a desktop off eBay hopefully no problems with it when it comes in but I’m curious has anyone encountered any issues running multiple iridium patches at the same time as far as voice stealing.
Thinking maybe like long release pads and a crazy arp.
Sixteen voices seems more than enough I could see the 12 with the core maybe posing problems but just curious.
It’s such a joyful synth😍
Still holding out for VST Editor though,
I’m feeling positive
No problems here 16s plenty !
I remember watching a Loopop video reviewing Wavestate’s firmware version 2.0 that came with a VST editor and he said something like a hardware synth that requires a VST editor can be a sign that the synth’s UI is not adequate on its own (I may be getting this wrong, but I think that was the gist of it). In the case of the Wavestate, which I love in theory for its potential, this was absolutely true. I even use a separate dedicated monitor right above it with the VST editor running to tweak things so I don’t have to use its tiny screen to access its incredible (and without the editor opaque) depth. In the case of the Iridium, I truthfully can’t see the benefit of a VST editor. The layout of the synth, and its overall connection to the screen, which is large, touch-enabled, has knobs surrounding it, is basically a totally hardware-dedicated VST in the Iridium itself. This is precisely why it is my favorite hardware synth–I can fairly easily do everything I want with it, despite its depth and complexity.
Nothing wrong with the iridium at all.
But definitely would be faster recording automation in an editor of some sorts rather than the faff with mapping cc’s.
Ken fit I mean cov?
First day with an iridium. Super stoked
But plz tell me there’s a way to turn off the colors on the pads for the desktop one.
Not sure if you can turn them off but you can definitely dim them down.
Iridium not hand right now but
Global:Settings:General (p170)
LED Brightness: controls the brightness of all LEDs from 0 to 100%.
(my emphasis)
I did some digging and I guess you can change all the pads to the same note which will turn them all to the same color.