Download this project: Tempo Bug.cwp
Play it.
You'll notice that the notes stop playing when tempo is decreasing, around 20 bpm.
I've noticed this in several projects.
For example, 10 bpm, nothing sounds.
It is certainly a bug.
 

rogeriodec
You'll notice that the notes stop playing when tempo is decreasing, around 20 bpm.
I've noticed this in several projects.
For example, 10 bpm, nothing sounds.
It is certainly a bug.

I tried this file and played it as downloaded. The issue happens here as well , even after shortening the notes a little.

However, I loaded Rapture pro (and used a piano patch) and Truepianos (Full version 1.95) and the issue did not occur - the file played all notes correctly. 

Looks like it may be an issue with the TTS synth itself rather then Sonar's playback.

Not sure what to suggest.  Others may have an idea...

promidi
 
However, I loaded Rapture pro (and used a piano patch) and Truepianos (Full version 1.95) and the issue did not occur - the file played all notes correctly. 

Looks like it may be an issue with the TTS synth itself rather then Sonar's playback.

Not sure what to suggest.  Others may have an idea...

This problem also occurs with Kontakt.
For example, in a part of my project from 10 BPM nothing sounded. I had to switch to 15 BPM to work.

Hello, I wonder if anyone else could emulate this effect, if it is worth submit a complaint to Cakewalk?

I played back your project and noticed that a couple notes didn't sound. However if I moved them even slightly, they did. Perhaps there is an interaction with the tempo change, e.g., a speed up occurs just before the note-on and skips past the note-on on the timeline. AFAIK TTS-1 will not "go backwards" to see if it missed any note-ons between the time it was asked to speed up and the time it ended up in the new place on the timeline. If this is the case, it would not be a bug; you are instructing SONAR to jump ahead of where it could read the note-on, so it dutifully doesn't read it.
 

I do not know if I can agree with your arguments, because if a note sounds at 30 BPM, it should sound at 10 BPM.

just out of curiosity, does one even need to run at 10 BPM ? I must admit, this is a first.
cant you simply use 40 BPM and use the note equivalent formula (1/4 note).
 
don't get me wrong if something isn't working properly it should be fixed (though im not even sure we have determined that)
 

rogeriodec
I do not know if I can agree with your arguments, because if a note sounds at 30 BPM, it should sound at 10 BPM.

If there's anomalous behavior, I'm the kind of person who's more interested in finding out the cause than reflexively posting about some presumed "bug." What you are describing is NOT a bug in SONAR. I will explain it more clearly.
 
First of all, SONAR is perfectly capable of playing back successive MIDI notes at a tempo as low as 8 BPM, which is the program's lower tempo limit. Second, if instead of the TTS-1 you use True Piano, Rapture, Z3TA, any of the SI series instruments, Dimension Pro, etc. etc. you will not encounter the "missing notes." Try it. The problem is not with SONAR or it would affect these instruments as well.
 
I believe the problem is that you are using an older multitimbral synth. You have quantized your Note-On, Note-Off, and tempo changes so they occur at exactly the same time. If the TTS-1 cannot respond rapidly enough - and remember, because it's multi-timbral, it's dealing with 16 instruments at once - then if a tempo change occurs before the TTS-1 can detect the Note-On, SONAR will have already moved further down the timeline, past the Note-On, because you have asked SONAR to speed up. The TTS-1 never sees the Note-On, therefore it cannot play it back.
 
Does that make sense now?

chuckebaby
just out of curiosity, does one even need to run at 10 BPM ? I must admit, this is a first.
cant you simply use 40 BPM and use the note equivalent formula (1/4 note).
 
don't get me wrong if something isn't working properly it should be fixed (though im not even sure we have determined that)
 

Fermata. If you want to keep synchronism between the project and a score (Sibelius), it is important that both keep the same notation.

Anderton

rogeriodec
I do not know if I can agree with your arguments, because if a note sounds at 30 BPM, it should sound at 10 BPM.

If there's anomalous behavior, I'm the kind of person who's more interested in finding out the cause than reflexively posting about some presumed "bug." What you are describing is NOT a bug in SONAR. I will explain it more clearly.
 
First of all, SONAR is perfectly capable of playing back successive MIDI notes at a tempo as low as 8 BPM, which is the program's lower tempo limit. Second, if instead of the TTS-1 you use True Piano, Rapture, Z3TA, any of the SI series instruments, Dimension Pro, etc. etc. you will not encounter the "missing notes." Try it. The problem is not with SONAR or it would affect these instruments as well.
 
I believe the problem is that you are using an older multitimbral synth. You have quantized your Note-On, Note-Off, and tempo changes so they occur at exactly the same time. If the TTS-1 cannot respond rapidly enough - and remember, because it's multi-timbral, it's dealing with 16 instruments at once - then if a tempo change occurs before the TTS-1 can detect the Note-On, SONAR will have already moved further down the timeline, past the Note-On, because you have asked SONAR to speed up. The TTS-1 never sees the Note-On, therefore it cannot play it back.
 
Does that make sense now?

Thanks for the reply, but no.
The example I sent attached in post 1 was only because TTS-1 is a standard installation of Sonar.
I use Kontakt, with very recent version (x64 5.5.2).
At the same time my hardware specifications are updated as well, as you can see in my signature.
What about your argument on simultaneous processing, the problem occurs in a slow BPM, with only one channel, ie it gives more response time for processing the events.
And also this did not occur in older versions of Sonar.
Unfortunately I have no other DAW here to simulate and compare.