emusonacid!

Instead of hijacking the other thread here's a dedicated one:

Control your eos sampler as a vst/au inside your daw!


For the last few months i've been getting into Ctrlr, a midi-plugin development environment wich makes it do-able to make custom interfaces for controlling midi hardware.

Not finding an EOS panel anywhere in the database i started making my own, and i am now very happy to report that all the long hours of coding are starting to pay off :-)

Downloads and info @ http://ctrlr.org/forums/topic/emu-e4-functionality-demo/#post-5450

Cool indeed!

I'm watching this like a hawk!

-v 1.2 updated -
Many improvements, including:

-Parameter feedback from the device to the panel is now in place, the gui reflects the state of the selected voice when changing voices. Note that a big number of sysex messages are being shoved around when changing voices, it takes about 1 second to fully update the panel.
-Graphical representation of the amplitude envelope.
-Easy setting up of presets in multimode.

Controls for:

-Preset select
-Voice select
-Sample select
-Samplezone select
-filtertype
-cutoff
-resonance
-cords 00 to 03 (source, destination, amount)
-Amplitude envelope
-Lfo 1
-tuning
-chorus amount & width
-samplezone root/low/high key

Link to panel @ first post.

Happy samplin' ;-)

This is getting very interesting.
I would love to see some video of it in action
Thanks for taking the time to build the plug-in.
I hope you continue development to it's maximum potential.

WOW imagine a GUI that can interface with ALL the functions of EOS.

Hi Heccticcc,

when loading your EOS panel in CTRLR I get about 42 times a "lua runtime error", regarding the "getValue"-method.
Do I have to install something else than CTRLR, e.g. JRE??

regards,
mosorb

Hi mosrob,

I had the same issue. Open the .panel file in a text editor (notepad or equivalent). Is there a line of XML code at the top? Probably something like this:

<?xml version="1.0" encoding="UTF-8"?>

If so, delete this line and re-save the file. Then try loading it into Ctrlr again. This fixed it for me.


Kudos to Hecticc for making this!

The value error is related to the version of ctrlr you are using, this panel has to be opened in one of the latest nightlies. The stable version has not been updated for a while, and the methods regarding value getting/setting have been simplified in the nightlies .

example in stable:

x = panel:getModulatorByName("somemodulator"):getModulatorValue()

in nightly:

getModulatorByName("somemodulator"):getValue()

Editing the xml is not very safe so i would advise not to do this.

Cheerz,

H

Oops! I assumed that was a redundant bit of code. Ignore my post, mosrob.

Stumbled on a nasty bug when testing in Reaper and Ableton, a fix is in the making but it will take a while as i have to rewrite the midi received function and its around 4000 lines long.
The problem is situated in automating the sysex parameters directly, when an envelope assigned to a sysex parameter is set to write. It looks like once the envelope is armed the host starts polling the parameter at a very high rate, wich causes the panel to send out a continuos stream of messages, completely hogging the bandwith of the mididevice.

I have now rewritten a small portion of the panel and all is working as expected, will update once the midi received is comletely ok again.

Anyone here having the same issues in other daws?

On a side note:
I can now confirm without a doubt that Ableton's midi timing to and from external mididevices sucks bigtime, timing problems in midi notes sent out are clearly audible, a straight hat pattern sounds like a heavily swung jive, different every time
I did a small test with my rs7000 sequencer, making Live slave to the RS and locking in on the bpm and clock signal it receives, and instead of following the clock it kind of "bounces" around the received clock, slowing and speeding up the tempo like it's hooked to an lfo instead of a clock

Oh yeah, Reaper works fine

Looks nice !

...but didn´t work here as AU under OSX 10.7.5 with Logic 9.1.8.

good Luck .

Damn, sorry to hear...
I have no access to a mac & logic but if you can give some more info like Ctrlr version used and midi routing i can ask @ the ctrlr community if someone can also try it out and i can try to locate the problem.

Thanks for checking it out!

Cheerz,
H


**edit**

It seems the "official" mac build is lagging behind, but one of the users has made a standalone build with more recent sourcecode. Obviously it will not do au for now, but some creative midi routing should sort you out.

Find it here:

[URL] ctrlr.org/forums/topic/nightly-standalone/[\url]

Made a little demonstration video this afternoon using the latest panel revision
It shows how to set up the panel, demonstrates some functionality and a bit of basic automation stuff using Ableton Live.

http://www.youtube.com/watch?v=biG7Yd9SmlE&feature=youtu.be

Wow this is beyond belief.
Thanks for showing it in action.

Once fully developed will the software allow you to assign any source to any destination with any amount?
Can the software work on individual groups within a preset, or are all voices on that midi channel effected in the same way?
Will it be possible to automate parameter changes to occur during sequencer playback?

Once fully developed will the software allow you to assign any source to any destination with any amount?

If you mean all 18 cords, yes.

----

Can the software work on individual groups within a preset, or are all voices on that midi channel effected in the same way?

The plugin works channel-independant (sysex messages) , the active voice within a preset (ie the one selected using the buttons) is always the target of editing. This is due to the way eos works.
So for example in a preset with multiple voices the one you select will be affected, the rest will remain as they are.

----

Will it be possible to automate parameter changes to occur during sequencer playback?


Yes, but doing so for different voices will require automating preset and voice selection to select the correct one, and because switchin between these generates a lot of sysex activity it will throw the sampler out if sync for a brief moment.
You can work around these "hickups" by doing it on a moment the sampler is not playing any notes, or just stick to plain controllers a-h for realtime editing on the specific midi channel.
I will make some more videos, and stuff like this will be covered so you can see and hear what this means. Words are not always enough to explain :-)

Cheerz,
H