quirky things in 1137

[msepsis]

#1 ProgramChange MIDI message type.. the only way I can get my program change knob working is if I go to edit mode, change the midi message to something else, then back to program change. I’ve tried with just a generic new uiSlider with nothing changed but the midi message type. works initially, but save, close then re-open the panel and it does not work…

-importing resource on top of pre-existing is not writing over old resource, regardless of setting in ctrlr preferences (after verifying setting, closing and re-opening ctrlr)

-edit lua script from properties panel on right side does not work.. seems you must open lua editor from toolbar, then click edit script.. twice. It’s kinda quirky and I’m sure you’re aware of it but it’d be great to see this fixed as it can get a little tedious. Sometimes you can not open/draw focus to the lua editor at all by clicking a script’s edit icon in the right side modulator properties list.

-sort by name in method editor doesn’t work ” title=”Sad” /> will be nice when it does!!

-some quirkiness when adding groups/folders to the new method editor – minor but there seems to be a spacing issue before the group/folder’s name when looking at that tree view in the left side of the new Lua method editor. First time I added any folders, I named them, added some scripts to them, saved the panel but then when I came back the next day the group names were gone. Not a big deal and hasn’t happened again since I renamed them, but thought it worth mentioning.

Monstrum Media | Music, Sound & Software Design, Chicago / San Francisco listen

[atom]

I’m aware of some of this stuff, some of it is fixed already, some i’ll take notice and fix.

But the new nightly will have a major LUA API change, and nothing old will work i’m afraid, i need to migrate the old API to something more usable and extendable. I’ll try to document the new stuff much better.

[msepsis]

"atom":nt8c14oq wrote:

…the new nightly will have a major LUA API change, and nothing old will work i’m afraid… [/quote:nt8c14oq]

uhh… define "nothing" please. ” title=”Neutral” />

Monstrum Media | Music, Sound & Software Design, Chicago / San Francisco listen

[atom]

Just the LUA stuff, i mean the classes will change names so it’s all one standard of naming stuff. Also no more nasty wrappers that i wrote, i’m trying to bind pure JUCE classes that are sure to work, and my stuff might be buggy. Also it will be simpler to update later on. Loads more drawing stuff, and hopefully the ability to create child components so you can create really complex components.

[TK.]

Could you please give us a [b:2edchx4u]vision[/b:2edchx4u] for a consistent Windows and Mac release with all outstanding issues fixed?
Somehow I feel that you don’t listen to the users – we are [b:2edchx4u]lost[/b:2edchx4u]!

Best Regards, Thorsten.

[atom]

I’m fixing issues as i’m changing things right now, there are issues posted in the bug tracker i’m trying to fix them.

i’m also working on some major issues and to fix them i need to change some parts, i simply wrote them wrong and now they create issues.

visions… i don’t get them, right now is to stabilize the LUA API and make the Program Manager to work, fix the bugs that were reported. I’m not planning any changes in the structure or anything else. Stability is my concern, i want to remove stuff not used and make the code as stable as possible.

[msepsis]

"TK.":20q497qz wrote:

Somehow I feel that you don’t listen to the users – we are [b:20q497qz]lost[/b:20q497qz]![/quote:20q497qz]

Maybe a bit more heavy-handed than I’d say it but I agree with the sentiment that it’d be nice to get as many of the priority bugs/issues sorted before implementing what sounds like a wide-sweeping Lua Class changes that will necessitate changing all our Lua scripts. If you’ve got one or two scripts no big deal but on a panel with ~150< scripts… holy christ, I’m not looking forward to that. Could that be put off for a bit or is that actually integral to the bugfixes/stabilization?

You’ve got your hands full keeping up with changes/developments to Juce, Lua, Boost, LuaBind all while listening and implementing user requests, so I’m not sure I’d say you[i:20q497qz] don’t listen[/i:20q497qz] to users… I don’t think that’s a problem at all actually.. it [b:20q497qz]is[/b:20q497qz] worthwhile though to get some input from the users on change/feature/bug fix priorities as it is to hear from the developer what the general road map is based on that input. I’d certainly vote to do as much stabilizing of what’s there before implementing much more new — it sounds, atom that that’s also your priority at this point too..

