John Vere

Which video did you watch? I have a bunch and each one is about something different. So I'm not sure what you are saying when you say my video said to use a midi interface? Which model of Behringer did you purchase? Does it have midi ports? And do you need them? as in you are trying to record midi via a midi keyboard that does not have USB but has 5 pin style midi ports.

Well your back after (edit) 7 months Your complaint is kinda odd at least to the majority of us who are used to having to actually put a little effort into our craft. Things like this are just a routine habit.

I only have one gripe about the Tungstun Theme and that is the Black PVR screen. Years ago I fixed this and saved a custom Theme as "My Tungstun" It still shows on both my computers as an option but as most will know you can't use these anymore or your workspace graphics will go nuts. Half of the icons are hidden etc. So after putting this off for a few years I really need to make this one change and I have basically given up after (only) an hour of trying to figure this out. So I opened the theme editor and opened and saved "My Tungsten" and according to directions this should update this theme to the currant format. Nope, Still screwed up. S0 I loaded the default Tungsten theme and tried my best to modify it so the PVR is white.. I get different variations all of which are unusable!! OK so I could use Mercury which solves the PVR issue but now I'm a bit peeved I have a very bright pastel looking track view!! Why on earth do we only have 2 bad choices and are forced to use a theme editor that only a very advanced programmer could possibly figure out. So does anybody out there have a modified Tungsten with a white background on the PVR? I'll send a virtual bottle of Whiskey if you do!

Obviously nobody else experiences this. Even huge complicated projects only should take a minute to export on a modern computer. On the rare time I've seen this issue it was either a weird plug in, ( you tested this ) or as scook has pointed out a song with no end, or your computer is bunged up because the hard drive you are writing to is either full or faulty.

99% of the time people are hearing no sound is due to the master bus has been diverted to something like a digital output. Check your Master bus output.

A sub forum would be a good idea in general for Bandlab users. A lot of people have posted here over the last few years asking questions and were frustrated there was no forum for them. But, keep in mind, the forum will only be useful if those folks participate and help each other out. That's how forums work. There's a lot of helpful people here on the Cakewalk forum, many of us go way back in time too. But most of us have no interest or experience with the Bandlab app. It would have to grow a new community.

Possibly there would be less confusion if we return to calling our favourite Daw Cakewalk and drop the Bandlab extension. That way there’s just Cakewalk the Daw and Bandlab the music app. To me at this point if someone says Sonar I know they are using the pre Bandlab version. If they say Cakewalk I know that they are using the new version ( or really really old ) They don’t need to say Cakewalk by Bandlab anymore.

It would help if you supplied more info. Like what audio interface are you using, does it have a loopback function? Is the piano a real piano you recorded with a mike? Are there other audio tracks or just midi?

Ya actually re reading the OP I think they were expecting the audio to be transmitted via the $10 USB to midi cable. Should I tell them that they need the $20 cable to make that work or is that mean

The OP does mention he loaded up CW and has timing issues. That was the last update and there is now a fix. There's going to be a lot of people with posts about timing issues until everyone updates the the new early access. I thought 147 was the latest but SteveC pointed me to here.. I just downloaded it now.

I’m on my phone so can’t copy the link but look for the thread Timing issue solved and on page 2 Noel posted an update build 147 which might solve your issues

The time that I’ve seen this happens is you start from midi file and forget to change to a CWP before recording and the audio can get put in the global audio folder. There’s a few situations where this happens. So what you end up with is a project that seems fine but the audio is not in the project folder but is in the global folder. You would not notice until you move the project folder to a different computer. The problem is solved when you use Save as and check copy audio with project and back it up in a different location. Another big reason for backing up using “ Save As” If you still have the computer the project was started on look in the global audio folder

+1 to all Scook has said. If your keyboard only has midi ports and doesn’t have USB you have these options: That cable is useless because it probably doesn’t have a midi driver 1. best choice purchase an audio interface with midi ports. This will also solve other problems that you will have with audio going forward 2. purchase a keyboard with USB midi connection. It will have a midi driver. 3. purchase a midi interface that comes with a driver. This will be money you could have put towards an audio interface.

Yes thinking of what Noel just said you would be messing with which driver is in control of your timing and latency calculation. For accuracy you definitely need ASIO. And this is the reason only one ASIO device can be used at a time. Cakewalk needs the driver to calculate the latency and this is not possible when 2 different devices with 2 different specs are involved

I made a tutorial on loopback testing. It's in our Tutorial sub forum. It's just not called loopback testing. But in the middle I show how to do it in Cakewalk. Focusrite drivers are always spot on, but the last release of Cakewalk had a timing issue they jumped on it and fixed it with build 147.

I think that's how I got started with Cubase via my Tascam interface came with a disk with Cubase LE on it. Only thing I do like about it is you can open any audio file in the wave editor which works just like Wave Lab. Otherwise it's just another DAW. And if you want to wait for a week for an answer to a question give the forum a try. And you can't even post on most of the sub forums unless you own the product. So no way to ask about how stuff works if you were interested in that product. VST's that say they are free and make you jump through a few to many hoops to get there, just ain't worth it. And the stupid e licenser software will drive you nuts.

So did you try the drag to the timeline? I've gotten this to work perfectly a few times now. It really depends on the audio track. I think anything with a steady beat and lots of transients will work. And did you watch Mikes Video. He' explains the audio snap method step by step.

You need to let Staff know which plug ins are causing this, They always jump on it and most times it can be sorted out. @Noel Borthwick @Jesse Jost Post which plug ins and they will probably respond now I tagged them.

So does your Tascam have Loopback? You said something there about the "Loopback Drivers" I had to use WASAPI shared to feed OSB studio screen Capture until I discovered that my Motu's Loopback channel shows as an option as an input in OSB so I can now use ASIO and stay out of trouble. The Loopback channels also show in Cakewalk as input options and that captures any audio from my PC. Everything is going through my interface this way. The main thing is what ever your playing has to have the same clock rate as Cakewalk. Because of this I often use 48hz which seems the standard for videos on You Tube. If you use on board audio it is up to the drivers for that and not many support "What you hear" option. None of my 4 PC's have that option with my on board audio. I know because I tried everything. It's why interfaces with the Loopback are popular now. Tascam's newer models seem to have it.

You need an audio interface with a Loopback Feature.

To use input echo and real time effects you need a combination of a real powerful PC and a top end audio interface so that you can run a low buffer settings. Audio Interfaces and features- https://youtu.be/z6gjvuCV4GE

Sound Blaster cards have a very badly written ASIO driver and are not recommended. You're better off to pull that card and use your on board audio. Long history of issues. It obviously doesn't support WASAPI. But you have a proper interface you should use that for in and out and things will work properly. If all you have is computer speakers then plug those in using an adapter to the interface headphones or the rear outputs. https://youtu.be/Avtw7dOb0fM https://youtu.be/iAeqy0nW5uY

There’s another thread with same question First thing you should always do is Enter your question to Google. But there’s 2 ways First is drag the audio to the timeline and melodyne will try and create a tempo map. Second is audio snap. There’s lots of tutorials on the subject. My favourite is the one by Mike of Creative Sauce

You need to supply a lot more info. There’s nothing to go on to help you. Don’t be afraid to go into details the more we know the quicker the solution Is this just one old project? W10, certain plug ins there’s lots of reasons.