I accidentally slid the SD card into my Iridium Keyboard in the first week. It’s very easy to do. Fortunately I was able to open the unit and retrieve it, but with the exposed contacts of micro-SD, I was pretty worried about it when it first dropped in. That aside - I love the Iridium. I got the keyboard because of the poly aftertouch. Otherwise the core or standard Iridium would have been fine.
Great walkthrough! I’m not sure if anybody mentioned it but you can filter patch types on the load screen by moving the top right knob (it says feature by default on that page but lets you cycle through types like bass, pad, etc). Preset loading has been a pain for a while now. Just a huge unmanageable list (I had the desktop, now moving to the Core)
Yes, there are filter by category, creator or bank. That’s how I’ve been organizing the preset - by tagging it with my custom tags. But still, search would be very handy.
Thanks for your reply. you inspired me to do a bit more digging and I found that you have to set the CC type in the faderfox to CCA1 (I think from memory) not CCAH. works perfectly now.
9:50 I don't understand what you did there with the bunch of midi map files...... is there more to it than being able to map up to 128 out of 3000 in a given moment? EDIT: oh I get it, you were somehow page downing thought the list of all parameters in batches of 128 rows in order to figure out it's 2500 altogether?
thanks for this - i've been trying to get my faderfox to work with the core without any luck. - i just used the standard midi learn cc method of mapping inputs using the cores midi learn function. But it doesnt seem to recognise the faderfox. Did you do something clever to make this work..
Nothing clever really, just connected faderfox via usb to Core, instantly recognized by core and map away. Editing the mimap file is just to make life easier. Oh one thing comes to mind - if you’re connecting via midi and not usb, faderfox is type A and core type B, so maybe check that…
@@xrcstrecordsIn the video, you said the Core midi connex are Type A, which is accurate.... Not Type B, as you say here 🤷♂️.... FaderFox is indeed Type B, so from FaderFox, type B adaptor --> regular 5-pin midi cable --> type A adaptor into Core 🤙🌌
Re: CC mapping, this guy over on elektronauts got all the parameters plus a step by step tutorial on CC mapping, check it out: www.elektronauts.com/t/waldorf-iridium-16-voice-duo-timbral-quantum-desktop/133191/1235
![[LIVE] : ONE ลุมพินี 89 | คู่เอก "ยอดไอคิว vs คิริลล์"](http://i.ytimg.com/vi/Z3vYkHJ_5Ig/mqdefault.jpg)
Finally, Someone I can relate to!Don’t want any more computer work at home, lol!
The iridium core WOULD be a great solution but the prices are all over the place, I often see them around the price of the Iridium table top.
I accidentally slid the SD card into my Iridium Keyboard in the first week. It’s very easy to do. Fortunately I was able to open the unit and retrieve it, but with the exposed contacts of micro-SD, I was pretty worried about it when it first dropped in.
That aside - I love the Iridium. I got the keyboard because of the poly aftertouch. Otherwise the core or standard Iridium would have been fine.
Great walkthrough! I’m not sure if anybody mentioned it but you can filter patch types on the load screen by moving the top right knob (it says feature by default on that page but lets you cycle through types like bass, pad, etc). Preset loading has been a pain for a while now. Just a huge unmanageable list (I had the desktop, now moving to the Core)
Yes, there are filter by category, creator or bank. That’s how I’ve been organizing the preset - by tagging it with my custom tags. But still, search would be very handy.
@@xrcstrecords You are 100% correct. :D
Thanks! I bought the connector from a local electronics eshop and than just soldered the barrel connector on the other end
Do you know when this track will be released from the science fiction club?
@@moe47988in a couple of months hopefully
Thanks for your reply. you inspired me to do a bit more digging and I found that you have to set the CC type in the faderfox to CCA1 (I think from memory) not CCAH. works perfectly now.
Glad you worked it out
very comprehensive review! where did you get your mini din to barrel connector? or did you make it yourself?
I just bought it from a local electronics shop and soldered the cable myself
9:50 I don't understand what you did there with the bunch of midi map files...... is there more to it than being able to map up to 128 out of 3000 in a given moment?
EDIT: oh I get it, you were somehow page downing thought the list of all parameters in batches of 128 rows in order to figure out it's 2500 altogether?
That’s basically it, yep
thanks for this - i've been trying to get my faderfox to work with the core without any luck. - i just used the standard midi learn cc method of mapping inputs using the cores midi learn function. But it doesnt seem to recognise the faderfox. Did you do something clever to make this work..
Nothing clever really, just connected faderfox via usb to Core, instantly recognized by core and map away. Editing the mimap file is just to make life easier. Oh one thing comes to mind - if you’re connecting via midi and not usb, faderfox is type A and core type B, so maybe check that…
@@xrcstrecordsIn the video, you said the Core midi connex are Type A, which is accurate.... Not Type B, as you say here 🤷♂️.... FaderFox is indeed Type B, so from FaderFox, type B adaptor --> regular 5-pin midi cable --> type A adaptor into Core 🤙🌌
@@darkuniversesoundyep, you’re right, it’s the other way around, faderfox is B, Core is A
Thanks.
Re: CC mapping, this guy over on elektronauts got all the parameters plus a step by step tutorial on CC mapping, check it out:
www.elektronauts.com/t/waldorf-iridium-16-voice-duo-timbral-quantum-desktop/133191/1235