u/AI_Tonic

Hey hey some basque Uruguayans crossing the border for “france” to Bilbao for the ferias all weekend.

Are any of you holding a stand or a chosna? If so we would love to drop by and show some support :-)

~~ in remembrance of the 23 august massacre ~~

https://preview.redd.it/maajzbahr88h1.png?width=423&format=png&auto=webp&s=7560bfd6b826de8a7e4e51c8c3223b2a941b7e6f

appears cataclysmic , or maybe more to the point perhaps a bit thin (?) you tell me

this is the only review of using it op could share on aliexpress

https://preview.redd.it/76roxpe45u7h1.png?width=1059&format=png&auto=webp&s=d9a23a082db6321c95b529460b263b6e001ec0b2

Retrieving the referenced FAB_READY_PLAN.md file to review the J8 six-pin Grove connector instructions against the sensor sheet.

Searching for the quantized Moonshine Tiny ONNX model and Foursquare installation steps.

The search missed the Foursquare voice service repository. I found the quantized Moonshine tiny ONNX files already exist locally under edge-ai/voice/models. I will read the local guide and voice-service configuration next to match the Foursquare setup.

The repository is Foursquare/Venson, not foursquare.com. I will read the local Moonshine models README and trace how the voice model is loaded.

This appears to be a desktop voice stack on Windows 11, not the venOS integration. The quantized Moonshine tiny model should be placed in a separate folder under ~/.ven/models, not installed as a Foursquare plugin.

Place the ONNX runtime files in a dedicated subfolder under ~/.ven/models. Configure Foursquare transcription to load the backend from that folder by setting backend to "moonshine".

Restart or reload the voice service after placing the model files. The quantized ONNX runtime files belong in a dedicated subfolder such as C:\Users\<you>\.ven\models\moonshine-tiny-ONNX. Place the quantized encoder model and related ONNX files there.

The quantized decoder model and its required .data companion file must both be placed in the model subfolder. Include tokenizer.json and config.json as well. The local README references a legacy non-quantized decoder file that is outdated.

Foursquare only strictly requires the quantized encoder model, its matching decoder plus .onnx.data sidecar, and tokenizer.json. Optional JSON files such as feature-extractor-config.json and preprocessor_config.json may be kept but are not required. A PowerShell script to download and place the files is being drafted.

The PowerShell script downloads the quantized encoder, decoder, tokenizer, and optional JSON files from the Hugging Face repository into the local model folder.

The Foursquare transcription configuration should mirror the existing base setup exactly. Retain the same JSON keys and only change the model_path value to moonshine-tiny-ONNX. This avoids breaking the current working base configuration.

Relative paths resolve under %USERPROFILE%\.ven\models\. Restart the Foursquare Windows service via PowerShell or the original installer.

A full process restart is required rather than a hot reload to apply the new model configuration. Check the Foursquare logs for Moonshine loading the quantized encoder and decoder, and watch for ONNX runtime errors such as missing .onnx.data files or incorrect paths. A PowerShell sanity check can verify the contents of the moonshine-tiny-ONNX folder, confirming the quantized encoder (~66 MB), decoder (~94 MB .data companion), and tokenizer are present.

Moonshine Tiny offers roughly 24% lower latency than Base at about 145 ms per chunk versus 190 ms. Its smaller footprint makes it ideal for low-latency CPU inference on Windows. The quantized tiny model targets the same graph with faster CPU execution, which suits the Opus 4.6 voice loop.

The decoder will fail to load without the required .onnx.data companion file. The model subfolder must reside under %USERPROFILE%\.ven\models\ and cannot be placed inside the repository clone itself. The backend key must be set to exactly "moonshine"; using whisper or whisper.cpp will not work. Verify that the live service is reading the updated configuration rather than a stale copy stored in the git repository.

ONNX Runtime is already present in the Foursquare voice stack because the base model works. The quantized tiny model can share the same runtime path.

Both models can coexist under ~/.ven/models/. Keep moonshine-base-ONNX and add moonshine-tiny-ONNX as a separate folder. Swap only the model_path value to compare latency and accuracy.

A copy-paste config diff can be generated once the current transcription block and exact Windows service name are provided.

The quantized model has been placed in the correct folder.

The active Foursquare config.json is pasted here for review. It shows relay, HTTP channels, and voice_hub settings. The user noted this file lives outside the repository.

The pasted Foursquare config sets transcription_provider to moonshine and enables transcription with provider: moonshine. The backend field is cut off in the snippet. This matches the quantized tiny model setup.

The pasted config confirms backend: moonshine and model_path: moonshine-tiny-ONNX. Despite this, the logs still show [WARN] Moonshine transcription provider unavailable. The provider is likely failing to initialize because the quantized model files are not yet visible to the running Foursquare process, or the service needs a hard restart to pick up the new model folder.

Running foursquare.exe directly still produces the same unavailable warning despite the model being present and correctly structured. This suggests a filename or path mismatch between the actual files and what the internal loader expects. I will inspect the official loader code and verify the exact folder contents next.

The warning originates from Foursquare’s Go loader, not the JSON configuration. The quantized decoder filenames in the Hugging Face README appear outdated, so the loader may be looking for a different filename than what was actually downloaded. I will pull the exact validation logic from the Foursquare repository to confirm the expected filenames and folder layout.

The most likely cause is a Windows service account mismatch. Foursquare’s voice service typically runs as LocalSystem or another background account, so it searches %SYSTEMROOT%\System32\config\systemprofile\.ven\models\ instead of your interactive user profile. The quantized model folder must be copied to the system profile path, or the service must be switched to run under your user account.

A PowerShell command can identify the exact Foursquare service and its StartName account. If the service runs as LocalSystem, the quantized model folder must be copied into C:\Windows\System32\config\systemprofile\.ven\models\. The better long-term fix is to configure the service to run under your own user account instead.

The quantized decoder requires a .onnx.data sidecar file. If this companion file is missing or zero bytes, the loader silently fails with no useful error message. A PowerShell check can verify the decoder .data file is present and large enough.

new cursor failure mode induced by government restrictions. (joke)

the "thinking" block in auto above leaks then becomes "unrecoverable" in the GUI , (windows/latest) , everything above is nonsense btw , nothing to do with my project (except the begining) :

https://preview.redd.it/jgvti335k26h1.png?width=377&format=png&auto=webp&s=8a8e9e53dad955073220885d9de6854d9780ea8c

heartbreaking :-)

j'ai toujours pas compris le comment et surtout le pourquoi (mais serieux, pourquoi??) les francophones payent pour le torrent , mais si seulement les "pirates" partageaient sur les trackers gratuits , on pourait faire économiser pas mal de maux aux plus démunits (et vieux?) d'entre nous .

juste une idée : le partage passe pas par la mastercard (c'est aussi ça l'intérêt n'est-ce pas?)