Forum Replies Created
-
Posts
-
Sorry, not working here. Maybe the cause is VMWare Fusion…, but OTOH it doesn’t work on a Mac also. I will try (later) on a Windows laptop. (Maybe I’m missing some setting, but looking at your jpg it doesn’t differ from mine.) But again, don’t waist too much time on this, I’m still fine 😉
I wrote about this, the “dragging bubble” can’t be changed that easily. …
Understandable and no problem, but the fact that the ‘other bubble’ doesn’t change it’s appearance when changing the properties might be a minor bug. Again, no problem and it doesn’t restrict me from further development of my panels.
I’m on Win 7 (and Mac 10.7.5). I have changed the properties (see attached screenprint), but still no change in appearance. Still the same black text on a white background… (Don’t know about Win Xp. It is also running on my computer. If needed I can test this issue on XP, but maybe its better if ‘atom’ steps in, may save time ;-).
I’m still confused. I downloaded the latest versions (nightly) for Mac and Windows. Both have now the extended properties for bubbles. I adjusted these (e.g. back ground colors) and ctrl click on a modulator, but on both platforms NO change of the ‘bubble’. (See attached screen print.) Anyway, I think it would have been more logical to have all these bubble properties for the ‘dragging bubble’ than for the ‘ctrl click bubble’. BTW right clicking has also the effect of showing the ‘short cut menu’ bubble.
I’m trying to work with the ‘bubble’ properties, but none of the settings seems to have any effect on the appearance of the bubble. Am I overlooking something? (Mac Ctrltr Nightly version 5.1.2. build 1254)
Sjoerd Bijleveld wrote:
I didn’t test it yet, but if it works it will save me a lot of work.The au/vst/standalone will open, but they don’t work for me, unlike the latest version of ctrlr.
I just tried to use the TX7 as AU in my DAW and though it opens fine, when I activate sliders there is no MIDI-activity. So probably the latest version of CTRLR is needed. At the moment I’m working on two other panels which is already a lot of work (and I’m not sure if it is ever finished), but sooner or later I will start on a panel for the TX7. Luckily I have a working Unisyn v1.52 (from MOTU) for older Mac’s which has an editor for TX7 (amongst many others), so I can study and use all the sysex messages Unisyn is using and I can even use the layout of this editor. I did the same for my Proteus/1 panel which I hope to finish in the near future.
… I’ll try to put an example how to deal with larger chunks of memory and how to efficiently get parts from it and use that data.
Thanks in advance for this example! In my case I think speed isn’t that much of an issue (yet…), because my Lua-script only loads the preset data in my panel for editing. For sending data to the device I use mainly ‘direct’ sysex messages, without scripting at all or some very very small scripts. This works very well in my case, because I just want to change one modulator at a time to hear the effect on the sound or preset. Sending the final result of my editing I have to rely on the snapshot feature of CTRLR, isn’t it? (I experimented a bit with this feature, but had some inconsistent results, meaning that the device showed receiving other data than were send… But I will dive deeper in this in the near future.)
About using strings as numbers. I am studying ‘Programming in Lua’ and noticed (chapter 2.4) that Lua provides automatic conversion of strings to numbers, so that’s why (for example) I confidently added up strings and numbers, but also took the advice to convert strings to numbers using ‘tonumber’ to be on the safe side…
Well anyway I’m always open to better programming resulting in faster code execution and please be as critical as possible to my programming attempts! I don’t mind at all and I’m used taking in critics!
Yeah, time for nostalgia. I am still the first owner of a DS:3 system (1985), the poor man’s Emulator, complete with Apple IIe, piano keyboard and of course MIDI (only MIDI-in though…). I remember sending a letter requesting MIDI-out, so I could use the keyboard to control my other gear. But they went out of business soon after. The DS:3 was extensively used by John Molloy and Murray Monroe, being Mainframe. Because of MIDI I still can use it in my present setup! Amazing, isn’t it
OK, back to CTRLR and Lua!
Don’t do things like that, there are specialized classes for this stuff. Like BigInteger for dealing with MSB/LSB, to string conversions and add 125 etc, that’s scary. Explaing what you want to achieve i’m sure we can provide a much cleaner solution
I hope you’re referring to my (as it seems) crapy code 😉 What I want to achieve is the following. I want to edit a certain preset, so I send (using a dedicated modulator for this) to my device a message requesting all the parameters of this preset. The device answers by sending all the needed data in one message of 265 bytes. My panel receives this message and because I know exactly where in the message the bytes (always a lsb and msb pair) are for each parameter, I just ‘get’ these bytes, convert these to a string (in case of a preset name) or to a integer value. These values I send to the concerning modulators. In this way all the modulators have the right values when starting to edit this preset. I got my ideas (for doing it the way I showed in the code) from the panel Emu 1.2 (I believe Hecticcc made it). If you can provide a more efficient and less scary 🙂 code for this, that would be much appreciated!
From what I can deduct of your code (with my still very meager knowledge of Lua!), it seems that Lua is not getting a valid value to send to your modulator. Correct me if I’m wrong.
This is the code I use at the moment to get a data byte from a MIDI-in message, convert it to a number value and send that number to set a modulator to that value, in my case an instrument number:
— get primary instrument number
modValue_lsb = midi:getLuaData():getByte(53)
modValue_msb = midi:getLuaData():getByte(54)
mv1 = string.format(modValue_lsb)
mv2 = string.format(modValue_msb)
if mv2 == “4” then
mv1 = mv1 + 125
end
modValue = tonumber(string.format(mv1))
panel:getModulatorByName(“primaryinstrument”):setModulatorValue(modValue, false, true, false)Don’t pay attention to the elements of this code specific for my goal, but look at the conversion functions: ‘string.format’ and ‘tonumber’. Of course I’m not sure this is the perfect way, but it works for me.
I’m at the moment facing the task of getting preset data from my device and distributing the data to the various modulators on my panel. This example code gets me going! Thanks!
Yep, it worked! Thanks. (Again gained a little bit more knowledge … Getting there step by step ;-))
I did put the component (was also present in the downloaded zip file) into …/library /audio/plug-ins/components of my Mac and it did load fine in my DAW (Digital Performer). I didn’t test it yet, but if it works it will save me a lot of work. (I recently bought a TX7 for 60 euro’s especially to make a panel for this module.) I have attached a screen print of this module made by ‘lung’ and I must say it looks quite nice! My compliments and thanks for the upload!
‘send midi from other members of the group’, see this reply of atom: property ‘Send MIDI from other members of the group’. I’m also curious to know about the other properties mentioned by you. All in all it is maybe time to start writing a manual or some tutorials, but otoh I find it in some way rewarding to discover myself how CTRLR works, especially in combination with Lua-scripting.
Thanks! I definitely will study Das’s example and try to adapt it to my needs. His component is already almost usable for my purposes. Thanks for the offer to help if needed, much appreciated!
OK, thanks for the warning :-)! I will study and try to work with dastaker’s envelope example instead.
Thorsten, is it worthwhile to compile the latest nightly (r1217) for Mac? OTOH: sofar no problems with r1209 for Mac.
I am editing a particular vertical slider and when I want to change the color of one of the items of the component (in this case the thumb color) I am presented with a color dialog box and in this box a button ‘reset to default’. Clicking the button doesn’t seem to have an effect. (But maybe I misunderstand the function of this button.)
