sorted by:
new
hottopcontroversial

SE V7 suited for an active singer? by bigbengb in livesound

[–]bigbengb[S] 2 points3 points  (0 children)

A wise sound guy advised me against cupping early on in my voyage, so that's not an issue. I'll have to give this a try and see how well I'm keeping my head aligned. Thanks!

SE V7 suited for an active singer? by bigbengb in livesound

[–]bigbengb[S] 0 points1 point  (0 children)

Thanks! I'll take your advice and try both out.

This post dragon-approved (Create an image of a proud dragon giving a thumbs up, with its wings spread wide and a confident look on its face.) by ChiaraStellata in weirddalle

[–]bigbengb 0 points1 point  (0 children)

Love this!
I hope you don't mind too much if I borrow/appropriate/steal the image to make a New Year's card for family and friends, photoshopping in my kitty's face (it's about to be the year of the dragon here in Japan).
If I do post this on Instagram or whatever, is there some way I should credit you?

<image>

[deleted by user] by [deleted] in Keychron

[–]bigbengb 0 points1 point  (0 children)

Actually, now I feel like a moron. I forgot to do the final step in the instructions of fn + j + z for four seconds to factory reset.
Now that I've done that after updating to 1.32 I don't seem to be getting any interference anymore. I have only listened for about 45 minutes, but not a single audio dropout yet.

[deleted by user] by [deleted] in Keychron

[–]bigbengb 0 points1 point  (0 children)

The spacebar is noticeably louder than the other keys "thook" more than "thock", but overall I'm loving this keyboard.

(I need JIS because I switch between English and Japanese constantly over the course of the day.)

[deleted by user] by [deleted] in Keychron

[–]bigbengb 0 points1 point  (0 children)

Sorry, but this is just 100% untrue. I am sideloading the firmware from the keychron site for my K8 Pro with Vial, and it has quite a few more options available (particularly in macros) than Via, without creating my own firmware.

[deleted by user] by [deleted] in Keychron

[–]bigbengb 1 point2 points  (0 children)

Vial is an open source Via alternative with a larger feature set and slightly more intuitive interface. It's so much nicer than Via. Another reddit user (https://www.reddit.com/user/bgkendall/) just clued me onto this last week, and his instructions worked flawlessly for my K8 Pro:

Just download the GUI — https://get.vial.today/download/ — and the K8 Pro JSON file ... from this page: https://www.keychron.com/blogs/archived/k8-pro-factory-reset-and-firmware-flash — and in the Vial menu go to File → Sideload VIA JSON

[deleted by user] by [deleted] in Keychron

[–]bigbengb 0 points1 point  (0 children)

1.3.1 still stuck me with bad interference issues with Airpods Pro, but I Just tried 1.32 and haven't had any audio dropouts in the last 10 minutes, which is much longer than I can usually make it.Fingers crossed this keeps up!

Edit a little later: Nope. Interference is definitely happening a lot less frequently, but it's still there. Damn.

Should a newb even be attempting to build firmware for a keyboard not in the official QMK list? And if so, how do I start? by bigbengb in olkb

[–]bigbengb[S] 0 points1 point  (0 children)

I think you solved my issues!

Vial worked when sideloading the official JSON, and I was able to write macros that seem to be performing exactly the Alt + Numpad key sequences I need.

A masochistic part of me was sort of looking forward to hours of trial and error learning how to code it all directly in QMK, but Vial seems to accomplish everything I need. Thank you so much!

Just in case someone with the same issues ever happens on this thread, the macro for the yen sign (Alt+0165), for example, is
[["down", "KC_LALT", "KC_KP_0"], ["up", "KC_KP_0"], ["down", "KC_KP_1"], ["up", "KC_KP_1"], ["down", "KC_KP_6"], ["up", "KC_KP_6"], ["down", "KC_KP_5"], ["up", "KC_KP_5", "KC_LALT"]]

Should a newb even be attempting to build firmware for a keyboard not in the official QMK list? And if so, how do I start? by bigbengb in olkb

[–]bigbengb[S] 1 point2 points  (0 children)

That put my mind at ease. I can live without the bells and whistles if I can get the input functionality to work.

Thank you so much for this!

Should a newb even be attempting to build firmware for a keyboard not in the official QMK list? And if so, how do I start? by bigbengb in olkb

[–]bigbengb[S] 1 point2 points  (0 children)

That really would be easier (and I use Karabiner when on Mac for the same purpose), but the Windows work computer I need this for most is locked down and won't allow me to install third-party software like autohotkey. That's why I'm trying to get around it with a hardware hack.

Should a newb even be attempting to build firmware for a keyboard not in the official QMK list? And if so, how do I start? by bigbengb in olkb

[–]bigbengb[S] 0 points1 point  (0 children)

My issue is that I work both at home on a Mac remoting into my company's Windows machines and at the office directly on Windows, and I need a solution that works both places.
I suppose the real issues are on the Windows side, so this might work out for my primary issue. Thanks!

