| 25 Jan 2025 |
 laurynasp | * yeah, I haven't done much testing either, I just thought I could reduce 30s by using beefier cpu, and was suprised that it takes almost 10 times longer outside raspberry 4.
I have just tested against framework's Ryzen 7 7840U, and it is also 3-4min...
Upon closer investigations, faster-whisper on both Ryzen machine printed error wyoming-faster-whisper[2771726]: Error in cpuinfo: failed to parse processor information from /proc/cpuinfo, so perhaps to downgrades to single thread or smth
| 08:12:58 |
| laurynasp | * yeah, I haven't done much testing either, I just thought I could reduce 30s by using beefier cpu, and was suprised that it takes almost 10 times longer outside raspberry 4.
I have just tested against framework's Ryzen 7 7840U, and it is also 3-4min...
Upon closer investigations, faster-whisper on both Ryzen machines printed error wyoming-faster-whisper[2771726]: Error in cpuinfo: failed to parse processor information from /proc/cpuinfo, so perhaps it downgrades to single thread or smth
| 08:24:37 |
 uep | 
Download image.png | 08:28:49 |
| uep | it has these things in it, and it's running in a nixos-container so no access to whatever (measly integrated) gpu either | 08:29:35 |
 @hexa:lossy.network | laurynasp: it should be able to access /proc/cpuinfo since https://github.com/NixOS/nixpkgs/pull/372898 | 09:28:54 |
| @hexa:lossy.network | can you check systemctl show -P ProcSubset on your wyoming-faster-whisper systemd unit and report the value back? | 09:29:37 |
| @hexa:lossy.network | also check the new option description for model https://search.nixos.org/options?channel=unstable&show=services.wyoming.faster-whisper.servers.%3Cname%3E.model&from=0&size=50&sort=relevance&type=packages&query=faster-whisper | 09:38:26 |
| @hexa:lossy.network | * also check the new option description for model | 09:40:08 |
| laurynasp | value for systemctl show -P ProcSubset wyoming-faster-whisper-whisper.service:
all on pi 4 that works well (i.e. no cpu error, and proceeses in 30s), it is running nixos-unstable from yesterday, so it has the the PR in it
pid on both ryzen systems, both of which report cpu error, and both systems are older than the PR | 09:57:22 |
| laurynasp | Is there a lifehack to check if a PR has reached nixos-24.11? or is it just grepping in git branch/commits? | 09:58:25 |
| laurynasp | I see the PR has backport to release-24.11, so I guess it is on the stable branch now too | 09:59:58 |
| laurynasp | I will update 24.11 and report back | 10:00:14 |
| @hexa:lossy.network | nixpk.ga | 10:04:22 |
| @hexa:lossy.network | * | 10:04:26 |
|  @number42:matrix.rezel.net left the room. | 10:07:21 |
| laurynasp | hexa: Just retested with most recent 24.11 - that PR did wonders! Reduced from ~4min to 8 seconds, around a factor of 40x! | 10:56:48 |
| @hexa:lossy.network | cool | 10:57:04 |
| @hexa:lossy.network | might want to try a smaller model to make the pipeline more responsive | 10:57:31 |
| laurynasp | will start experimenting later today - thanks for the hint to look at the updated description for model option | 10:58:50 |
| laurynasp | * will start experimenting later today - thanks for the hint to look at the updated description for model option - its very useful | 10:59:13 |
 dotlambda | How do I search HACS without having it installed? | 21:56:17 |
| @hexa:lossy.network | https://github.com/hacs/default/blob/master/integration | 21:57:36 |
| uep | https://nixpk.gs/pr-tracker.html?pr=373454 | 22:51:40 |
| 26 Jan 2025 |
| laurynasp | right I got it now - if PR was merged into stable channel, then nixpk.gs will display pipeline for stable channels. And PR for meging/backporitng into stable channels are automatically recorded on original PRs into master | 09:29:32 |
| laurynasp | I noticed you have wake_word in extra components and running server on "tcp://127.0.0.1:10400". Are you using that for Voice PE or for a satellite? | 09:36:32 |
| uep | voice pe | 09:37:03 |
| laurynasp | Did you have much success with that? I haven't done in-depth research, but default setup for Voice PE does not seem to integrate directly. I guess that's because Voice use microWakeWord on ESP32 | 09:37:15 |
| laurynasp | * Did you have much success with that? I haven't done in-depth research, but default setup for Voice PE does not seem to integrate directly. I guess that's because Voice use microWakeWord on ESP32
Or have I confused myself? | 09:37:44 |
| laurynasp | Oh, I thingk I found a setting for Streaming wake word engine "hidden" in the tripple dots | 09:39:36 |
| uep | though most of the setup was from before voice pe, from a previous experiment like a year ago that didn't get far, and I just uncommented it agan | 09:40:27 |
