[lfo2vco]

dnaldoog wrote:

Hi lfo2vco,

Maybe this post will help you? (see post by diamondamps)

Multiple MIDI ports?

I also use these to get/set the output channel from a panel uiSlider etc:

panel:setPropertyInt("panelMidiOutputChannelDevice", value)
myChannel=panel:getProperty("panelMidiOutputChannelDevice")

Thank you, I knew there were some bright sparks around here : ~ )

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

Indeed I did make two sets of panels for my project, one for the app and one for the VSTs.

Here is the download link if you wish to peruse them:
https://www.dropbox.com/s/ob6jbxtzv6l7gn6/Kiwi-3P%20Editor%20Ctrlr%20Panels.zip?dl=0

Actually I think I deleted all the getProgramState() and replaced them with a single
popup timer call back in my initialise script.

I hope this helps.

• This reply was modified 4 years, 9 months ago by lfo2vco.

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

Hi John,

Yes that is correct if memory serves me right (and I stand to be corrected on this) it seemed that getProgramState() solved a problem when exporting the Standalone and also when working in ctrlr app.
However it seemed t cause a conflict when exporting VSTs. Sorry I can’t remember if I got to the reason for this or stumbled on it by trail and error.

I do not have much buffer to for memory and old info gets purged so I can function on a day to day basis with my 16 MHz microprocessor!

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

Well, I fumbled around in WordPress and managed to do something not too shabby. There are some CTA buttons if you know where to look, formatting the layout is a little restrictive so it is difficult to match the look of the standard panel page… but its close.

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

Thanks dasfaker, I thought this might be the case.

does anyone know if we have the ability to create Call-to-Action buttons in WordPress, or is that limited to the administrator?

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

Good point, I’ll check out the latest Mac download now my current project is done.

Macs have a utility called Bootcamp which lets you run Windows on the hardware bypassing the need for a VM running in the OS, which is a good option too (especially if you have a second machine to hand).

Thanks again Possemo.

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

The button are OK and work within the constraints of Ctrlr version 1590, options from the newer version are listed but just not available. I can work with that.

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

Hey Possemo,

I think I know why I have this peculiarity in my panel. I created the panel in Ctrlr version 1590, when I started my update I thought it was a good idea to download the then latest version (not sure of number), however I had some problems. I was advised to backdate to Ctrlr version 1590, however as I had worked on the panel and saved it there seem to be some artefacts of the newer version that are not implementable.

So in answer to your question if I make a new panel and create a new uiButton it is entirely as it should be for Ctrlr version 1590.

As I am familiar with this version, old or not I am kind of sticking with it for the time being, especially as the update is pretty much done. However what Mac version are you using (virtually)?

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

Hi Guys,

Well I thought I was going daft and missing something, however it would seem that it is my version of ctrlr that has something missing!

So for the moment I’ll have to go with dnaldoog’s method until I can sort out why these options are not available to me.

That said I am now looking for someone who can export restricted instances for PC / Windows.

Attachments:

You must be logged in to view attached files.

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

Thanks dnaldoog,

I had some spare time this evening so I tried out your solution on my panel. It works, thank you very much. The example panel was of great assistance.

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

Possemo wrote:

I am using an uibutton in most cases but it works with static labels as well. Important thing is using “on mouse down” instead of “when value changes”.

OK, where do I attach the method to the uiButton if I am not using ‘Called when the modulator value changes’?

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

Possemo wrote:

IMHO there is no issue directly related to the popup menu. In some cases lua scripts are executed on startup – e.g. when you attach a script to the “on value change” of a button. Use “on mouse down” instead and it will work as expected.

Hi Possemo,

The issue is all mine as I have been trying to work around this for a while : ~ )

So do I understand you correctly this can be done with a uiButton or do I need to use a static of some other component? I ask this as I have checked the ‘Trigger button on mouse down events’ check box under ‘Component Generic’ set the values for the On and Off states both to 0. However I am still getting the popups on load. My method is still attached via ‘Called when the modulator value changes’.

Hi dnaldoog,
Thanks for update, I am going to pursue Possemo’s comment first as it sound like it avoids workaround scripting… lets see how this goes. Nice demo panel by the way, very useful.

Cheers for your replies.

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

Thanks dnaldoog,

I’ll give that try and let you know how I get on.

lfo2vco

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

Hi Guys,

So I have been trying stuff out unsuccessfully… however my popup menu methods now look like this.

kiwiMenu = function(mod, value)
	if isReady() == true then

-- 		Main Menu
		kiwiMain = PopupMenu()
-- 		Load Bank Menus
		loadBank = PopupMenu()

-- 		Blah, blah, blah all the menu stuff which I‘ll leave out

		end

	elseif isReady() == false then
		return

	end

end

I have also been trying to implement this:

PopupMenu:dismissAllActiveMenus()

Trouble is whatever I try I either end up with popups that fail to operate at all or they still launch during my DAW boot up and when dropped into the sequencer window!

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

Quimquim wrote:

lfo to vco you said in a previous message…I have a working method to add bidirectional communication with iuCombos, thus I only required specific bytes of a CC message to achieve this.

I’m interested by your method can you post it?

Hey there,

OK so I lost my iMac to the current heatwave we are having here in the UK, so at the moment I an computerless. Thus this is not the most up to date version, but it will work.

