John Vere

This is repeated over and over on this forum. Best dependable results with Melodyne is to always Render the clip when finished. Otherwise clips can become corrupted. If further editing is required it is very easy to simply re apply the regional effect later.

#27 tutorial is how I use Melodyne

Developers take note of this person s issue. This is exactly what happens because of the poor quality of Cakewalks whole installation system as well as the outdated information on the web sites. That video the op watched should be updated I never included anything about installing Cakewalk in my tutorials because it would be wrong the next week.

I hope that they fix this someday. The claim is it’s less confusing for new users to not have all the options. I think I has the opposite effect and it’s confusing to everyone because there’s been a zillion posts with the solution always being — “ Change to the Advanced Workspace and the missing feature will return “. We have the flagship top of the line version of Cakewalk installed but the default is Cakewalk LE.

There is definitely something that is buggy about using save as and rename to a different location sometimes. I’ve had those same messages and similar ones too. But it seems to work on the second try.

Yes I found that if I set the sample rate the same in every setting location Windows , Cakewalk etc it seems to work better. For me that’s 48 because video is 48. It’s better quality anyhow and i convert all my projects to that format if I open older files.

Did you watch my midi set up video?

Your issue is probably related to how your audio interface ASIO drivers handle switching sample rates and other details. Example is my Focusrite interface has always worked no matter what I do it plays the audio from different apps and the internet even with Cakewalk open. My Motu interface doesn’t like sharing. It seems mostly to do with sample rate. So I have started using only 48 hz and for the most part, I have fewer issues, but it doesn’t work as smoothly as the Focusrite. Watch tutorial #1 and see if some of those settings help.

I updated my post to include the proper link to my tutorials. But because people reposted it a few times I can’t fix those. The tutorial I made that has clear instructions on one way ( the easiest) to do this. It is found in video # 105 Importing Midi. The title was on purposely wrong as it’s actually about Opening a midi file. I will no longer post direct links to my tutorials as I cannot control dead links when people repost. My thread in the Tutorial sub forum can be kept updated so this will be the best way to direct people needing help. That way they can also discover other tutorial options.

I still can’t use Strike drums because it can’t find the library. And when I try to uninstall it it crashes. I just wrote it off as not worth the hassle. But I have a lot of projects that use DB33 and so far that is miles above any other B3 I’ve tried. I’d hate to lose it. The company makes good stuff but there are bugs and they do not seem to answer e mail. I don’t think they have updated most of the collection in over 10 years. Must be why it’s so cheap. I got their entire collection for less than $100

Absolutely you just need to make your own custom templates if the default ones don’t work for you. You can actually use an empty project as a template. I like that because then it shows on the default start screen. Just remember to use Save As and rename it before you start adding stuff.

Seems obvious but did you connect the audio outputs of the module to your interface? Or as @parboo12 is saying possibly the Roland has a ASIO driver and transmits digital audio over the same USB connection as the Midi. Seems the only connection you would need is the USB if so. And hopefully you are reading the manual for instructions on setting it up

This ones better Tutorial #1 and #2 have all the information only difference is you will concider your Keyboard your Audio interface as well as the controller. Should not be a problem as I have used the Yamaha Steinberg ASIO driver before and it's a good driver. Unlike the Steinberg Generic Driver which I don't like. That gets installed with Cubase and Wave Lab and you have to remove it.

I always have a hassle when I rebuild installing the Air products. Great stuff but terrible installers. The pathways go nuts and you loose the libraies etc. But what you can do is use the search found in the upper right corner of explorer by opening your This PC and open C drive. Type in Air and it will show you where everything went.

Just start with tutorial 1 and keep watching and you’ll have everything working just fine.

Actually folks the OP’s Yamaha MOXf is a USB Midi and Audio interface using a Steinberg ASIO driver. So they will need to download and install the driver and do a little reading of the Yamaha manual too. Lots of video support for that series. I have yet to make a proper tutorial for this type of set up not having this type of device on hand. I was just given a older Yamaha piano that had a glass of pop spilled inside and I fixed that issue but the display screen is broken. I need to get it working to get at the USB setting

Forgetit.

