Recording starts of the beat_can anyone reproduce please : )

If I record onto a blank track (creating a new midi item as it records) and at ANY tempo OTHER than 120 (try 83 to be sure) and with or without "preserve PDC delay.." AND lastly, not at the start of a song, my midi items are out by 1/100th of a beat which isn't too bad until you drag the loop out over a few bars and it starts to drift because of it. If I then move the item a little it will snap but surely this is not the answer. I have had lots of these kind of "rounding" issues and it's either me and I need a reinstall or something needs sorting out in the background of reaper as I have ran across similar things in audio items and copying at any other tempo other than 120. Please try and confirm this so I can find out if it's me or not ;) If you can reproduce, please vote in the link below to confirm it thanks

Confirmed. At 83 bpm, the MIDI item is created very slightly too early. The offset I am getting is that small, that I can only see it when zoomed in completely and I can't even measure the length via time selection (it refuses to span that small an amount). But still it's there and shouldn't be. It puzzles me that I obviously get a far smaller offset than you. It's nowhere near 1/100 beat here. No preference or other setting I tried so far changed that. I always get exactly the same tiny offset. I thought it may have to do with "add recorded media to project" set to anything but "On stop", which is a known issue (though, it messes with the end of the item rather than the start), but that is not the case.

I don't understand how to reproduce *EDIT* When I change the tempo to 83 bpm And I position the playback cursor at 3.1.00 Hit Record Play some notes To find: the midi item starts at 2.4.99! This is what you mean?

That's ok i was a bit vague:) -start new project -set tempo to 83 (just to make sure you don't get a random one which works again as 120 is fine and works as expected) -place the edit cursor on exactly bar say 50 (anywhere but the beginning of the song really) -Insert a new midi instrument, armed and ready to record -start recording from exactly bar 50 and then stop a few bars out (just press record again to stop it asking for delete or save) Result for me is that if i click on the item to bring up the info for it i find that my reported start for the item is something like 49:4:99 and not bang on bar 50. I get it with or without "pdc record compensation". It could be sound card related (lynx l22)

Confirmed (see my first edited post as well) item start at 49.4.99 and not 50.1.00. Very strange indeed. Reaper related, not soundcard. *edit* image:

Thanks siko. :) Any more want to confirm before i post it as a voting bug report?

Nah. 3 of you is enough :) Post it up!

Done it :) vote here

The offset might only be that much but the indicator can only tell you it is not at say bar 50 exactly so you might be right that's sub sample as my other errors were too although I'm sure the noes get moved more then this when quantised and then moved as an item. The tempo thing making a difference is what's worrying though, seems to be related to the other rounding issues I found. Maybe it's not that bad but it's just a bit unsettling when looking to see if your notes quantize bang on and they are off. I find midi doing all kind of weird things regarding the start of the bar and the start offset. Wish you could expand the item start and end without causing issues related to the start offset (or am I doing something wrong?) this might not make much sense now as I'm falling asleep right now but thanks for answering anyway! lol

musicbynumbers I made your test with v3.15 I can see the pre-bar offset. It is very small, under 1 sample. It doesn't matter whether the track has FXs or not. I found this topic while looking for posts about midi timing issues. I've got one too maybe it relates to the same bug: In my case playback/record is getting midi data too early on tracks with FXs enabled. It goes unnoticed during playback but in loop mode it is annoying because events outside time selection are processed. I have MIDI notes with length=0 coming from near-but-out-of-time-selection items triggering drum samples (VSTi) when working on a loop section. In my case the offset goes way beyond -1 sample: it is directly related to buffer size settings. Maybe Reaper's rounding and/or latency compensation algorithms transform this -1 sample offset into a -buffersize one?