tinpanalley

THey weren't $80 when they came out. They were like $40. They're extraordinarily well built. Better even than some actual desktop keyboards.

I have this amazing little mobile keyboard which I bought when I lived in France so it's physically an AZERTY keyboard. But it's been a long time since we lived there and that ability my brain had to go back and forth between AZERTY and QWERTY is no longer as flexed as it once was. I'd like to make it permanently a QWERTY keyboard but there are physical differences. Can anyone think of any way to turn it into a QWERTY keyboard despite some of its buttons not all lining up perfectly? Just keymapping isn't enough.

I put on a new cable that happened to be 2.0 (...it's just that it's 25ft long and quite thick, we used to need it in a different apartment) and there's no flickering whatsoever now. Thank you for your help. Tiny ms bit of delay on the mouse but nothing major. But I'm now curious... The cable in question that wasnt working was a High Speed, so that's 1.4. The new TV takes HDMI spec 2.0. The GPU port on the PC says it supports 4K@60Hz as specified in HDMI 2.0b. So is it correct to assume I didn't have problems with the last TV because its ports were HDMI 1.4 like the cable?

How do I know if I'm using the right HDMI cable? It's been a while since I have changed any of them and it wasn't really an issue the last time I hooked things up to a TV. Do I check the version of the ports on the TV and then buy a cable that matches? Does it matter what the ports are on my GPU?

I've always had an HDMI cable running to my TV from my desktop for gaming and for some PC work. But we just got a new TV and switching to the TV from the PC (via an HDMI splitter) is causing the image from the PC to flicker. What causes this typically and what settings can I check on the TV and PC to stop it from happening? Thanks for any help!

Firstly... I need to thank you for your thorough explanation and castle analogy. That really helped me get my head around how this whole system works. In truth, I need to really spend time understanding Windows networking more. I would love to have more control over my use of my home network, my internet settings, and more and I am so good with understanding other computer elements but I'm severely lacking in networking comprehension. When internet, home network, related issues come up I'm always at a loss. I'd love to understand DNS more, how to really utilise every part of my home network, the connection settings of my Rpi Kodi install, etc and other examples so that I know exactly what home networking can do. Nevertheless, despite still wishing I could understand all the different settings in the router options, your analogy and your help went a long way towards giving me a relatable way to approach all this. So thank you for that. Understanding things better after your post, I went through the few elements that were controlling my ability to connect. Namely: the router options via the tplink app, the BubbleUPnP setup which is pretty automated and self explanatory, and the Windows Firewall settings. And you wouldn't believe what finally worked. In the Server Properties for the Inbound rule created for BubbleUPnP, you can choose which profile to apply the rule to. The only option selected was Private. I also checked Default and Public, and instantly the BubbleUPnP server page connectivity test worked. I'm not sure I get entirely why but what I gather is that only the Private profile was permitting access and that isn't the profile Bubble uses. Is that it or is it more complicated than that?

I don't know that because I hadn't looked at the firewall rule before to know exactly what it was doing. Port scanner says 58050 is closed. I don't understand at all why this has worked for years and now it's completely not doable. I also dont get what I'm physically doing. I'm opening up ports on my Internal IP? Then what is the Public IP for? How do I open those ports? What other program can I use to get the same access to my home desktop for music?

Irrelevant. Ignore it.

Yes, same machine. Win 10. Should be said, before this modem/router from my ISP I was on one of their "legacy" technicolor modems, but using the same tplink Deco mesh router. And when I would install the softwarefor BubbleUPnP, everything worked fine. Never needed to do a thing other than point the app at the program on my desktop.

My bad, i misspoke. And yes, the WAN from the router is the same as whatismyip.

Spoke to them today. They said, if we're putting the modem/router in Bridge mode they aren't doing anything to it at all other than handing off all control to our router. They said they dont block ports, but naturally they also can't offer help configuring our router.

Yes. whatismyip is the same as what Bubble calls my "Public IP address"

Where do I get confirmation of that public ip address. Where can I find it to see if Bubble has it right?

For internal I was using my 192.168... Ports, the 58050 port, I was going to do asecond rule for 58051. But Bubble still says,