It's not really a template at all when you open a Midi file. It is just the midi data and if it was a type 1 file it will open with each track the way it was originally saved by the creator. What you get is a raw Cakewalk project with no frills. The TTS-1 is the default instrument because they assumed you are opening a GM multi channel file. It’s a real handy option for preview of download Midi files. You can disable this. If you choose a Midi output in Preferences, example I can choose my Midi ports of my Audio interface, Then the TTS-1 will not load, all you will have is your midi tracks. You then needd to build your project around those tracks. Add instruments etc. Notice there is not even a master bus with a midi file. You have to add that as well. This is where Track templates save time. If I add a track template I created for True Pianos it then automaticly creates a Sub bus and a Master bus.

Yes the correct way to back up a project as midi only is simply use the save as option and change to the midi format you want. This is something I’ve always recommended as a future proof back up of all projects. A huge amount of work can go into the Midi part of a project and if your like me I spend more time creating Drum, Bass and keyboard parts than I do recording Guitar and vocals. And if you produce electronic music Midi might be everything in the project. So making a Midi back up makes you future proof because probably it will be usable 20-30 years from now just like my Midi files from 1984 still are. And it’s also part of the easiest way to transfer to a different DAW. You open the Midi file in the other DAW and then just import the audio as stems. Not really required but If you want to spend a few minutes and set each instrument on a different channel that makes them sort of GM friendly. Hmm, this just gave me the topic for my next video, thanks for asking.

And wait another month for a reply?

I opened a fairly busy project on my i5 Office computer so you could see that for me it works fine. I'm using WASAPI shared because I need to run other music apps and watch You Tubes. My buffer seems to default to 480 samples which might vary from machine to machine. WASAPI shared does not let me adjust the buffer size but WASAPI Exclusive will. So if you need to increase your buffer you'll need to switch to Exclusive mode. I took some screen shots so you can compare setting. Here's my specs which are pretty close to yours. Here's the project running and playing a song with about 12 different plug ins running plus a few VST instruments as well. You can see my cores are not even breaking a sweat. Here's my Latency monitor report look like yours I guess. This is with Cakewalk and Google chrome running. Here's my Audio preference settings

Ok yes progress is happening at a rapid pace. Next suggestion is to try and increase your buffers and see if that works. To me your computer should not barf on that few plug ins. But as you add stuff you sometimes have to increase buffer to more than 256 which is a sort of normal setting.

What I see is a list of junk you don't need or want on the device lists. You are attempting to use a few devices that are designed for Podcasting and are normally problematic when used for Home Studio recording with a DAW. System is OK because it passes the Latency Monitor test with flying colours. The CPU spikes are therefore caused by something else, most likely one of these low budget audio devices. Lets get rid of all that so we can get WASAPI and your realtek working as it should and then you can start replacing devices with things that are known to work with a DAW. The Samson Co1u was discontinued and its generic driver ( W7) will not support WASAPI which I will guess is the heart of the issue here. Unplug it and uncheck from list. Voicemeter while found to be harmless should be completely removed from your system as it "could" cause issues and you really don't need it. I would go into the Windows setting like I show in the video and disable all device except your Realtek Speaker output. Now open Cakewalk and choose WASAPI shared or Exclusive and play the metronome as I show in the video. You may want to watch it a 4th time and just carefully do what I say. Now drag any audio file into Cakewalk and it should play without crackles. If your plans are to record with a microphone you will defiantly need a proper USB audio interface. The type with a XLR connection. USB mikes are for Podcasting and have a long history of not working with Cakewalk or any DAW unless you own a Mac. Good luck and keep us posted. The folks here really do want to make this work for you and we won't give up until it does ?

Why didn’t we all ask for screen shots of all the audio settings in the beginning. Would have saved a lot of guessing and typing. Make mental note to self. But the good news is we are getting closer to solving your issues. I feel dumb for not asking for more info to start with and just assumed this was a case of only playback with a typical on board Realtek system. You actually have a lot of stuff connected and this makes matters that much more complicated. Now we find there’s a few low budget usb devices involved and it doesn’t take much to guess why WASAPI mode won’t work.

I wonder if Craig realized he was replying to Dave when he was much younger.