Alesis and the ioDock Fiasco

the work of others.
EPIC FAIL: The ioDock cannot pass SysEx messages a fundamental part of the MIDI specification,
Alesis promised a fix, then failed to deliver, they also removed posts detailing how to gert redress in
the UK courts – reproduced again below.
Oh and if you are working for Alesis trying to get rid of the truth…. good luck because now it’s on the
Wayback machine and cannot be erased, have fun with the court case against them  – and oh yeah –
US courts have no jurisdiction in the UK.
TO CONTACT ALESIS:

Biography via lead411 wiki

edit
If you need @alesis.com email addresses for Alesis, LLC, you can find them on Lead411 as Michael Bernstein’s email might be available. Michael Bernstein, the company’s CFO, also has extensive data on the site, including Alesis, LLC’s facebook account, linkedin url, and biography. Los Angeles, CA-based Alesis, LLC can be found on Lead411 under the Other industry. You can add a unique bio including links to your social profiles using the edit link above. Description: Michael Bernstein is Alesis’ CFO. With a Lead411 subscription, Alesis email addresses ( @alesis.com ) of the executives are viewable. Other information includes Michael Bernstein’s email, phone, biography and extension. We provide information from your LinkedIn network, see company profile, and soon we will be showing twitter, wiki, and facebook profiles as well. Lists are downloadble into your email marketing software or crm software. Typical management titles include VP, Chief, Vice President, Director, manager, & more. Similar names to Michael Bernstein can be found in our people directory. If this is you and you would like to be removed, then click this link. Keys: Michael Bernstein, Alesis, CFO, @alesis.com , email marketing,

About Alesis

Alesis, LLC, is in the Other industry. Their main office can be found in Los Angeles, CA, and they can be contacted through Alesis, LLC email using the domain @alesis.com, some important contact info like linkedin data, contacts for cfos, etc of which can be found on their Lead411 profile….more Alesis info

Other Alesis People

Jay Schlabs – Director of Sales and Marketing, phone – 401-658-3131, updated on 01/26/2012 23:24:00
Their Director of Sales and Marketing is Jay Schlabs. Their Lead411 profile is categorized under the Other industry. If you’re checking for Alesis, LLC email addresses, these are also available on Lead411 with the @alesis.com email addresses and possibly Jay Schlabs’ email. Alesis, LLC is based in Los Angeles, CA. You can also get Jay Schlabs’ linkedin info, twitter data, and biography on their Lead411 profile. Their information is filed under the Other category.

Dante Cantalini – CEO, phone – 203-374-0162, updated on 08/27/2011 17:10:00
For Alesis, LLC email addresses with the @alesis.com format as well as facebook info, twitter, linkedin data, as well as biography data for Dante Cantalini, you may check in Alesis, LLC’s Lead411 profile. Dante Cantalini is currently the CEO for Alesis, LLC. The profile of Alesis, LLC on Lead411 is filed under the Other. Their main offices are in Los Angeles, CA.

If you live in the UK and wish to know your legal rights of redress (Alesis does not want you to) you may find the following of use

You have six years after purchase in the UK to make a claim, specifically in this case: goods not fit for purpose, and false or misleading advertising.
http://www.moneysavingexpert.com/shopping/how-to-complain
Alesis employees are here to help.
Paulius Volkovas

iO dock doesn’t send sysex messages. Is there a fix?

iO dock cannot send sysex messages. Is there a fix?

i tried to send sysex message from Midi Touch app with no luck. After i wearched the net and found that sysex messages are not working on iO dock.

