Cantabile 4 Alpha Available

Hi @Derek. Thanks for sending those files. I’ve reproduced the problem and working to understand and fix it now…

Brad

Yes, I am and yep, I’m considering switching to 6.

Hi @Derek

I think I’ve resolved the issues with media players, however… I basically rewrote the entire interaction between the media players and the timeline view to also sort out some other annoying issues (like the flicker between the timeline axis and content render when switching loaded files in a media player).

So, I either fixed it or introduced some other bugs (or both?)

All that’s to say… give 4008 a go and let me know.

Brad

2 Likes

Hi, Brad

Yes, whatever you did seems to have done the trick :slight_smile:

Haven’t tried every single song in the set, but went though quite a few, and I checked some of the other sets as well to ensure that they remain OK.

1 Like

Great. (fwiw, part of the problem was related to scanning the audio peak data which is why it didn’t happen on all files, if the peak data was already available).

You have me intrigued now about the part of MIDI Ports (or the lack of) had to do with it, or was that a red herring? Or did the deletion of a port trigger a rebuild of the peak data?

I think it must have been a red herring. Nothing I changed had anything to do with MIDI ports. The peak scan thing was a bit random so it might have just been a false correlation.

Thanks for your help chasing this down… much appreciated. :slight_smile:

2 Likes

The C4 Alpha is really taking shape! I am using it exclusively at home for setlist, song and rack development and for practice sessions with no issues. I like the improvements and I’m not noticing any performance degradation from C3. If anything, the C4 UI seems a bit “snappier”.

2 Likes

I have 4.10 on my performance rig and ran rehearsal sets as I would with Version 3 and it worked great. Also noticed the “snappier UI” and liking the crispness of it. Functionally and graphically it’s a working tool to me at this point with I hope few errors that might surface for folks using it differently than me. I am leaving it up and running to see how it does with being left on long term. Planning full band rehearsals with it this weekend. Like @bpeterson1123 said it is really taking shape!

Dave

6 Likes

Hi @dave_dore and @bpeterson1123,

Pleased Cantabile 4 is starting to stabilize. Thanks for your help reporting issues and diagnosing the causes.

Brad

3 Likes

I’ll be doing some Pink Floyd practice over the weekend, ready for a possible band rehearsal over Christmas (but with the country seemingly locking down by stealth …) and will use C4 over C3 to see how it holds up over a few hours worth of playing.

I do not used many VSTs in Welsh Floyd, Hammond and Mini Moog in the new songs (oh and Farfisa and Echorec in Echoes!), but there is a lot of routing and switching going on.

3 Likes

I ran some tests to check how the MIDI sys-ex bindings for my control rack I use with the RD2000 & it passed all tests no problems. Also checked out my TouchOSC surface and all is working there too!

Dave

2 Likes

Pleased with how Cantabile 4 is coming together. Currently known issues::

  1. Possible performance issue with audio engine. (Still need to investigate as I’ve been focused on getting it stable first)
  2. jBridge plugins crash when their GUI opened (have contacted jBridge developer, awaiting reply).

Let me know if I’ve missed anything, or you find something new.

5 Likes

Before settling down to watch Dune on rental I ran through the following with backing tracks, clicks and my Montage/Kronos key routing and my FC300 foot control. Where I mention external below that could still be me playing my Montage and MIDI routed to the Kronos via Cantabile.

  • Shine on (B3-x and external)
  • Another Brick in the Wall parts 1 and 2 (all external)
  • Pigs on the Wing - the rare Snowy White version (B3-X under the guitar solo)
  • Echoes (B3-X, dual Farfisa and Binson Echorec and external Leslie piano)

All worked well other than for some reason I get an occasional volume drop on the Farfisa that I need to check, but I think I noticed that on C3 as well the other night.

So all in all a 50 minute try out with only that volume glitch to check out.

2 Likes

I haven’t had any issues with version 4 running my setlists and VSTs, but still have to test the songs with audio input (saxophone/harmonicas), will get to them soon.

One very minor detail I noticed (also verified in build 4011) is that the text field for the sample rate and buffer size remains empty (or black text on black background, I couldn’t tell which) when I have selected the values in the drop down. If I enter the settings later, then the text is visible. Purely cosmetic and not critical. I have not checked all the other drop down boxes, I was happy when everything just worked for me and got carried away playing music instead of testing software, sorry. Let me know if there is something in my setup that you need more information about.

And a few more in the cosmetic department:

  • If the menu bar is hidden and I press the Alt key, then the menu bar is shown in C3, but not in C4. It is still possible to press a short cut key, e.g. press Alt and then press V, then the View menu is shown.
  • The menu bar background is white though I am in dark mode.
  • The menu bar of unselected windows/plugin windows is white, though my Windows setup (in W11) asks for a dark color.
  • I have had difficulties turning display of the metronome off, somehow it felt like I could not select it. I can not reproduce now, so might be me that did something wrong.
1 Like

I just tested this here and I’m not seeing that. It looks like a bug that affected all drop downs in an earlier build, but since your other dropdowns look fine I’m guessing this is something else.

Question: when the field is blank and you click the drop down arrow, is the correct item shown highlighted in the list?

Confirmed - I’ll get this fixed.

Cantabile doesn’t currently look at Windows dark/light mode. I should probably do something about that. Currently the theme is coded to a white menu bar, which basically matches Windows 10. I’ll probably do something about this, but not urgently.

Do you mean the title bar? If so, that’s drawn by Windows, so not sure why it’d be wrong. Perhaps post some screen shots? (I’m not at my Win11 machine now to check myself).

OK… let me know if it re-occurs.

Yes, it is highlighted. And if I select another tab and goes back to the Audio Engine tab, then the text also shows correctly.

A few images:

  1. I have just selected Null Audio Driver, this is what I see.
    image
  2. If I click on a dropdown (same for both), the correct value is highlighted. If I click the same value or the arrow the drop down closes and shows no text.
  3. If I select another value then that value is shown correctly.
  4. If I select another value in both drop downs, then change one back to the original, I can get them to come and go and I can not fully make out the pattern what is happening. Can I post videos here?
    But it seems to be somehow related to when I change the audio engine selection.

Here are three screen shots with windows explorer plus Cantible with a plugin (VB3-II) open, I have a screen shot with each being in focus:
a) Windows Explorer has focus (Explorer dark, other two white):


b) Cantabile window has focus (Exporer dark, Cantabile dark, VB3-II white)

c) VB3-II has focus, now Cantabile turned white.

Let me know if I can provide any other information, e.g. Windows settings for the color scheme used.

1 Like

Ah that’s it… reproduced it and will get it fixed.

Yep, ok. I think apps need to opt into the dark mode stuff, so I might need to add support for that. Low priority right now.

3 Likes

Build 4012 is up now and fixes:

  • Alt key now showing hidden menu bar
  • Drop down combo boxes not updating when switching audio driver
  • Crash in text area editor when double click on word and drag past end of doc
2 Likes