Hi @qyron,
Should be fixed in build 4131
Brad
2 Likes
Just to point out something that’s obvious that I didn’t think about until I had a problem:
From the user guides:
My main laptop battery died, so I dropped in the backup. Nice test to see happens, etc. The main was running C4132 and the backup was still C4062. SyncToy was used to move all songs, notes, files, racks, etc to the C4062. C4062 was started and there were no errors on the load and the first song even behaved as expected. I’d not been saving any old songs to keep that compatibility between C4062 and C4100+, so that worked.
But, none of the midi PGRM changes worked. I figured I have to remap the midi in, but the PGRM change was making in through the expected port. Well, I opened the background rack and the binding page was empty.
I immediately upgraded to C4132 and it worked.
Glad the upgrade worked for you.
Definitely having a backup system with different version of Cantabile isn’t the best idea.
fwiw: instead of upgrading to 4132 you could also have just renamed the .pre4100 file.
Brad
I’ve been doing a lot of shows so I hadn’t gotten the 41xx versions on a gig rig till the last few days. On most of my standard song setups there were no problems. There are many songs to test so I will be looking into that the next few days. I have several so far that use some more complex rack tricks and I had to work through that but it was a changeover to a new auto fade rack that caused the extra effort. I have rehearsals and gigs this week and hope to run it for those with a 40xx backup rig for unexpected things. So far it’s going well! 
2 Likes
Glad you are testing 41xx. I want to catch up on the builds, but like you, I’ve been busy, and I learned several years ago NOT to upgrade before upcoming shows. Lucky for me you are the guinea pig! 
Glad you are getting good results so far. Brad is really working his butt off on the new builds. Quite an amazing guy.
2 Likes
I take the same approach, but am now between gigs, so have taken the plunge. I am probably not an extreme user, but I do have a lot of bindings in my songs, and so far so good……
2 Likes
Just a quick comment on this. As far as I’m aware 41xx is stable, but I’m holding off a little before officially pulling the trigger on it.
Regardless of stability I would never advise a big upgrade like this before a busy period of gigging. Leave it till you’ve got time to test it and sort out any issues that should never happen.
1 Like
Hey Folks,
I played for a full rehearsal last week & two 3 set gigs on the weekend using 4134 and it went fine. No issues to report. All my sounds, Dave racks and set-list management worked the same as in 40xx versions. Stability was the same as 40xx versions for me, runs for hours with no crashes. I’ve been running it hard for 3 weeks and I am going to consider putting it on the BU laptop soon. I’m still learning where everything is in the bindings edit window but it’s coming along.
Many thanks for your work, Well Done Brad! 
Dave
9 Likes
Thanks Dave. I think I will have an opening soon to make the upgrade. Keep us informed! 
1 Like
OK folks, for my uses 41XX is now the primary. I am switching the backup laptop to it next. I realize i don’t have a very complex setup compared to some here but I am actively using it as the regular now. My general song setup is
- Media player for song rehearsals and reference per song
- Master output rack and buss reverb rack per song
- 1 to 6 instrument racks with various splits and transpositions
- pedal input bindings custom per song
- automated fader rack on a few songs (uses Smoothie plugin)
- RD2000 hardware configuration rack (lots of sys-ex in this one)
- Custom controller bars for work and live views
- jpg lyric/chord display in Show Notes
- no backing tracks
I run pre-load for about 175 songs in the song list I draw off of using about 15 gig of memory for the whole set list. I am still adjusting to the new bindings layout but I’m getting there and really like the instant implementation of changes I am seeing when editing bindings.
For my setup I have not experienced any lost patches, just a few bindings repairs that led to Brad upgrade fixes. All in all I’m off and running with it. I did a thorough backup of 40XX before I switched to be safe.
Cheers,
Dave
5 Likes
Thanks Dave,
Yep, the new bindings is pretty much stable. I’m leaving it marked as experimental though until I get this next batch of changes ready.
Brad
6 Likes
In the bindings, for button and no-edge button, it is possible to indicate value(s). Can I provide more than one value, and if so, how does it work, is it like latch stepping through the values? And then, what is the format (aka separator), I have tried all the characters I could think of.
Hi Torsten,
The answer is yes it can or “it should”. I use it a ton. You use a comma to separate the values. the button presses will step through the values sequentially and loop back to the beginning when you reach the last value. If you use button or no edge controller it latches
but if you use just controller it doesn’t latch.
Cheers,
Dave
2 Likes
Thanks. Well, I try to switch between 0 (zero) and 0,5 (half), might be the reason it does not yield the results I expected :-). Seems I’ll need a chain of bindings to translate a value into the 0,5 that I need.
3 Likes
Ah, I’m used to European style using , as separator. Obvious mistake on my part. Will test as soon as I get home (at a birthday party).
Thanks!
1 Like
I’m not at my PC,but I think that Cantabile respects regional settings. With a decimal comma, you’ll need to use a semicolon as a separator.
So using 0;0,5 should do the trick, if I’m not mistaken
2 Likes
I think that’s right @Torsten, I didn’t remember it until you mentioned it but it has come up in the past. Thanks for posting, it should really help Torsten. 
Yes, for punctuation @Torsten is right, Cantabile follows the regional setting.
I had had problems with a similar setting, I was inserting the “,” but needed to insert the “;”.
To find out, because I was not aware of it, I noticed an old post in the Forum, replaced the punctuation and everything worked.
2 Likes
You can select whether it is regional or English:
And I had tried all options I could think of for separator, including ;. But turned out that my pedal was to blame, not stable and only goes to around midi 123-124, so sending a lot of noise, which caused the binding to fire seldom and kind of randomly. I’ll fix the pedal setting issue and use the bindings as they are intended to be used :-). Thanks for the help and support and confirmation that it ought to work, finally made me look elsewhere for the root cause.
1 Like