u/sslproxy

I've gone this whole time thinking the "Launch Party" was the pre-party but just realized that's actually Thursday. Reading comprehension is hard... I am a bit confused though as the launch party only has 9 artists on it, which is part of the reason why I automatically assumed it was the pre-party. So am I understanding correctly that the rest of the lineup will be squeezed into Fri/Sat?

And then what does the pre-party/early arrival entail? The early arrival post they made back in March does advertise that the "Music begins on Wednesday". Do we have any idea what artists will be playing the pre-party?

Finally dove into the world of espresso and ended on my very basic beginner setup.

-Casabrews CM5418
-Baratza Encore ESP
-Single walled bottomless portafilter
-Other essentials - wdt, tamp, espresso scale

It's been going well so far. Based on a decent amount of prior research it seemed like the CM5418 would do the job to get my feet wet, as of course beans and grinder were the bigger things to concentrate on. So far that has been true and I've been getting decent results. But the one thing that alludes me is keeping that strict 1:2 ratio for output.

I'm pulling shots manually, IE hitting the 2 cup button and then hitting it again once I'm ready to stop. This scenarios with it's own problems:

Scenario #1: Let the shot continue to pull, and physically remove the shot glass once 1:2 output is met. Problem with this is it's impossible to time this correctly without being off be a minimum of 0.5g at best.

Scenario #2: Kill the shot output on the machine when I'm a few grams off. I have a relatively good feel for timing this so the output flow is minimal enough to pull the shot off in time and get a more precious output. However for those last few seconds/grams of output the pressure has now dropped significantly. I believe this is a result of the two way valve on the cheap system? To be honest I'm not entirely sure the impact this has on the shot itself.

The machine does have custom dispense liquid volume amounts that can be set but to be honest I haven't messed with it. From what I read it was far from consistent, and combining that with the fact I'm switching between different beans and bean weights on a sub-weekly basis, it doesn't seem worth it.

Am I just describing a pitfall of a cheaper machine? If so, what's the best procedure to choose on this machine?

I've spent soo much time trying to track buffering for users. Most of the time it's their shitty ISP router or client causing the issues, but sometimes I've identified it's on my end. And there are multiple places that could be the culprit.. For example, I recently correlated some buffering for users to a specific disk in Unraid. This disk only recently started to get file population in the array, and it was also one of my oldest repurposed disks. Turns out it had much worse concurrent r/w performance than my other disks, and was rearing it ugly head as both qbit and multiple streams would hammer at it simultaneously.

I looked around and didn't see any solution that would easily track everything so I decided to try and build an aggregated dash for every link in the chain. Everything below is a result of 100% vibe coding. I know for a fact below represents a hobbled together solution, that could use more work both from the software and the UI side. I'm but a humble network engineering wanting to have an easy way to correlate data and be 100% sure when I tell users "It's your end". Ultimately it works for me but I'm still actively working on it. I am curious on what the thoughts may be on this, what I missed, what I can included, and most importantly, did I go down a rabbit hole when something already exists that covers all these bases...

Tracking Elements below, listed from each of the devices of origin

Plex (baremetal on i3 with quicsync)

• Full Pex syslogs: used for all session/user mappings and buffer events
• Plex SQL DB: DB back up periodically generated and used for bitrate tracking, as well as file name and location mapping
• CPU/iGPU logging
• Individual client stream RTT/retransmissions
• NIC stats

Unraid

• WAN health tracking: Via pings to google/cloudflare
• Disk I/O logger: iostat monitoring all disks

Opnsense

• GW health check on WAN int
• Interface stat counters
• Monitoring FQ_CoDel: Specifically if there are drops/backpressure on prioritized Plex rule

This all gets ingested into a Ploty frontend, using a handful of scripts and docker compose running directly on Unraid. I have a few tabs but the most meaningful is the Correlation tab.

https://preview.redd.it/b77areqn2w6h1.png?width=1553&format=png&auto=webp&s=114ec331428205de9430e144a35ec2d3103db922

This admittedly is an absolute dumpster fire of an eyesore and something I'll work on tightening up but... it still works well enough for me. I can select both individual users and disks, and the graphs will populate accordingly. The above timeframe has a few different buffering events that can be used to trace back, seen below.

Event 1 - High I/O on disk 4 leading to buffering

Above clearly puts together the picture that high I/O alone on disk5 caused buffering on streams originating from that disk.

Event 2 - Single client high latency/RTT leading to buffering

Based on above, buffer events correlate to a single user with high latency/RTT on their end. Only one user hitting buffering, and can see a single user with high latency/RTT while the rest of the user streams remain unaffected, and no backpressure seen elsewhere.

Event 3 - 100% load on transcoding

In above all elements stay roughly the same, outside of a seen increase to transcoding streams and complete saturation of CPU and quicsync. This one was artificially created with my single account running multiple streams, which is buffer events only show for one individual user. I was streaming the same file for all streams which actually further shows another element. Same file, same disk, and therefore shows spiking high disk I/O for said disk, but I/O latency is still relatively okay so points to issues elsewhere.

And then finally at the bottom I have a whole table of each buffer event, and their correlating values, which elements are elevated, correlation to a isolated or systemic event, etc:

https://preview.redd.it/3hp43k6p6w6h1.png?width=2968&format=png&auto=webp&s=324a1e92bacc3fdb31e766792ae351bfb68c1c08

Relatively new to immich. Moving over after finally getting fed up with having nextcloud auto uploads fail/miss over and over again over the years. Everything is working great but there is one hiccup I haven't been able to to figure out.

Using android and latest app, I have "Sync albums" set in backup settings which should match from phone folder "Camera" into relative album in immich. I've found that most of the time this doesn't work and auto upload files drop into immich without an album tag. If I go into the app and hit "Organize into albums", this instantly corrects all the mappings.

Am I missing something to remove the need to parodically go into the app and manually run this? Delay new assets was originally set to 30 seconds. I've reduced this to 5 seconds but still no change.

Edit: Actually just realized it wasn't even the manual "Organize int albums" doing the correction here. Seems like just opening the immich app alone will correct this. So the background upload process doesn't handle the album tagging, but once the app is open it corrects.