21 PEOPLE LIKE THIS IDEA
INCLUDING YOU
This topic is no longer open for comments or replies.
  • sbangs (Community Manager) 1 year ago
    Hello, thanks for your interest.
    Unfortunately this is not a feature of the iO dock at this time.
    I will pass it on as a suggestion.
  • Sylvain Guiraud
    but that mean that the interest from it is hugely reduced than ( i own one already)

    because only the function to sequence the ipad app from midi is still available and you can’t control any other midi equipment 🙁 that’s a shame on such good quality product. is there a way to update firmware or something like that or should i sell directly my io station ?

  • Jef Durand
    Will sysex will be imolemented in an incoming upgrafe?
  • Paulius Volkovas
    any news on this subject? will it be updated?
  • jeremy coker

    4
    I’ve just ordered an IO Dock (UK) and to say that Sysex is not a current feature of the IO Dock is an escape clause… Sysex as I understand is fundemental in Midi and is expected (i.e. implied/assumed). If Alesis wish to continue selling this product with less people returning them…then it’s about time Alesis got their finger out and provided the correct midi implementations that have been around for 30+ years as standard from cheap modules of a few quid to a roland G8…

    Come on Alesis – pull your finger out…..

  • MrMike

    2
    I bought an iO dock last week and I was pretty suprised that it didn’t support Sysex when it states full CoreMIDI compatibility. This meant I couldn’t use the iO Dock to control various hardware synths and make programming templates in TouchOSC. I have since bought a generic non-Apple camera connection kit and class compliant MIDI / USB cable (under £10 for both) and this does transmit Sysex.
  • gerard

    1
    holy crap, are you guys kidding me?

    how can they say it is midi compatible then? As someone already pointed out, they way the io dock is described it implies sysex is supported…

    this is just nuts…

    i just found this out after coming here to get some help on the hiss/crackle/noise on the mic pres… looks like this is going back to the shop for a refund…

  • eyeball
    “Great” to hear this after weeks of trying to send sysex from MIDI touch to no avail. I blamed the software for that and not a professional hardware product from an experienced producer like Alesis. Now it’s too late to send the IO dock back. It must be a joke that I would have to buy the cheap camera kit to work with sysex data on my iPad. Without sysex support the IO dock is absolutely useless for me.
  • DBM
    +1 for this request . sysex is quite necessary for many many many of the popular used gear pieces that I can only assume makes up a decent percentage of your target market .

    Is it not possible due to the class compliant chip set , like the one used in the Akai MPK’s ? Or is it just a matter of coding ?

    Also if you guys ever do a MK2 of the i/O dock , USB HOST !!!
    The only thing keeping this from being the end all be all of devices for iPad ( aside from sysex ) is the fact that it can not act as a host for USB based devices …seams a bit of an oversight considering a real good chunk of controllers ( even some from the Numark brands ) are usb only .
    Note I want that + Midi din , just to clarify 😉

  • Sylvain Guiraud
    the most bad thing is that no one from alesis spend 5 minutes to reply us, is that teh new alesis support we should espect ?
  • Jonas Hardwell

    sad
    This is very surprising to me as well! Come on, Alesis, add SysEx support!

    I have a Moog Voyager that I was hoping to have some fun with my iPad 2.

  • lasse.thomasson

    sad
    1
    Very disappointed after getting the Lemur app ($50) for controlling Cubase via Mackie protocol and it’s not working. Can’t get any emulated “LCD text” since there is no sysex.

    Can’t see this mentioned anywhere in the sales documentation or specs here on the site. Only says MIDI/Core midi functionality.
    And too late to send it back.

    Not a happy customer (sort of understatment). Will not recommend!

  • Jef Durand
    Any news from Alesis about this?
  • This reply was removed on 2011-12-13.
    see the change log
  • Sylvain Guiraud

    1
    seems that nobody at alesis care about it, i will sell this useless products that cost me much more than a basic usb kit and cable to at the end get nothing working . how can they pretend a midi support without the sysex 🙁 such a pitty really
  • Matthieu Vlrm-oux
    We NEED sysex ! We NEED sysex !!!!!!!!!!!!!!!
  • komak
    ive wanted to buy one, but after all, if sysex really not work, i am not buying
  • lcc.ppu

    sad I’mfrustrated
    Very dissatisfied, I spent ~£400 on an iPad, £130 on an iODock and £35 on Lemur. And it doesn’t work with sysex. Non-MIDI 1.0 compliant. What the hell were you thinking Alesis? this is a PR disaster. I personally could influence about 200 people through my work alone.

    If you want the firmware sorted to pass sysex, throw me an email with the code, and tell me what dev system you use, and I’ll do it for you for standard developer rates. Good god, open the software via GNU licencing and we’ll do it for free!

    HUGE HINT: Asus, Linksys.

    Appalling

  • Tom

    sad I’mfrustrated too
    1
    I am also a very unhappy customer.
    I love the iO Dock for it’s design and capabilities, but the ability to send sysex is quite essential for me. I send Alesis support three e-mails about this and I got no response at all. So for a long time I didn’t even know if this is a missing feature or a malfunction of my unit.

    As far as I am concerned, the statement that it is ‘Core Midi compliant’ is misleading information. Together with the ‘no-reaction policy’ I don’t feel that Alesis cares about it’s customers.

    Such a pity for a company with such great products.

  • Just letting everyone here know that Beta testing for updated firmware to allow SysEx is going well.

    If everything continues to go well, we should be releasing the update soon.

  • komak
    yes!!
    nice news
    thanx to have gave a look to that issue
  • eyeball
    FINALLY!!!!
    Good news. I wonder why Alesis didn’t let us know that they are working on the new firmware, before. There wouldn’t have been so many bad posts.
  • We wanted to wait until we had a solution that was working well and can release in a timely fashion.

    As I’m sure you have seen on this and other forums, as soon as you announce you are working on it, the next question is when. We didn’t want to get hopes up if it didn’t work right, caused other issues, or needed a longer time to develop.

    Thanks,

  • This reply was removed on 2012-01-19.
    see the change log
  • Jason Herbert
    Very happt to hear that SYSEX is on the way. I was waiting to find this out before I purchased my io Dock. Thanks Alesis!!
  • Ricky Wong
    new firmware out yet?
  • We have a solution that allows SysEx, but the size is limited. We are working on a solution to expand or remove the limit on size.

    The main delay right now is the release of the iOS update. Most likely this firmware update will be released after the iOS update we have all been waiting for.

    This is to confirm compatibility with the release update (the limited version works with the Beta), and to avoid confusion with this update.

  • edward
    Is it the 5.1 update that you are referring to? I just bought the IOdock a few days ago assuming sysex abilities as well. if it is not coming soon I do not need this, and will bring back.
    • J Sandeen (Technical Representative) 8 months ago
      We hope to have this for you soon Edward. We have just started our 5.1 testing and are working the bugs out.
  • mjsynth

    sad I’mfrustrated
    6 months ago admits no sysex support.
    2 months ago supposedly in Beta.

    wait for IOS update
    wait for new iPad
    wait for what else?

    It has been more than 6 months to add sysex a basic ‘Core Midi” function and we still don’t have it. Is Alesis new to the MIDI business or something. I will not buy another Alesis product when it first comes out EVER.

    My advice to anyone who is can take it back to do so now. When I found out sysex
    didn’t work I thought they would fix it. I have been patiently waiting and consequently can’t take my iodock back.

    Please don’t make my same mistake.

  • Sylvain Guiraud
    same over here, i can’t return it and i am fair man so i couldn’t consider this to a friend as i know it will be useless until to use it as a stand 🙁 so i consider already i loose this money) , but alesis loose a customer for sure and i will not ever recommand to buy alesis products when i see a such lame support. the new ios is out since a while and nothing comes just for sysex, when even with a cheap 3rd party cable can do the job alesis could not !
  • MRHoltz

    sad I’mfrustrated
    A-men, my friends. How about an update, Alesis?
  • mjsynth
    David or Sandeen,

    Do you have any news about when MIDI sysex will be supported by the iodock?
    It works great as a control surface but some apps need to use sysex and some others have the ability to use it.
    Please give us some news.

    Thanks,
    mj

  • M?ka

    sad I’mfrustrated
    Hello !

    I’m waiting for SysEx send receive through iO Dock too !
    Take so long time for basic feature that you can find everywhere it’s a shame !
    But if Alesis can’t make firmware iO Dock update quickly I will take the new Behringer dock …
    Thank you

  • Red Ochsenbein

    sad I’mfrustrated
    Fix this please. How can it be a product like this can’t handle SysEx? This is ridiculous
  • Bruno

    sad I’mfrustrated
    I need sysex on iodock !!!!

    You use “PRO” word to seel it, but it’s seems to be a lack of precision with your products !
    I wasn’t inform about this, i’m just desapointed since i ve bought iTX81z !

    Please do something quickly, or tell us if this is not possible to fix.

    Thank you
    Bruno from France

  • Adam Schabtach
    I think a status report on this issue would be appropriate at this time, because the front page of the Alesis web site has an image with “5.1” superimposed on the iO Dock image.  Also, the FAQ for the iO Dock says “For optimal performance with the iO Dock, Alesis strongly encourages updating your iPad to iOS 5.1” This implies that Alesis has done a good deal of testing with iOS 5.1, which seemingly contradicts J Sandeen’s statment that “We have just started our 5.1 testing and are working the bugs out.”

    Thanks. I understand that these sorts of updates can be tricky, but I also agree with the sentiment that the iO Dock really should have supported SysEx from the beginning. We’d all feel better if we had some reassurance that this defect will indeed be corrected soon.

    –Adam

    • view 1 more comment
    • and a lot of customers have a lot of sysex freezing in their iO Dock !!!!
      So, you hope a Stockholm syndrom ?
    • J Sandeen (Technical Representative) 7 months ago
      “sysex freezing in their iO Dock” ?
      -Meka, I’m not sure what your talking about sorry.
  • mikelacton23

    sad I’mfrustrated
    A typical business model would be to perform all the testing prior to release, implement the core functions that the device should provide, and inform & warn customers when there are adverse effects due to changes outside their control, eg incompatibly with the IOS ….

    One would then question Alesis’ direction of making more versions of ipad docks oppose to fixing the existing device, how they dealt with IOS5, their poor customer service with trickles of indecisive info and the ongoing SysEx issue.

    As a result I have lost all faith in Alesis and it will take some serious convining before i buy another Alesis product…

    • view 11 more comments
    • I’m looking forward to it. Yes, I bought a MIDI editor software for my ipad to control my bunch of synths with. Many parameters can only be changed via sysex. I first blamed the software for it, when I realized that it’s the io dock that doesn’t support sysex. If I had known this before, I had bought the simple camera connection kit and a MIDI adapter.
  • lasse.thomasson
    Well, isn’t this getting a bit silly?

    I bought the dock so that I could use my iPad as a controller in my studio. And for this I needed Sysex implementation. I actually read all the tech specs beforehand and with my, at that time, trust in Alesis, I never imagined that it wouldn’t work.
    And then, for all kind of reasons, I didn’t take the time to test it before the expiration of the return policy date.
    Stupid of we, I admit, since I’m now stuck with a peace of tech junk (from my perspective).
    The handling of the issue in this thread isn’t adding to make my situation less confusing and better.

    So I’ve lost a bit, but I think Alesis loss is far bigger.
    Since there is very little trust left from my point of view I would be wary in the future of buying anything from Alesis. I’m not saying I never would but given a choice of a comparable product from another manufacturer Alesis would have a really hard time convincing I should go with them.

    But hey, life goes on, and there is music to be made 🙂

  • mjsynth

    1
    This thread started 8 months ago (9/17/2011) and sysex still doesn’t work.
    Can I expect this level of support for all Alesis products?

    Either make the firmware fix or stop advertising it as “Core MIDI” compliant.

  • lcc.ppu

    sad I’m pissed off
    2
    The device is advertised in the UK as “Core Midi compliant” Core Midi includes Sysex – your product is NOT midi compliant, therefore it is NOT “Core Midi compliant” you are in breach of UK and EU law. Please remove the text.
  • Bruno

    1
    Sorry…

    but i sold it…

  • scott.leroc

    sad I’mAnnoyed
    God, I just got my io dock back from Alesis and discovered all the sysex programming I did with the iPad camera kit doesn’t work with the dock grrrrr. This code has been around 30 years why cant it work with the io dock?
  • Guus Ten Brink

    sad I’mfrustrated
    Didn’t want to wait anymore and sold it….

    Never Alesis again!!!

  • Gösta Bergfeld
    something new about it? Just bought the io dock 3 days ago to communicate to cubase via lemur ….
  • Adam Schabtach
    Considering the amount of time that’s gone by, I’m guessing that Alesis gave up on this. Sad. FWIW I just bought a compact mixer a few days ago and I didn’t even look at Alesis’s offerings because of this very issue.
  • Sylvain Guiraud
    when you see that a company like alesis is totaly unable to fix such vital function after 11 months there’s just one things to do is to boycott their products as i did after i sold my io dock
  • Gösta Bergfeld

    sad I’mfrustrated
    Me too, on saturday I will bring it back to my dealer and will get the iConnectMidi
  • dissapointment

    sad I’mDissapointed
    Very sad, bought myself an io dock yesterday only to learn here today that it will probable never support sysex.. Alesis this is just stupid, everyone selling their io docks because the problem, wich is clearly a design faillure, is not to be fixed. Shame on you!