OK so the following message is attached to the ‘Called when panels receives a MIDImessage’ dropdown in the panel settings.

midiMessageReceived = function(midiMessage)

	-- Controller Byte
	midiCcID = midiMessage:getData():getByte(0)
	-- MIDI Channels
	if midiCcID >= 0xB0 and midiCcID <= 0xBF then

		-- Parameter Byte
		midiCcMod = midiMessage:getData():getByte(1)

		if midiCcMod == 0x08 then
			dcoOneRangeMessage(midiMessage)
		elseif midiCcMod == 0x10 then
			lfoModeMessage(midiMessage)
 		elseif midiCcMod == 0x67 then
			atLevelMessage(midiMessage)

		end

	end

end

So I don’t know how much you know already, so please excuse me if I’m telling you how to suck eggs. This method grabs the MIDI message via midiCcMod, then if midiCcID >= 0xB0 and midiCcID <= 0xBF identifies it as a continuous controller. Then midiCcMod = midiMessage:getData():getByte(1) grabs the parameter byte which identifies which modulator to assign it to. Then if midiCcMod == 0x08 then etc., passes to another method that acts on the modulator. Such as this:

dcoOneRangeMessage = function(midiMessage)

	-- Value Byte
	midiCcData = midiMessage:getData():getByte(2)
	if midiCcData >= 0x00 and midiCcData <= 0x23 then
		DCO1Range:setModulatorValue((0), false, false, false)
	elseif midiCcData >= 0x24 and midiCcData <= 0x53 then
		DCO1Range:setModulatorValue((1), false, false, false)
	elseif midiCcData >= 0x54 then
		DCO1Range:setModulatorValue((2), false, false, false)

	end

end

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

Well, I may have got to the bottom of this issue.

I removed the Index Bootstrap variable from most of my scripts to see what would happen. The result was that I encountered the same error message as was being created by the VST version. This speeded up debugging as I didn’t need to export a VST every time to check the results of my changes. I also noted that it only affected two scripts when I have multiples in a similar format.

Index Bootstrap Variable:

	if panel:getRestoreState() == true or panel:getProgramState() == true then
		return
	end

First action was to double check that the syntax was exactly the same on the two erroneous scripts as the other non problematic scripts; it was. This lead me leave the coding and look for other possible issues within the panel.

Upon inspection it turned out that one of the scripts was also assigned to a Modulator via the ‘Called when the modulator value changes’ menu. This was obviously wrong as the script is intended to assign a value to a Modulator not vice versa. I corrected this, it worked.

I could not find a similar problem for the other script, however assuming it was a similar problem I renamed it. This also worked, I guess as it broke any possible links to a Modulator via ‘Called when the modulator value changes’.

So now all I have is an issue with pop-up menus that launch at Panel Boot in the VST to sort out, but that is in another thread.

Thanks again for all your help Possemo and Daimondamp.

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

This is the trouble with copyright law, in addition to protecting intellectual rights ownership as intended it can also be used to leverage marketing strategies. Its a shame when someone like Roman who has created a non-profit and very useful utility for musicians, putting many, many hours of his own time for no personal monetary gain is shut down in this way.

Bravo Steinberg… and thanks a bunch.

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

Hi Guys,

Sorry Daimondamp I didn’t understand what you were posting, my skills in this area are limited so I fumble through with a lot of help from guys like Possemo and yourself.

I noticed the DMCA notice on Roman’s Github page the other day. I thought it was rather crap considering all the effort Roman has put into ctrlr and also taking into account it is non profit software.

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

Thanks for the feedback guys,

Possemo, I have taken on board your suggestion regarding the comments, I am currently going though and amending all my scripts putting the comments on a new line. When completed I will test to see what effect this has first, and then if necessary move onto adding the ‘nil’ value between ‘if’ and ‘elseif’ as you suggested.

Diamondamp, thanks for the pointer regarding MIDI messages being overwritten this hadn’t occurred to me. I will try the local variable and see if it makes any difference, once I have completed and tested the changes discussed with Possemo.
Regarding your last post, I have a working method to add bidirectional communication with iuCombos, thus I only required specific bytes of a CC message to achieve this. But thank you for the detailed suggestion and code.

I will report back and let you both know how I get on.

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[lfo2vco]

OK so I tried adding this to lfoModeMessage:

	elseif midiCcData == nil then
		return

It stopped the error at boot but also stopped the method working at all.

So I am wondering if this might work instead:

midiMessageReceived = function(midiMessage)

	if panel:getRestoreState() == true or panel:getProgramState() == true then
		return
	end

	midiCcID = midiMessage:getData():getByte(0)  		-- Controller Byte
	if midiCcID >= 0xB0 and midiCcID <= 0xBF then	-- MIDI Channels
	elseif midiCcID == nil then
		return

		midiCcMod = midiMessage:getData():getByte(1)	-- Parameter Byte

		if midiCcMod == 0x08 then
			dcoOneRangeMessage(midiMessage)
		elseif midiCcMod == 0x10 then
			lfoModeMessage(midiMessage)
 		elseif midiCcMod == 0x67 then
			atLevelMessage(midiMessage)

		end

	end

end

Any thoughts or pointers in the right direction are always welcome.

Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal

[Author]

Posts