[Rwp] Focusing problems with reaper and Osara

[James Teh]

It'd be great if you can file a GitHub issue with a list of exact steps to reproduce this in the simplest way possible, including what actions to take, what settings to set when, etc. For now, just one case is enough; I'll ask for more if needed. I'm having trouble following exactly what to do here.

Also, it's worth checking that the stretch marker is really there. Sometimes, the stretch marker navigation commands seem to move to spots that previously had stretch markers, even though they don't now. You can confirm this by pressing delete to see if you get "stretch marker deleted". If you don't, there isn't a stretch marker there after all.

Sent from a mobile device

> On 29 Nov 2015, at 9:06 AM, Tor Tollhag <tortollhag at gmail.com> wrote:
> 
> Confirming again that the stretch marker problem happens when you set
> Project timebase to beats position length rate and change the Project
> bpm.
> If you have timebase set to time and add stretch markers things work fine.
> As soon as the Project tempo changes along with the rate of the item
> the stretch markers can no longer be focused. Reaper goes to the
> positions where they are but they're not announced, and we can not
> move them if that happens.
> This also includes keeping the Project tempo the same but adding a new
> tempo marker at the start of an item or in the beginning in the
> Project.
> This also happens when I don't change the timebase or tempo in the
> Project but do it on the item.
> Again like James wrote not sure if this can be fixed now but hoping to
> figure out some kind of workaround in the meantime.
> 
> 
> 
> 2015-11-28 13:23 GMT+01:00, James Teh <jamie at nvaccess.org>:
>>> On 28/11/2015 7:40 AM, Tor Tollhag wrote:
>>> I recorded on it but the guy playing messed up so I had to go and
>>> remove that item and start over.
>>> The problem was even though I was on the right track, suddenly when I
>>> pressed Control Arrow keys reaper couldn't focus on the item, it's
>>> like if it weren't there.
>> I checked the code and just now fixed a bug which I believe might have
>> caused this. Basically, if you delete the current item, moving to other
>> items on that track sometimes failed. If I'm right, moving to an item on
>> another track first would have fixed this.
>> 
>> Jamie
>> 
>> --
>> James Teh
>> Executive Director, NV Access Limited
>> Ph +61 7 3149 3306
>> www.nvaccess.org
>> Facebook: http://www.facebook.com/NVAccess
>> Twitter: @NVAccess
>> SIP: jamie at nvaccess.org
>> 
>> _______________________________________________
>> RWP mailing list
>> RWP at bluegrasspals.com
>> http://bluegrasspals.com/mailman/listinfo/rwp
> _______________________________________________
> RWP mailing list
> RWP at bluegrasspals.com
> http://bluegrasspals.com/mailman/listinfo/rwp