Hi, I’m playing around with the Live typing option and am curious if anyone else has experienced this problem or if they might know what I did wrong.
I typed out a sentence and saved the .txt to recurboy using the F1 key. This replaced the “Live” option in the menu, and I am no longer able to type. I can switch between/manipulate the example text file and the one that I created, but am unable to create new.txt files as far as I can tell. I’m sure it will fix with a reflash, but it is my intention to use this feature live, so I’d like to figure out the best way to fix.
Thank youuuu,
nodnodnod
interesting - it could well be a bug. i will be able to fix if i can reproduce it. will try testing this tomorrow. any tips on how to reproduce ? or if you share a video i may learn more - thanks
These were the steps I took:
- Typed sentence
- adjusted fonts/position to my liking
- Pressed F1. This saved it in the text list and removed “Live”
A couple of extra things I found after my first post:
The keyboard began manipulating the size and position of my text after this. the number keys would change the position on screen, and I think F would remove or place the same text.
Also, fiddling with the keyboard in this state long enough led to a crash of some sort
i tried to reproduce but the LIVE
option for me remains at the top of the TEXT
list regardless if i have saved a new text file or not…
is it possible that you have scrolled down the list so the top item is not visible on the screen at this position ? or entered a folder in the text menu which would need to move up out of before can see the LIVE option?
this is expected behavior (although perhaps not well documented) - when not in live mode the keyboard acts as an input source… similar to external midi controller… you can see the list of commands (and edit/remove them if prefered) in the actionMap.json:
["q", "exit"],
["w", "moveUp" ],
["s", "moveDown" ],
["a", "moveLeft" ],
["d", "moveRight" ],
["p", "enter" ],
["f", "fxSwitch" ],
["r", "playSwitch"],
["c", "switchInput" ],
["1", "stepShaderParam0"],
["2", "stepShaderParam1"],
["3", "stepShaderParam2"]
I definitely checked to make sure it wasn’t a scrolling issue. I will reflash and try again some time tonight and see what happens.
The only thing I can think of that may have caused a problem was swapping from USB Drive to USB Keyboard without changing the media that was playing from the USB.
I found that if you eject the USB drive with one of the files still playing, the pi will continue to play the video, so I may have just overwhelmed the Pi a little.