[Llamatron]

I made this panel, first of all thanks for your interest in it.

For the load command I just tried and it works for me, are you sure you connected midi in and out to the panel and synth?

For the snapshots, as you guessed it’s been made with an older version of Ctrlr and I don’t remember having them. Guess I should take a bit of time to understand how they work and how I could make my panel use them, or don’t hesitate if you feel like modifying the panel.

[Llamatron]

I think you have to export instance while inside Live, at least on Windows it’s how I get a VST dll

[Llamatron]

To start with I don’t know if it’s necessary but I disabled all ports except the ones I needed in miditrix, that would be the virtual ports ins and outs and the interface’s output port connected to the synth. (MIDI > Input devices… / Output devices…)

In Ctrlr MIDI>Output>Device choose a virtual port, in Live’s midi dialog enable sync on the other virtual port in the Output section only, and make sure nothing is selected for the 3 other virtual ports entries (in & out). I don’t know your midi interface so I can’t give you any advice if it got some settings.

Miditrix’s boxes turn green when some midi signal travels through them, and midi sync is a flow of constant small messages so the box should turn green when sync goes through it, and you should see the other box temporary turn green when some notes or control messages go through. This hint could help you get the right setting.

One last thing: if you midi devices order change (like for example an interface that is not always turned on) you might have to redo miditrix’s config.

[Llamatron]

The only option I can think of would be using loopMIDI ( http://www.tobias-erichsen.de/software/loopmidi.html ) to create a couple of virtual midi ports, one for Ctrlr and the other one for Live’s midi clock messages, and merge them on your physical midi output connected to the synth using Midi-OX or the simpler miditrix http://www.hermannseib.com/english/miditrix.htm

did a quick test and I could get sync + Ctrlr working at the same time with loopMIDI and miditrix

[Llamatron]

Setting the input channel to “All channels” wouldn’t work for what you want to do?

[Llamatron]

Here is how I convert midi received in the function to lua data in the data variable, then assign the first byte to a variable called b:
data = midiMessage:getLuaData()
b = data:getByte(0)
Then you have to make conditional statements with if … then … end according to the desired logic. If it can help you thoses messages you want to get are program change messages: Cx, where x is an hexadecimal between 0 and F that indicates the midi channel between 1 and 16.

[Llamatron]

I can’t find it there, but I just figured the “About” window says I’m on build 1300 with 1301 or 1305 windows versions, even after I reinstall, it might be the problem?

[Llamatron]

By a quick look at the Virus B manual I found online the Virus B seems to be able to send its patches in a sysex dump, look from page 255 on the english manual. Gonna be quite some work to implement that tho as there’s a lot of parameters apparently.

[Llamatron]

From the Ctrlr side it’s definitely possible, my panel for the DW8000 does that, I just have to send a specific sysex message and it sends the current patch’s settings in a big sysex message.

Check your synth’s midi implementation if it can send a dump of a given patch.

[Llamatron]

Works perfectly in rev 1285, thanks a lot for the fast fix.

I agree that making an option to ignore realtime messages would probably be a good idea.

[Llamatron]

The thing is that I don’t really need support for thoses messages, but my synth keeps sending active sense messages every 300 ms and there is no way to stop it.

If you think Ctrlr shouldn’t support realtime messages you are probably right, but in that case I think it would be better if they don’t trigger the LUA method at all, instead of calling it with an empty message.

rev 1284 apprently still calls the method with no data.

Thanks for your quick answer.

[Llamatron]

Pretty sure the problem is in this code, but I can’t figure where as even if I uncomment the console message nothing shows in the console. Without a method linked to midi message reception or the default empty method there is no crash. It seems to happen when receiving 1 byte midi messages, but I’m not 100% sure.

midiReceived = function(midiMessage)

—    console(“Midi message received”)

s = midiMessage:getSize()
sysexData = midiMessage:getLuaData()
b = sysexData:getByte(0)

midiChannel = panel:getGlobalVariable(1)
programMessage = 0xC0 + midiChannel
dumpMessage = 0x30 + midiChannel

if b == programMessage then
—        console(“Received program change”)
dumpRequest = {0xF0, 0x42, dumpMessage, 0x03, 0x10, 0xF7}
m = CtrlrMidiMessage(dumpRequest)
panel:sendMidiMessageNow(m)
end

dumpByte = sysexData:getByte(2)

if b == 0xF0 and s == 57 and dumpMessage == dumpByte then
—        console(“Received dump”)
assignValues(midiMessage)
end

end

[Llamatron]

No I don’t use getRange

[Llamatron]

noisemonkey wrote:

so just to clarify, in Ableton midi settings you turn off monitor and tracking?I wasn’t sure what you meant regarding the audio effect/ inputs/outputs

For the midi ports go to menu Options->Preferences->Midi Sync, and in there put everything on the port(s) connected to your synth to “off”, so Live doesn’t get in the way of Ctrlr when it connects to them.

The external audio effect trick is if you have your synth plugged to your sound card and want to have the audio coming from the synth inside Live, and on the same track you control it from. Live allows to use external hardware effects with an effect called External Audio Effect (in the Audio Effects section of Live’s own plugins, not the VSTs), who will send audio it receives from its track to an effect and receive the modified sound. What’s usefull for us is that it will always receive any audio it receives and send it into the track, so we don’t send anything, but receive the synth’s sound. It’s not what it was designed for but it works.

One thing I’m not sure tho is if the External Audio Effect is included in all Live’s versions, I own Live Suite 8 so I got it but it might not be available for you if you use another version.

Don’t hesitate if you got any other question or unclear stuff in what I wrote, also I have a french version of Live so some words in settings might differ on your version.

[Llamatron]

My method for ctrlr in Live:

– Disable the midi ports of the machine you want to control in Live

– Put Ctrlr on a Midi track, load your panel. Be sure to select the output and “Thru from host to device” in Panel settings

– Put an external audio effect after Ctrlr in the track’s chain, select no output for Audio To, and your sound card’s channel receiving the synth’s output in Audio From

There you go, you can automate your instrument regardless of them being CC or Sysex, they might not show up immediatly, in this case click the small triangle on Ctrlr’s “object” in the track’s chain, click configure and move the controls you want to automate in the panel to see them appear here.

You can also use the External audio effect’s latency compensation to fix any latency.

To avoid doing all that every time you want to use Ctrlr you can drag’n’drop the track in Live’s file system browser to save it, it might crash Live when you do that (it does for me), but you can load it after.

If you also enable snapshot on load there almost won’t be any difference between a VST instrument and your synth, only the fact it needs midi and audio set properly to work.

• This reply was modified 11 years, 3 months ago by Llamatron.
• This reply was modified 11 years, 3 months ago by Llamatron.
• This reply was modified 11 years, 3 months ago by Llamatron.

[Llamatron]

Yup it looks like there’s a timeout on editing posts, it should be removed imo. If you don’t have time to look for that atom I already managed some CMS (postnuke then zikula) so maybe I can give a hand, never used wordpress before tho.

Also on a side note as I’m not sure you saw my second post in the snapshot thread, it seems the 1196 build still can’t send a snapshot at load.

[Llamatron]

on demand snapshot works fine now, but it looks like it doesn’t send snapshot on load

[Llamatron]

thanks for the quick answer, and happy 2013 to you! 🙂

[Llamatron]

New version with cleaner “code” and the waveforms list taken from the manual shown in the UI, done with latest nightly (1194)

Attachments:

You must be logged in to view attached files.

[Llamatron]

I confirm that my getRange bug seems gone

[Author]

Posts