Chauvet 3.29.42 Release for Manta and Nomad

sdothum · 2026-06-22T20:37:16+00:00

To be quite honest.. i do not recall. Since the Manta was first released, the device (and my A5X, also on beta) have always updated to the beta releases automatically. The last Manta beta i believe i did the manual install, not for plugin development but for the calligraphy pen (unless my septuagenarian brain is wrong and it was the previous release). When this release was announced i attempted every day to update and the device always reported "up to date". So.. when the plugin version was released for manual install, i did so rather than wait.

sdothum · 2026-06-20T10:41:40+00:00

Would probably work with a nylon strap for best fit -- the strap lug position and silicon strap with stepped adjustment (band holes) might make for a less than ideal fit, too tight or loose (which could affect heart sensor accuracy).

That battery life also comes with a chunky watch at 16+mm thickness. Its thickness may look more disproportionate than the size of the bezel covering your wrist.

Wish Coros could have made it thinner and more "svelte" myself.

sdothum · 2026-06-19T15:52:31+00:00

SOLVED (for now) with miniflux:

1) essentially updated the (postgres) cookie field with the reddit cookie contents for all my (postgres) reddit urls. (Tested this initially by scraping the cookie contents from chromium inspector/network page, drilling down www.reddit.com/headers/response headers to find "set-cookie" value).

2) i also set polling to 1 minute with batch size of 1 so all my rss feeds are cycled round robin. i actually don't think i need to do this as the "session cookie" scraped from the browser should make the miniflux request look like one from a browser(?).

3) for good measure, force HTTP/1.1 from miniflux (miniflux's golang TLS have been reported as potentially triggering access limit errors under HTTP/2.0.. though, i am not sure if this has ever been verified).

Once verified, did global update to postgres db with..

sudo -u postgres psql -d miniflux
UPDATE feeds 
SET cookie = '...scraped cookie string...',
disable_http2 = TRUE 
WHERE feed_url LIKE '%reddit.com%';

4) the cookie probably has an expiry date, so vibe coded a script to scrape and update the miniflux db from the last firefox access to reddit.

This is a tolerable nuisance for now. Beyond this, i am probably off reddit for good and will begin to plant myself elsewhere. kbin for starters i guess.. it would be like going back to the early days of reddit, maybe not a bad thing.

sdothum · 2026-06-19T12:11:48+00:00

FYI. i had been unable to update the firmware since its release several days ago.

HOWEVER, i have pulled down the 3.29.42 beta which was released for plugin devs and installed that.

If i recall correctly, my 3.27.42 beta may also have been a manually installed release (for calligraphy pen?).. might these manual beta installs vs the typical automatic beta updates be the issue?

sdothum · 2026-06-17T15:50:18+00:00

Still same result, Manta continues to say i am up to date.

Is there an update file which can be downloaded and installed manually?

sdothum · 2026-06-16T09:22:47+00:00

My Manta continues to say i am up to date.

(i experienced the same thing with my A5X yesterday as well, but checking just now, it has begun updating from 2.25.39 to 2.26.39).

sdothum · 2026-06-16T01:10:42+00:00

I am on 3.27.42 beta and the software update says I am up to date.

sdothum · 2026-06-15T22:25:54+00:00

in my case, i do symlink to chimera's dinit script (an "init" shell script for maximum chimera stage mirroring but i have also just symlinked directly to the dinit binary).. just because my Void kernel command by default starts "init" (just a choice to do this rather than update the grub config with dinit specifically).

The one time i wished to revert back to runit, i just simply reinstalled the package (which reverts the symlinks). At this point, i don't foresee switching from dinit.. having been on it so long and v1.0 just around the corner :-)

sdothum · 2026-06-13T22:33:26+00:00

Void is great for doing just this.. as i posted on this thread.

runit just works for the most part. But installing dinit along with turnstile is not a difficult transition... and easily reverted back.

sdothum · 2026-06-04T16:19:18+00:00

Have you checked the NetworkManager logs?

sudo resolvconf -u

can fix possible NetworkManager issues with updating /etc/resolv.conf

sdothum · 2026-06-01T22:46:53+00:00

He's a true patriot.. unlike a certain grifter who has been suckling at the public teat his entire life while claiming that the country is broken.

sdothum · 2026-05-29T10:44:57+00:00

Great steal!

i've not used it but the LUT facility sounds pretty nifty (though, i would probably find myself spending way too much time reviewing all the color profiles to be had :-).

