[Puppeteer]

It would be OK if the export sized the window and the background image correctly. In Win 8.1 64 bit, this doesn’t currently work. Another option would be to make it so that the author could choose whether or not to allow the window to be resized, by introducing an option at the panel level, and would probably be the most flexible compromise.

For simple panels it shouldn’t be too difficult to scale and move the elements to let the end user resize the window, or to do something like the impOscar plugin and provide different sized presets.

The Puppeteer
http://godlike.com.au

[Puppeteer]

Hi Atom,

I see that this was changed on the change log

a2ef918 RomanKubiak Thu Apr 23 18:00:44 2015 +0200 Added a small check for restricted instances, to disable resizing.

Can I ask why this was done? It makes it next to impossible to export a VST properly, at least on my system.

The panel size parameters don’t seem to work properly and the background image always gets messed up and the end user can’t adjust things to make the window the right size.

The Puppeteer
http://godlike.com.au

[Puppeteer]

Will getMidiMessage(0) continue to work in the future? I’m still on build 107 and will stay with it until the panel resizing in VST’s is fixed.

The Puppeteer
http://godlike.com.au

[Puppeteer]

OK, thanks that works.

The Puppeteer
http://godlike.com.au

[Puppeteer]

I get this error (attached)

I’m trying to follow the advice and examples in these threads.

change midiMessageType of a modulator in LUA

Changing Images – what could be wrong in that LUA code

Attachments:

You must be logged in to view attached files.

The Puppeteer
http://godlike.com.au

[Puppeteer]

No, it was the version I had sitting on my tablet, so gave it a go.

The Puppeteer
http://godlike.com.au

[Puppeteer]

Somehow that panel is working OK again now. One other panel is still half broke (half the resources load, the rest don’t).

I think what I did was to load up the bpanelz that was working in the standalone and then open the other panels (ie more recent versions) by double clicking on them in windows explorer, and then things seemed to sync up again.

I still think there’s an issue with resources being somewhat cached or global between panels. I think that each panel should go out and fetch the resources when it is opened, if they are not saved within the panel as a bpanelz. When standalones or instances are created, the resources should be packaged with them.

The Puppeteer
http://godlike.com.au

[Puppeteer]

For whatever reason I cannot export panels with resources from my main computer. I can export the exact same bpanels from a separate computer and it works every time, but from my main computer it no longer works.

I’ve wiped ctrlr, deleted the AppData/Ctrlr directory, generated new UID, saved to new locations, reloaded resources, reattached resources to the existing controls, run as administrator and resources just do not work from this computer.

I’ve installed 1655, the same version as I have on my tablet and still no resources.

The exe files are about the right size (10MB), but even if I move them to another computer, there are no resources on the other computer.

Generating the exe from the other computer generates an exe with the resources that displays fine on that computer, but when I try to open the exact same file on my primary computer, again there are no resources.

I’m lost as to what I can try to get the resources back on my primary computer.

The bpanelz opens fine and everything shows up OK, but as soon as I make an instance or limited instance, the resources don’t display.

Is there anything else I can try? This is doing my head in.

The Puppeteer
http://godlike.com.au

[Puppeteer]

Finally got these exported by opening the bpanelz on another computer in Rev 1655.

The Puppeteer
http://godlike.com.au

[Puppeteer]

I’ve tried deleting /AppData/Ctrlr and /AppData/Ctrlr Panels with no success.

Any other recommendations to get this to export? I’ve pretty much finished the panel and need to get it out to my beta testers.

The Puppeteer
http://godlike.com.au

[Puppeteer]

Have you tried placing the image and slider on different layers?

The Puppeteer
http://godlike.com.au

[Puppeteer]

Thanks, that works.

The Puppeteer
http://godlike.com.au

[Puppeteer]

I’m having the same problem. I’m trying to export restricted instances of panels and the resources aren’t there either in standalone or as the .dll.

The bpanelz opens fine.

Anything I can try to get this exporting?

The Puppeteer
http://godlike.com.au

[Puppeteer]

Hi Atom,

how() in the console returns an error

ERROR: std::runtime_error: ‘Trying to use unregistered class’

what(panel) works fine though.

The Puppeteer
http://godlike.com.au

[Puppeteer]

I can get what() to run (eg set a push button that runs what(panel))

But how(panel) returns this error

At line [-1]: [C]
What: C
Namewhat: global
Name: class_names
Error message: std::runtime_error: ‘Trying to use unregistered class’

This is my function

WhatMethod = function(--[[ CtrlrModulator --]] mod, --[[ number --]] value)
how(panel)
end

Is that how it’s supposed to be used?

The Puppeteer
http://godlike.com.au

[Puppeteer]

BTW – I’ve found the entire sysex docs for the DP4+ if anyone needs them.

The Puppeteer
http://godlike.com.au

[Puppeteer]

I know this is an old thread, but I was wondering if the API docs are still available somewhere. This link is dead

all the possible properties for each component/modulator/panel are documented in the API DOcs here: api/namespace_ids.html use only those.

The Puppeteer
http://godlike.com.au

[Puppeteer]

I’m happy to start on Chapter 3. It will be a quick summary of what I know of LUA generally followed by a bunch of examples on accomplishing some specific tasks.

I imagine it will expand over time.

Part 4 and Part 5 I’ll be able to contribute more to as time goes by and I start getting into the MIDI In part of the plugin.

The Puppeteer
http://godlike.com.au

[Puppeteer]

I’m running 5.3.107 on my Win 8.1 64 bit machine with no dramas at all.

I just installed it and it works fine as standalone and the 64 bit plugin works fine in Ableton Live.

The Puppeteer
http://godlike.com.au

[Puppeteer]

Thanks for doing this. I’d be keen to add to it with my experiences of LUA from my Kurzweil PC3 panel, and thought of doing something similar. If you are open to it, I’d be keen to add to your document as I develop the Kurzweil PC3 panel. It’s uses some unusual MIDI so I have to craft a lot of stuff manually in LUA.

Just answering some of the questions you have in the document.

Regarding the colours, the first hex pair is normally alpha (or transparency)

Regarding the librarian section and sending parameters, normally these are done directly when you move the parameter (and in fact if you receive a patch and set the component to match a value it will send them by default as well – there is a post on the forum about how to workaround this). You could use LUA to send a dump or all panel components at once.

For the bubble, there is a parameter in the panel on the right to enable this for particular components. I think it’s down near the bottom. I need to look at this some more as I’d like it to show a mapped value rather than the MIDI value, but that’s for another day.

For the file extensions you pretty much have it right. The various options control file size and whether resources are collected together with it and packaged as a binary.

One other thing is that to create the VST’s etc you need to open your panel in the VST version and then export it from there. The VST version has different export options than the standalone. That’s the only way that I know of to build protected instances (without the panel menu). This is important to me as some of the info I have on the Kurzweil PC3 I’ve received under NDA so can’t share it.

The Puppeteer
http://godlike.com.au

[Author]

Posts