ruffsl @ ruffsl @programming.dev

I'm a robotics researcher. My interests include cybersecurity, repeatable &

---

Read more

Posts

77

Comments

97

Joined

2 yr. ago

You could get a fiber optic display/HDMI cable, a fiber optic USB cable, and the USB hub, then just move the desktop tower into another room and run the cables through the walls or ceilings to your display setup. Might only be $100 or so cheaper than then a used business thin client, but at least you could still do something 4K 120Hz HDR 12bit over some distance without compromise. E.g:

• https://www.youtube.com/watch?v=lsuE0YjfTNI
• https://www.youtube.com/watch?v=BMn6PvhL_Ms

Looks like Moonlight does have their app up on the Apple store or iOS, and Sunlight has binaries for most operating systems. Personally, instead of Sunlight's server, I still use Nvidia's GeForce Experience software to stream games, as it takes less effort to configure. Of course, Nvidia may not be applicable if you're using integrated or AMD graphics instead.

Although, with Nvidia recently deprecating support for it's shield device, Sunlight provides support for the same protocol that Moonlight was originally developed against, but it's also open source. I've not used multi monitor streaming with GeForce Experience, something Sunlight would be much more flexible in configuring.

As for connectivity, I'm unsure if iOS supports the same USB network feature that Android has. I'd imagine at least the iPhone would, as that's a core feature/option for mobile hotspot connectivity, but maybe that's nixed from iPad iOS? Alternatively you could get yourself a USB C hub or dock with an ethernet adapter and pass through power delivery, so you can connect your iPad with a wired network and charge simultaneously.

Or you could just use Wi-Fi, but with wireless networks dropping and retrying packets, that'll impact latency or bitrate quality when casting displays. Although for something mostly static like discord windows, that's probably less of an issue. Windows 11, and maybe 10, also have a hotspot mode, where you could share your wired network via your PCs wireless radio via and ad hoc Wi-Fi SSID. That could reduce latency and improve signal reception, but you'd have to start the hotspot setting every session or whenever the device disconnects from windows' hotspot for more than 15 minutes or something.

You could try other remote display streaming software as well, like Parsec. However they have a online account login requirement with the freemium model, so I prefer the open source client Moonlight instead. However parsecs a lot easier too use when streaming from outside your home, or when remotely single screen co-oping with friends, without having to configure firewalls or domain names.

If you already have a similarly sized tablet, you could just buy a dummy HDMI plug, a few dollars, to add a second virtual desktop and then simply cast that screen to the mobile device.

There are pretty nice Android tablets now with 2.5k 120 hz HDR OLD screens. You can just connect it directly to the computer via USB, enable USB network tethering, then use something like the Moonlight client app with Sunshine screen casting server. With the wired connection, and a high bit rate such as 150 Mbps, you can get single digit millisecond latency and hardly tell the difference from an native HDMI display.

Tablets like those might be on the high end, but at least you'd have nice secondary display that's a bit more multifunctional. Or just go with a cheaper LCD based tablet or old iPad, if color accuracy, refresh rate, or resolution isn't a priority.

A while back, I tried looking into what it would take to modify Android to disable Bluetooth microphones for wireless headsets, allowing for call audio to be streamed via regular AAC or aptX, and for the call microphone to be captured from the phones internal mic. This would prevent the bit rate for call audio in microphone being effectively halved when using the ancient HFP/HSP Bluetooth codecs, instead allowing for the same call quality as when using a wired headset. This would help when multitasking with different audio sources, such as listening to music while hanging out on discord, without the music being distorted from the lower bit rate of HFP/HSP. This would also benefit regular VoLTE, as the regular call audio quality already exceeds that of legacy Bluetooth headset profiles.

Although, I didn't manage to tease apart the mechanics of the audio policy configuration files used by the source Android project, given the sparse documentation and vague commit history.

• https://source.android.com/docs/core/audio/implement-policy
• https://android.googlesource.com/platform/frameworks/av/+/dc46286/services/audiopolicy/config/audio_policy_configuration.xml#147

I'd certainly be fine with the awkwardness of holding up and speaking to my phone as if it was in speaker mode, but listening to the call over wireless headphones, in order to improve or double the audio quality. Always wondered what these audio policies fall back to when a Bluetooth device doesn't have a headset profile, but it's almost impossible to find high quality consumer grade Bluetooth headphones without a microphone nowadays.

For the call setting under Bluetooth audio devices, I really wish they would break out or separate the settings for using the audio device as a source or sink for call audio. Sort of like how you can disable HSP/HSF Bluetooth profiles for audio devices in Linux or Windows.

Thanks, fixed!

Has Bryan done any more recent recorded talks?

The only experience I have with working with Fortran would be setting up gfortran when building SciPy from source, and perusing its codebase to see how it's FFT functions were so optimized. Not enough to diligently mod I'm afraid.

I was thinking of cross posting this to a Fortran community, but it looks like we don't yet have one.

Similarly reported (in more detail) by TechCrunch:

• https://techcrunch.com/2023/11/21/flipboard-stops-tweeting-launches-new-podcast-about-decentralized-social-apps/

I'm not sure why, but GitHub's search engine, Blackbird, seems to be returning some erroneous results for this query:

• /tnt_select\(.*2\^32/ language:C++ OR language:C
  • https://github.com/search?q=%2Ftnt_select%5C%28.*2%5C%5E32%2F+language%3AC%2B%2B+OR+language%3AC+&type=code&ref=advsearch

Any chance you could narrow down your search to a list of repose that use the library that pulls in tnt_select() function, then clone and manually grep just those, or is it's use too common to index by?

Real funny that even narrowing down GitHub search to just the same repo doesn't help the query results:

• repo:ocelot-inc/ocelotgui ldbms_tnt_select
  • https://github.com/search?q=repo%3Aocelot-inc%2Focelotgui%20ldbms_tnt_select&type=code

Pain... This too painful to be posted as just a meme...

Perhaps, is there an engineering meme community I could cross post this to?

Private Eye - essential for staying online 24/7

What was that device, an early cellular modem or 802.11 wireless bridge? The thing ontop of the briefcase looks like a head visor with an antenna. Google search keywords are just noise.

I'll note that when using multiple windows, I recall that switching the user in one window would switch the user for all other windows as well, so support for simultaneous user sessions would probably have to be added as well.

Do we have a community for computer architectures or computer science on this instance or anywhere else?

Related: https://programming.dev/post/1851005

I don't know of many recorded audio books, but you could also use a Text to Speech engine to listen to any technical blogs or articles. I use Android apps like Pocket or T2S to queue up a backlog of TODO read items, then when I'm out for a long walk, I can just press play and let the TTS do it's thing. Of course, I curate this list for longer pure text reads, devoid of code snippets, equations, or visual graphics that TTS would have a tough time conveying over audio.

Looks like I may need to find a successor to pocket. They do a great job scraping connect via readable mode, but I'd like to find a shelf hosted or mobile+offline app equivalent for queuing up web articles, just in case pocket gets cut from further development by Mozilla management.

Scrum 's a thing that can't get no love from me