Note snap incorrect when creating MIDI item (snap disabled arrange wind) FIXED

[tohubohu]

Mac OS
Reaper 6.67

Hello,

QUICK AND SIMPLE DESCRIPTION

When you create a midi item with snapping disabled in the arrange view, the insertion of notes in the midi editor is not set exactly on the grid, which can prevent you from hearing the first note when you start playback.
It can be really confusing.







MORE DETAILED DESCRIPTION


1 - Arrange window snapping disabled
2 - I insert a midi item anywhere and stretch it a bit.
3 - I open the midi editor
4 - Note snapping enabled in midi window.
5 - I insert a note.
6 - Note zoom
7 - we notice that the note is not set exactly on the grid but slightly shifted to the left of the grid.

problem :

8 - this is a big problem, because when you zoom out and think you are placing the cursor on the grid at the start of the note, in reality the cursor is not at the start of the note. As a result, there is no sound when you click on play at this point. (if the option "chase midi note-ons in project playback" is disabled). it's very annoying for beginners who wouldn't understand what's going on.






Other less serious problem below

9- Arrange window snapping disabled
10 - I insert a midi item anywhere.
11 - I open the midi editor
12 - Note snapping enabled
13 - I insert a note and zooming in, we can notice that it is slightly to the right of the line of grid
14 - in this configuration, it is not a problem to hear the first sound





no problem the configuration below

14 - the same but with snapping enabled in the arrange window
15 - it's ok.

[tohubohu]

bump!

[Vincent Sermonne]

same

[sardonicus]

Same as well.

[jeranx]

Pareillement.

[sockmonkey72]

Maybe rename this bug report: "MIDI Editor note snapping incorrect when arrange window snapping disabled" or something, which is much more descriptive of the problem and might get someone's attention?

[tohubohu]

Originally Posted by sockmonkey72

Maybe rename this bug report: "MIDI Editor note snapping incorrect when arrange window snapping disabled" or something, which is much more descriptive of the problem and might get someone's attention?

Hello,
Since you made a remark to me about a report of a bug that I considered serious on the score editor, I no longer dare to put something like: "Important bug..." in the title.
I happened to have already changed the title of this thread because no one was responding. This one talks about the consequence of the problem. And still no response from anyone before I asked to support me on the French forum following a remark from a user on the same problem (coincidence).
I'm considering your proposal.
(this is said without malice but with annoyance). thanks anyway

[sockmonkey72]

Originally Posted by tohubohu

Hello,
Since you made a remark to me about a report of a bug that I considered serious on the score editor, I no longer dare to put something like: "Important bug..." in the title.
I happened to have already changed the title of this thread because no one was responding. This one talks about the consequence of the problem. And still no response from anyone before I asked to support me on the French forum following a remark from a user on the same problem (coincidence).
I'm considering your proposal.
(this is said without malice but with annoyance). thanks anyway

The problem sounds "important" to me, but it's not for me to tell the devs which bugs are important or not. It's like when someone writes you and says "this is urgent, can you stop everything you are doing and help me?", it may not have the desired effect. It's common sense.

My title proposal is clear, objective and doesn't add unnecessary drama. There are certainly other options, but I don't think you'll get what you want (a fix) if the bug is" bad for beginners".

This is also said without malice but with annoyance FWIW. 😂

[tohubohu]

Originally Posted by sockmonkey72

The problem sounds "important" to me, but it's not for me to tell the devs which bugs are important or not. It's like when someone writes you and says "this is urgent, can you stop everything you are doing and help me?", it may not have the desired effect. It's common sense.

My title proposal is clear, objective and doesn't add unnecessary drama. There are certainly other options, but I don't think you'll get what you want (a fix) if the bug is" bad for beginners".

This is also said without malice but with annoyance FWIW. ��

this bug is not important to me. I hadn't put anything. I don't need help because I got around it. This is a pb that affects everyone since no sound is emitted on the first note.
As far as the notation editor was concerned, it was a crippling problem.
After that, I don't care. it is just free help for a community.

[tohubohu]

Hello Justin and Schwa,

I added a very short and simplified description of the problem in the first message.

This important issue can be solved by a workaround if the fix is complicated, as you know

[Jaydo]

Hello, I noticed snapping of midi notes is completely wild. It randomly snaps a few pixels left or right off the actual grid. If turn off snapping completely, midi notes still snap, even more randomly! What is going on? I don't recall this being a problem in the past.

[tohubohu]

@jaydo
I didn't understand. can you be more specific please? with an example in gif or screenshot. thank you

[skylar_battles]

bump

[tohubohu]

thanks for bumping.
this bug is quite important and annoying and affects everyone.

[jeranx]

Allez tiens, je passais par là, je vais bumper aussi.

[tohubohu]

thanks jeranx.
you understood the importance of this bug which should be solved.

[dangguidan]

The latest version of dev has solved this problem.
The minimum precision in midi is tick, and the working precision of reaper is much higher than that, so the note may be on -0.0000005 tick, I guess!

