John Vere

Depends on the audio and which version of Melodyne you have You can drag a bass track to a midi track and that always works for me. But guitars do not.

That behaviour tells me you might have a hidden dialogue box open so minimize your workspace screen and look behind it. Or it could be a corrupt instal try re installing. Clear the picture cache?

When I’ve had this issue it was because windows update had overwritten the midi driver for the device. Try re installing the manufacturer supplied midi driver if it came with one. Most name brands like Roland and Yamaha do

By A pro do you mean a Roland A pro Keyboard? If so make sure to go to the Roland website and download and install the Midi driver.

Ya must be a typo, I notice the OP reacted to your post but still has not answered CJ's questions.

I have over 200 pure midi projects. They are all saved as both mid. and CWP files. The mid. file is strickly for future proofing all my work. They will probably open in software until I'm dead and gone. The CWP files are so my songs play correctly with the effects and proper VST instruments. A midi file will open with TTS-1 only and sound pretty boring.

You can easily end up with 4 or more folders that the installers will use or create durring install. The normal duplicates are the ones that end up in both the Program FIles and the Program Files (x 86) folders. A lot of 3rd party VST's use the Steinberg VST folder which is also found in the 2 main Program folders. If I grab a new VST and it is just a .dll file I always put that in my Steinberg folder so I can keep track of them.

In my signature is a link to my web page and there is a tutorial on using a downloaded midi file to create a backing track. Step by step. Midi World has thousands of free midi files and a simple download system. Just click the download link and on my system the file goes to my download folder and opens in Media Player so I can pre view the file. It's hit and miss with quality but I have found dozens of great tracks here. There is also pages and pages of helpful info about midi. https://www.midiworld.com/ I also attached a CWP file for you that is just simple midi. I used stock Cakewalk VST's Talking About My Baby.cwp

The presents of "ASIO Focusrite" shows it was installed correctly and recognized by windows and Ableton. The other driver is probably a generic driver so don't select that. Go to your windows Audio settings and see if the Focusrite device is on the list and set as default for recording and playback. WIth USB audio interfaces make sure you always use the same USB 2.0 port. Swapping ports or using a USB hub can cause issues. Now try playing a music file or any audio/ video. Get this working first. If it doesn't then I guess your interface is useless. If Widows can use the Focusrite then your DAW should too.

The whole suite is only $60. That's what I bought and it has certainly paid for it's self. It looks like just the burning ROM is a free download but might be a trial. its not clear. https://www.nero.com/enu/downloads/#download:nbr2020-tstub:formShown

You really need to explain your issue. I have no clue what your problem is.

There's some truth to that. My first drum machine ( still have it ) a Roland 505 was purchased after our 3rd drummer wandered off with no warning. Took me a few hours to write out BPM's and the correct patterns to use for our 60 song set list but that was the end of real drums for us for a few years. I quickly learned about midi sequencing and purchased an Atari to drive the 505. I really couldn't stand pain looped patterns and no fills. Next came bass and onward. That was 1984?

Last time I had to re do from scratch, about a year ago, it was not that big a deal. It's time consuming but I work on my laptop while the other computer is busy doing it's thing. First I had saved my Command Center download folder which had the majority of my plug in executables from the Sonar days stored. We all talked about this at length on the old forum when Gibson pulled the plug. Back it up and make sure to have a document that has all your serials and activation codes stored safely as well. We were also given activations for 3rd party software thanks to those vendors who stepped up to the plate back than. Not sure if they still honor this but companies like Overloud emailed me lifetime activation codes after I emailed the request including a screen shot of my Sonar "about" screen with the serial number. If you haven't yet done this look into it. I bet they will still honour it. So everything from that Splat Command center era is safely backed up to multiple external hard drives. All pre command center Sonar software I have digital copies and the serials and activations codes for. They do not need on line activation. This stopped at X3 So to rebuild I copy all the executable files and DAW related stuff to a DATA drive on the new machine. This also includes CWP folders. I first installed the drivers for my 2 Audio interfaces and midi controllers. Sonar/ Cakewalk seems to like to see this stuff when it comes alive. I then installed 8.5 64 bit bare bones just to get the few things like true piano's and V Vocal. I Then I install command Center. But hold on, don't run it yet. Now I copy all the files from my back up hard drive to the newly created Command Center Download folder. C/ Program Data/Cakewalk/Command Center/Downloads Now when I run Command center all the software installs real fast because it doesn't have to re download. Once Sonar Platinum is up and running with all those great goodies I then install the Bandlab Assistant and Bandlabs Cakewalk. I then install my collection of 3rd party VST's most of which go to my Steinberg VST folder.

