Hi @TorstenH,
Not sure what might be causing this. Can you reduce it to a simple sample song/rack that I can use to reproduce the issue here and I’ll check it out.
Brad
Seems to work in the very simple setup I tried - I am not sure if there is anything to do than trying to start all over in a Cantabile setup, there seems to be issues accumulating around in my configuration.
Edit: found a way to reproduce it in a simple setup, I will email you the files needed. Thanks!
It’s been almost four weeks. Stable Release?
I think it’s reasonably stable, but I first want to push it out to the experimental release channel, but I’ve been holding off on it because I’ve been busy with some personal stuff the last couple of weeks and want to be available when I do. Hoping to do that this week.
2 Likes
My main gig is tonight and currently nothing planned after that, so hopefully will be able to give it a spin now when you push out the next experimental release.
Build 4119:
with:
- Fixed - performance hit when playing media file and timeline open
- Fixed - main menu bar not rendered correctly when OpenGL enabled
Same fixes are also available in 4064.
5 Likes
Very nice - the performance hit from using media players seems to be gone!
1 Like
Awesome - thanks for your testing and help with it.
1 Like
Now that the gigs I have spent the last six months writing songs and prepping for are now over for a while, I have taken the plunge with the latest build.
Running through the set quickly tonight, it all seems to be working as it should. It’ll take while to get used to the changes in this area, but I am sure it will be for the better.
2 Likes
Hey @Derek… thanks for that.
I think you’ll quickly get used to the new system - the UI is much better organized and you can see pretty much all the settings in one place. The biggest difference is some (not many) binding points have moved so you might need hunt around for them, use the learn function or look at an upgraded song from previous version.
Brad
2 Likes
No problem. Took me longer than expected to get around to, but no gigs for a while now, so will do my next batch of set programming on this version and above now I have made the switch.
@brad I think there may be a ‘learn’ issue in 4119.
If you try to adapt an existing binding by copying and relearning, the learn fields fail to take on the new input.
Best
Adrian
Uh-Oh: looks like I’ve found another gremlin:
In my keyboard rack, I have bindings that make buttons act as “Octave +” and “Octave -” for a route. These somehow got deleted, and I tried to re-create them in the new bindings system:
When receiving a CC13-127 from my Background Rack loopback port, this binding should transpose the route “Notes” up by 12 semitones. I assume that that’s what the Binding Point “Adjust Transpose” is for. But unfortunately, that binding point makes Cantabile crash consistently whenever I select it, so I haven’t been able to select it (may try creating the binding in 4064 and upgrade it; will let you know if that works or if it creates more mess). For the moment, I’m using “Transpose” as a target, but that limits me to transposing by 12 ST versus the original transpose, but I can’t use it to transpose by another 12…
Hope you can fix that gremlin…
Update: just re-created these bindings in 4063 on my studio PC and loaded them into 4119 - they look and work just fine:
but as soon as I change the Point to something else and want to change it back to “Adjust Transpose”, Cantabile comes crashing down.
So it looks like the functionality is OK, just the editing is somewhat messed up…
@brad - When binding to rack states in 4119 you have the option to Load State with Index.
The selection process does bring up the state names but the result is only the number.
Obviously, numbers are not nearly so informative.
Is there any way to have the text in the Index field?
Cheers again!
The reason for this is that the text associated with a number can change independently of the binding and I don’t have a suitably efficient way to detect that internally and update what’s displayed on the binding.
I’ll look into it though and see if I can come up with something.
1 Like
Investigating now… Found and fixed. New build coming soon.
1 Like
Fixed for next build.
1 Like
Build 4120
- Fixed crash when selecting “Adjust Transpose” binding point
- Fixed Learn button not updating all source binding point fields
Here: https://download.cantabilesoftware.com/SetupCantabile-4120.exe
3 Likes
Thanx @brad - now my Adjust Transpose works!
Here’s a new gremlin: in my songs, I have a bindings group that fires on “StateChange” to start scrolling for LivePrompter - sends out a couple of CC messages to activate scrolling on different connections
I use the “Enabled” state property for the group “Prompter Start” to select on which song states these bindings should trigger. So the three bindings within the group always stay on; just the “Enabled” for the group changes by state.
With build 406x, this works nicely; with 41xx, however, nothing happens - no MIDI messages get triggered. Looks like there’s something messed up with the processing sequence of groups vs. bindings: in this case, on a state load the “Enable” for the bindings group needs to be processed first to enable the group, then the individual bindings within the group need to fire for the state load. But this doesn’t seem to happen.
Another indication of something going wrong: when I enter the state with the bindings group set to “enabled”, the three sub-bindings stay “grayed out”:
When I un-check and re-check the “enabled” box for the group, they become white again - but now they fire on every state load, even though the group is disabled for all other states.
So it looks like the enabling and disabling of binding groups via song states is broken…