Paulius Volkovas

iO dock doesn’t send sysex messages. Is there a fix?

iO dock cannot send sysex messages. Is there a fix?

i tried to send sysex message from Midi Touch app with no luck. After i wearched the net and found that sysex messages are not working on iO dock.

21 PEOPLE LIKE THIS IDEA
INCLUDING YOU

following

(unfollow)

Not planned
This topic is no longer open for comments or replies.
next »« previous
  • dissapointment
    And i will get the iConnectMidi as well
  • eyeball
    Just put mine on ebay. Shame on Alesis. I’ll never buy an Alesis product again.
  • Denis Mujakovic
    i am also sad to realize the sysex is not supported after so much time.
    i will never again buy an alesis product and will spread the word of this debacle. io dock was actually a promising product crippled by bugs, half finished features, and poor documentation. such a shame.
  • earthnail

    sad I’mfrustrated
    Oh c’mon Alesis, how hard can it be to release an update for SysEx messages?
  • lcc.ppu

    sad
    Alesis will never update the software, it is vapourware.
  • lcc.ppu
    It is nearly the first birthday of the last software update – I’m having a party.
  • Denis Mujakovic
    considering they announced the sysex so long ago i also think it was unsincere.
    at this point it just looks like a strategy not to lose potential customers.

    like i mentioned- i really doubt i will buy a product from alesis (and i have a couple)

  • earthnail

    sad I’mfrustrated
    1
    System Exclusive Messages have been an integral part of MIDI from the very beginning, that is, the MIDI 1.0 specification in 1983. It is not an optional part that can be left out. The CoreMIDI speciication does in no way exclude sysex messages. Thus, CoreMIDI compliance requires sysex support – there is no room for interpretation here.

    I would love to see Alesis add sysex support to its premium audio dock. Or allow customers to return the product. I own the dock for more than half a year now, and all it does is collect dust.

    • view 4 more comments
    • This comment was removed on 2012-10-25.
      see the change log
    • A quick google search for the detailed MIDI specification results in this PDF:
      http://madamebutterface.com/assets/do…

      See pages 4-5, chapter “Message Types”, for information how integral system messages, and system exclusive messages, are for the MIDI standard.

      The CoreMIDI specification actually does explicitly mention system exclusive messages in the “Overview” of it’s “MIDI Services Reference” – which is the general starting point for browsing through the CoreMIDI documentation (not a hidden chapter called “optional features”): “…such as MIDI receive channel and system-exclusive IDs.”
      http://developer.apple.com/library/io…

      Thus, a CoreMIDI compliant device definitely has to support system exclusive messages. Only because Apple certified it, doesn’t mean you can transfer your responsibility for missing features over to Apple. You built the device, and you claim full CoreMIDI compliance. Obviously, one integral part of CoreMIDI support is missing. Yes, Apple did overlook that, but no, you still have to fix it.

      EDIT: had posted it twice, first answer didn’t show up immediately, so I mistakenly thought something went wrong. Deleted the first answer and removed the note saying “I posted it already” from the beginning of this post.

  • Denis Mujakovic

    sad
    mine is a professional dust collector aswell. apparently sysex wont be implemented and we can ?t return the devices. so what now?
  • lcc.ppu
    I was faithfully promised by email that the next firmware update would address the issue – this was months ago – and I still have the email safely archived. Nothing has happened. This now adds insult to injury, I ask again, release the source code and let US fix it as YOU can’t. I can post the email here if that serves any purpose.
    • J Sandeen (Technical Representative) 19 days ago
      We had something that was in the works, unfortunately this did not work out.
    • So what does that mean? You aborted the effort to provide users with this essential missing MIDI-feature? Or is there still work going on?
  • Denis Mujakovic

    sad I’mconfused
    1
    i am frankly astounded that sysex implementation is such an impossible task.
    • I don’t understand that either.

      System exclusive messages can have an arbitrary length. This makes them more difficult to handle than other MIDI message types. If you handle messages as whole blocks and wait for the end of a system exclusive message to arrive, you could run out of buffer space. CoreMIDI solves this by restricting the block size to 256 bytes. If a system exclusive message is longer than 256 bytes, you will receive a second message chunk with the next bytes – but no message type at the beginning that indicates that this is a continuation of the previous message. It is up to the developer to handle these data chunks correctly.

      In other words, CoreMIDI does nothing special to handle system exclusive messages, it simply splits each block to 256 bytes. Therefore I don’t see any problem in getting CoreMIDI compliant sysex messaging to work.

      I must confess I don’t know if what CoreMIDI does is in line with the MIDI standard. In any case though, I think it’s a desired behavior as a small block size prevents long latencies.

      Dear J Sandeen, I would volunteer in testing the beta firmware that you had in internal development. Maybe all that your testing overlooked was that CoreMIDI _always_ splits longer sysex messages to 256 byte chunks (you can verify this by establishing a MIDI connection via WiFi or Bluetooth to your iPad).

    • J Sandeen (Technical Representative) 18 days ago
      Is more of a hardware limitation rather than a development limitation. I don’t have anything beta to offer sorry.
  • sn1730

    1
    Don’t bother replying to this topic any longer, folks. Alesis is now deleting comments that demonstrate that they’re wrong on this issue. I have the deleted comments in email but obviously there’s no point in posting them here. Maybe a few people will see this comment before it’s taken down.
  • MRHoltz

    1
    Small Claims Court, anyone? Or, Class Action?
    • J Sandeen (Technical Representative) 4 hours ago
      This is not the place to discuss law. Please call and speak with our legal team if you feel you have a “case”. Again, being coreMIDI complaint has nothing to do with being SysEx complaint. That is a fact.
  • This reply was removed on 2012-11-13.
    see the change log
  • This reply was removed on 2012-11-13.
    see the change log
  • lcc.ppu
    Source code please.
  • This reply was removed on 2012-11-13.
    see the change log
  • J Sandeen (Technical Representative) 4 hours ago
    Sorry SysEx did not work out for the iODock. This is something we had hoped to implement but things did not work out as planned. Sorry for the inconvenience to you all.

Leave a Reply

Your email address will not be published. Required fields are marked *