jcsteh / osara

OSARA: Open Source Accessibility for the REAPER Application
GNU General Public License v2.0
127 stars 46 forks source link

Media Explore No Longer Usable #199

Closed ironcross32 closed 5 years ago

ironcross32 commented 5 years ago

In the media explore, enter now tries to press record, rather than navigating folders or inserting an audio file onto a track. This is as of the latest version on the appveyor page.

jcsteh commented 5 years ago

I don't know of any changes in OSARA recently that should have affected Media Explorer. Can you verify with an older version of REAPER? Trying to determine whether this was a change in REAPER, in which case it needs to be reported to Cockos.

ironcross32 commented 5 years ago

@jcsteh After these tests, it seems like it is Osara. I installed a portable version of one version older of Reaper that I currently use (specifically 5.96). I then installed the current version of Osara into it (osara_2019.1pre-123,b22e8acd). The issue carried across. I then removed that version of Osara and installed the previous version into the portable reaper wherein the issue vanished, and the media explorer worked as per normal.

jcsteh commented 5 years ago

Thanks. When you say you tested a previous build, what was the build number? Was it 2019.1pre-122,f05abab0? if not, could you please test this build and report your findings?

ironcross32 commented 5 years ago

The build: 2019.1pre-122,f05abab0, does not have the issue, and the media explorer works normally. That is indeed the one I tested with after confirming that an older Reaper didn't fix the problem. The build: 2019.1pre-123,b22e8acd, is the build which is currently installed in my main Reaper, and was directly upgraded to from 2019.1pre-122,f05abab0; which was the previous version I had been using.

jcsteh commented 5 years ago

Okay. Thanks.

@leonardder, looks like this might be caused by #194. Would you mind taking a look?

LeonarddeR commented 5 years ago

I'm certainly going to give this a try.

@ironcross32: Just to make sure, could you provide exact steps to reproduce this issue?