• SONAR
  • 99 Problems, but Paying Cakewalk Ain't One (p.5)
2015/05/30 14:06:59
Anderton
It would be interesting to find out why some people with large projects run into problems while others with large projects don't. I regularly run 100+ tracks, all with plug-ins, when doing loop or sample library development but those don't require large orchestra libraries.
 
I have noticed a lot of the people having problems use the East-West libraries. Not sure if that's a clue or not, but if there was a recent update, that might be significant.
2015/05/30 14:11:39
Stuntpickle
Pragi
Agreed,
your problems in the first place aren´t Sonar specific (sure this software isn´t perfect),
it´s the person sitting in front of stuntpickle´s monitor.
 
Sorry , but this has to be said cause of the thread title which obviously has to be changed.




Wait. When you say "problem" are you referring to the one the Cakewalk staff member confirmed was a problem? I only ask because we seem to be having communication issues, such as when you interpret my statement that I have a Foscusrite audio interface and an on-board sound card to mean that I have both Presonus and Focusrite audio interfaces.
 
I have provided information, photos and video documenting this problem -- which, as far as I can tell, is fairly extraordinary relative to the other threads of this nature on this forum. That, having seen all this, you remain stumped yet utterly convinced I am personally the cause is hilarious, ludicrous and utterly inexplicable.

Not so surprisingly, I posted this thread precisely because I had hoped I was the problem, which I could then personally remedy. Unfortunately, I am beginning to doubt it.
 
Oh, and I can't imagine why the name of this thread would so offend you that you think it must be changed. Cakewalk is as free to change it as I am to fire Cakewalk.
 
I can only remember encountering such a gratuitous defense of something when the defender was trying to copulate with the defended. Are you working on Sonar Jr.?
2015/05/30 14:17:24
Beepster
The unwanted data being written sounds like a track being MIDI write enable with a connected MIDI device that has "wandering" controls. As in the control, even though you aren't touching it, is either so hyper sensitive that it is sending control data which obviously then gets written (because the track is write enabled so it's doing its job properly) or outright faulty and sending false signals (in which case the track is still doing it's job by reading the data and writing it).
 
I have no idea about the rest. Probably system specific/user error. I'd imagine a stunt performing pickle may not be as attentive to detail as say a calm, demure and fastidious pickle.
2015/05/30 14:21:07
Stuntpickle
Anderton
It would be interesting to find out why some people with large projects run into problems while others with large projects don't. I regularly run 100+ tracks, all with plug-ins, when doing loop or sample library development but those don't require large orchestra libraries.
 
I have noticed a lot of the people having problems use the East-West libraries. Not sure if that's a clue or not, but if there was a recent update, that might be significant.




 
There was a recent play update; however, I have since investigated other iterations of the project within Sonar and discovered small traces of the problem. As crazy as it sounds, it seems like it may have been present throughout and only become noticeable following some period of exponential compounding. When I called support, I was having problems on one track. Now, it's every track.

More than Play, I have suspected TenCrazy's channel switcher. I was thinking (or intuiting) that because Sonar (as far as I'm aware) doesn't natively support the functionality that maybe midi data from different channels is getting layered. Was just a thought. Are you familiar with the plugin?
2015/05/30 14:30:03
Anderton
Not familiar with that specific plug-in, but do have some TenCrazy plugs. I would definitely suggest removing it at least temporarily to see what happens. So many SONAR issues relate to third-party software, so that's always a good place to start. And don't forget about the MIDI buffer setting.
2015/05/30 14:34:57
microapp
Not sure if this applies to your SSD or not but Samsung has had serious problems with SSD's using TLC NAND technology. It is up in the air as to whether they have fixed this issue. Essentally the read performance of the SSD degrades to HDD speeds as the stored data ages. 
http://www.extremetech.com/computing/199673-second-patch-for-ongoing-840-evo-ssd-performance-issues-being-prepped-by-samsung
 
