Bass Guitar

This thread is from September. Somebody dug it up. And yes sales are over but they said in that thread they are working on a fixed price which is expected to be less than the original $150. All these sales just add to to frustration for those who either paid the full price or like me they won't honor it if you are already a member. They seemed to be sorting this mess out and hopefully stop messing with our minds. They should follow the example of another Daw I now own. They too had a free version and being a registered user I received an email offing to upgrade to the paid version for only $49. regular price is $199. How could I resist! But the difference is I now own it for life.

In most cases when playing via hardware you need to choose a Midi channel, Bank and a patch. The users manual will explain how to set this up and have a Bank and patch list somewhere. Yamaha is pretty together about that stuff. It probably even has a Multi channel GM player built in.

Why is everybody so defensive of a company that obviously made it clear that they are not focused on long time users and what we think? This Daw has become just a piece of "merch" in a cooperate strategy to sell subscriptions. Doesn't take much to figure that out. Nothing wrong with it otherwise. Continue to save your hard work in a format that belongs to a Cooperation whos goal, understandably, is to make money for the shareholders. Nothing wrong with that either, it's how the world is run. Sonar is a great Daw! I hope it survives all this BS. We should be buying shares in Bandlab! But this Membership deal and Cakewalks pop ups have lost a lot of loyal users. My observation is that Daw's that are owned by the developers do care what the users think. So if that is important to you, then you should seek that out. Our developers care but they have no control of the marketing. So my feedback about the new release is I'm all for them adding advertising and making people sign in once a week. PT 1st ( free) makes you do it every day. If you don't like it either take the bait or --

It funny this just came up in the other new thread today. So I won't repeat what I said already. But YES PLEASE! Add ARA! it's a PITA to have to continually work in the Stand alone editor for Melodyne. Simple things like Audio to Midi are missing. Here's my wish list: ARA support Mixer View - Next is alone in this glaring omission. And please allow that you can undock these and the midi editor while your at it. Next is the only Daw I use that can't use 2 monitors. Then please add db readings to the meters? A favorites list for adding plug ins. Most Daw's have this. Midi output option on instrument tracks for hardware support.

No, Next is very basic and is missing a lot of more advanced features. They seems pretty slow at making improvements. After a whole year gone by we finally got a tempo map. You get the impression this is a part time job for one developer. What I am forced to do with things like this is use Melodyne stand alone. If Next had ARA support it would happen internally like it does in other software that supports ARA. Presently you would have to find that clip in the audio folder and open it in the Melodyne editor and transpose it there and it "SAVE AS " and add the new note name. I have Melodyne studio so I can create complicated chords from just that one note. People only think of vocals but I use Melodyne for audio editing way more than vocals. Its possibly still on sale. This is the best time of the year to upgrade. Most people have the essentials version which comes free with a lot of Daw's. Even one free Daw I have included it. They will use that license for a cheap upgrade.

Interesting, this was sort of my experience too. The emails were all polite and obvious boiler plate auto reply. Never did find out what caused the crash. At least it never happened again.

Why do I bother, the last 3 answers I gave on this stupid forum resulted this sort of reply. Signing off.

This! Do it. Noel offered his help and you sort of ignored him. He takes these things seriously and they need the report as it is what in the end makes Sonar stable. We all benefit from users cooperating with this. And if you go into the crash dump you will be able to possibly see what caused the crash. But there's always more to it that is best those who can decipher have the info. Windows Debugger, also known as WinDbg, is a tool made by Microsoft to help troubleshoot bluescreen minidumps. Windows Debugger is a tool that helps you read the minidump file.

Actually he is correct. The UM22 is one of the poorest choices for use with a Windows PC because it does not come with an ASIO driver. It is supported fine by Core Audio and that was the market it was made for. Mac. It is a huge waist of time to try and make it work on a PC. Give it to a friend who has a Mac. The Focusrite is actually another poor choice because bang for buck. It is lacking in features other similar price 2x2 interfaces have. Do your research. I had just watched this video the other day so that's why I had just found this out. https://youtu.be/YcDGKuBJ2VI And this is another real good one to watch. https://www.youtube.com/watch?v=gMuA-2FbJxE&t=1013s

I think this sort of says it all. The driver hasn't been updated since 2007! I have the us1641 audio interface which is same vintage. they updated the driver in 2016. But it no longer works very well with W11. It kind of worked with W10. I still have 2 computers running W7 for this very reason and I can use it no problem to record 14 tracks of audio live. But yes it's a great piece of gear that has only been forced out of use by windows updates. I also have a M-Audio Fast track pro that is the same issue. There's zero wrong with either of these interfaces but they only work on W7.

I remembered you posted this and in the Next help menu is a "View Release notes" option. I clicked on it and a box popped up in the notifications saying there was nothing available at this time??? I find it odd how silent Bandlab is being about Next?

Simple solution. Go into preferences, Keyboard shortcuts and my choice was the "Z" key got assigned to open Melodyne and the "X" key to render. This keys were not every used by me. This eliminates a zillion mouse clicks when working on a track that is chopped into shorter clips. I re-assign a lot of the main shortcut keys as I hate having to use Combination shortcuts. I'm a mouse type person. I even re-assgned the "T" key to be Transpose because I rarely need to open the tool menu that way. The "V" key is now save.

Troubleshooting needs to be a process of elimination as your issue could be caused by a few different things. Here's a few thoughts I would try. I said to Bypass ALL the effects as those could be the cause for different reasons. This eliminates things you might have missed like Pro channel modules. It could be a drop out that only happens at that point because something is taxing your system. Like an effect or a VST instrument. So increasing your buffers to around 520 might solve the issue. You have a new Audio interface and there's no telling if it will perform better than your old one. Example I was surprised to find my Motu interface would drop out at the same buffer setting that all my other interfaces didn't drop out. Does the Apollo have DSP processing? Turn that off if it does. Freeze the Midi instruments.

I've only had it happen in one track. If you zoomed in there was nothing odd showing. So I just split the track there and add fade outs and fade ins and it would be gone. but your saying it's across multiple tracks and each one makes the sound when soloed? Try by passing all effects.

Freeze midi track/ Drag to timeline/ Unfreeze midi track. Open the tempo track and Inspector view of it. Now turn on ripple edit/ turn off snap to grid. Drag midi track until downbeat lines up to measure grid properly. Now check that every downbeat is lining up properly. You might have to edit the the tempo track. You can also use Set Measure Beat at now to edit anything that was wrong. But for me this has always worked for most of material. The stronger the transients the better the success. You can also do this in Melodyne stand alone or from within Sonar and export a tempo map. But it needs to be audio first.