I bought Nero 7 a long time ago and it seems to still work great. Because I have that I have never even tried anything else. But I know all of my Wave editors offer CD burning options. And some of them I got free. I have Gold Wave, Audacity, Sound forge, Wave Lab and Acoustica.

Drums are pretty important and of course there's no real substitute for the real thing. A drum machine will always sound like a drum machine. The better ones give you more options and most will have multi samples that if you have the time and patience to learn the interface can produce a much more convincing drum track. If you were lucky enough to have bought the old Sonar you might have Session Drummer or Addictive Drums. I mostly use Addictive drums because the interface offers a lot of tweaking. But Session drummer has way more variety in samples and you can even make your own. I sampled my own drum kit and can play it via a midi track with SD3. For a while I was using Air Strike 2 drums as they were on sale for $12 but found the interface and layout real confusing. I kinda like my drums to be GM compatible. I have used SI drums for simple backing track stuff and if you pick the right kit and tweak it a bit it will suffice. But if you have a higher standard then you better start shopping and comparing the better multi sampled VST's packs out there. Always wait for a sale. Sign up for Emails at a few plug in vendors like this https://www.pluginboutique.com/deals

OK, so you haven't downloaded from the website? This is a "must do" for all interfaces. Toss the CD out and go to the website and grab the latest driver. https://customer.focusrite.com/en/support/downloads?brand=Focusrite&product_by_range=542&download_type=software It's worth a shot seeing as your still on W7 it might be OK. But I would still start looking for a newer interface anyhow. They start at around $100 and up from there. I made a list of stuff that is what I figure you need to think about before your start looking. Everyone has different needs and sometimes it's best to spend a few extra bucks and get the correct features. Like needing 2 headphone jacks. Lots miss out on that one little feature and end up spending another $100 just to by a headphone amp. Here's my blurb: There is a lot of choices. Make a list of your requirements first. What kind of connectivity do you require? and how many of each. These are some of the options: XLR, 1/4", Combi jacks, RCA, ¼” line level, ¼” Instrument level ,MIDI, SPDIF, ADAT,MADI How many ins and outs do you think you'll need now and in the future? Are they accessible? Front or rear panel? Are all ¼” jacks Balanced? Is there a true stereo pair? Some don’t have a matched set of inputs. This makes recording a stereo instrument difficult. Pre Amps will fall under the “you get what you pay for” rule, but check out the reviews anyhow. Your on your own with this one... A/D convertors will also fall under the same rule and generally all are good these days. Are there peak level meters or just a little LED for each input? Are there channel Insert jacks? Are there separate controls for Monitor level and headphone level? Is there a blend control for mixing Input Source with Computer ( DAW) ? How many Headphone jacks? A level for each? Are the input pads or line / Instrument toggle switches on the front, back or software controlled? Is it a metal box or cheap plastic? Is it light and portable or large and bulky, Rack mountable? Does it have an on / off switch? Does it use Buss power or a power supply? Buss power can have issues with noise and Phantom power. Look for at least an optional power supply. Does it have DSP effects built in? Does it use a GUI mixer? Having a software (GUI) mixer adds more options. Can it be used as stand alone? Some interfaces are also handy as a small mixer and some mixers are handy as interfaces. What are the Round Trip Latency (RTL) specs? Do you need low RTL for real time processing? Low RTL is going to be at a higher price point. A $200 interface will have hidden buffers etc. Zero Latency monitoring is not the same as RTL. All interfaces have some latency. Zero latency is just marketing hype for monitoring directly from the interface. And most important of all, Does it have top notch drivers for your OS. What is the word on support from the company? Does it come with free software, An LE version of a DAW you would like to try? Everyone will recommend the interface they have chosen, that doesn't mean it is the right one for you.

If your going to use amp sims then you better buy a better audio interface that is capable of a very low round trip latency. And your computer will also need to be capable of supporting very low buffer settings without drop outs. See the very bottom line on this dialog box- "Total Roundtrip"- that has to be below 6ms for most people to not through your playing off time. One solution is to blend the playback with the direct sound.

Holy cow. How old is that Saffire 6? The download page doesn't even mention which version of windows the driver is for? And maybe the issue is related to the fact it was made for USB 1.1 and not 2.0 https://customer.focusrite.com/en/support/downloads?brand=Focusrite&product_by_range=410&download_type=all Yes a new interface might be a good idea. The Mackie will not have good drivers either. I know, I had that mixer. I had to re-read the entire post as I have lost track of the original issue. You should try my tutorial on getting started and see if that works. It's very basic but I explain step by step how to use a downloaded midi file to make a project. Go to my site found in my signature and look for the Cakewalk tutorials on midi.

