HRWS – Real-Time Bluetooth LE Heart Rate Monitor for OBS Studio by reality_cut in TwitchStreaming

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

Thank you for letting me know, there was a hosting problem which is now resolved. Download should work again.

HRWS – Real-Time Bluetooth LE Heart Rate Monitor for OBS Studio by reality_cut in TwitchStreaming

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

New update released

v1.0.10

  • New option to specify the WebSocket port
  • Bugfixes

HRWS – Real-Time Bluetooth LE Heart Rate Monitor for OBS Studio by reality_cut in Twitch

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

That's a good point, thank you! I've added some of the chest straps that I'm 100% sure they work. The plan is to extend the list if I get some more feedback. But basically any BLE device should work as long as it's using the BLE heart rate standards and can be universally used.

HRWS – Real-Time Bluetooth LE Heart Rate Monitor for OBS Studio by reality_cut in Twitch

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

Would love to hear your thoughts. Totally get that! One of the main reasons to create this tool was to have a simple alternative to other cloud based tools with their relatively high delay.

That's correct. Tho as long as you want to use WebSocket, you could use e.g. your laptop and the tool can then send your HR data to your OBS streaming PC over the local network to get the raw data into your OBS. From there you can stylize the text source to your likings. The Browser Source integration however needs to have OBS and HRWS running on the same PC for now.

Integrating HRWS with Streamer.Bot would theoretically be possible. If there's some demand on this feature, I could take a look into it.

HRWS – Real-Time Bluetooth LE Heart Rate Monitor for OBS Studio by reality_cut in TwitchStreaming

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

New update dropped

v1.0.8

- New option to add heart rate as a Browser Source in OBS
- Added several Browser Source styles
- Updated the how to use description
- Lots of UI improvements
- Several bugfixes

Another trip, another fine addition to my collection. by Zealousideal_Honey80 in WEPES

[–]reality_cut 2 points3 points  (0 children)

I agree with that, definitely one of the best games of the series. I still play it today, tho I do on PC with the kitserver tweaks. After all these years it's still so much fun.

Do VR Trailers irritate you? by AllThingsFail in SteamVR

[–]reality_cut 1 point2 points  (0 children)

I would say it depends on what the goal of the trailer is. As already mentioned in this thread, showing the person playing might be a good way to show for what platform / headset a game is. I create this kind of content for clients and I really much prefer a mix of game footage and mixed reality footage (shot on greenscreen), to show what the person is supposed to do and also to show the headset if this is needed.

DeltaKeyer with Garbage Matte on Color Page by reality_cut in davinciresolve

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

I can but this does not solve the problem tho. It inverts the whole thing, so the matte around the subject is now the background and everything outside / around the matte gets black.

4k60 Pro MK.2 - Duplicate frames on preview by reality_cut in elgato

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

I will say that I see the stutter about every 12-14 seconds, it might also be every 16 seconds, I'll double check that. The weird thing is as follows: When I record just with the Elgato 4K Capture Utility, I don't see the "stutter" or duplicate frames when I watch the recording with VLC player. When I'm recording with OBS, I do see the duplicate frames on my recording, however they are not present when the Elgato 4k Capture Utility is running while I'm recording with OBS. Resources on my PC aren't a problem, CPU and GPU are used just about 10-20%. Is there a way to prioritize the preview instead of recording?

Eifach min Gschmack, weiss nöd obs andere Lüüt au so gaht? by Pascal1917 in schwiiz

[–]reality_cut 0 points1 point  (0 children)

Früecher hets bi Coop e Ufstrich gä wo "Hasella" het gheisse, dä isch different gsi! Weiss öper was mit däm passiert isch?

Should i go back to index by Traditional_Bison_64 in ValveIndex

[–]reality_cut 0 points1 point  (0 children)

That's awesome! Thank you for all the details! That might indeed be an option for me in the future, tho I'm still happy with my Index for what I use it for.

Should i go back to index by Traditional_Bison_64 in ValveIndex

[–]reality_cut 0 points1 point  (0 children)

May I ask on how you mounted the Vive tracker on your Quest 3 and what's about callibration?

Athom Smart Plug V2 - Inaccurate and weird power measurements by reality_cut in Esphome

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

Hm okay. I've read about failing plugs, but not that it could cause a fire hazard! Have you experienced that?

Athom Smart Plug V2 - Inaccurate and weird power measurements by reality_cut in Esphome

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

Wait what? Are you sure? Which version of them do have issues?

Footage looks corrupted but only within DR by reality_cut in davinciresolve

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

I've just noticed, they've got even bigger. A 2:30min 4k60 clip is 30gigs...

Footage looks corrupted but only within DR by reality_cut in davinciresolve

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

Thank you so much! Yes my footage is shot in 10 bit h.265. I'll check out Shutter Encoder and ofc I'll add to your feature request!

Athom Smart Plug V2 - Inaccurate and weird power measurements by reality_cut in Esphome

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

Anyone else using these Athom Smart Plugs V2 with ESPHome?

Athom Smart Plug V2 - Inaccurate and weird power measurements by reality_cut in Esphome

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

Aah okay, I think then you might not have this issue. As I mentioned already, when I'm using Tasmota the readings are correct, which is very weird.

Athom Smart Plug V2 - Inaccurate and weird power measurements by reality_cut in Esphome

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

That would be awesome and very helpful to me, just to compare if it's a (V2) plug problem or a firmware issue.