chuckebaby

I picked up a Focusrite 18I8 for this very reason. It has 4 combo XLR-1/4 jacks and 4 line in jacks. Ive seen them as low as 199.99 used at Guitar Center. Good drivers, works/plays nice with Cakewalk.

Very impressive Too bad we wont be alive to hear the outro and fade out

The mfc120u.dll is directly linked to the Visual C++ Redistributable Packages. It should be noted, It is imperative to reboot your PC in order for these packages to fully install properly. Also of great importance is downloading them directly from MS. and no where else.

Im very surprised by this. Waves usually follows up within a day. Possibly the best support for any plug in on the market. Your errors are Visual C++ Runtime errors. This is synonymous with a failed C++ installation or one not present. That would be the first thing I would check. Second, just so we are all on the same page here... This is the latest Cakewalk by Bandlab your trying to use ?

Seems like the Sustain pedal is a common theme with both of your issues. Have you tried not using it and see if you still get stuck notes ? Why don't you post a .CWP project file here (midi only is fine) and I will take a look at it. You could also send in a project to Cakewalk and have them take a look at it but it might be helpful to include repro steps with your submitted projects. Those steps might be able to be figured out here in this thread. The default is 250MS.

I have to agree as well. At first I was puzzled by this behavior and it is tiresome when you are pasting different subsequent variations each time you use Special Paste, but after a while, it makes life easier when you have a ton of "same type Paste specials" in a row. Its a trade off with more benefits to keeping changes stored. That's for me anyway.

Sometimes overlapping notes can cause serious bodily injury when it comes to missing/dropped midi notes. Is it the same notes sticking all the time ? If it is than open the PRV and do a visual. I find 500MS is the typical norm. Did you start there and move up to 850MS ?? there's also some info here that may be helpful

When ever I export a project I have Start/End times. This is done using the Edit/Select menu (From here/Thru here). Your project is Including the 136 measures because you didn't specify a region for export.

Because not everyone wants to delete a whole track along with a marker. We all work in different ways.

I've known you for a long time on these forums. Im not doubting you P-Mid. Just trying to help narrow down weather it might be specific builds, set ups, soundcards, exc. I applaud your follow up with Cakewalk, it helps when users submit stuff like you did. Helps us all

Windows 8.1 X64 Using latest build and I am able to open projects without issue. Possibly you can upload one of your older projects that you cant open and give others a chance to see if they can.

Why not purchase an inexpensive USB soundcard, Like a Focusrite Solo ? And have you tried WASAPI or ASIO4ALL ?

You might have to use the Marker view for now until you Contact Cakewalk with a Project that exhibits this type of behavior. As a test I just loaded up the newest version and I AM getting the double-sided M arrow and I CAN delete markers using the Delete key. As mentioned earlier, I would contact support.

And this was my other suggestion

There used to be a bug in previous versions of Sonar where Toggling the FX button in the Control bar would reset the metronome. Which version are you running ?

Yes if I remember correctly laposa was one of the people pushing hard for that Ripple edit light indicator. 😀

If you would please direct your attention towards my 1st post.... Sorry just having fun

This could also be due to Cakewalks Track Focus vs Track Selection. You can be working on Midi track 13 but have Audio Track 12 selected. Just because you make a selection on track 12 doesn't mean it is selected, it just means you have focus on that track. Make certain the track you are pasting to IS selected. This can be achieved by visually inspecting the track widget to make sure it is illuminated.

After first reading your OP my first thoughts were similar to @mettelus and @Lapasoa. When creating projects that have audio I find it is always best to start the project at 1:02 rather than 1:01. This gives time for the audio engine to do its job properly vs asking it to spit out audio as soon as you hit the Play (SpaceBar) button. But I have a feeling it might have to do with the Mixer knob on your interface. Its a direct monitoring knob. Turning it counterclockwise is your input. Turning it clockwise is you DAW playback. If your using an Amp sim like guitar rig, you'll want to have your Input echo engaged.

This has happened to me before using a mouse that it is slowly building up dirt, oxide or faulty buttons. I would test another mouse just to rule that out first. If the mouse is not the problem we can try to figure it out from there.

have you tried playing with the Mix knob on your interface Gerry ?

have you tried to open the ASIO menu and check your settings ? Your still using the Presonus audiobox correct ?

I believe freeze is the best way as well. You can quickly unfreeze to edit which makes it very practical. I do agree with what some of @Blogospherianman was saying though. I would hate to save a project, open it later and try to unfreeze a synth and have it not unfreeze. This hasn't happen to me but I believe with some older synths...anything is possible. I don't freeze synths personally, but only because I use a max of 10 per project and I don't see a tremendous core spike in only 10 (I say only 10) but I tend to make back ups of anything I intend to commit to. That would include the RAW midi data saved in a file (which I always do) and a soft synth template. I never swim without a life jacket.

Because recording audio using MME is impossible. Are you using ASIO mode, WASSAPI ?

Using Google chrome as a browser ?