Architect beta for macOS, Windows, and Linux. 0.10.5 now available

[mannymang]

I was hit pretty hard this winter as well. I feel for you Colin. Hope you get well soon.

[cturner]

Hi Colin- I thought I'd ask before I headed down the rabbit hole: would it be possible to send NRPN (CC98/99) with the current [pack controller] object?

[colin@loomer]

You can, but you must use multiple calls to a [pack controller] to send each NRPN element separately. Because order is guaranteed, you needn't worry about other MIDI messages appearing in the middle of your NRPN message. I can make a NRPN macro, if you'd like to see an example of this?

[cturner]

Thanks Colin! I'll give it a try myself, and if I come up stumped, I'll get back to you.

[UmFuFu]

Hey Colin,
Curious how it's coming with the library. Have you moved on to working on that at the moment?

Cheers,
B

[David]

Hey Colin,
Curious how it's coming with the library. Have you moved on to working on that at the moment?

Cheers,
B

Exactly my question, too!

[colin@loomer]

Partially, but I've been mainly working on finishing up the outstanding work for the 0.10 release, which adds an out-of-process (and therefore impossible to crash) plug-in scanner. Once that's out, then my main focus will be on the 0.11 release branch, which is primarily concerned with bolstering the library.

[lalo]

Partially, but I've been mainly working on finishing up the outstanding work for the 0.10 release, which adds an out-of-process (and therefore impossible to crash) plug-in scanner. Once that's out, then my main focus will be on the 0.11 release branch, which is primarily concerned with bolstering the library.

i'm lost...isn't 0.11 already out? i've installed it on both my systems.

[colin@loomer]

The current public releases are the 0.9.x line, so you've probably got 0.9.11 installed.

[lalo]

The current public releases are the 0.9.x line, so you've probably got 0.9.11 installed.

i was totally going over the "9"
thanks!

[colin@loomer]

No problem: I did have to double-check that I hadn't butchered the version numbers in the last release, though!

I know version numbering can get confusing, but essentially bigger changes will see a bump in the second digit, whilst smaller changes - bug-fixes and smaller features - will bump the third digit. Working this way allows me to maintain a stable release branch into which I can quickly include bug fixes, whilst still developing new features in isolation.

[lalo]

No problem: I did have to double-check that I hadn't butchered the version numbers in the last release, though!

I know version numbering can get confusing, but essentially bigger changes will see a bump in the second digit, whilst smaller changes - bug-fixes and smaller features - will bump the third digit. Working this way allows me to maintain a stable release branch into which I can quickly include bug fixes, whilst still developing new features in isolation.

[UmFuFu]

Partially, but I've been mainly working on finishing up the outstanding work for the 0.10 release, which adds an out-of-process (and therefore impossible to crash) plug-in scanner. Once that's out, then my main focus will be on the 0.11 release branch, which is primarily concerned with bolstering the library.

Got it. Looking forward thanks!

[mannymang]

Hi Colin, would it be possible to get a minimum/maximum note range for "force to scale"? Thanks.

[colin@loomer]

Hi Colin, would it be possible to get a minimum/maximum note range for "force to scale"? Thanks.

Do you mean in the sense of clamping notes outside the given minimum and maximum to these given limits? If so, that's easily doable: in fact, I believe I could do you a macro right now.