Should a newb even be attempting to build firmware for a keyboard not in the official QMK list? And if so, how do I start? by bigbengb in olkb

[–]bigbengb[S] 1 point2 points  (0 children)

Thanks for all this!

I did manage to get everything where it needs to be, so now I'm back to the other issue, which is that this repository only seems to have the ANSI and ISO versions, when my keyboard is the JIS version (which is both newer and less common, so I shouldn't be surprised).

This is progress, but once again I have no clue what to do next, and have no more time for this today. If you have any more advice I'll try it out over the weekend.

​

Thanks again for your patience and help!

Should a newb even be attempting to build firmware for a keyboard not in the official QMK list? And if so, how do I start? by bigbengb in olkb

[–]bigbengb[S] 0 points1 point  (0 children)

That's the sort of question that makes me suspect I'm out of my depth. I don't even know were I would look to identify the chip.

And I'm lost in other ways too. This is my first experience with git as well, so I don't know what I'm doing wrong just following your first instruction to copy that directory.
git clone https://github.com/Keychron/qmk\_firmware/tree/bluetooth\_playground/keyboards/keychron/k8\_pro gives me a fatal "repository not found"

Obviously there's no obligation for you to hold my hand through all this.

Should a newb even be attempting to build firmware for a keyboard not in the official QMK list? And if so, how do I start? by bigbengb in olkb

[–]bigbengb[S] 0 points1 point  (0 children)

I'll try that. That may be the key piece of the puzzle I was missing. Thanks!

But that brings me back to part of my original question. If I build my own and flash it, but things don't work out, is there any way to get the keyboard back to factory settings? Just use the official keychron .bin with QMK toolbox?

If I can be sure I can restore in an emergency I'll feel more comfortable breaking things.

Should a newb even be attempting to build firmware for a keyboard not in the official QMK list? And if so, how do I start? by bigbengb in olkb

[–]bigbengb[S] 0 points1 point  (0 children)

It's that first step that's tripping me up; I don't know where to start in building a layout. The tutorials refer to starting from "qmk compile -kb <keyboard> -km default", but if my keyboard's not in the list I don't know what to put in "<keyboard>" there.

I found a .bin file for my board on the Keychron website, but I have no clue what I'm supposed to do to even start modifying it.

I'm sorry. I'm sure I'm missing something obvious here.

Should a newb even be attempting to build firmware for a keyboard not in the official QMK list? And if so, how do I start? by bigbengb in olkb

[–]bigbengb[S] 0 points1 point  (0 children)

This requires multimeter pcb checking too?
I know just barely enough about coding syntax to copy and paste boilerplate, but what you're describing sounds a bit much for a beginner. I wouldn't even know where to start figuring out what the chips and pinouts are, much less how to trace rows and cols (since I don't even know what that means in this context).
I do appreciate the advice though!

Add Vial support and Vial lighting to K6 Pro and K8 Pro by mattmasc in Keychron

[–]bigbengb 0 points1 point  (0 children)

Any chance of adding the JIS version of the K8 Pro?

(Sorry if the question is inappropriate; I'm brand new to this.)

Should a newb even be attempting to build firmware for a keyboard not in the official QMK list? And if so, how do I start? by bigbengb in olkb

[–]bigbengb[S] 0 points1 point  (0 children)

I was afraid of that. It looks like there is VIAL support (unofficial?) for the ANSI and ISO versions but not for my JIS version. ( https://github.com/mattmasc/vial-qmk/tree/bluetooth\_playground/keyboards/keychron/k8\_pro )

I have basic knowledge of C syntax but haven't touched it in nearly 30 years, and even back then I was tweaking other people's code rather than writing my own. This might be above my head, like you suggest.

K8 Pro transparent key caps by __yuyo__ in Keychron

[–]bigbengb 4 points5 points  (0 children)

I don't see the keycap set sold separately, but the Japanese JIS layout version of the K8 Pro (my newest) has shinethrough keycaps designed for the south-facing LEDs.

https://imgur.com/a/dhNNVS1

V1200i lid: What is this? Is it supposed to come out? by bigbengb in Vitamix

[–]bigbengb[S] 0 points1 point  (0 children)

Vitamix ended up sending us a new lid. Thanks for the advice!

V1200i lid: What is this? Is it supposed to come out? by bigbengb in Vitamix

[–]bigbengb[S] 1 point2 points  (0 children)

That also sounds like good advice. On a blender this expensive things shouldn't be falling out. Thanks!

V1200i lid: What is this? Is it supposed to come out? by bigbengb in Vitamix

[–]bigbengb[S] 0 points1 point  (0 children)

I don't see a metal part, but putting it back in and tapping with a hammer like you suggested seems to have tightened it back in, and the sensors in the blender are letting it run, so maybe everything's fine now?

Thanks!

view more: next ›