@Brad, I am working with your latest v4 issue. I can’t judge performance differences very clearly and help out there. VST4 seems to work fine. Have some crashes when I switch too fast in racks of big sample libraries (e.g. East West Play) between sample/RAM-thirsty states. I need PLAY to take its time to load them (I have ultra fast SSD’s so loading time no issue for me luckily), to avoid crashes of Cantabile, but after full load of the state, there is no issue anymore.
I just had a crash on using the East West Play Rack with 4.24, upon changing states, but while feeding new notes (the new notes may also be the bottleneck). Sent in a crash report just now.
Maybe there is a way to have Cantbalie not crashing on those situations, but it is not a big deal for me, I can avoid it.
Ad
By the way you have a done great work again @Brad with V4. I know it can be not very rewarding changing the (for users hidden) architecture and language of the code, especially if functionality does not change drastically for the users (I know since I lead a scientific model development team). So users might not understand/reward the changes at first vision. But I guess they’ll realise when you can build changes in future versions of 4, that you could not have done with v3. So a big thanks
Hi @TorstenH, my fault, thanks for noticing. I am using version 4.24, but wrote incorrectly 4.14. Will correct in my posts (done). Also did come across East West PLAY rack crash just now, still in 4.24
I just did some testing on this and it seems to be working fine. Can you send me a reproducible case?
Yes there was an issue here which was fixed at some point in the v4 alpha.
Hard to say - if it’s the plugin itself crashing Cantabile doesn’t do anything to suppress those crashes (deliberately, since masking issues just makes them harder to find). I’ll check out the crash report during the week and see what’s going on. Just had a look at the crash report, it’s definitely crashing in the plugin during audio processing. I’d say this is a bug in the plugin.
I assume I am doing something wrong, so I will give the steps to reproduce:
Create a new empty song
Add a plug-in, I used Pianoteq
Create a state, name it Play (to be used without GUI visible)
Create a linked clone of that state, name it Setup (to be used with the GUI visible)
Select the Pianoteq plugin and in the “State Behavior - Puging” tick the Editor Visibility check box plus right click the check box and make sure that “Exclude from Linked Clones” is marked.
Select the Play state, and if the Pianoteq editor is visible then click Esc to hide it.
Select the Setup state, and if the Pianoteq editor is hidden double click the plugin to show it.
Now select the Play state again.
In my test the editor is now shown in the Play state, which confuses me.
Hi Brad, in our last rehearsal i played around with cantabile 4. I play in a Marillion Tribute Band and I have some complex rigs. All Instruments worked fine. There was no problem with CPU or latency. The only thing that happened that the usb connection to my oxygen 49 got lost two times in about 3 hours.
As Vsts I use native Komplete, the Arturia V Collection, Omnisphere and the Juno 106 Emulation from cherry Audio
Hi @brad,
I noticed a ‘cosmetic’ issue - perhaps it’s intentional.
When a binding is disabled, but has a filter applied, the filter is ‘lit’ instead of grey.
Great. An even smaller minor detail, in the Edit Midi Ports window, if I press Alt-A as a shortcut for Add, then the Add button is selected, but I need to press Enter to open the drop down. I am pretty sure that in C3 the drop down was opened (but I haven’t checked).
Yes. All fields are disabled. It works fine for me with C3.
Now, I just tried External Tools on my desktop machine and I have the same issue with C4, but it also works fine for C3.
Found a possible bug in v4 while working with @dave_dore’s new B-3X Factory rack. When clicking Custom Button 2 to create a new state the GUI Editor takes the foreground in v4027 but doing the same in v3701 the GUI Editor is placed in the background.
This isn’t a bug, the timing of the display items when opening many things at the same time is not always the same. It is a part of the way tasks are done in C3. I am going to see if I can improve this using the new delays features Brad just released. I’ll let you know if I can improve this part after I get the hang of using the new feature, I’m sure I can, the flexibilty and precision is definitely there I just need to get familiar with it. But it will be for Cantabile 4 only.
