Forum Replies Created
-
Posts
-
Thanks Llamatron, i tried again this afternoon without virtual midi stuff and it works as it should 🙂
Damn, that means i’ve been doing the virtual midi cable merry-go-round for no good reason at all in my daw testing, making things needlessy more complex…
Silly me!Going to try again tomorrow with Live & Reaper without virtual midi, thanks for the info das 🙂
You can use Ctrlr in Live if you use virtual midi like midi yoke or Maple, sending the midi out of Live & into Ctrlr using one of those, and make sure the midi-device your microwave uses is disabled in Live’s preferences.
This way you can still tweak the controls, but then there is still the crappy midi timing of Live, making the whole setup near useless…
Another option is to Rewire live in some other daw that is more reliable, and put the Ctrlr plugin there. But then again this limits Live’s capabilities, and personally i don’t like this “schizophrenic” workflow, too confusing once your project gets large.
On a side note, i sure am curious about this Bitwig thing, the makers are former Ableton programmers and claim they are making the “better” take on Live. Let’s hope they get their midi system right.
Live has a very unstable midi system. Add external hardware in the mix and you’re set for trouble.
I had noticed this before when i used my rs7000 as master and Live as slave, the Live set’s tempo wobbled around what it was supposed to be.
Also it does not support sysex so if the panel you are using needs sysex communication you need to do some midiyoke/maple midi routing.
I still love live as a sequencer for audio and simple midi, but for “serious” midi editing for multiple outboard stuff i use Reaper.
For example the panel i am working on works great in Reaper, but Ableton refuses to play ball…
Maybe the new version has improved midi? Sure hope so…
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 clockOh yeah, Reaper works fine
Yeah i still have to find a way to fix this, it is used to draw the keyranges the way the unit does in the samplezone settings.
If you go into the lua editor and save & compile the script you can see it working @ the samplezone settings.
Only does 3 zones correctly for now, will make it do what it should once i get this error cleared up.Thanks for chiming in, i am glad to hear it works as expected with a later OS version than i have 🙂
Thanks Thorsten 🙂
-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.—IMPORTANT—
The way Ctrlr works makes the panel shoot out all midi-messages when the panel is loaded.
To make sure your presets don’t get messed up please use one of the following strategies for starting and setting up Ctrlr & your sampler:
Turn on the sampler after the panel is loaded.
Set the device-id to a different number than yours before closing down Ctrlr(or its host) This number is remembered, and the next time you load the panel your sampler will not respond to the midi-messages. Be sure to remember to change it back to the correct one once the panel has loaded.A way of avoiding this problem is in the making.
Happy samplin’ 😉
Thorsten,
thanks for the tip, i understand what you mean but cannot entirely visualise how to do this in code.
Would you mind posting a small snippet to enlighten me?
I had the same Lua issue today.
After saving, quitting Ctrlr and re-opening the panel later all the Lua scripts were gone…
Luckily i had seen this thread beforehand and made manual incremental saves along the way so didn’t lose much work. Reverted to 1184 atm, don’t want tol risk losing lots of work.
Fwiw: before i lost the scripts i had changed the font setting of the lua editor, maybe that’s what broke it??
Glad to hear it will be of use, i am curious about the “user experience” from someone else but me.
Ps – now working on parameter feedback on voice changes so the panel reflects the state of the selected voice instead of staying “as is”. Will upload fresh version when it’s all inthere.
Ok good to know i am on the right track, thanks Atom.
Found a small workaround, working on it got me thinking about why this happens.
Is this logic right? (Atom?)
Panel loads, lua scripts \canvas\…load, modulators are created and get values that were remembered @ last closed, lua sees all these modulators change value and triggers scripts.
V1.2 demo is here!
I am rebuilding the whole thing from the ground up, this panel now features:
user-settable device -id
visual feedback on selected preset/voiceparameter controls are available 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 keyHow to setup:
In order for this panel to function properly both midi IN and OUT ports of your sampler must be connected directly to the midi-out and midi-in of the panel.The controller midi-input is used to feed the panel midi data (keys, daw, controller…)
Go to the “Midi & device settings” tab in the panel and set the “Midi device id” to the number of your sampler’s device id
press the “Get general info” button to see if your sampler was found.
load up some presets and TWEAK!Panel built in ctrlr for windows rev.1196
You are propably referring to zoeos, the dev (same guy from touchOsc apparently) dropped it and open-sourced the code. It is all java, and there are some people working on it.
The source code is hosted here:
http://code.google.com/p/zoeos/
Although it is superior to the ctrlr panel as a preset builder its not a vst so no integrating in your daw is possible.
Please do dust off your emu and give it a spin, i’m sure you’ll have fun 🙂
I forgot to give some important info on how to use this panel ::doh::
(i’m used to the eos behaviour by working with it alot but if you dive in nose first it can ermmm..surprise you sometimes)
Because of the way eos works you have to keep these next things in mind:
To edit a certain voice in a certain preset you have to use the “select preset” and “select voice” buttons to navigate to the desired editing target.
The changes you make will ALWAYS be sent to the last selected preset on the panel. It does NOT edit the preset/voice displayed on the screen of the device (unless you are looking at the one selected in the panel) – it works “behind the screens”
Whenever a new preset is selected the first voice is automatically targeted.
This means :
If a preset only contains one voice then it is automatically targeted when the preset is selected.
If a preset contains multiple voices you have to change the value with the ‘select voice” buttons to navigate to the desired voice. Keeping in mind that the first voice is automatically selected when you navigate to a new preset, if the voice number displayed in the “select voice” buttons is anything other than 1 this will NOT correspond to the voice you are editing. You have to change the number to select the desired voice AFTER selecting a preset, else you will be editing voice number 1.
This panel should work on all devices of the E4 product line:
E4
E64
E64FX
E4K
E4XT
E4X
E6400 (aka “classic”)
E4XT Ultra
E6400 Ultrahmmm attachment missing… trying again
lil’ question @ whoever should know:
Is it normal that after a certain period of time you cannot edit your posts/post titles anymore?
I wanted to update the title of a thread i started to [resolved]blahblah… but i can’t seem to be able to…
Same for the contents of another post i want to update, seems a bit silly to have to do it in a reply.
I can confirm the ascii bug, all characters that have values coming from an incoming hex-message are acting up. Instead of all characters i sometimes see one character being displayed, and stepping up and down the values produces different characters for the same values.
Internally updated messages (ie value comes from a modulator, not midi-in) work correctly.
I also get strange behaviour from a script that works in 1183, it looks like ctrlr makes an internal midiloop with a 3-byte message, and the timestamp is a negative value …
*edit*
win 7 ultimate 32bit bare install
Good idea!
I am using alot of sysex and i use these all the time:
Insert values into a hexstring:
val1 = 1
val2 = 10
hexstring = string.format(“f0 18 21 %.2x 55 01 02 5f 01 %.2x 00 6b f7″, val1, val2)produces:
f0 18 21 01 55 01 02 5f 01 0a 00 6b f7Of course you can also get values from modulators and use those
val = panel:getModulatorByName(“myModulator”):getModulatorValue()
_______________________________________________________________________
Grabbing values from an incoming hexstring
Suppose this is the string you received:
f0 18 21 01 55 01 02 5f 01 0a 00 6b f7
Now to extract the byte with value 55:
extractedByte = midi:getLuaData():getByte(4)
Notice that although 01 is on the 5th place it is infact the 4th byte, as ctrlr starts counting AFTER the header “f0” .
You can also extract a range of bytes:
rangeOfBytes = midi:getLuaData():getRange(3, 7)
this will store the values “01 55 01 02 5f” in rangeOfBytes
_____________________________________________________________________
To check the results of these operations in console you need to do some conversion or you get errors like “sting expected, received number”:
string1 = string.format(someHexString)
console(string.format(string1))_______________________________________________________________________
Will add more in time
