[msepsis]

Hi thank you for checking and addressing that so quickly. Yes that fixed the issue. I’m wondering if that fix could be applied to the most recent stable release for both mac and windows? I’ve been reading of bugs in the revs of ctrlr since 5.3.201 (win) and 5.3.198 (mac) but at least for me those latest stable releases do seem solid.

Thanks again,
Rob

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

[msepsis]

no pressure Roman, no pressure 🙂

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

[msepsis]

Uiwaveform is a component that allows you to visually load, plot and manipulate, as its name implies, waveforms! Its not obvious but if you right click on the component you can load in waveforms. Its what mad my waldorf microwave and mwXT editor’s wave editing possible. There is a struthi editor somewhere that used the component very well

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

[msepsis]

Im really glad you got it working. Also great to compare notes and get some confirmation from someone else with a similar experience. I hope you didnt try each one since 1590 until you got what you were expecting out of it!!

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

[msepsis]

Common misconception you might share:
“Latest is greatest”
Not true here.

I would recommend going back a few versions in ctrlr.
Incidentally you haven’t mentioned what ctrlr rev you are using – that’s paramount to the types of issues you describe. .

Try it in 5.3.50.. does the issue persist? If so go back earlier
1590 is my go-to for sanity checking things like this as it was quite solid although missing a few of the updates (Lua, Juce, etc) that the more recent revs have.
Generally in the larger picture of functionality and stability 1590 likely isn’t missing anything you need to be honest, although I have no clue what it is your panel is to be doing.

Also incredibly important at least in my experience when debugging stuff like this and testing out different ctrlr revs –
CRITICAL that you trash ctrlr preferences to ensure you’re starting w/o snowballing issues. This is especially important when changing revs.

If you’re running into issues testing an exported instance (app, exe or vst/au) you’ll be wanting to trash the preferences for that panel instance name… settings/prefs for that panel will be in the same location as the ctrlr folder, but the folder will be named the same as the panel’s exported instance. .

• This reply was modified 7 years, 7 months ago by msepsis.

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

[msepsis]

For the time being I’m sticking at 5.3.50 – version just before “MIDI Settings” were added to the menu (which IMHO confuses matters further since the old method is still there, just not usable the old way by ticking the options.

pretty much have identified the original issue i started this thread about – you’re to use the midi settings dialog, not tick the options in the MIDI menu.. but until the options in the midi menu are removed (the old way) it’s confusing.

I’ve noticed a few quirks here and there in 5.3.50 but nothing added into ctrlr since then I feel is absolutely necessary.

• This reply was modified 7 years, 7 months ago by msepsis.

Attachments:

You must be logged in to view attached files.

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

[msepsis]

Thanks for your follow up here.. it helps to compare notes to track these things down.

I went through last night and tried all these below (yes indicates whether the issue I’m talking about occurred)

5.3.198 yes
5.3.163 yes
5.3.122 yes
5.3.85 yes
5.3.83 YES (device list listed “error” for every device)
5.3.81 yes
5.3.57 yes – (when new MIDI>Settings) dialog appeared in ctrlr
5.3.50 no
5.3.3 no
5.3.0 no
5.2.139 no
5.2.99 no

When looking at the 5.3.57 and higher revs I just happened to notice the MIDI Settings dialog under MIDI – Settings.

I’m just inferring on what occurs that the preferred method now is to set these settings here as once you do they appear ticked in the locations we normally would manually set these. I don’t know if those actually get saved with the panel as a default – it really should since theses are necessary settings for the VST to operate as a normal human would expect it to.

**Thanks for posting your workaround, I noticed these global options as well – that should be the way to get them set by default.

So there was a ctrlr rev where snapshots and MIDI library actually functioned properly? 5.3.83? Where was that at in 5.3.50 before the introduction of this new MIDI Settings dialog?

• This reply was modified 7 years, 7 months ago by msepsis.
• This reply was modified 7 years, 7 months ago by msepsis.
• This reply was modified 7 years, 7 months ago by msepsis.

Attachments:

You must be logged in to view attached files.

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

[msepsis]

all hope is not lost. 🙂

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

[msepsis]

I went on another mac and confirmed it’s the same here (both running latest mac os el capitain… i went back a number of mac revs 5.3.163, 122, 85.. I then jumped back a bit further and tried 5.2.99, 139 which is the most recent rev I’ve tried where this doesn’t seem broken.

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

[msepsis]

my 2 cents?
For the most part as far as my experience best practice is to only use controller in when using stand-alone for connecting a (you guessed it!) MIDI controller in case you don’t want to just use the gui.

All other cases you generally want the MIDI IN and MIDI OUT devices pointed to and from the synth you’re controlling. Unless doing something really bizarre there should be no reason to use the controller in device when using ctrlr as a VST/AU in a DAW.

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

[msepsis]

Ok so i figured out what changed since the last stable mac/win/nix ctrlr i was using.

The method called when the contents of a LCD label changes gets triggered when the panel is loading now (seems its been that way for a while) so i had to put a isLoading check on line two.

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

[msepsis]

Hi GW, thanks for your reply.
It’s true about seeing the full context but I’m fairly certain the issue is within those two lines, the rest of the function is dumb stupid simple stuff 🙂

I like the method you suggested so as to init on panel load although doing so for literally “all modulators” shouldn’t be necessary unless calling them in Lua.

Thanks again for your reply

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

[msepsis]

mosen – I appreciate the bump. I’m actually waiting on updates to ctrlr in order to address the sort of issue you’re describing. I believe the matrix 1000 editor used a different rev of ctrlr that likely has the issue you’re referring to addressed – HOWEVER the more recent releases have introduced new bugs, particularly on the mac…

I did not forget this and have been doing a good bit of pinging and checking in myself.
In the meantime I’m drafting an email to you for a workaround solution.

Cheers,
Rob

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

[msepsis]

Hi Mo,
Thanks a lot for your patience. It’s been an incredibly ridiculously busy month so it’s taken me a lot longer to get back to you.

If I did not already ask you to try this please do, forgive me if they seem trivial:
-Trash preferences located in: \Users\(your user name)\AppData\Roaming\(editor name)
-Possibly try a different DAW? Reaper?
-Possibly try a different new fresh windows 7 user account

I was having difficulties with my windows 7 partition the last time I sat down with time dedicated to attempt to reproduce this on my testing machine. I believe that issue is sorted and am going to attempt to reproduce what you’re reporting on my system this evening.

Thanks again for your patience. If I might ever be slow to reply there’s one thing you can always count on – I will reply 🙂 So thanks again for your patience.

Rob

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

[msepsis]

Any word on this?

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

[msepsis]

*bump* this is a problem. Can not export instances from ctrlr linux

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

[msepsis]

I was not having success with snapshots on my most basic panels … maybe it’s something I’m (not) doing…

I’m just curious if the compatibility flag could be set to 10.6? I still work on 10.6.8 and still IMHO consider it the last good OS X for pro audio especially on the last good mac pro 5,1 cheese grater tower. If it comes at the expense of loose compatibility for current forget it but I don’t think it should…

Rob

Attachments:

You must be logged in to view attached files.

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

[msepsis]

Thanks a lot Atom,
i’ll be giving this a spin in the next coming days.

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

[msepsis]

Possemo wrote:

I would try this:
panel:setPropertyString("midiMessageChannel","1")

except that will just set the midi channel to 1. If you want to use a knob or combobox etc to set the channel you’ll want to change that “1” to “value” and assign that lua script to the knob/combobox.

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

[msepsis]

*bump* on the mac build with working snapshot – it’s been a while. I would LOVE to see these snapshots that work!

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

[Author]

Posts