2015/05/30 15:28:18
tlw
I seriously doubt an SSD, whatever its problems, can generate spurious MIDI data in Sonar MIDI tracks or anywhere else.
 
I've just had a look at Tencrazy's MIDI channel switcher's documentation (such as it is). Personally if I were using it and having MIDI data turn up in unexpected places I'd create a fresh blank project without it and see if the problem turned up in that project.
 
Can you delete or edit the MIDI using the event view?
 
It also occurs to me that depending on the MIDI routing you've set up tracks might be receiving data on more than one channel or the data is being duplicated on several tracks. Again, a test project without the MIDI switcher and using only Cake plugins would seem a useful thing to try.
2015/05/30 17:00:02
williamcopper
yikes.   this is such a typical thread.   fwiw, I don't think your video card audio, or your hardware, or "connected wandering midi", is the problem.    One thing to track down is the midi channel associated with each midi event in your tracks:    unfortunately, the way PRV works, events in multiple channels ( a valid midi thing ) in multiple tracks (a valid Sonar thing) get created very very easily.    I use the following CAL program, set to a single-character key-command in keyboard shortcuts, to re-re-re-re-rechange the controller per event to ONE channel.
 
(do
 (int new_chan 1)
 (int i 0)  ; counter, not needed if you don't care
 (getInt new_chan "New Midi Channel: " 1 16 )
  (-= new_chan 1)
 (forEachEvent
     (do
      (= Event.Chan new_chan )
     (++ i )       ; count it, delete if you don't care
     ) ; end do
  )  ; end forEachEvent
   (pause "Adjusted " i " channel events. " )   ; tell how many, delete if you don't care
)
2015/05/30 17:28:20
slartabartfast
As far as the MIDI events (expression data) appearing from nowhere issue, I have to agree with earlier suggestions about spurious signals from a controller while the track is armed for recording being the most likely culprit. MidiOx is a good way to troubleshoot this, as it will capture the events as they arrive, and it will tell you on what channel they are arriving as well. Sonar does that as well (hence the unanticipated controller data) but if it appears in both programs independently, then you can stop blaming a Sonar issue. Pitch wheels and the like can often send signals when they are apparently in neutral/off positions, more or less randomly due to the analogue control signals that are interpreted into MIDI in the controller circuits.
 
It is highly unlikely that this indicates a system problem, from a demanding video driver or whatever, which is far more likely to produce a system or application crash than to repeatedly insert false data into a track in Sonar. Missing data because the system was unable to process it as it arrived is possible, but that is not the case here. 
 
MIDI data that is somehow misrouted is conceivable, although the source is a mystery. Unexplained MIDI data would most likely be sourced from a MIDI out of an active softsynth. Most softsyths do not have this capability, but some do and may output controller events. It may even be possible to set up a MIDI feedback loop that could cause some confusing crap by setting a synth MIDI input to the same synth's output. Check to see if there is a synth appearing as an input to the MIDI tracks or if there is a synth that was inserted with the option to "enable MIDI output."
2015/05/30 17:37:56
Pragi
Stuntpickle
Pragi
Agreed,
your problems in the first place aren´t Sonar specific (sure this software isn´t perfect),
it´s the person sitting in front of stuntpickle´s monitor.
 
Sorry , but this has to be said cause of the thread title which obviously has to be changed.




Wait. When you say "problem" are you referring to the one the Cakewalk staff member confirmed was a problem? 
 

No.
Simply the thread title is offending Cakewalk
That´s how you started .
You are offending cakewalk and now me , 
the one who starts has to be ready to get offended either, you are not, or?
 
And to finish your joke,
I´m working with Sonar Platinum jr and you 
with 3 Audio interfaces (the Presonus Audiobox, Focusrite Solo and the one of the video card)
and surprisingly having issues, right?
 
Still I hope, you can fix the issues.
 
best regards
Pragi



 
 




© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account