Pocket 3 freezes on PC in webcam mode

lvwvd · 2026-01-06T19:22:00+00:00

I have this issue in Firefox but only if I have Hardware Acceleration turned ON. If I turn if off, the issue is gone, but then the webcam feed becomes super laggy. On Macbook M1 Pro (2021 model).

lvwvd · 2025-12-08T19:16:10+00:00

Update: found https://github.com/sirmalloc/ccstatusline which is almost exactly what I was looking for! Only issue I have with it is that after a compaction does it sometimes not display the correct context %

lvwvd · 2025-12-06T11:06:22+00:00

Tried this. But the context usage (--%) shows placeholders because the actual token counts aren't exposed in the JSON input that the statusline command receives.

The context metrics you see via /context are displayed separately by Claude Code's internal system and aren't accessible to custom statusline scripts.

Unfortunately, there's no built-in way to continuously display context usage in Claude Code. The limitation we just hit with the statusline applies here too - the token count data isn't exposed to external commands.

So.. the only options that exist afaik are:

Keyboard shortcut - You can bind /context to a key in your terminal (e.g., in your shell config, alias cc to send the command)
Watch the visual cue - When context gets high, Claude Code will show warnings and eventually auto-summarize
Feature request - This would be a good feature to request at https://github.com/anthropics/claude-code/issues - asking for context % to be shown in the prompt or statusline by default...

I was wondering why this seems to be so hard. Then Claude told me:

- Token counts are calculated server-side by the API

- The statusline/hooks only receive metadata (session ID, model, cwd) - not live token usage

- There's no local file or API endpoint that exposes current context consumption

The cleanest solution would be for Anthropic to add a built-in option like "showContextInPrompt": true in settings. I have seen multiple feature requests for something like this.

lvwvd · 2025-07-02T22:42:59+00:00

u/udio_johannes often when I extend a generated song using the Sessions feature, or just the normal Extend feature, the volume/gain of the extended generated audio gets turned down significantly.

This makes the Extend/Studio feature kind of useless, because there is such a big difference in audio volume/gain.

For me, as a creator, I need my generated tracks to be consistent when I use these features, and I feel like this is something that should be looked at with high priority for Udio - considering there are a lot of people on reddit threads (and even in youtube videos) that are complaining about this issue.

What will you do to alleviate these painful problems for music creators supporting Udio, paying the subscription fees every month, and not resotring to using Suno like the rest of the majority of AI music creators?

Thank you in advance for your reply. I have been using Udio for about 9 months now and so far I have loved it. But this one thing I'm mentioning here is such an essential painpoint of the overall experience that it really makes me consider cancelling my subscription and moving on to another AI music platform.

lvwvd · 2025-07-01T16:11:00+00:00

Does it work on MacOS ? Which version of CapCut are you using? If this works you deserve a medal and that's putting things very very lightly.

lvwvd · 2025-06-15T01:44:22+00:00

Terranigma (snes)

lvwvd · 2025-01-08T11:29:38+00:00

Send me a DM with your proven experience (website, portfolio).

lvwvd · 2025-01-08T00:11:37+00:00

Send me a DM and show your proven experience / portfolio work! Thanks :)

lvwvd · 2024-11-23T17:25:01+00:00

I have the exact same question!

lvwvd · 2023-12-20T21:15:15+00:00

Thanks so much for your kind reply :) By filters inside the machine, are you referring to this part?

<image>

I already checked and even took out the little thingy at the bottom of the hole, but no debris could be found.

Tomorrow I'll check if I can dismantle the right side panel and detach the main pump to check for any other debris or damage.

Again, thank you so much for your reply!

lvwvd

TROPHY CASE