Exactly the same problem I'm having, sounds like. My project worked fine in X2 before I upgraded from Windows XP 32-bit to Windows 8 64-bit. 

Tech support is having me do some troubleshooting by email. I'll let you know if I find out anything.

Mark

mwall


Exactly the same problem I'm having, sounds like. My project worked fine in X2 before I upgraded from Windows XP 32-bit to Windows 8 64-bit. 

Tech support is having me do some troubleshooting by email. I'll let you know if I find out anything.

Mark

Thanks a lot Mark!


John

Did you try switching the "playback and recording" driver to ASIO or one of the other drivers? ASIO only works for me, WDM or MME gives me drop outs of sounds.

So it does occur in X1 as well.  I don't recall having this problem with other projects in X1, so maybe there's something corrupted in this project.  I'm going to try to create a project from scratch to see if I can duplicate it with a simpler example.

I haven't switched from ASIO drivers because they've been solid for years, and there's no trouble with audio tracks.  Also, I have Melodyne and I believe it only works with ASIO drivers, though I haven't verified that.  Maybe someone who knows could comment on that.

John

CoteRotie


UPDATE: Several of the tracks had the MIDI transpose effect in the MIDI effects bin. When I removed those and manually transposed the notes in the PRV the drop-outs went away. Now I'm thinking that there may be a bug in the transpose effect. I'm going to do some experiments to see if I can find something reproducible.

Anyone else notice any problems with the MIDI effects?

I record MIDI tracks all the time, as I am primarily a keyboard player (and some guitar).  But I never use the MIDI effects - I just apply regular audio effects to the audio tracks associated with a given MIDI track.


I also definitely do not transpose that way.  I always use the Key+ slider in the (EDITED) Track Inspector to adjust the notes up or down in increments of 12 to do one octave at a time in either direction as needed.  It's mostly so I don't have to reach too far from wherever I am sitting when I am recording.  My keyboard rig is at a 90 degree angle to my computer table and display monitors.  So, if I am recording a bass track, I may transpose down an octave or 2 so that I have a comfortable reach to my 76-note controller that is my bottom keyboard in my rig.  Strictly a reach thing for me.  But this never causes me any issues.


Give that a try and see if that makes any difference.


Also, are you using any hoggy audio effects?  People keep mentioning Perfect Space and there are some others.


Just some thoughts here while other things are being researched.  I am also still looking for threads on some other stuff for you.


Bob Bone

FWIW I've had a similar problem with midi dropouts (plus going out of sync with audio).
My project is all midi tracks. Some of the midi goes out to external synths & back as "live" audio. The rest of the midi goes to soft synths (including DimPro).
If I put a mastering plugin (eg Ozone, TRacks etc) on the master bus the problem occurs.
Increasing various midi buffers reduces the problem but doesn't eliminate it. Toggling PDC reduces the problem but doesn't eliminate it.
Turn off the mastering plug & the problem goes away.
I suspect my combination of data flows is seriously upsetting the PDC software. I don't recall the problem happening in Sonar 8.5, it's an old project.

I'm on XP so YMMV, but it may be related.

Thanks a lot Bob, Bruce and others.  I do have various audio plugs, some of them are processor hogs (though my machine doesn't seem to hardly notice them.)  I'll remove all the plugs and if the problem goes away I'll start adding them back one at a time until I find out which one is the issue. 

Great tip!

John

With my issue the plugs have a look ahead function, rather than being a processor hit issue IMO.

Hi guys,

The ideal MIDI buffer size depends on a few factors.
- The audio latency (higher requires larger MIDI buffers) 
- The net plugin delay in the project
- The number of preroll buffers
 
For the next update I have changed the code to make the MIDI buffer size adaptive. i.e. the specified value is just a minimum value and the actual buffer size used takes into account the total delay in the project and the other parameters that affect this.
This should greatly eliminate the need to ever touch the MIDI buffer size. I have tested it with several scenarios that would lead to dropped notes in all prior SONAR versions and it works fine now.
For example prior to this change, if you had a synth track and something like perfect space or other PDC inducing plugins downstream, notes could drop out until the MIDI buffer size was raised.

Noel Borthwick [Cakewalk
]

Hi guys,

The ideal MIDI buffer size depends on a few factors.
- The audio latency (higher requires larger MIDI buffers) 
- The net plugin delay in the project
- The number of preroll buffers

For the next update I have changed the code to make the MIDI buffer size adaptive. i.e. the specified value is just a minimum value and the actual buffer size used takes into account the total delay in the project and the other parameters that affect this.
This should greatly eliminate the need to ever touch the MIDI buffer size. I have tested it with several scenarios that would lead to dropped notes in all prior SONAR versions and it works fine now.
For example prior to this change, if you had a synth track and something like perfect space or other PDC inducing plugins downstream, notes could drop out until the MIDI buffer size was raised.

Thanks, Noel, that's good news!
 
John