Any chance, atom you could shed some light on what might be going on with this modulator I have w/ a program select midi message type assigned to it? I don’t seem to ever ever have this issue with this panel up until 1137, now I’m seeing it in 1102 after reverting.. Any ideas why I need to change the midi message from program Select to something else, then back to program select for it to actually send a program select message? I seem to recall this issue long ago w/ modulators that were sending sysex midi messages. Same deal.

Monstrum Media | Music, Sound & Software Design, Chicago / San Francisco listen

[atom]

I don’t know what to say…

– i checked the program change slider i couldn’t stop making it work, can you create a small panel that demonstrates the problem ? i can’t reproduce it
– i’ll try to keep the compatibility level at maximum, what i’m changing are the names of classes, i’m not removing any LUA functionality i’m just adding some, and renaming some classes to keep it consistent
– in parallel i see a lot of bugs and issues that i’m fixing
– please remember that i have to make decisions like that, 2 days ago JUCE changes the way it calls slider setValue() methods, i had to refactor a lot of my code, noone asked the author to remove the change or was worried that they have to change the code, either they did or they stayed with some older versions.
– i bought an AKAI LPD8 so i can start writing some controller code, so you can link any modulator to controller events (i need to re-work the MIDI settings dialog to get that working)

[atom]

The group names are fixed
Sorting is also fixed

[msepsis]

"atom":oc8fhfhz wrote:

I don’t know what to say…

– i checked the program change slider i couldn’t stop making it work, can you create a small panel that demonstrates the problem ? i can’t reproduce it[/quote:oc8fhfhz]

will do. At least helpful to know whether this is reproducible. I’ll pm you a link to the panel in question and you can take a look for yourself.

"atom":oc8fhfhz wrote:

– i’ll try to keep the compatibility level at maximum, what i’m changing are the names of classes…
– please remember that i have to make decisions like that, 2 days ago JUCE changes the way it calls slider setValue() methods, i had to refactor a lot of my code, noone asked the author to remove the change or was worried that they have to change the code, either they did or they stayed with some older versions.
– i bought an AKAI LPD8 so i can start writing some controller code, so you can link any modulator to controller events (i need to re-work the MIDI settings dialog to get that working)
[/quote:oc8fhfhz]
-great. Maybe I over-reacted to "the new nightly will have a major LUA API change, and nothing old will work i’m afraid"… that sounds kinda drastic ” title=”Neutral” />
-I definitely feel for you on this one. Keeping up with change can be a royal PITA.
-awesome. I’ve got an LPD8, it’s a great little controller.

Monstrum Media | Music, Sound & Software Design, Chicago / San Francisco listen

[msepsis]

"atom":1ms6k8kj wrote:

– i checked the program change slider i couldn’t stop making it work, can you create a small panel that demonstrates the problem ? i can’t reproduce it[/quote:1ms6k8kj]

Ah ok I had removed the default "blank" F0 00 F7 sysex message that’s attached to every modulator on creation. Also, like I did on all of my modulators that don’t send CC messages, I set the MIDI Controller Number to 0 to avoid possible reaction to, say a generic CC01 modwheel sweep from the user’s keyboard controller. . . So I usually delete out any sysex formula if the modulator is not sending a sysex message and set any MIDI Controller Number settings to 0 if the modulator isn’t intended to send a CC.

Seems if I just add the F0 00 F7 message back to the sysex formula for the program select modulator on my panel it works again w/o me having to reset the MIDI message type to programSelect.

Ive never noticed any other modulators that break if you remove the sysex formula.. so this is still strange although I’ve found the "fix".

Monstrum Media | Music, Sound & Software Design, Chicago / San Francisco listen

[Author]

Posts