I wish I could get it to make a soundcreativesauce wrote: ↑Mon Dec 23, 2019 10:37 am Hi folks! I want to thank the Cakewalk community for telling me all about the features they would like to see improved. I've made a video with my suggestions, and have highlighted some that the community suggested. Let me know what yours are!
WATCH HERE: https://youtu.be/BsogIvcVOf0
I wish I could get a plugin to make a sound lol. I've uninstalled and reinstalled cakewalk several times now, finally got it to load the full version. Now it doesn't make a sound. Any sound. I have and use quite a few DAWs, some I paid for (MULAB, Presonus) Some free (Traction 7), and I know how to set up my audio interface (Focusrite s212 2nd gen), load my amp sim vst of choice (that does show up), but nothing will make a sound, not even a signal on the meter from my guitar. Any help with this would be greatly appreciated and thanks in advance if you can help me get this software working. Props on your tutorials. I've watched many, still no sound or signal. ??creativesauce wrote: ↑Mon Dec 23, 2019 10:37 am Hi folks! I want to thank the Cakewalk community for telling me all about the features they would like to see improved. I've made a video with my suggestions, and have highlighted some that the community suggested. Let me know what yours are!
WATCH HERE: https://youtu.be/BsogIvcVOf0
One of the "Preferences" is to set any selected track to "input echo" by default. That can save you some time and trouble, if it fits well into your workflow. Of course, you can always turn input echo off on any track you've selected, but when you select a new one, it'll be ready to go.
That could also lead to more forgetfulness. When it selects the new plugin it deselects the old one.planetearth wrote: ↑Sat Dec 28, 2019 12:10 am One of the "Preferences" is to set any selected track to "input echo" by default. That can save you some time and trouble, if it fits well into your workflow. Of course, you can always turn input echo off on any track you've selected, but when you select a new one, it'll be ready to go.
Steve
Yes, but you can then either manually activate input echo on the new plug-in (if you want to layer sounds, for example), or just adapt your workflow to it and get used to it. That only takes a couple of hours, and you might find it improves your workflow afterwards. Then again, it might not. It all depends upon what works for you, but the option is there if you want it.Saffran wrote: ↑Sat Dec 28, 2019 12:17 amThat could also lead to more forgetfulness. When it selects the new plugin it deselects the old one.planetearth wrote: ↑Sat Dec 28, 2019 12:10 am One of the "Preferences" is to set any selected track to "input echo" by default. That can save you some time and trouble, if it fits well into your workflow. Of course, you can always turn input echo off on any track you've selected, but when you select a new one, it'll be ready to go.
Steve
To be precise, it does not select a plugin, it routes the audio through the track. Other DAWS require to record arm the track to do the same, something that confused myself in the past because I do not get why must I do that when I do not want to record at the moment. The auto mode is fine for most situations, but the Input Echo button is very visible in the track's header anyway.Saffran wrote: ↑Sat Dec 28, 2019 12:17 amThat could also lead to more forgetfulness. When it selects the new plugin it deselects the old one.planetearth wrote: ↑Sat Dec 28, 2019 12:10 am One of the "Preferences" is to set any selected track to "input echo" by default. That can save you some time and trouble, if it fits well into your workflow. Of course, you can always turn input echo off on any track you've selected, but when you select a new one, it'll be ready to go.
Steve
I'll leave this up in case someone else has the same question.
Sounds very odd. Maybe you should go to the Cakewalk forum and post there, the developers are very responsive.fmr wrote: ↑Sat Mar 28, 2020 11:45 am I have a pupil who is experiencing a lot of problems with Cakewalk by Bandlab. It started with Multi Samplers, like Kontakt and Aria. After instantiating the instrument in the Rack, and loading several sounds in it (each on its own channel), we then created MIDI tracks, each oe addressed to the recpetive sound/channel. Playing with the MIDI controller, everything was well.
We then recorded a track. After recording, the sound was muted (in Kontakt) or with the volume severely reduced (in Aria). Unloading and reloading the sound would make it back to normal. However, after recording a new track, ALL tracks (even the one already recorded) would present the anomaly again. There were no controllers or commands in in action that could cause that.
Yesterday, after uninstalling and reinstalling EVERYTHING related to Cakewalk, a new anomaly appeared. This time, Cakjewalk was stoping to respond to the MIDI controllers. Using other software (like Kinbtakt standalone) allowed us to verify that the MIDI controllers were working as expected - the anomaly was only in Cakewalk.
Frankly, I don't know what else can I do. I advised him to simply give up on Cakewalk for good. What intrigues me the most is that I used and am using Cakewalk on several systems, one of them Windows 7 and the others Windows 10, and I never experienced or saw this problem before.
© KVR Audio, Inc. 2000-2024
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement
