PDA

View Full Version : bug report keyboard disabled


terrymc
01-31-2008, 04:37 PM
Don't know if this is already known.
When trying to save a file, I couldn't type in a name, but the mouse still worked. when trying keyboard commands in reaper, no response, but again mouse still worked. Had to quit and restart reaper and it was ok, but lost work. Other open programs behaved normally at the same time (ie keyboard still worked).

10.4.11 PPC G4 Dual

Terry

John Forster
02-01-2008, 08:17 AM
When trying to save a file, I couldn't type in a name, but the mouse still worked. when trying keyboard commands in reaper, no response, but again mouse still worked.

I've experienced the same thing, but I did a "Save As" instead of a "Save", and it accepted the input. I assume that it's a bug in that input field, and not a general keyboard issue.

John

livedead13
02-01-2008, 11:35 PM
if the mouse still worked, you could have copied some text and pasted it, and not have lost your work.

DAnttila
02-05-2008, 02:27 AM
Yes this happened to me too. I opened a texteditor, wrote some stuff and then copy & pasted it to save my project so its a solution. I also wasnt able to delete takes in the timeline with backspace or the delete button, had to go via the rightclick menu. But maybe thats a known bug already.

terrymc
02-05-2008, 03:10 AM
Some consolation in knowing it's happened to others -- not so much in knowing you're all that much smarter than me!
tm

ankely
11-17-2011, 11:46 AM
I realize that this is an old thread...

Has there been a solution to this problem, of the mac keyboard not working?

I have had it happen more than once.

It can disable keyboard input system wide, not just in Reaper.

A reboot fixes it.

Any help appreciated.

Thanks.

Ollie
11-17-2011, 12:05 PM
Please note that the OP reported a slightly different issue (the keyboard loss was not systemwide and it still worked outside of REAPER).

Some Macs seem to be known to occasionally lose their keyboard (systemwide) for some reason, the usual workaround (for USB keyboards/wireless kb receivers) is to pull the keyboard and reconnect it after the system recognized that it's missing. http://support.apple.com/kb/TS1996?viewlocale=en_US

What Mac/keyboard/OSX version are you using?

ankely
11-17-2011, 12:18 PM
Thanks Ollie,

That was a fast response !

I'm using a MacBookPro.

I hadn't noticed this problem causing a system wide problem before.

It did happen today though.

Losing keyboard input seems to occur when I'm doing a lot of detailed editing, such as chopping loops into individual hits and moving them around, etc.

I wonder if it can be related to the number of edits in a short period of time as that seems to hang Reaper in general for me.

Another problem I get often is that my Kensington Expert Mouse loses the ability to scroll using this Action:

Opt+Mousewheel --> View: Zoom vertically reversed (MIDI CC relative/mousewheel)

Maybe they are related.

Thanks again.

Ollie
11-17-2011, 12:47 PM
Sorry if I was not clear on this, the systemwide keyboard loss is not a REAPER (or any other application for that matter) related problem at all, it's a general problem of some Macs, whereas the cause and solution may or may not differ between the affected models. That's at least what I found out when googling for the cause of the same issue with my Mac Mini (which loses its keyboard occasionally, even when I didn't run REAPER on it for weeks and just use a browser).

Hence scroll wheel anomalies would be unrelated to that and I can't seem to reproduce your problem with a standard mouse, sorry. Do you have a different mouse to check whether or not that is specific to the driver of the Kensington mouse maybe?

ankely
01-18-2012, 12:38 PM
Ollie,

I may have found the issue.

It appears that Default Folder X has been known to interfere with Peak:

http://stclairsoft.com/blog/2011/11/09/default-folder-x-4-4-7-resolves-issues/

It also states that this can happen with other programs.

I haven't done testing as the problem hasn't shown lately.

I have kept up with Default Folder X updates, so it may have sorted itself out.

Thanks for your help.

Maybe this info will help others.