how’s this going for everyone?
got it working? what’s your thoughts?
its definitely a step up if you want to work with plugins with your Osmose 
I’ve got it working with Ableton, seems pretty cool …
though, honestly most of the daw control stuff, id do via Push , as you have more visual feedback, but its nice to have.
might be useful for others, if you see similar issues.
the install instructions and the advance section of the osmose manual are pretty good, but a few things I found…
a) there’s a lot to install 
the firmware update is almost instant (assuming you were already up to date)
but then you have to install ctrl-e (and for some reason EE website was very slow), then you’ll probably want to install/update the vsts ctrl-e supports.
b) switching presets constantly
ok, so when I first fired up Ableton with Ctrl-E on it, it was constantly switching presets within Ctrl-E.
This was something to do with the Haken port sending CC messages and Ctrl-E responding too it… possibly due to changes in Osmose midi ports. once I ensured I only used Osmose (play) with Ctrl-E it seemed to be ok.
ok, mostly this has not changed… except the usage of usb midi ports slightly…
a) hardware settings (osmose)
Midi IO
ext clock usb play 1/3
usb haken mode 2/3 note + matrix (assuming you want to use Haken Editor)
haken local control on or off (to taste, see below)
Ext Midi setting - usually MPE, but to taste.
b) Ableton setup
so this is how Ive set things up, and all appears to be good…
Midi settings
Surface
you will already have a new surface , Osmose with Osmose (daw control) as in and out 
Midi In
Osmose (Play) - enable , check MPE
Osmose (sound engine) - enable , check MPE
Midi Out
Osmose (sound engine) - enable
you want all other Osmose ports disabled/off
decide if you want to use Clock or not for Ext In/Out
Id assume its not really necessary if you are using daw control.
d) Haken Editor 10.52
yes, we are still on 10.52, so don’t update 
all you need to do is going into Midi Global setting and set Osmose (Haken) as the port for in and out - as this changed.
(again, you’ll need to have midi io - usb haken mode set to 2/3 note + matrix)
e) Ableton tracks
Generally, you want to use Osmose (play) as the midi input, and make sure you select this - do not leave to ‘all instruments’.
Ctrl - E track - you will want to use Osmose (play) as input.
and likely Ext Midi mode on Osmose set to MPE.
Osmose Haken Midi aka MPE+ track
Osmose (sound engine) → Osmose (sound engine)
MPE Setting lower channel , 2-14.
(you can use Osmose (play) as input, if you just want normal MPE)
Osmose Audio - I have an audio track, that I use if I have haken local control = on, my normal use-case.
if you always have local control off , you could use Ext Instrument rather than separate audio and midi track.
similarly if you don’t care about MPE+, and your happy with just MPE, don’t enable Osmose (sound engine) in Midi inputs then hopefully ‘all instruments’ should work fine… i.e. you don’t get the duplicate data caused by having both Osmose (play) and Osmose (sound engine) enabled.
so what’s your setup? did I miss something ? a different way?
any tricks / tips for other daws?
note: I think Windows used ports numbers 1-5 , no names, see advance section in osmose manual for details.
had a pretty long play with this yesterday… and I really like it !
my thoughts :
is it a game changer? not really, and yes at the same time…
I only ever used the Osmose for the EM sounds, as a standalone synth (except the odd test), but making having Ctrl-E on a track (in my template setup in Ableton), makes far more tempting to just dip and see whats there. I can see me using things like Noisey now.
so the reduction of friction could change my pattern of usage.
amusingly, I also can see EE motivation…
Ive already been looking at their other expressive suites ! its a win-win for us both.
a couple of things I think are missing / id like changed:
preset browser for Ctrl-E labelling? (major)
its just controls. e.g. when you ‘filter’ by plugin, or category its not shown, and similarly the preset name is not shown anywhere.
this means, you really have to have your computer screen in front of you, I have mine behind me (deliberately) to avoid distraction.
Ctrl-E plugin/ suite compatibility. (minor)
I think EE should make it much cleared on thier web site, what plugins/preset suites are compatible with Ctrl-E … rather than just what is included. e.g Im assuming Hive 2 expressive suite IS supported, but no presets are ‘contained’ in base pack.
Startup mode (very minor, nit picking)
I really wish it would either remember your last mode, or default to sound engine.
I like the osmose as an instrument, and that ‘menu’ at startup breaks that feel a tiny bit
Other than that…
apart from reconfiguring it was flawless (see above)
that said, I’ve had the ctrl-e plugin (?) crash Ableton a couple of times…
seems to be when selecting user presets? because its empty? so perhaps I can workaround?
looking quickly on facebook, seems others have not been so lucky, with quite a variety of midi issues… that said, every update we see the same.
its a natural bias, people are more likely to post if they have an issue (in hope of a solution) - than if it just works - so hard to judge if it is a small or large %
but for me…it basically, just worked
holding off for a week or two, to see if there’s a bugfix point release.
I’m told the load time on internal presets is Down from the last release. pleased to hear that, at least!
could be wise…
it seems stable to me, I think most user issues are likely down to the move to 5 usb ports, and reflecting in their setup (e.g ignoring some of these ports, or knowing which to use etc)
the rest seems like they have ‘just’ ported the osmose ce code over to the osmose, so the osmose functionality is unchanged. (and critically, the dsp firmware was not updated) , so if you aren’t using daw control/ctrl-e very little difference to 2.1
internal preset loading - Ive seen this, though, honestly I cannot say I noticed… perhaps a bit, or perhaps Id just got used to it?
that said, its very possible EE have tweaked their midi implementation for the launch of the CE, as its obviously critical on the CE.
I’ll say Ive been using local control on the Osmose, as early on, I found the midi implementation a bit “problematic”, so was easier to bypass.
I am tempted to give it another go now, as I’m sure it must be pretty solid on the CE otherwise there would have been an huge outcry !