I think people get totally confused about latency and where it matters. If you use direct monitoring it doesn't matter what buffer size etc you use. You will hear your input synced perfectly with the output. DO NOT TURN ON INPUT ECHO on new audio tracks your about to record. Use direct monitoring. RTL only matters if you are trying to listen to what you are inputting AFTER it has passed through your system. There will always be latency if you do this. And ya,, with a top notch system and interface you can get that way down to something like 2.5 ms but there will always be latency. Most run of the mill systems ( Computers/ audio interfaces) run at more like 8ms to as high as 30 ms. I have a pretty basic system and my RTL is at best 12ms so that is unusable for monitoring as I overdub. I use direct monitoring and therefore I'm listening at zero latency ( or very close). Now all this above is related to recording audio. Midi is different. Midi latency can be caused once again by the entire system. I find it's important to use a good midi driver that comes with most of the better controllers. I had terrible latency all of sudden a while ago and it turned out the issue was caused by W10 update overwriting my Roland midi driver with a generic midi driver. I re installed the Roland midi driver and the latency was gone. The other times I will experience midi latency is when I have certain effects like the LP multi band active. The latency goes away the minute I bypass all my effects. So I'm in the habit of making sure I by pass all my effects before I try and overdub midi parts with my midi keyboard or my midi drums. As far as I can tell midi latency has little to do with audio settings. There is for sure still some latency which will be caused by the system. I can hear just a bit of echo if I listen to my midi drums brain mixed with a VST drum output. So once again I use direct monitoring when playing drums and only monitor the brain while tracking. On a top notch system it might not be as noticeable but on mine it is. Someday I'll purchase a better interface like RME but for now I get by fine with a Focusrite or my Tascam.

I have been following your other thread and you are asking very good questions and taking the time to learn about the complicated world of DAW recording. Audio interfaces always will have the direct monitoring feature. This is a feature that allows you to monitor your input source directly before it passes through the A/D convertors so therefore the sound is direct analog and has zero latency. This is mixed in your monitors/ headphones with the playback from your computer via the ASIO audio / USB / D/A convertors which your DAW will automatically adjust for latency so that your overdubbed tracks are perfectly in snyc with the already recorded material in your DAW. You can have issues if you have VST effects that use a " look ahead" buffer. It is best to perform all overdubbing ( tracking) with all effects bypassed to eliminate this issue. You can also have issues with latency if you try and overdub tracks while listening the the sound of the output of the DAW instead of the input. The output of any DAW will have some amount of latency depending on the quality of the system. Input of interface A/D convertors add latency The system of your USB and computer add latency Your DAW can add latency and if there is a lot of effects it can grow. Your buffer and sample rate settings can change the amount of latency Then the USB going out and the D/A convertors sending to the monitors can add even more latency. So direct monitoring solves all this and then a good ASIO driver that correctly reports to your DAW what it's latency is so the DAW can correct this is also important.

Good sounding electric Guitar is possibly one of the more elusive sounds to capture and there might just be as many ways to accomplish this as there are brands of guitars and amps. Easiest method by far is to mike up a great sounding guitar/ amp combo using a SM 57 or equivalent. Any audio interface with a mike input set at the proper input gain will record more or less the sound of that amp. Best to wear headphones to play along with the backing tracks so they don't bleed into the new track. This is a very easy recording process that is worth the time it takes to get it to work properly. Electric guitars respond best when interfaced with a proper pre amp gain structure. DI sound typically can sound thin or wet noodle. So feeding a wet noodle tone into a A/D converter is not going to ever sound like feeding it into a hi voltage tube pre amp. Think about it,, Some people like the sound of processed wet noodle guitar, each to their own. Most of us want that tube amp overdrive that only a good amp delivers. There are some excellent guitar pre amps as well but expecting a A/D in the box emulator to sound the same as hardware??? close but no banana.

Exactly You got it.

Mabey a screen shot of my preference settings will help. This is not my main system but just substitute Focusrite for M Audio.

must be because i never see that

You insert 2 stereo busses. One is for the drums/ percussion the other is any other synths like bass, piano etc. So you pan one bus hard left and to other hard right. It's a simple matter of sending the drums to the left buss and all other instruments to the right. You could even have a bunch of sub busses if you so desire and just by panning each buss create a custom split track wave file. I like this because sometimes we do want a full stereo track and all I need to do is un-pan the busses. These backing tracks also get used as our bed tracks for recording full albums too. In my tutorials I show how to get at the master buss in the buss pane https://sites.google.com/view/cactus-studios/part-1-midi-and-cakewalk To insert a new buss just right click in the buss pane to open the dialog. You can name the buss anything you want. Make sure it's output is going to the Master buss.