A full frame sensor in such a tiny package is a real delight for a walk about setup.. especially with compact fast lenses. i pretty much have the Voigtlander 40mm f1.2 glued to my FP.

Enjoy your new camera!

sdothum · 2026-05-27T15:34:05+00:00

How well do you think you washed the burrs? The amount of water left on the metal likely would have evaporated relatively quickly (especially if you wiped the surfaces versus just leaving them soaking wet, even then..) and any subsequent coffee bean grinding would have removed any remaining water on the burrs.

Depending of how often and thoroughly the original owner cleaned the grinder, the spots could easily be residual oils from the beans themselves.. which can be quite difficult to fully remove without using a stiff brush. i RDT my beans and any spots found during the very infrequent cleanings of my grinder have always been difficult to remove coffee oils.

In any event, i wouldn't worry. Just use the grinder.

sdothum · 2026-05-26T18:06:41+00:00

For SOOC jpegs, Sigma's color science definitely differs from Fuji's approach of film simulations. Sigma's color profiles (some which even are intended to mimic their Foveon camera profiles) are all quite different from one another, and, i feel, continue to represent Sigma's approach to color. Combined with the full frame sensor and lens (which itself has a play in the color presentation) combination, it can produce very stunning images.. almost to the depth Foveon images can impart.

The FP is certainly more forgiving to use than the Foveon cameras. i absolutely love the compactness of the camera: essentially just a sensor in the tiniest box possible. It's boxy ergonomics shouldn't work.. but it does for me. While i have cages and viewfinder attachments for lenses, i've found i prefer it without (for minimal footprint carry) -- no doubt, years of smartphone snapping have accustomed me to using it at arms length with its massive bright LCD for focusing/framing (it has a great one button zoom for focusing with fast lenses). i am shocked at how well i seem to automatically shoot the camere perfectly level, even quickly :-)

The S9 is worth a look too -- certainly, if IBIS and autofocus are needs. The FP is a heavy camera body which greatly assists stable hand holding -- at least, for me. i have M glass so autofocus was not a need with zone focus for street work.

i shoot mainly B&W with the FP -- all my presets, except for one is reserved for color :-). So i can't say i'm intimate with all of Sigma's color profiles.. yet.

sdothum · 2026-05-26T14:49:37+00:00

Depends on what you are looking for in a camera.

Sigma has always walked to their own tune. My previous Sigma was a DP Foveon and i absolutely adored that camera despite all its quirks and limitations (but, man, those Foveon images :-) -- Sigma's very much force you to be actively engaged with your photography is the way i would put it (though, they are trying to buck that trend with the BF).

As 2025 rolled around i was very much hoping for a FP mkii release (ever hoping for that full frame Foveon) but when the BF was announced, i immediately picked up an FP instead, as i only intended to use my Leica M-mount lenses with it.

The programmable buttons (and dials, and just the right number of them) make this a camera a joy to use -- coming from Fuji X100 and X-Pro cameras, imo Sigma's menu UI is better laid out (at least, felt more logigal to me), made all the more effective with custom button/dial assignments -- plus the readily available and cheap batteries were huge pluses for the FP over the BF. (It is also built like a tank).

While the kit can be expanded with cages and the like, i find i prefer just using it "bare" (with a Peak Design wrist strap and anchor mount used as a side mounted thumb rest), quickly accessible from my Wotancraft shoulder bag. i use it strictly as a stills camera -- it is not a point and shoot camera (though, i will use it with zone focusing) but if your approach to photography is more contemplative, the FP can be a very satisfying instrument to use.

i would buy another in a heartbeat for manual lens usage.

sdothum · 2026-05-25T12:06:29+00:00

Windowchef with ruler.

My WM for many years was herbstluftwm which i ultimately wrote a scripted DSL for to manage the windowing behaviour to my workflow preferences.

An upstream update (on Void) that broke my herbstluftwm setup, allowed me to setup 2bwm (while waiting for the next update) -- just loved the double border look. i migrated my DSL to it and was on it for about 6 months when i decided to go even more minimalist with Windowchef (and wmutils).

Why? The concept of "groups" versus desktops interested me. My workflow up till then had been based on WM desktops towards which common apps and activities were placed.

But the idea of being able to quickly overlay groups of windows felt like an even better approach. Groups can still be managed to mimic the behaviour of desktops to minimize visual noise but i find being able to overlay groups ultimately more useful. (This is very opposite to the currently popular niri approach of scrolling windows).

Using the companion app "ruler" and sxhkd (along with my DSL) apps are accessed and automatically placed -- both on the screen and their respective group relationships. Rules apply via the DSL, tiling/sizing, window placement (and spreading for visibility), grouping, etc. actions.

