Posts

Showing posts with the label Mark Powell

Not sure whether I'm mis-remembering how it worked, but under the 2.1.1 community release posted by Mark Harris, I'm...

Image
Not sure whether I'm mis-remembering how it worked, but under the 2.1.1 community release posted by Mark Harris, I'm going to a VST plugin and trying to configure for per-note expression.  When I change 'global' to 'per note' under Control Scope and click OK, it fills in the box on the routing matrix, but also the 15 below it.  This means I have each channel mapped to a different parameter on the VST.  I've tried 2.1.1 experimental that Geert Bevin  posted a few weeks ago and it does the same on that.  Am I dreaming or did it not used to do this in previous versions?  Is this a bug?

Has anyone used Apple Mainstage with MIDI input from EigenD?

Has anyone used Apple Mainstage with MIDI input from EigenD?  I presume that, since it's a derivative of Logic, it supports note-per-channel MIDI?  If anyone's used it do you find it stable?  I'm thinking of spending the 20 quid and having a play as a setup where I just want to start up and play but have the option to record if required. I've seen a couple of threads complaining about latency issues, so don't want to bother if it's a complete waste of money, but on the face of it it looks pretty good.

Is eigenlabs.com down? I can't get onto the site.

Is eigenlabs.com down? I can't get onto the site.

For those of you playing with multi expression using u-he Bazille, Groove 3 have just released a video training...

For those of you playing with multi expression using u-he Bazille, Groove 3 have just released a video training course for it.  If you go here then you can get a 30 day free trial courtesy of Propellorheads - the code expires tonight though, so be quick! https://www.propellerheads.se/groove3offer/?utm_source=newsletter140717&utm_medium=email&utm_content=newsletter140717&utm_campaign=newsletter140717

I'm playing with the new MIDI processor agent in version 2.1 and having an odd issue.

I'm playing with the new MIDI processor agent in version 2.1 and having an odd issue.  I want a talker that turns the midi processor on/off.  If I use the Belcanto 'midi processor 1 closed to true set' then it correctly sets the 'closed' flag on the agent to ticked.  However, if I use 'midi processor 1 closed to false set' it seems to have no effect.  Running the statement in EigenCommander returns 'ok' but shows an underline where the false would be in the statement.  Any ideas whether this is something that I'm doing wrong or a bug in the agent?

Not sure if anyone's already seen this, but someone posted a link in the Leicester Ableton Users' Group on Facebook.

Not sure if anyone's already seen this, but someone posted a link in the Leicester Ableton Users' Group on Facebook.  The relative notation works really well with the Eigenharp and is a nice way of visualising chord and melody progressions.    http://www.hooktheory.com http://www.hooktheory.com

Hi All

Hi All, Hope everyone is well.  After a bit of a break from all things EigenD, I've been playing with Mark Harris's fantastic Creator.  I've never made the effort to get over the learning curve in the past, configuring everything via Workbench, but after playing for a day I've got my head around it and it's a revelation - what was taking hours to build in WB is now scriptable and taking 10 seconds to rebuild at will.  Brilliant work Mark!   Now to my question: One of the things that didn't used to be possible via Belcanto was setting up the MIDI routing matrix.  Is that still the case?  That's the final step in my quest for completely automatic rebuilding of my setups. Cheers, Mark.

I know that some of you have the original version of the iConnect MIDI for connecting to the iPad (Geert Bevin and...

I know that some of you have the original version of the iConnect MIDI for connecting to the iPad (Geert Bevin and several others).  The smaller of the two new ones - the iConnect MIDI2+ - is now shipping and there's a cracking deal flagged up on Discchord.com, giving $20 off if you order via MusiciansFriend.com and use code FALLSALE13B.  I've just ordered and, including import duty, taxes and express delivery to the UK, it came to 77 quid with a guarantee of nothing extra to pay on import.  I had one on order from Thomann.de, who weren't expecting stock until the end of the month, and they wanted 92 quid including delivery.  The new version looks really nice, as it lets you use the ipad audio feed direct to your DAW.

There seems to be a bug in the arranger (or my setup) when sending to a MIDI rig.

There seems to be a bug in the arranger (or my setup) when sending to a MIDI rig.  I've essentially taken Alpha Factory 2 and rewired Arranger 1 to MIDI rig 2 to send drum patterns.  If you set up a pattern it will generally send the right notes, but then, for no obvious reason, start sending a completely different note for a few bars, then go back to original.  I remember Mike Milton showing this to Geert Bevin  in one of the G+ hangouts a year of so ago, but not sure what the conclusion was.  Has anyone else seen this problem, and are there any ways to correct it?

My only work with the Eigenharp this weekend; my eldest playing the clarinet.

Image
My only work with the Eigenharp this weekend; my eldest playing the clarinet.   Given that she's four, this fairly conclusively disproves the 'you can't just pick up and play' argument!

It's still a work-in-progress, but for the benefit of Randy Brown and anyone else who's interested, here's a quick...

It's still a work-in-progress, but for the benefit of Randy Brown and anyone else who's interested, here's a quick (very rough) demo of my work on the Eigenharp Ableton control surface script.  It's currently dependent on a very Heath Robinson modification to the Midi Input agent, so not published just yet, but once I've tidied things up I intend to properly issue it so that others can use/amend to their hearts' content. Because I've had to use the built-in Macbook webcam for now, the Eigenharp is shown sideways on, but essentially each of the five columns on the Alpha represent a track in Live.  Rows 1-6 mirror the clips that have focus (determined by the 5x6 blue box on the Live screen, which can be moved from the Alpha).  Row 7 allows each track to be turned on/off, 8 allows each track to be solo'd, 9 allows each to be armed for record.  It's multi-touch, so you can arm/solo multiple tracks by clicking several buttons at once.  Also any changes in...

I recall someone (Geert Bevin I think?) recommending Harrison Mixbus as a good audio-only recording solution a few...

I recall someone (Geert Bevin I think?) recommending Harrison Mixbus as a good audio-only recording solution a few months ago.  I won't be using it myself as I'm 100% Ableton-based these days, but for anyone who's tempted it's currently on offer at $39 at DontCrack.com.  I've bought from them before and they've always been excellent, plus it's electronic delivery, so no issue with it being in the US.

"Server undergoing maintainence

"Server undergoing maintainence The Eigenlabs server is undergoing maintainence and repairs. Please check back later." Hmmmm.  Updates regarding the charitable setup, good old fashioned technical error, or something else? http://www.eigenlabs.com/

As mentioned in Randy Brown's thread about his FCB1010, I'm trying to setup an Ableton Live Control Surface...

As mentioned in Randy Brown's thread about his FCB1010, I'm trying to setup an Ableton Live Control Surface specifically for the Eigenharp.  However, I've hit a slight snag with Talkers.  I know how to trigger a talker based on a specific MIDI note input by linking the MIDI input agent to the talker and using the key row number to indicate the note number, but I'd like to do something slightly more complicated.  I want to trigger different actions, not just based on the note, but also based on it's velocity.  For example, turning a specific light off if the velocity is zero, green if 10, amber if 20 and red if 30.  Is there any way to do this, either by filtering the midi input and sending to different talkers based on the note velocity, or by triggering the same talker, but making a decision on colour based on the value received, rather than hard-coding it in the action script?  If not then I'll look at rolling my own code, but I spent most of yesterday looking...