[tohubohu]

This is it?

MIDI: when disabling note chasing via option, fix cases where note starting exactly at edit cursor may not get played

[tohubohu]

Originally Posted by dangguidan

The latest version of dev has solved this problem.
The minimum precision in midi is tick, and the working precision of reaper is much higher than that, so the note may be on -0.0000005 tick, I guess!

i still have the problem i think

[tohubohu]

I did a test only on mac os 10.6 and there is still the problem

[dangguidan]

Can you provide a small demonstration project?

[tohubohu]

here is a project.
I have no sound with '...chase..' deactivated when I put the cursor on the grid

[dangguidan]

There is a hidden defect here, but I haven't fully figured out how to reproduce it. It just appears randomly.
The note currently appears to be at 0 tick, but it is actually at 479 tick.
There are several steps to avoid this situation. The starting point of the item is aligned with the grid, and the item is glued once.

[tohubohu]

these problems appear when the item is not created with snap as explained in the demonstration.
this is not fixed

[tohubohu]

forcing items to snap to the nearest grid in all item creation situations would probably fix the problem

[shaelter]

bump

[tohubohu]

thanks for the bump.
many people are complaining about this problem which is still not solved.

[tohubohu]

bump

[jeranx]

Originally Posted by tohubohu

bump

Pffff.
Et les français, bumpaient, bumpaient, ....

[tohubohu]

Originally Posted by jeranx

Pffff.
Et les français, bumpaient, bumpaient, ....

It's the last for a long time

[jeranx]

Originally Posted by tohubohu

It's the last for a long time

Yes, I find you very tenacious, with not much of an answer in your face.

I won't hide from you that I have never encountered a problem with snapping in Reaper. So, whether you get your way or not won't change my life. But this pugnacity inspires respect.

Bye.

[dangguidan]

Everyone has their own specific workflow and needs to understand it better.
In fact, the current situation of missing notes occasionally occurs.
When the starting point of an item is not in the grid, there is a slight error between the apparent position of the note in the MIDI editor and the actual position, which has always been a problem. For example, if the note attribute is at 2.0.000, it may be at 1.4.479 (time base 480) when using a script to read the note position.
The best way to avoid this now is to align the starting point of the item with the grid.If the problem persists, glue it once.

[tohubohu]

hello, I got around this problem a long time ago.
my bumps are for the thousands of users who encounter this problem that makes Reaper not serious. if I was a beginner and saw that, I would change software immediately.
thank you jeranx and danguidan

[matiasosa]

I, and many users, have the same problem, but the notes are after the beat which is weird. In my case, there is a big issue, because the notes also end after the beat, and when you play back something like drums you can hear the hit from the beat before. Like you said, this makes people think Reaper is not too serious. It really bothers me when I'm working and encounter this issue. I work a lot recording with MIDI and it's annoying having to always having snap of because sometimes I just want to record after a bit or using MIDI overdub and forget to have snap off or don't really need it other than not having this problem.

[tohubohu]

Originally Posted by matiasosa

I, and many users, have the same problem, but the notes are after the beat which is weird. In my case, there is a big issue, because the notes also end after the beat, and when you play back something like drums you can hear the hit from the beat before. Like you said, this makes people think Reaper is not too serious. It really bothers me when I'm working and encounter this issue. I work a lot recording with MIDI and it's annoying having to always having snap of because sometimes I just want to record after a bit or using MIDI overdub and forget to have snap off or don't really need it other than not having this problem.

I solved the problem by a custom action when inserting midi item.
But good Luck for beginners or those who don’t know the trick
they are certainly tearing their hair out or maybe giving up the use of reaper

[Justin]

Originally Posted by tohubohu

here is a project.
I have no sound with '...chase..' deactivated when I put the cursor on the grid

I'm not sure what we can do about this -- you have the note starting before the grid, and you have "chase notes" disabled. Normally you should chase notes! I suppose we could chase notes if they are within some threshold of the starting point, but I fear that if we do that then that threshold will be the key thing and you'll still unpredictably have some items before it and then it won't work as expected...

[tohubohu]

Wouldn't it be better, when creating the midi item, for it to snap to a very very close grid?
that's what I did to work around the bug, in a custom actoin.

EDIT : when the midi item is snapped, the problem disappears.

[Justin]

Originally Posted by tohubohu

Wouldn't it be better, when creating the midi item, for it to snap to a very very close grid?
that's what I did to work around the bug, in a custom actoin.

EDIT : when the midi item is snapped, the problem disappears.

Hmm yeah I suppose, there are a lot of places where this could still go wrong but I guess we could get the common spots

[tohubohu]

it's better but all the copy-paste doesn't work
and all the 'draw a copy...' in mouse modifiers either
the action 'Insert or extend midi items to fill time selection' does not work either

[tohubohu]

the copy/paste with the razor edit and the time selection don't work either...