Bass Guitar

Tomorrow is the end of life for Cakewalk anyhow. So why waist your time. You should be using Sonar by now.

Changing the tempo of a project with audio in it has limitations. As you increase or decrease the audio will start to degrade quickly as that amount increases. So first experiment with the midi part of the song which is not affected by any tempo changes. As you work just record scratch vocals or guitar parts until you settle on the right tempo. Then start recording your audio parts. If the audio parts are just loops and samples then it would depend on how much you can stand the artifacts.

I recommend you simply start with the free version first. Then you will have a chance to learn about the basics of the software. Then you can decide if the add ons are worth it. If you have the older versions then you will already be most of the way there.

The OP I noticed has a habit of posting, returning a few days later and then not responding to the thread.

Seems people rarely visit this sub forum so best to contact support directly as Ashwin has directed above.

That is why I stopped asking about people’s specs 10 years ago 🙃 But one thing never changes and that’s not having optimized it for audio production.

First test is bypass all effects using the toggle in the control bar. Also make sure you have all your audio and other settings exactly the same as in Cakewalk. Take screenshots to confirm. Confirm you are using the latest ASIO driver A modern computer that was optimized for audio should run the average project at 256 buffer with out any dropouts. You can run the Resplendent Latency Monitor to test your system. Always reboot your system and re start your interface when troubleshooting.

The step sequencer works well for this. Use the SI drums or Session drums for the track. Session drums has tons of different samples you can add to the octapad thing. I remember having to do this when trying to make a Clave beat.

I would investigate the matter of you adding those numbers to the plug in name. If the plug in shows up in plug in manager as Wave Rcomp and all it finds is Wave Rcomp. Then it will ignore it and keep looking for 2Wave Rcomp

Ya sorry I realize that it’s not even something I often do anymore. I actually find instant gratification by simply entering my Daw questions in Google search. The AI now digs up the answer. And it actually gets it correct most times. And often it is quoting from user forum posts. Go figure. I hate take lanes with a passion. I always end up with a totally unusable bunch of trash.

The buffer size is usually set in the control panel of the audio interface. I keep mine in the taskbar. One click. Mine can be set to open when Windows boots. I prefer that option because then I’m dead sure my settings are correct before I start my day. So find the Interfaces Control Panel app in programs and pin it to desktop or taskbar and see if it has hat setting in it’s options.

It’s a good option for people like me who often work on groups of projects that I might be accessing using Windows Explorer. I just want to have a quick listen. It saves a move when you have a project open and you are now are finished listening to it and go to open the next project from explorer. The old project will close automatically. The new project preview option on the start screen seems to only works on projects that have been opened and saved.

Cakewalk saves projects as CWP files which can be opened in all versions of Cakewalk and Sonar going way back in time. Yes they still open in the new version of Sonar. Nothing has changed in that regard. Cakewalk Next uses a different file extension and cannot open CWP files. However it is possible to easily transfer CWP files from the new Sonar to Next using the new Cakewalk Interchange format. CXF.

Im pretty sure a staff member answered this and said that they would simply lock it into read only just like the old forum is now. I guess we’ll find out after Aug 1st!

The difference between 32 bit and 32 bit floating is that 32 bit files have all 32 bits for each piece of data. Floating 32 bit will fluctuate saving a little bit ( pun intended) of storage space. Generally speaking most Daw’s internally render audio using the Floating. But if you choose 32 bit as the export option the wave file will be solid 32 bit, not floating. So be careful about what settings you use when you import the file to the Daw or Wave Editor you use. Example in the case of Sonar, any audio dragged into a project will be converted to the project Sample Rate. The bit rate is maintained however. So make sure the new project shows 96 in the transport.

For sure this is important! I had totally given up on it and one day I got the video links they email me at least once a month. I started watching them at finally got it! I try and watch them as they come out but most are demonstrating stuff that I would never do. But the starting out videos are worth watching a couple of times. I just love that I can basically work with audio the way you work with midi. I would imagine that getting the audio of the solo into Melodyne would be a good way to actually see the notes and the timing.

