I canât do that
I dislike any other DAW for a reason or another
one doesnât recognize my controllers, another doesnât want certain plugins that I use every day (like Bitwig)
and almost all have GUIs I cannot cope with
so I am stuck with cashes on closing, but I can survive to it because I open the DAW again, I select to NOT retrieve the project, then I open that project as usual and it works
it just crashes when I close the DAW, nevertheless I save or not save the project before
If you google âableton crashes on closingâ youâll see other experiment that
And there is always the hope that an update fixes it, even if
this bug was there in 2007, and the support always says the same silly thing âdelete the customizationsâ What? The customizations are useful, even essential, sometimes
So you CAN save before you quit and it just crashes when you close? Sounds like an annoying but not very serious issue at the moment. If you couldnât save then that would be a major problem.
Welcome back - oh wait, you never left!
Yes
A very silly behavior indeed
Well, when I find some time Iâll try to debug
OR
Iâll come back to Bitwig
The problem in Bitwig is that there is no a âScale toolâ like the one in Ableton, and as far as Scaler Keys-Lock work so badly, I cannot do solos without a tool like that
AND
Bitwig seems recognizing my 2 controllers, but after a while it stops seeing them, dunno why
sometime the close the app crashes can be due to audio IO contention, and can also be file contention (sometimes the file handles opened for âtracksâ as temp even, if some other process like A/V scanners, cloud services, other apps can cause an application (not just a DAW) to crash on close).
can you close the project but not the app? or either causes the crash? or there is no option to âcloseâ a project - in which case, after the save, do a ânewâ, and then close the app.
This worked for me long ago when Live was doing that for me. The next update fixed it. But I learned to Save current project, Make a new project and then quit. That did work great. I had forgotten that since Live is totally stable for me these days and for a long time.
I use Cantabile all the time, and find it very useful. If you splash a few EUR on the âSoloâ version, that has really good and intuitive midi routing (very flexible filters). I use it quite often in conjunction with LiveâŚ
Using my M-Audio Keystation MINI 32 was hard or impossible with DAWs, while here I just used 2 clicks to do that
So now I can use the Keystation MINI 32 to activate the UJAM Style Phrases while Scaler plays chords, and I can use the main keyboard to plays solos with the AAS Strum guitar
BTW, I found that the 3 data buttons of Keystation MINI 32 are defaulted to activate the Force and Damp button in the UJAM interface and itâs super cozy
Very interesting
I have 2 questions for you:
1 - if I try to export the Scaler status within Cantabile, the latter freezes and I have to kill it in Task Manager (I asked their support and the forum, but no replies so far)
2 - I am trying to have Cantabile recognizing my 2 MIDI controllers (Korg Nanokontrol 2 and AKAI MIDImix) but they arenât seen
So does mine - never noticed that. However, we canât jump to conclusions here which it is here. I see you have posted on the Cantabile forum - let see what comes out of that. Brad normally picks up on these things.
âCantabile recognizing my 2 MIDI controllersâ
Iâm note sure that âSoloâ will do much, but certainly you should be able to setup an input MIDI port and link it to the MIDI post exposed in Windows. Iât wonât recognise it automatically I suspect. I use LoopMIDI
to create the internal ports, then link these to Cantabile
You can see my Arturia Keylab in there.
Then to respond to the controller you could used MIDI rules capability, but that will probably fail your â20 minuteâ test , but getting the midi in should be straight forward.
I think it is more a problem with Korg drivers, because even the Korg Editor doesnât see it
Somebody in other forums advices to not use them
And
I also found that every time you move a USB device from a port to another, Windows 10 keeps it as a ghost device instead of removing it, so just now I deleted tons of ghostsâŚ
I am a ghostbuster then?
Well, Cantabile has not a mixer, so not a big problem
Nevertheless, I always wanted to use the nano 2 for my Hammond plugin
Iâll do other tests
But before that I have to (try) to rebuild all my 30 Ableton Live songs in Cantabile: quite a though task,
I have to open each Ableton project, exporting all MIDIs, audio, presets, picture of plugins, etc. hoping I can import in Cantabile the Scaler status at least
Well, at the end I gave up with Cantabile, because it crashes, and quite often also, YUK
I realized that my system is just unsuitable for multiple RAM-sucker plugins, nevertheless the DAW or the no-DAW workflow, so I keep using the workflow that I know better and is easier to use for me
Well, I suspect that musicians find Cantabile rock-solid because they are mostly keyboard players: it means they use their hardware instruments for effects and maybe they almost never use sample-based plugins
OR, they just have suitable computers
