Reaper informs wrong sample position

[ArdeII]

Hi,

I'm still learning the VST programming and my arpeggiator is now working pretty well, but I found this odd behaviour which may be a bug in reaper.

To reproduce the bug:
1. Load the bug.RPP project. There are too MIDI loops: working one and NOT working one. Notice that both start at sample position 493714.
2. Start playing project at 1728000 and place your breakpoints to ProcessMidiMsg. When loop ends and then immediately starts program is stopped at break point. Place new break point to ProcessDoubleReplacing to investigate the sample position at beginning of the loop. It is 493715 with Not working MIDI loop! Thats not right!

Is this a Reaper bug or am I doing somwthig wrong?

- Arto

[ArdeII]

Can someone confirm if this is Reaper problem or not.


- Arto

[cerberus]

i do not have any code with a ProcessMidiMsg thread, where i could set breakpoints... do i?
(and this would be assuming i could get a debug build to work with xcode, which
thus far... um.. not yet. )

[ArdeII]

The wdl package includes IPlug Example project. You can add this implementation to receive MIDI messages
PlugExample::ProcessMidiMsg(IMidiMsg* pMsg){
switch (pMsg->StatusMsg())
{
case IMidiMsg::kNoteOn:
break;
case IMidiMsg::kNoteOff:
break;
}
} where all midi messages will come.

I assume XCode projects work perfectly out of the box.

- Arto

[cerberus]

I assume XCode projects work perfectly out of the box.
hah! no, not exactly... it took me many hours and i don't remember how i got it working.
by contrast, i don't know the first thing about windows, but i built my own plug-in with
visual studio within minutes of installing it on my "virtual pc" (runs inside osx).

if nobody else wants to deal with this issue, i'll see about getting the debug versions built...
thus far i am debugging using only cout statements and (at times when cout does not
work in osx)* printf.

*cout makes "DWARF errors" when directed to output integer variable values. debugging
in osx would seem to be less straightforward than in windows... weird!

btw, would one need to build debug/trace versions of iplug too? (afaik iplug doesn't
need debugging while i am debugging my .cpp... we don't need to build lice in osx)

=======================

as for rounding errors in reaper on playback/rendering... yes, these are known to happen.
i've confirmed a couple on the issue tracker that beatbybit has reported. check his recent
post history, perhaps with key word: "rounding" or similar, if you wish to research details.

i hear that reaper4 will be available for testing soon. fixes for playback/render rounding issues,
such as you have possibly identified here, are my number one wish at this time for reaper 4.
let's hope!

[ArdeII]

btw, would one need to build debug/trace versions of iplug too? (afaik iplug doesn't
need debugging while i am debugging my .cpp... we don't need to build lice in osx)

You don't have to use iplug debug version to debug your plugin.

I hope this issue is fixed in v4.

- Arto