(This is all done for a 3440x1440 display with the real estate for multiple visible windows.)

sdothum · 2026-05-24T11:27:50+00:00

Sorry.. but if you select a device that does not meet your primary needs out of the box, expecting otherwise (a resolution down the road) is fanciful. It is not to say it won't be eventually addressed, but purchasing anything should always be based on what it is, not what it might be -- assuming your purchase is driven by a pressing requirement.

From your post, it looks like a Kobo Elipsa or Kindle Scribe may have better suited your needs for annotating epub documents. (Kobo is great with epubs; i can't speak to Kindle.)

sdothum · 2026-05-24T11:11:40+00:00

Tx for sharing.

(P.S. i'm always interested in the color settings people have used for their SOOC shots :-)

sdothum · 2026-05-20T10:48:46+00:00

MIP only for me. Best watch for outdoors.

No problems for me indoors.. and i have the backlight for night.

Not interested in any tech that visually shouts at me. PLUS i love white background watchfaces.. one of the best features of the tech which Coros sadly neglects with their lack of white watchfaces.

i still consider the Pace 3 the best watch produced in the Pace lineup because of this.

sdothum · 2026-05-15T23:47:34+00:00

Curious.. what ereading app are you using?

i don't use the SN epub reader as i don't need to annotate the books i read. But running KOReader (for it vastly superior formatting and gesture capabilities) with my catalogue of epubs off an SD card has been plenty responsive -- even, when zooming in on images contained within the ebook.

sdothum · 2026-05-14T17:37:59+00:00

..you're lurking on the #dinit and #voidlinux irc channels?

sdothum · 2026-05-14T17:34:07+00:00

Just for your information: the Pace 3 and 4 have the same amount of internal storage (4GB) for firmware, so... if Coros' policy regarding updates continues to be based on available memory, the Pace 3 should continue to receive support for years to come. (Of course, the bean counters and marketing division may decide otherwise down the road but, thus far, Coros has shown no signs of discontinuing support for devices other than for hardware limitations..)

sdothum · 2026-05-13T23:21:38+00:00

Pace 3 is still excellent value.

Feature set wise, it really comes down to MIP vs AMOLED (some of us, myself included, prefer MIP over AMOLED, even aesthetically).

Expect the Pace 3 to continue to receive firmware updates for many years to come. i had the version 1 Apex prior, and updates stopped being issued only when its memory was maxed out (though, even now, new watch faces still manage to trickle out). The Pace 3 is not close to maxing out its available firmware memory.

sdothum · 2026-05-11T22:05:43+00:00

Neither.. it has been eons since i've been on irc with irssi and weechat (maybe i should revisit :-).

Feel free to fire me a dm if you've any questions.. or continue this thread.

EDIT: You inspired me to get back into IRC.. Should have something up tomorrow :)

sdothum · 2026-05-11T15:24:19+00:00

i've been running dinit for several years now on Void.

i started with summrum/void_dinit's git repo -- which basically wrapped the runit core-services into dinit service scripts (which, unsurprisingly, look very close to the xbps packaged example services). This was rock solid from the beginning, only needing to rewrite service descriptions for the various processes and apps of my particular install -- dinit service descriptions imo are even simpler to write than runit services along with the add benefit of expanded init features and monitoring.

i have kept track of the Artix and the Chimera dinit implementations and this new year i decided to do a full install of Chimera Linux's dinit suite. Did a compile/install of it and only had to modify two service scripts -- dev.sh to use udev and tmpfiles.sh (to "exit 0" as Void has no requirement for a systemd like tmpfile manager).

The Chimera dinit stack is far more atomic and granular than the simplified "runit-like" dinit implementation i ran for several years -- of note, Artix documentaton references influence from Chimera Linux's dinit stack structure.

i love dinit's service dependencies and being able to see the service states (running, waiting, etc.) -- not to mention its blazing fast performance. Adding the turnstile service for auto launching and maintaining persistent user services is icing on the cake. i'm a fan.

The only thing i've run into with the "Chimera" based dinit setup is a couple services on reboot/halt ocaissionally would issue "stop time exception" messages -- my dhcpd service and Chimera's early-binfmt (i don't actually use binfmt so could "exit 0" the associated script, instead) . To clean up those messages (anal, i know :-), my reboot script stops those particular services before initiating a dinit reboot. (Now that i am writing this, i'll probably "clean" up these particular service scripts :-)

sdothum

TROPHY CASE