John Vere

All of this is very clear and explained in detail in the video. But one thing that makes no sense is that WASAPI didn’t work? This could only imply you have a weird MoBo? Pull up the specs for your computer and let us know what the audio chip is. And in the end this is why an proper audio interface is always the best solution if your wish is to use a computer for audio recording. See my video #106

Worth mentioning on this topic is if you can also use UNDO for as long as the project is open. This has been my saviour when I suddenly realize a project is going sideways. If you think about it it’s exactly the same results as opening an auto saved file that was created in the same session. It’s actually more precise because you just keep hitting CTRL Z until you get back to the point where things went wrong. Autosave is only useful if you have the bad habit of forgetting to save as you work and you experience a crash. And as far as retrieving a project that was saved a few days back that is another good habit to include in your workflow. Use “save as” at the end of each day to make a dated back up copy on a different hard drive. Shut down routine: Save project Save as to a back up drive and date and check copy all audio with project box.

In the Preferences/ Sync and Caching dialogue that shows what ASIO device is used to report the latency— is this the same as your ASIO audio interface? I cover this in a few videos #1 and # 106

I can try opening a different project on my second computer I just updated Melodyne now on that one. I read the list of what the update was about and didn’t really see anything other than a lot of bug fixes. So by rights it should actually work better! The thing about rendering right away is long standing advice from regular users where this will sort of guarantee everything will work properly afterwards. I’ve certainly never had an issue with Melodyne or crashing projects so I stick with the program. You can always re apply the effect at any time later.

I just updated Melodyne yesterday as it popped up the minute I opened it. I saved my work, closed Cakewalk and followed through with update which was pretty fast and without issues. I re opened the project and worked on it using Melodyne for a few hours without issues. Question. There are no active Melodyne Regional effects still open in the project? That can cause a crash if you leave un rendered Melodyne clips in a project.

Yes and no. I use WASAPI shared when using on board audio, otherwise I can't use other apps that produce audio. But if all you use your computer for is Cakewalk then Exclusive mode has way better performance. I actually get around 7ms of RTL at 256 buffer. It would be a great driver if it reported this to Cakewalk correctly so the timing offset was correct. Another selling point for purchasing a proper ASIO interface. On board audio is actually at lot more complicated to use if you want things working properly. At one point I even swore I would stop helping people who use it and quickly realized that would be the majority of new users. So I took the time to figure it out and spent a couple of months using it on my "Studio B" desktop editing midi and even working with Melodyne. But bottom line is forget about recording new audio unless you don't mind nudging tracks back a 1/16 note or more.

Troubleshooting is a process of elimination. You are on the right track to eliminating things that cause this issue. But somehow I don’t think you have followed through with what is in the videos I made. 1. Did you run Latency Monitor? That will rule out fussing with things like the BIOS. 2. Did you increase your buffer settings? 3. Did you set all clock rates the same? https://www.resplendence.com/latencymon

Obviously the first solution is to register the plug in as instructed. If you do not own a license for it, then either purchase it or un-install it. If it is built in to Cubase then you might have to ask on the Steinberg user forum how to either register or remove. If it does not show on the list of installed Apps in Windows then you might be able to simply remove it from the Steinberg VST plug in folders. It might be in 3 locations if so. Program Files/ Steinberg / Vstplugins - Program Files ( x86)/Steinberg/Vstplugins as well as the VST 3 version folder location which can vary from system to system but is Normally found in Program Files/Common Files/ Vst 3

I think this was mentioned before but the free versions have limited functions. Check with the Ample web site for details.

It's too bad the Musician was left on their own without professional help with set up. But this is how we learn. To me there's absolutely no question the track is garbage and needs re doing. I would only consider using it if the instrument was in the background and the metronome became part of the songs percussion section!

Lucky you. You don't need to use a 3rd party driver written for Windows XP anymore. See tutorial #1 for Audio set up in Cakewalk.

Tutorial number 1 will definitely help you out

What I’ve found myself using to navigate the track view is the ALT mouse scroll wheel. I zoom out to see whole project place now time on the place I was looking for and zoom back in. But then I seem to always use a mouse for as much as possible and not keyboard shortcuts.

The levels are always set at the audio interface before heading off through the USB connection. The DAW has no control over this level but one can most certainly check it by arming the tracks and observing the DAW’s track meters. Some interfaces do have a software mixer in line which you also need to check. The good news is because it’s digital it should not matter and all you need to do is apply gain or normalization to the tracks. I’ve had plenty of low level tracks from live quick mixes and what was easiest was highlight the whole project and apply Normalization at -8.0db.

@User 905133 Good to know, My Tascam 1641 was made in 2008 , last driver was issued in 2016 and says W10. Tascam make good Windows drivers. I'd say that my 1641 driver outperforms my brand new Motu M4 driver in some ways. My reason for mentioning the Tascam was when I saw it didn't support W10 I was wondering if the OP was still on W7 ?. I tried Googling " Does Windows 7 support VST3" and came up with no answers.

Thinking about other info that might be related to issues. Here's some more things to chew on. In the OP signature they list their Audio interface. A quick trip to the Tascam support page finds we are dealing with a very obsolete device. We actually don't know if the OP is running W10. Do VST3's run on W7? I google the question and there was no immediate answers.

Yes lots of unanswered question from the OP. That ALL VST3's are crashing has never been actually verified even though it was a question asked by scook early on. Looking at the list it would seem Sample Tank, Syntronik and Iris2 would also be crashing? I also noticed the duplication of all VST3 and VST 2 instruments. The OP might want to check the boxes in Preferences to prevent this.

When I read this the first thing came to mind is the fact that even my $40 version of Vegas supports multi track audio. My thinking is if faced with this problem I’d somehow be using those audio tracks to export samples of different audio synced to the video. I drag and drop audio clips into Vegas all the time seems pretty easy to me.

Actually looks like he joined in 2019. Just glad I didn’t say anything dumb like is my habit sometimes. Specially when someone repost what you had said and now it’s in fixable

I tried a bunch of different widening tools and the most transparent was Izotope Imager which just happens to be free. https://www.izotope.com/en/products/ozone-imager.html

@Billy86 Thanks for the kind words about the tutorials. If you use 44.1 then you would use 44.1/32. I use 32 because Cakewalk is working internally at 32 floating point. Then no dithering is required. The benefit might be very small but hard drive space is no longer an issue for me so might as well use it.

Like I said in your other post, your issue is not Cakewalk, your issue is with the vendor of the plug in. Your obsessing over the plug in icons?? that is just plain weird. We have all told you that is what they look like, that is nothing to do with a plug in not working. E mail support for the plug ins that are not working it takes a lot less time than you are spending posting here. I am honestly sorry we really can't help. All those VST 3 plug ins work just fine for the rest of us. I use as many VST 3 plug ins as available from vendors. They are all working great.

Different types of plug ins are different colours. Not at my DAW, but VST 2 and VST 3 and DX are each different colours and then I think 32 bit are Green So what I see is you have the VST 3 and VST 2 versions available

Seems this is a issue you need to talk to Ample about.

I've said it before and I'll say it again. The forum should lock all threads after around 1 month of inactivity. It would most certainly make it much harder for trolls to find food. I someone wants to reference a locked thread it's easy to just post the link to it in your new thread. This is about the 3rd Zombie thread un earthed by a troll in the last few days. Edit: I see the moderators removed the troll/ I guess that's the best thing to do, don't respond, just report them.