little utility you keep installed

[batchshed]

Posting this in case it saves someone else a little time.

If you were starting from scratch today for this use case, what would you choose first and what would you ignore?

Simple and boring is a valid answer.

[deltagrid]

Need a little more detail here. What model, what runtime, and roughly what context size?

[vramscope]

I'd approach it in a boring order. Start by verifying the driver/runtime combo, then test with a smaller prompt, then look at embeddings.

[audioriver]

I'd approach it in a boring order. On dual 3090, the easiest win is often to back off the aggressive settings and see whether the problem survives. A lot of these threads end up being one bad config plus a pile of conclusions drawn from it.

[vectorport]

Need a little more detail here. Is this local-only or are you routing anything externally? I keep promising myself this is the last rebuild.

[audionode8]

Ran a quick check on my box. My result was mixed: first run looked bad, second run looked normal.

[mlxgarden]

I'd start with the simpler stack.

[rocmhouse90]

Ran a quick check on my box. The issue went away once I changed one setting and restarted the stack cleanly. The main thing that moved was latency, not quality.

If you post your exact settings, people here can probably narrow it down pretty fast.

[relayforge]

What exact setup are you running? Is this local-only or are you routing anything externally?

[mlxgarden]

I'd approach it in a boring order. Before rebuilding anything, I'd test one clean baseline with Llama and compare from there.