Sonar 2025.02 Feedback

[Will.]

3 minutes ago, David Baay said:

That's just because the track isn't scaled properly in Sonar to show all the notes.

Doesnt show on my end. The other thing is - I've tried to offset notes myself then open in Sonar and it showed correctly. Maybe I'm doing it wrong?

[Promidi]

3 hours ago, David Baay said:

That's not exactly what I'm seeing or saying. Sonar doesn't change the offset, musically, it just always references the entered/displayed value to 960PPQ.

Here is a shot video showing this issue.

https://drive.google.com/file/d/1_vsRPeXIpHICjZ8cfmiJewZK-ZfYw4M5/view?usp=sharing

[David Baay]

3 hours ago, Promidi said:

Here is a shot video showing this issue.

What it doesn't show is that if you do a loopback recording of the MIDI, the re-recorded notes will actually be 10 ticks late in the 192PPQ timeline as expected. So bringing an old project into Sonar isn't really a problem unless you notice that the displayed offset has changed, and change it back to what is was on CbB. Then you'll actually get the wrong musical result.

Bottom line: There is an issue to be fixed here, but it's a display issue.

[Promidi]

3 hours ago, David Baay said:

What it doesn't show is that if you do a loopback recording of the MIDI, the re-recorded notes will actually be 10 ticks late in the 192PPQ timeline as expected. So bringing an old project into Sonar isn't really a problem unless you notice that the displayed offset has changed, and change it back to what is was on CbB. Then you'll actually get the wrong musical result.

Bottom line: There is an issue to be fixed here, but it's a display issue.

Yeah, I could have done the  loopback recording of the MIDI test.  However, as soon as I saw the +10 change to the +50 between CbB and Sonar, I stopped the video.

As long as it's just a display issue, and even then only if not using 960 PPQ (which I have not done since 2017), I am not going to lose sleep over this one.  It'll be fixed when it’s fixed.