I think this is the heart of the problem with this new version due to the overhaul of the graphics . I have a long list of weird behaviour issues that are all graphic related. Example : yesterday I was exporting and I unchecked a track’s microscopic selection box. But the track was included in the export? I reopened the export dialogue and the box was still unchecked. It’s almost invisible to see. I had to squint and get closer to my monitor. So I re checked it and it didn’t show? It took 3 tries? I then unchecked it again and re exported the song and this time it worked. I also have had lots of issues working with the PRV where common moves Ive made a million times in older versions worked perfectly fine and now do not. It’s sad that they truly have done something wrong with the interface of this new version. You kinda just get used to the weirdness and carry on. Hopefully this will improve with time and by then we can also purchase a license.

It's random. I think it depends on what the original workspace was in Cakewalk. I figured out how to get rid of it using the Views menu. Most of the projects seem normal with the exception of now the Help module is showing which is another view I never used. But those work as expected where the divider will re-size and the down arrow hides it. The one project I was talking about those did not work at all.

It’s not lost. As explained very clearly it is something that you customize yourself. Lots of information about how to do this in the good old fashioned user guide.

Those I think are all proper( kind of) ASIO drivers. For sure the Soundcraft driver is and I own that. Those are not a problem for Sonar. As you say Sonar will grab the device that was turned on and booted up with windows. You can even swap It out with Sonar open but no project loaded, Sonar will complain when you turn off the first interface, then ask you if your want to use the one you just turned on. Done this hundreds of times. It is as Noel said the "Generic Wrappers" that will screw up on loading because they are running in the background I guess. Seems Steinberg and Magix and Presonus? install them as a convenience for users who don't own interfaces. Magix installer will ask you. Cubase installer doesn't. Cubase and a few other daw's install a lot of Bloatware. I had to re install Windows to clean my computer up.

Melodyne basic version always worked to extract a tempo in Sonar going way back to X3 I think. Melodyne has always require you create an account even for the free version that is included with most Daw's these days. Small inconvenience. That will get your foot in the door and upgrades are dirt cheap, especially on black Friday. Melodyne is possibly one of the most important tools you'll ever own. People think it's just for vocal pitch correction. It does WAY more than that.

Only Sonar has this issue. I had at least 6 other Daw’s installed and all used my Interface no problem once I selected it. Sonar is the only one that would screw up. And this was because I own Cubase and it had harmlessly installed a driver it kindly installed for folks who can’t afford interfaces. Don’t blame Steinberg. Sonars Audio system has always been hyper sensitive. The thousands of posts on the topic are proof.

One of the missing features of the free tier is Workspaces. Ok should be no big deal but today I opened an older project and the browser has the synth rack at the top and the Browser at the bottom. For the last umpteen years my custom workspace never included the synth rack. I haven’t used it in years. So I tried to close it because I wanted the browser full height. Seems like this is not possible. Or is this yet another example of the new graphics and the place where you click on is microscopic? I also tried resizing it but this also seems to elude me.

This works on most songs that have a steady beat. Separate song into stems using Next or Audacity. Now drag the drum track to the timeline of Sonar and the Melodyne dialogue will open. Choose auto or percussive This will automatically create a tempo map. You can also do this directly in Melodyne stand alone and export the tempo map as a midi file. To have measures line up Turn on Ripple edit and turn off snap to grid. Drag all the tracks until the downbeat is on the start of measure 2 or 3. I have done this dozens of times with rock cover songs. The metronome should now follow the song. Stem separation AI has not really gotten sophisticated enough to extract individual parts. The solo you are after probably has easily available tab or notation available. Possibly even videos of how to play it. I’d tend to start there first.

How I sometimes work is I load a song into Next. Run the stem separation tool and then I use the Export as a Cakewalk Interchange Format CXF file. Now I just open this in Sonar. But!! At this point you will be seeing that the down side of the Bandlab system is the Wave Files are 44.1/ 16. I only like to use 48/24 minimum. Not that it matters for stems as they are terrible quality still anyway. I only use them as a reference to recreate the original song. So for me Audacity and its new stem separation tool is preferable because you can choose any format. It also works locally using your CPU.