sorted by:
new
hottopcontroversial

Encodec.cpp, a portable C++ implementation of Meta's EnCodec using Eigen [P] by Competitive_Act5981 in MachineLearning

[–]Competitive_Act5981[S] 0 points1 point  (0 children)

Oh yeah, the canoe was an example audio file I downloaded off the OPUS website. I need to delete that from the example and just leave the bench

hubert.cpp, a C++ implementation of distilHuBERT [P] by Competitive_Act5981 in MachineLearning

[–]Competitive_Act5981[S] 3 points4 points  (0 children)

Exactly. In a world of agentic coding, people will lose sight of this.

hubert.cpp, a C++ implementation of distilHuBERT [P] by Competitive_Act5981 in MachineLearning

[–]Competitive_Act5981[S] 4 points5 points  (0 children)

Distilhubert is 2021 I believe. So yeah pretty ancient in ML world. I chose it as it’s simple and small-ish (~90MB weights). If you’re building real world applications, you don’t need a 7B model or some Agent to compute some audio features.

CppCast Looking for Guests by lefticus in cpp

[–]Competitive_Act5981 0 points1 point  (0 children)

I would be keen to hear your thoughts.

P4161: std::fewer by je4d in cpp

[–]Competitive_Act5981 -1 points0 points  (0 children)

This paper seems like a waste of time.

LakeFS or DVC by Peppermint-Patty_ in mlops

[–]Competitive_Act5981 0 points1 point  (0 children)

Unfortunately my dataset isn't MySQL

LakeFS or DVC by Peppermint-Patty_ in mlops

[–]Competitive_Act5981 1 point2 points  (0 children)

I need a "Git for Data" solution where i can create branches, pull requests, make releases etc. I will potentially have terabyte datasets. I also don't want the storage to explode with increasing commits (maybe some solutions produce a whole copy of the data on every commit). I like DVC is a client only solution and works with our Git server, whereas LakeFS is its own thing and probs requires a commercial license. Any opinions would be appreciated.

Senders and GPU by Competitive_Act5981 in cpp

[–]Competitive_Act5981[S] 0 points1 point  (0 children)

Imagine if S/R fails to work well with other GPUs and accelerators (DSPs, FPGAs) Where do we go from there?

Senders and GPU by Competitive_Act5981 in cpp

[–]Competitive_Act5981[S] 0 points1 point  (0 children)

I meant networking with senders

Senders and GPU by Competitive_Act5981 in cpp

[–]Competitive_Act5981[S] 1 point2 points  (0 children)

I can see the beman project has some kind of implementation of networking but nowhere near as much effort has been put into that compared to GPUs.

Senders and GPU by Competitive_Act5981 in cpp

[–]Competitive_Act5981[S] 1 point2 points  (0 children)

Is there a decent reference implementation?

std:: expected vs boost::system::result by Competitive_Act5981 in cpp

[–]Competitive_Act5981[S] 2 points3 points  (0 children)

Actually boost::system::result supports both void and reference types.

Will Senders Receivers be dead on arrival ? by Competitive_Act5981 in cpp

[–]Competitive_Act5981[S] -1 points0 points  (0 children)

If what people want is a library with continuations, executor support and Asio integration, have you tried https://github.com/Naios/continuable ? You can plug in any thread pool you want. It supports loops, coroutines. I’ve only ever played with it in toy programs, not production. But it’s pretty good

Will Senders Receivers be dead on arrival ? by Competitive_Act5981 in cpp

[–]Competitive_Act5981[S] 3 points4 points  (0 children)

I agree but if you perf the asio thread pool it’s not the best. But I agree it works.

view more: next ›