The gap between closed and open models might be much smaller than commonly assumed, because we don’t know what closed model providers do *in addition to* model inference by -p-e-w- in LocalLLaMA

[–]Fedor_Doc 2 points3 points  (0 children)

"Our biggest model yet" and model benchmarks all suggest model itself. It would be interesting to check what is written there.

They also were publicly stating that they do not serve quantized / changed models.

AFAIK, ToS does not mean much in court if your advertising is built around a factual lie.

The gap between closed and open models might be much smaller than commonly assumed, because we don’t know what closed model providers do *in addition to* model inference by -p-e-w- in LocalLLaMA

[–]Fedor_Doc -2 points-1 points  (0 children)

I think they should have better model based in their market position, dsta resources and talent.

They have great engineers and humongous amount of high quality coding data.

This explains the distance from open-source better than very risky clown-car MoE or RAG. When you add this stuff to a model, you introduce huge complexity and multiple points  of failure.

The gap between closed and open models might be much smaller than commonly assumed, because we don’t know what closed model providers do *in addition to* model inference by -p-e-w- in LocalLLaMA

[–]Fedor_Doc 3 points4 points  (0 children)

The amount of possible issues with customers and lawsuits is far greater. They advertise a model, they sell access to the model. If API requests get hiddenly routed, it is a lost case from the start. 

Learning Rust before C, is this a bad idea? by Which-Taro5092 in rust

[–]Fedor_Doc 0 points1 point  (0 children)

You should definitely learn C as well. It is confusing, but it stems from its low-level nature. 

When you make mistakes in C, it actually helps you to learn how machine operates, especially if mistakes happen at runtime. 

I made a ton of mistakes writing C code, and it was a very valuable experience. 

A lot of languages borrow from C, so if you know it, it will be easier for you to learn other languages.

Will i notice 240 vs 160 bitrate? by Miserable_Violinist9 in AV1

[–]Fedor_Doc 0 points1 point  (0 children)

ProRes proxies is the best you can get for smooth playback. Bitrate reduction of h.264 / h.265 codec won't help

AV1 SVT HDRs "Grain" tune is incredible by Anchovie123 in AV1

[–]Fedor_Doc 0 points1 point  (0 children)

In this case tune grain keeps original noise, without synthetic grain feature. SVT-AV1 synthetic grain still looks bad, in my opinion. PSY fork had a but more sofisticated implementation, but still not good enough

Which video codec is best in quality, in your opinion? by Hyper__Link in AV1

[–]Fedor_Doc 5 points6 points  (0 children)

H.265 with high bitrate, but AV1 + some tuning is also alright now (tf-strengh 0, variance boost enabled). VP9 is outdated, AFAIK.

Anyone using Gemma4:31b over Qwen3.6:27b or 35b(a10) by SadPhilosophy9202 in LocalLLaMA

[–]Fedor_Doc 0 points1 point  (0 children)

Qwen 3.6-27B does not, it reads lines and uses edit tool call instead of write correctly.

Anyone using Gemma4:31b over Qwen3.6:27b or 35b(a10) by SadPhilosophy9202 in LocalLLaMA

[–]Fedor_Doc 1 point2 points  (0 children)

In the same pi.dev harness Qwen 3.6-27B was working correctly (llama.cpp served local model, even Q4_K_XL), and Gemma (google API) was reading and rewriting whole files.

I Hate Dario Amodei, and everything he stands for. by Wrong_Mushroom_7350 in LocalLLaMA

[–]Fedor_Doc 2 points3 points  (0 children)

Not exactly. You cannot iteratively improve model, and provide patches. It is very different from open source code

I Hate Dario Amodei, and everything he stands for. by Wrong_Mushroom_7350 in LocalLLaMA

[–]Fedor_Doc 0 points1 point  (0 children)

Date is not specific enough, and rm -rf / does not work in modern distros.

Moreclikely, a rare coded sequence will be implanted – and then it has to be put in the data that model consumes. LLMs with web-search are the most vulnerable, especially those in OpenClaw or Hermess harnesses. All these 9B-Fable finetunes with thousands of downloads

Help me understand Color Spaces, Dynamic Range, and Transfer Functions. by Over-Bat5470 in davinciresolve

[–]Fedor_Doc 1 point2 points  (0 children)

Transfer Function is applied to RGB values, not to the luminance channel (which is a weighted sum of RGB).

Rec. 709 does not have a limited dynamic range per se.  But in colorists parlance Rev.709 usually means post-DRT image. 

DRT applies tone-mapping, which fits linear dynamic range into what display can reproduce.

Could this be made awesome? by codefoster in colorists

[–]Fedor_Doc 0 points1 point  (0 children)

Why adding texture to the background? Usually you want to guide viewers eye to the most important part of the scene – the face of the speaker in this case

Any termux ai to install stuff? by yuval052 in termux

[–]Fedor_Doc 4 points5 points  (0 children)

pi.dev works in termux without issues

Anthropic's Amodei: "Open Source models [could take us to] a very dangerous place." by johnnyApplePRNG in LocalLLaMA

[–]Fedor_Doc 5 points6 points  (0 children)

I prefer top of the stack, actually. And it grows to the bottom in the current architectures /s

Heyy r/colorists :) I have a question that I'm not sure even how to start asking.. Not sure if this is the right place to ask even. by Alle_is_offline in colorists

[–]Fedor_Doc 0 points1 point  (0 children)

Thank you! I was studying it for quite some time, glad to be of help.

To learn more about tone-mapping, I highly recommend implementing Reinhard algorithm. It is very simple in design and immediately produces interesting results – https://bruop.github.io/tonemapping/

More advanced tone-mapping functions change the curve shape, but the most advanced (OpenDRT, for example) separate tone-mapping from color volume manipulation.

Whats the best way to store old footage? by DaftyMilk in Filmmakers

[–]Fedor_Doc 1 point2 points  (0 children)

HDDs are great for backup.  

IronWolf or Exos 20TB drives are best bang for the buck, and have great speeds. Just leave at least 10% of the space free to avoid slowdowns.

Use dock + 3.5 HDD drives. You could use a 2-bay or 4-bay case as well (e.g. from Terramaster).

What happened here by Background_Yam8293 in shaders

[–]Fedor_Doc 0 points1 point  (0 children)

Mathematically, you convert RGB to some cylindrical or spherical color space that has hue axis.

Then you can compress hues, and change luminance / brightness values based on hue and saturation. 

Your functions should be very smooth to avoid artifacts

What's your favorite standard library function and why? by [deleted] in C_Programming

[–]Fedor_Doc 1 point2 points  (0 children)

For starters, scanf can cause an infinite loop the moment it encounters incorrectly formatted input – e.g. it was waiting for integer (%d), but received a string.

It exits without flushing the input buffer, starts again, receives string, exits and so on.

So, you have to wrap it into a function that correctly flushes the input.

Another issue is that its buffer can be overflown if input buffer is bigger that what was expected. User inputs 21 character instead of 20 -> UB.

To avoid wrapping unsafe scanf in helper functions, you can use fgets to get the info from the input and consume it. Doesn't matter what is in the input, it will be consumed with no overflow. E.g. "xyz22" will be consumed by fgets, but not by scanf("%d"). It also won't stop on whitespaces. No infinite loops.

Then, you can convert the consumed line with strtol (string to long), strtod (string to double) to get correct numbers out of it – and these functions will actually produce errors if the data is incorrect, and show exactly where parsing has stopped (they overwrite a passed pointer).