Indeed, it’s because routes are disconnected and reestablished when changing song. I think the website is really talking about songs being preloaded, so you don’t have to wait for seconds each time you switch songs. You can achieve seamless changes across songs, with held notes etc, but you need to have your MIDI and audio routes entirely within the linked rack, so the routes are not affected by the parent song change. It’s fiddly but it works if you need it.
Hi! I am using the solo version of cantabile and built up songs which contains different instrument or instruments for layering and splitting, it is ok but the loading up process takes some time from one instrument to the other one, for example if I change for Scarbee EP-88 or Vienna Imperial piano, the loading time is between 5 to 10 seconds . The background rack contains the bindings for changing the instruments(songs) from Roland fc300 or from the laptop keyboard. I am thinking to use cantabile with Windows 10, is there any cons?
I know, I know! But this workflow doesn’t fit my needs. That’s why I look for alternatives. The website says clearly:
If you switch between two songs that use the same linked rack, that rack will be kept loaded and continue to process uninterrupted.
This was discussed in another thread, and many suggestions were made. Terry Britton was also taking suggestions in order to make some videos, BUT, in Terry’s defense, that would have been quite some undertaking. Cantabile is an ever changing marvel, and keeping up with it would be difficult at best. I suggested sticky notes, but, even those would have to be updated frequently. There are so many ways to set the program up, and there are so many different inputs, and instruments, plus every individual wants something different. That is the beauty of C3, and the curse of learning guides. I place bookmarks on anything I think that might be of use to me at some time. Of course, they now number into the hundreds. The best thing we have is the search engine, which very few use, according to repetitive threads (of which I am guilty also) . God bless the newbies…the learning curve has increased since I started. I got through the initial stage eventually, but still feel like a newbie on many other things…and I like it !!
I think it would be a good idea - the hard part would be making it generic enough to be applicable to a wide range of users, with different hardware and configurations. Some “quick start” examples for common scenarios, and best practices (how to decide if something goes in a song, a rack, or the background rack, that kind of thing) could be really useful.
Or how about simply a FAQ?
But for anyone who hasn’t yet, I’d strongly recommend reading through @brad’s Cantabile User Guides carefully, because they’re a treasure trove of information about all the features.
Well, truth be revealed, my video recording setup in the studio is finally back in place (lights and everything!) - a two-camera setup using OBS as the hub. Things became discombobulated when I decided to dedicate a computer to the video end of things - so, audio routing became a biggie.
However, that is no real excuse, as I could have been using the main computer to do camera-less videos, but hey - I got caught up in the process of doing this change!
Yes, Cantabile has been a moving target, but now many videos can reasonably be made, as I think the big changes have been done. So, sure, let’s crank out some videos!
Brad has already covered the basics with his videos, and the Guides are fantastic. Hmmm… what to do first???
I think it would help if everyone just shows his way of working with Cantabile… tutorials could be made separately and is another topic. But if it comes down to workflow examples, such videos would be great.
I’ll join this… but not yet, because I’m planing a next revision of my cantabile-keyboard
I have no set workflow. I just figure out what I need for particular song and go at it. So far I’ve only using C3 to set up live versions of pre-existing songs though.
I’d be quite happy to do a few “guided tours” of my setup and explain how I use Cantabile’s features to keep things easy to manage, configure and debug, even in more complex setups.
BUT: I’ve never done a screencast / tutorial video, so I’ll need a bit of advice on a pragmatic set of tools to capture and edit these clips, including the typical bits like mouse highlighting, zooming, annotating, etc… Also I guess combining audio from my voice-over with Cantabile’s output will require a bit of fiddling with Voicemeeter, which I have avoided so far.
So: @terrybritton, as our resident voicemeeter guru, and @brad, Mr. Tutorial amongst other things, can you give me some suggestions on a basic toolkit?
CamStudio is the easiest screen recorder out there.
Here is the download to the version that does not require you use the ad-supported installer:
I have a ton of videos on using it, but the topmost one is my most popular:
The default audio is only your microphone. You need something like Voicemeeter to do a mic and the Cantabile audio properly.
If you want to just use Hangouts on Air to record for you, follow this video on using Voicemeeter and Cantabile with that:
HOA’s record the stream while you talk, and you can easily share the screen from the tool on the left side. You end up with a video automatically appearing in your YouTube channel.
I use Bandicam for screen/audio capture. It has the ability to capture from two different audio sources at the same time and write to two different files. I usually set Cantabile to WASAPI shared mode which Bandicam is able to capture from and an external mic for voice.
Bandicam can also add mouse recording/highlight and mouse click animations.
Once recorded I use VirtualDub to “fix” the video into something the Adobe tools like. Not sure why but without this H264 video from Bandicam ends up with weird tearing artifacts.
I use Audacity to clean up the vocal recording. Some eq, noise gate etc…
Then I composite everything together with AfterEffects (CS5).
It’s not the most elegant workflow but its what works for me. @terrybritton obviously has a lot more experience with this though.
As for zooming and annotations - I’ve never really done this, but I would recommend leaving zooming to after you’ve recorded. There’s enough to think about while recording without fiddling with the recording tools. In AfterEffects (and presumably other video editing tools) it’s pretty easy to zoom sections later. (The only time I’ve done this is with this video).
With Cantabile there are many ways of doing the same, or similar tasks. This is very much a strength of the software, but it requires the user to try a few things, make a few mistakes, travel a few cul de sacs and ultimately arrive at a way that works for them.
One of my most recent ‘Doh!’ moments was when I finally realised that naming my MIDI inputs generically would have saved me a fair bit of re-work when I changed keyboards. Now my MIDI inputs are called ‘Left Upper’, ‘Right Lower’ and the like. If I swap out my A100 for my System 8 for my ‘Right Upper’ keyboard, the software doesn’t miss a beat. Brilliant!
Why did it take me so long to figure that one out!?
Thx for the input guys.
I’m asking this because i learned allot from Thorsten his setup and also some other guys pointed me at wrong setup in my rack so that some functions didn’t work. I need to check what it was.
But overall the learning curve was quite steep, so i think for this kinda program it should be easier or some templates pre configured?
Actually, just doing simple stuff isn’t that challenging. But you know how musicians are!!
“Now if I could only route my Expression pedal to the volume on that VST and also to the filter on this other VST and have it change state while I’m holding this chord so the pre-recorded background vocal track could kick in and that loop I have set up in Maschine can…”
You know what I mean.
I’ve just applied the “Torsten Effect” to my Akai MPK249 controller, abstracting ALL 3 banks of the knobs, sliders and switches in the MPK’s “MIDIout” preset into a rack (done once, never have to do it again, thank Gad) - that’s 3 X 8 X 3 = 72 entries in the outputs, plus another 72 in the bindings section! Plus the transport, notes, aftertouch, and pitch wheel. Then made a dedicated rack for the pedals and expression pedals. Very flexible (to the extreme!) - but I have a simple “alternate” non-Torstenized setup that just does things the old way for simplicity still sitting there as a rack for quick tryouts. However, none of those elements need to be tied to the same VSTi now, which is really quite freeing!
If anyone wants this rack, I’ll upload it here after I make some raw form of it. It should work the same for an MPK261 and can be trimmed down for an MPK225, which has no sliders. (Oh, what the heck - here it is as-is. You’ll need to make it relevant to your needs, though.) The big secret is right-clicking on the rack title, going into the Rack MIDI ports and adding new ones. Then you use the rack’s bindings to send stuff to those outputs. That’s already done for you here. Install the rack as an existing linked rack, then hit the “Add Route” button after using the rack’s arrow to open up the outputs section below the rack. You’ll see. You’ll have to edit the bindings to customize further, but the outputs are already pretty powerful. All Song-state-aware!
setup basic connections for midi and audio, the right way, because there are different ways
have the screen keyboard connected already (the hack to see the keys moving)
setup a basic rack
(insert your vst)
thinking of routing options to send the main signal and a different signal to headphones so the output level stays the same, although i think volume is part of expressive playing
this way not controlling the level of each Vst but rather 1 output level
maybe a correct way to set a limiter or compressor?
i have an input from the mixer so i can monitor to my inears via the headphones from my soundcard
Would it be an idea that a wizard popup helps you out to get the first things going?
Or just a template to get you started?
I know that all my songs are configured the wrong way, because of initial trial and error.
That’s why i ask.