[Rwp] Focusing problems with reaper and Osara

[James Teh]

OSARA just asks REAPER to find stretch markers at the cursor position, 
so more likely, it breaks the REAPER API in some way. I do have this 
feeling REAPER is keeping track of stretch marker times and not updating 
them correctly. I can't be 100% sure there isn't a bug in OSARA, but I 
have a nasty suspicion this is a REAPER bug, in which case whether or 
not it gets fixed is anyone's guess. :)

Jamie

On 28/11/2015 8:51 PM, Tor Tollhag wrote:
> Hi there. Well I just figured something out.
> It seems to lose focus on stretch markers if I put the Project
> timebase to beats position length rate, and change the Project bpm
> Before I do anything else.
> The default settings is to have the timebase at time since I sometimes
> try to do dj mixes in reaper, so I load an audio file in, get the bpm
> right and then I switch the timebase so I can then change the Project
> bpm.
> I'll experiment some more with this but I wonder if the fact that the
> bpm with the length and rate of an item Changes effects Osara in some
> way so it can't see stretch markers correctly?
>
>
> 2015-11-28 2:23 GMT+01:00, James Teh <jamie at nvaccess.org>:
>> I've seen cases where REAPER doesn't seem to fetch stretch markers
>> correctly. I haven't seen item issues though.
>>
>> Regarding the item issue, note that the item navigation commands will only
>> move in the correct direction; they never wrap. So, if there's only one item
>> on the track and it starts before the cursor, going next won't move there.
>> This is probably obvious, but I mention it because ReaAccess confusingly did
>> wrap back on itself in certain cases.
>>
>> In order to have any chance of diagnosing this, I need to be able to
>> reproduce it, which means I need clear steps or a project it is occurring
>> with. I realise that's not easy to achieve in some cases, but that's
>> unfortunately what is needed.
>>
>> Sent from a mobile device
>>
>>> On 28 Nov 2015, at 7:40 AM, Tor Tollhag <tortollhag at gmail.com> wrote:
>>>
>>> Hi.
>>> It's a bit late but today I've started to have some serious problems
>>> with reaper. It could have to do with Osara I'm not sure but here's
>>> the problems.
>>> Early today at work I was messing with stretch and tempo markers and
>>> Everything worked fine.
>>> Then I had a recording session with some people, and here's where the
>>> problems started.
>>> I had 8 tracks in the Project and added a 9th one.
>>> 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.
>>> In the end I had to remove the track, add it again, record again and
>>> this time it worked.
>>> Later on I'm having another problem now using stretch markers.
>>> I add a marker with Control M, I know it's there cause when I move
>>> with the other hotkeys reaper moves to the posisions where the stretch
>>> markers are.
>>> However Osara doesn't announce that there's a stretch marker there
>>> even though I know I added them.
>>> This also means that I can't move the stretch markers, cause even
>>> though it goes to where they are, Osara suddenly Thinks that there's
>>> no markers there.
>>> I've tried this with both Jaws and Nvda, even restarting my laptop,
>>> and still I get this same problem.
>>> Would like to get some help here.
>>>
>>>
>>> Tor
>>> _______________________________________________
>>> 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
>>
> _______________________________________________
> RWP mailing list
> RWP at bluegrasspals.com
> http://bluegrasspals.com/mailman/listinfo/rwp

-- 
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