Forum rss-feed

Forum

Software: Nested Belcanto and Variables

Most Recent

written by: keyman

Hi 0beron...
About that 22 bar record setting try this...

kgroup 100 listen
global recorder talker 1 listen
11 to 1 from 2 colour ify
when 11 do 22 bar as bar when 11 define

I still got a 'no agents accept the verb 'do' but it works!

keyman

written by: sfellner

Mon, 3 Jan 2011 16:26:52 +0000 GMT

may be this is from the top shelf sweet box and still out of reach, but Eigenbrowser shows some interesting nested belcanto-commands for Pico

selecting scale:

" empty join 

scale manager hey
cancel
scale manager hey
variable sm1 choose when activation
using scale manager
` empty join
scale manager activation scale as sm1 define
talker 4 hey
5 called 1 cancel
midi input talker hey
72 called 1 cancel
kgroup 1 , talker 4 hey
all scale to activation when 5 called 1 set
kgroup 1 , midi input talker hey
all scale to activation when 72 set
` do
` scale manager scale browse ` do
" when 1 do


recorder selection:
" recorder 5 hey variable bar record " when 9 do 

this goes together with actual bar-selection:
4 bar as bar when 7 define


So, how to use variables and nested commands?
Seems like the scope of "sm1" in first sample spans both levels ('...' and "..."). In second sample the scope of "bar" seems even global.

Just daydreaming that note indicator lights could be set along by scale selection and intervals highlighted relative to any key.
Any hint how to expand the current scale selection with additional commands?

stefan


written by: 0beron

Mon, 3 Jan 2011 18:33:08 +0000 GMT

Yeah it looks like some nice things are possible. I've been trying to set up recorder talkers ( to move the per keygroup recorder arm keys onto the percussion keys) but with a talker in the conversation i am repeatedly told that ' no agents accept the verb 'do' '.


written by: john

Mon, 3 Jan 2011 19:09:32 +0000 GMT

Hi Stefan, 0beron

This isn't so much on the top shelf out of reach as about to change dramatically. The way that this stuff works at the moment is pretty insane, and we really don't like it. We have been getting ready to change it for a while, and the way that variables work will be completely different in the 2.X series, at which point it will be documented as it'll be a lot easier to explain, to put it mildly. The actual syntax and functionality of this stuff was added in a real hurry in the two months leading up to launch in the autumn of 2009 and it's a kludge, it wasn't what I would call well designed. We understand a lot more about the way the system is used now than we did then and I think the upcoming changes will make it a lot easier to work with Talkers in general. The goal is to make it possible for advanced users to edit and change them easily with Workbench, something that the current system does not support. This requires a considerable syntax and systemic change to the way variables work, so it's probably not such a good idea to spend ages figuring out the way they work in 1.X.

We don't keep this stuff from you just for the fun of it, if it were not going to change it'd be there on the Wiki right now, but there's not a lot of point in everyone getting used to something we know we'll break later. Its really that the Talkers (which were a late brainwave of Jim's and just sort of thrown in for fun) turned out to be so incredibly useful that they took on a life of their own in Dave and Sam's hands when making setups and playing in 2009. They didn't really get enough engineering to make them user friendly on the first pass. It's one of our next jobs after we get 1.3 into Stable.


John


written by: sfellner

Mon, 3 Jan 2011 20:04:34 +0000 GMT

Hi John,

just did not imagine that drastic changes could to be made to what looked like fundamental parts. Sorry for wasting your time with impatience again. Good luck with the upcoming transition, sounds like open-heart surgery to me!

The pico is a pure joy to use. From time to time, looking at belcanto gets me excited about things to come, and the eigenharp seminars do their part. It will become an exciting year!

Stefan


written by: sfellner

Mon, 3 Jan 2011 20:08:03 +0000 GMT

Hi Oberon,

just found out that any 'do' requires an "interpreter listen" before. But maybe we wait for the things to come...

Stefan


written by: 0beron

Mon, 3 Jan 2011 20:31:45 +0000 GMT

Ah , good find. I'm not about to launch into major scripting, just moving the recorder arming keys (and having a 22 bar record setting) would be really handy. I'm quite happy to relearn and rebuild setups when this stuff gets a facelift.


written by: keyman

Tue, 4 Jan 2011 03:10:18 +0000 GMT

Almost a year ago "about changes" check John's post...

A lot as happen, and more will come I'm sure.
Let's keep our inventive and discovering spirits alert.

keyman


written by: keyman

Tue, 4 Jan 2011 04:49:44 +0000 GMT

Hi 0beron...
About that 22 bar record setting try this...

kgroup 100 listen
global recorder talker 1 listen
11 to 1 from 2 colour ify
when 11 do 22 bar as bar when 11 define

I still got a 'no agents accept the verb 'do' but it works!

keyman



Please log in to join the discussions