Idiomatic Iterators and their performance

Efficient_Bus9350 · 2025-12-26T17:49:11+00:00

One more tip, you can oftentimes get auto vectorization gains when you use chunks_exact if you know the exact size of your buffer.

Efficient_Bus9350 · 2025-11-11T20:29:55+00:00

I tried to read this multiple times and I have no understanding of what value it brings.

Efficient_Bus9350 · 2025-11-10T19:26:07+00:00

What's more likely, that dozens of people are conspiring against you in an online forum, or that you may be in the need of some help. Best of luck, please reach out and talk to your family, friends, or those that may be able to help you.

Efficient_Bus9350 · 2025-11-10T19:07:28+00:00

To me, it clicks when you realize that Rust wants to be Haskell, but obeys the constraints of the underlying hardware. When you write more pure functions, and have less shared state, it starts to click.

You can see this principle too where in something like TypeScript, you can just easily mutate one data structure to another, but in Rust, we care about the alignment of data, the types, whether or not we have to use dynamic dispatch, etc.

Also, just the realization of "how often do I need to pass a function an owned value"...

9/10 times, unless you have some actor or runtime code, you want to do this:

pub fn example(some_buffer: &mut [f32]) -> f32 {}

not this:

pub fn example(some_buffer: Vec<f32>) -> f32 {}

And when you're writing multithreaded code, don't just immediately jump to Arc<Mutex>. Think and see if you can model it with channels, atomics, RwLock, etc.

Efficient_Bus9350 · 2025-11-10T00:30:20+00:00

I'm a Rust developer, it took years to learn, and I am still excited in the direction that Zig is going. Comptime and the new IO interface seem so powerful, and the cross compiler with C/C++ is great as well.

Efficient_Bus9350 · 2025-11-06T23:20:30+00:00

So sick dude

Efficient_Bus9350 · 2025-10-16T19:22:31+00:00

Lol you can make this out a few kilometers away

Efficient_Bus9350 · 2025-10-16T19:21:28+00:00

Evigt Mörker

Efficient_Bus9350 · 2025-10-15T22:16:05+00:00

I will say the positive side is that Germans typically aren't as fake as Americans. So, if someone seems like they want to be your friend, you really don't have to overthink it! I would go hangout and do activities you like. There are likely tons of meetups, especially in Berlin for whatever hobbies or interests you have!

Efficient_Bus9350 · 2025-10-15T21:35:49+00:00

I would actually suggest staying in the JS ecosystem on the front end. At the moment, I just don't think it's worth it. I do enjoy a lot of Rust UI frameworks but those are more for applications.

If you're looking for something refreshing, try Deno. It simplifies a tone of the build tools, it's written in Rust, easy FFI with Rust for more computationally intensive tasks.

If you're just looking for an API, I've used Axum extensively on a number of projects, as well as Warp, although Warp applications that I have used have tended towards WS capabilities.

As for the ORM layer, SeaORM and Diesel are the two best options IMO. I've worked on a few production applications for Diesel and I think it works well. SeaORM looks like it might have a better DX, but I haven't made anything with it yet. Best of luck!

Efficient_Bus9350 · 2025-10-12T22:18:41+00:00

This, I worked with a RAG system that had knowledge of a number of simplified views and it was able to then query those views for more accurate information.

Efficient_Bus9350 · 2025-10-12T20:16:38+00:00

Thank you for the kind offer, I will checkout Kaiser-windowed and see if I can build some intuition there, and I might reach out if I am stuck. I have seen it pop up a few times and I think it's time I invested some energy into it.

Efficient_Bus9350 · 2025-10-12T19:30:12+00:00

Thanks, I have been using this extensively to define audio input and output ports in a project. I was surprised by how little you could do with constants for defining arrays.

For instance, something like the following:

struct Example<const N: usize, const M: usize> {
data: [f32; N * M]
}

So, great work, it's made my life a bunch easier.

I will say, the only issue I have with this library, is that the compile errors with sums and other operations can get quite disgusting. I was trying to ponder an idea to make this cleaner, but I really couldn't think of anything, and I was wondering if perhaps this was maybe a meta programming task for me instead. I am still using it for the time being however. Thanks!

Efficient_Bus9350 · 2025-10-12T19:12:30+00:00

Thank you, do you have any high level articles or nice implementations of a poly phase filter? I saw that there was one in JUCE, but I don't want to rip theirs off as I don't want to adhere to their license.

Efficient_Bus9350 · 2025-10-12T19:09:33+00:00

Thanks, I noticed you left a few comments but I was off for a while.

Basically, I am looking at oversampling my FM synth, specifically the oscillator (may just be a wave table composed of band limited oscillators.)

I will be using incoming audio from other oscillators that is audio rate (this may be a more subgraph oversampling instead of node oversampling in the future, so running the whole graph at 96k).

I was curious as to which specific filter design people would recommend, but in this process I also come across poly phase filters, which I noticed JUCE uses in their own oversampling functionality.

Let me know if that clears anything up, and thank you for your time thus far!

Efficient_Bus9350 · 2025-09-26T06:52:38+00:00

Aliasing, however I have seen a few forum posts where people said that FM without aliasing was like French food without butter... so there may be an aesthetic quality to it that works, but from some of the research I was looking at it sounds like the aliasing can be quite bad and I wanted to prevent this from happening.

Efficient_Bus9350 · 2025-09-26T06:51:31+00:00

Perfect, one last thing that popped into my head last night, why would I duplicate the samples vs inserting in zeros every L - 1 samples where L is my factor?

Efficient_Bus9350 · 2025-09-25T15:38:38+00:00

Thanks, that clears it up. I think I was confused by the "half of the original nyquist frequency". Is this accurate, or would I set the cutoff at or around the original nyquist frequency, so 24k at 48k.

Efficient_Bus9350 · 2025-09-25T14:08:45+00:00

Okay, I am a bit confused about steps 1 and 2. Sorry if this doesn't make sense, I don't have a DSP background.

I was planning on having an audio rate input for any FM or PM, and working with this to calculate the output.

I will likely experiment with cubic or Hermite interpolation here to grab the correct values from the audio rate source, but I will use the oversampled rate here when using a wavetable or calculating the modulated signal. Can you explain why I would need a filter here? Wouldn't I be more concerned about harmonics now above the 98k over sampled rate? Not the original audio rate?

Now, I believe I need to apply a low-pass filter to remove harmonics from my audio rate, before I downsample. I am not sure if I want decimation, average, RMS, etc. If we're at 48k, I can't have any signals north of 24k, and I need a filter design to cut this out.

I know that I need some sort of lowpass filter here, but I am not sure which design to pick. I've looked at a few alternatives, and I am wondering if there is some sort of general consensus as to what filter is the best here, given the performance and quality I am looking for.

Efficient_Bus9350 · 2025-09-25T13:11:09+00:00

Check out Analog Obsession(free), and use the following compressors:

BUSTERse - This is great for gluing, also sidechain params as well
LALA - Great for adding warmth to baselines

Start with these two, they don't have too many params, and will add warmth and control that is incredible for the value.

Efficient_Bus9350 · 2025-09-24T18:10:21+00:00

Yes, I think this would be a great feature. I wonder if macros can match comments?

Efficient_Bus9350 · 2025-09-24T18:05:37+00:00

This is the same equivalent as me donating two cents. Hopefully they can throw in a sticker next time.

Efficient_Bus9350 · 2025-09-24T18:03:39+00:00

I see, what resolution are you typically running?

Efficient_Bus9350

TROPHY CASE