HN Simulatornew | past | comments | lists | submit | zuInnp's commentslogin

The whole “how to take a video” bubble in the internet is rather confusing. You find so many hints and tutorials and advice about how to shoot and color correct … it is pretty confusing. Last year I learned about the correct position of the log to rec 709 transformation, which makes sense looking now at it, but which also means I did it wrong for some years

Depends on what you mean by correct though.

Unless you are sending your stuff for broadcast, which has a clear and rigid delivery spec, then frankly it all about what looks good.

Most displays are only really capable of displaying 8bits of srgb. even then its suspect. Manufactures will put colour tints/transformations/LUTs to stuff look bright and colour rich, even though the underlying footage/screen is sup standard.

At the end of the day, can you make your output look good on a TV and or phone? if you can, thats video, well done. Ignore the purists unless you want to get a very specific feel of colour that requires what they are selling.


I mean having an affair with someone who works below in the company hierachy, is also a huge problem (if the thing about second affair is correct)

Before writing about how I feel about AI, some ideas that sometimes help me: - plan your breaks, e.g. "1h hour of work and then go away from the computer for 5 or 10 minutes" * try to break the "just plan a little further" loop

- accept that you cannot be concentrated for hours and that reading an AI chat is mentally challenging (see first point about breaks)

- Talk with your coworkers about it. You are not alone, it is important to talk about how you feel

- set some boundarys, e.g. I don't work in parallel on different stuff

- do NOT doom scroll while the AI is "thinking". Try some meditation or mindfullnes exercises. Doom scrolling on reddit, HN or youtube will mess up your brain even more.

- from every task, try to do something on your own, and then scale this up by AI. That tip is from a former co-worker. Their idea was that you need to figure out things first and then let AI do the boring task to scale it up. Depends on the topic sadly.

- do some things by hand, especially if they are fun for you. E.g. I really like UI design, somethign that basically is gone now for me.

It feels very strange on multiple levels.

There is the tiredness of reading text all day long. The fear of loosing my coding abilities because Claude does is. I am totally loosing track of what I did when. I can tell you about things I coded 5 years ago, I cannot tell you what I did with Claude last week.

And don't get me wrong, I LOVE planning stuff out before doing that. If there is anything positive about AI, then it is people actually PLANNING before doing.

On the other hand, I can now do/try out things I did not do because I did not have time. But at the same time, it feels like I am working on making myself not needed anymore in the future.

Worst thing, I feel like I am getting dumber. My attention spans or the "I need to know why this happens" span gets shorter, because with AI everything has to be faster?! Riiight?

I don't know how this will turn out in the future.

I see people underselling themselves becoming anxious about working without AI (either because of how they think about their abilities or management pressure).

I am getting chat snippits from AI conversations via Teams, PR checks are skills now and we need 3 rounds of discussing findings with AI ...

We live in interesting times. But yeah, I am feeling with miserable about it.


Hm that’s interesting, I would have thought that Pixar and Disney Animation use the same render software, but no.


Dreamworks used Renderman(Pixar’s Renderman) along with several other commercial package for a Shark Tale. When Dreamworks acquired PDI, who made Shrek under contract for DWA, there was essentially a war between the two pipelines and PDI won. I was on the PDI side of the company, but there was a lot of positive things about the Renderman pipeline.


Hey I was on the PDI side as well, ahoy, nice to see you here! I had forgotten about Shark Tale using RenderMan, but I will say to the degree there was competition and to the degree that PDI won any pipeline battles, DWA eventually won the war. :P ;) There was plenty of cooperation as well, it just takes time for two companies to integrate, and plenty of people on both sides were quite attached to the cool tools they made. (I was certainly guilty!)

PDI’s toolset was pure magic for it’s time. When I joined, I was in heaven with how easy it was to make procedural animation, build new effects that crossed pipeline stages, render anything you could imagine… I wished I could share it with researchers and hobbyists.


We all had to imagine making our next show using each others pipeline and that was fun. In the end, I think Richard, Jono and other PDI folks ended up having a bit more influence because Shrek was so darn successful.

Custom vs. commercial was a constant issue. Were you around for the whole NextGen effort? DWA spent a fortune on some custom tools that only were used on a show, or maybe just a few sequences, before they were replaced with commercial tools.


Oh definitely - custom vs commercial. I remember the R&D team having to write a yearly report to justify the development expenditure, explain repeatedly why we were writing custom tools & renderer when these things were available off the shelf. I heard a few strong rants here and there about how the suits just didn’t understand. I remember the term “NextGen” being thrown around but I don’t remember if I lived through it or it was just getting started when I left (before S3). Jono I and tried for a while to stop having our shaders rewritten in C++ (without otherwise changing them nor adding any features). We eventually gave up and just kept building new things, but that was a fairly successful strategy to nudge the IP, tech, and support southward. Possibly the right strategy in retrospect, but felt a little rough at the time.


Were the shaders written in “script”? :) We had to deep dive into that runtime a reverse engineer and fix it during the fun you must have missed during the 32 to 64 bit transition we did right around Bee Movie timeline.


Nope, they were just written in C. It was object oriented C, but without a C++ compiler. Do you know the story about the whole C++ toolset that was rolled out by R&D and promptly rejected by production? That happened before my time, but according to legend is what lead to PDI’s strict avoidance of C++… until a couple of years into the DWA merger. (Clearly there were some problems beyond C vs C++, but I don’t know the whole story.) Anyway, yeah I remember starting on the 64b transition, but left before that was finished.


I wonder why PDI was better than Renderman ?


“Better” is a loaded word. When you write your own renderer, you have a lot more control and a lot more support. Renderers at the time had not all converged on the same algorithms, so you could have a competitive advantage by writing a good one. PDI’s shader system was different than RenderMan’s and had some real advantages — compiled shaders, geometry & light shaders (not just materials), particles & particle shadowing, compositor integration, etc.. The renderer also needs to integrate into the pipeline deeply, so PDI’s renderer fits the PDI/DW pipeline better, whereas with RenderMan you have to try to mold the pipeline to fit the renderer in.


It wasn’t the renderer as much as the pipeline. The renderer is just one process in a stunning amount of complexity that must be managed. We may even agree that Renderman was better than the PDI renderer but there was so much much more.


Because all this animation tech is a moving target, each production's management chooses the software and versions of that software a production will use and then freeze it. So the studios already have in place a subsystem for every production to be running different software for different productions, doing the same jobs as other productions using other software. This allows some experimental renderer to be used in some sequences, and so on, as well as trials of all kinds of software too, such as AI tracking of camera paths, and the soft and hard objects in their view, AI assisted rendering, assisted color timing assistance and then experiments directly with AI video models in a hybrid pipeline.


Both companies each had their own renderer & rendering development team before the acquisition. And their own pipelines. A couple decades later, that’s still true.


I mean there are like a million reasons to replace American technology since .. well you know when...


But honestly, even well before that.

When did Doctorow coin enshittification?

When did Zuck call his users stupid fucks?

When did Amazon start comingling counterfeits with originals?

When did Google buy DoubleClick?

When did Google start reading your Gmail?

When did Boeing start skimping on safety?

This is a decades long trend. Don't be giving Trump credit he doesn't deserve, otherwise the lessons of history will not be learned. Blaming Trump is yet another easy answer that allows for all of the other things to be swept under the rug.


Yes, I see your point, but for me it gets a new dimension when it is happening on the government level.

Yes, a company can fuck you up but you can find a new provider. But if the government of the country can control allmost all the providers prohibits them to sell their services to you, that is more serious.


Yeah but as a European those things are livable with FB/Google/Amazon/Boeing all provided decent service if annoying at times.

But siding with Russia invading Europe is a different category.


Quite funny that the agent starts speaking with a French accent after reading French :D


Amusingly, the agent also spoke German with an English accent. I guess it takes a bit to switch contexts.


You mean it speaks French with an English accent?


I’ve noticed the same thing with ChatGPT. If I start speaking in Chinese first, and then ask it to say something in English it will speak with somewhat of a Chinese accent.


Yeah, the german is also hilariously bad if it's supposed to sound native.


From the two examples I could find on the page, it sounds stilted, but not "hilariously" bad.


Ah, yeah, the voice samples on the page are much better than the one in the video.


Interesting article, there is also youtube video by the author about it:

https://www.youtube.com/watch?v=QYMbF7VH350


I like the strumming part, could you add an option to not auto strum a chord when I do a chord change?


I don't buy that. We see nothing.

> Software teams are capturing a lot of the speedup in the form of more leisure or quasi-leisure time. (To greatly simplify: software teams are offering 2x speedups to their companies. They're then using tools that allow them to work 10x as efficiently, and taking nice long coffee breaks.)

That is just an insult. With AI we are working more than ever, either because of "you should be faster now" or because half the people are getting layed-off ...


I have no clue where the author is working but...

We've lost 75% of the team over the last year.

We write code faster. It's not getting merged faster because we usually find something janky.

Decisions aren't made faster.

Understanding doesn't come faster.

Code doesn't have value. A well working system has value, the bottleneck is now between having code and having a working system, rather than producing the code.


> Understanding doesn't come faster.

With AI you can write a new Harry Potter novel in under an hour. But if I ask you about the story you can only answer “It involves wizards”.

In pre-AI era you could solve a bug in one week. But you would end up having a detailed mental picture of the system, which requires time to be created. That mental investment helps you make better decisions on the system or solve related problems instantly.


Agreed. The recent Epic Games story (mass layoffs followed by the remaining staff being forced to use AI to crunch) is more in line with reality as I see it. I've been told by management to 'use AI' when I really need to hire.


Who are "we"? We have less (almost none) issues on Sentry, better measured performance, reduced server costs. At the end AI is just writing the same bytecode so you're not going to suddenly see software that didn't exist before.


> We see nothing.

Clear your glasses. For example - https://getartcraft.com/apps Thanks to those people we may soon have great alternatives to monopolies.


Have you tried one? They are like gargling dog shit.

Adobe is cheap compared to that miserable experience.


It's an alpha phase. Why you people consider a project that is being actively developed for only couple of weeks a finished product? It's improving on a daily basis. Adobe and Microsoft had several decades. You're asking for the same in order of weeks? And for free? Is it me who is unreasonable here?


The point is you can't throw a product on the market and claim it's a replacement for everything else, with all the associated press around it. Because that's not what it is. The person prescribing what to do has absolutely no idea what all the end users actually want and need out of a product.

What it really shows is ego, arrogance and disdain for the users while running an AI cargo cult.


Let's continue that a year from now.


I don't see where they claim that it's a replacement for everything.

> What it really shows is ego, arrogance and disdain for the users while running an AI cargo cult.

It seems you have unreasonable expectations of a new piece of software because you don't like people who use AI.


> They are like gargling dog shit.

Sounds exactly like every Adobe product ever. I guess they went too far on feature parity.


Everyone loves to hate Adobe because someone else does, but their products are actually pretty damn good.

And that is because they've had 30 years of effort thrown into them. It's not the big picture that's the issue, it's the thousands of small things. Stuff hidden in the menus that millions of people use. The corpus of educational material out there to help you get stuff done. And the flexibility which is really difficult to match. A good example is the ability for Lightroom to pull reasonable detail out of shadows from RAW images. No other product can touch that, not DxO/affinity/Photomator/Darktable/RAWtherapy.

LightCraft's exposure slider doesn't even work well. Blows everything out. No interpolation curve. It's just BAM!


They are good only if you never seen anything else. I don't know a single image editor worse than Photoshop. Adobe Acrobat and the associated format is a blight on human civilization that needed invention of fricking arificial mind to untangle. Illustrator had idiotic bugs that surely costed millions in misprints.

And remeber Flash? The software that Adobe bought and murdered becuse of their software development inaptitude? If it didn't end up in their hands it would be part of web standards by now and all of the human creativity that this software spawned wouldn't end up smashed into smitherines.

Adobe is cancer of user facing software. Always has been.

Adobe is a company that firmly squats in few very large niches of human activity and despite its mediocrity and awefulness starves any other software that dares to venture into them. It should have been broken by anti-monopoly laws 3 times by now.

I don't know how somebody can look at how much and in what manner they are charging their customers with cancelation fees and such and think that it's an evidence of providing great value and not that's it's a sign of clearly patgological grasp on the market that they have.

I will never forgive them killing Fireworks and Flash and developing Acrobat, Photoshop and Illustrator the way they did.

I haven't touched any of their stuff since content aware resize. I'm sure that they learned to polish their turds, because it's 2020's, everyone did. I'll be celebrating their ride down as more and more people start banging out simple tools with AI agents to make the edits they need instead of digging through tons of documentation and "educational" materials to find the one almost correct option at the bottom of nested menus of Adobe crapware.

> A good example is the ability for Lightroom to pull reasonable detail out of shadows from RAW images. No other product can touch that, not DxO/affinity/Photomator/Darktable/RAWtherapy.

> LightCraft's exposure slider doesn't even work well. Blows everything out. No interpolation curve. It's just BAM!

Do you know that an agent can build a simple Rust app for you that's going to be small, blazing fast and will implement for you the best 3 algorithm for that, straight from their respective papers and give you knobs for adjusting every parameter they have with any manner of precision?


Dude, have you seen Acrobat Reader "lately" - let's say, in the past 20 years or so? It's an unnecessary bloated and complicated product, nowadays slow as hell, and of course, the minute you open a PDF it starts with a compulsory "AI assistant" popup, whether you like it or not.

Unfortunately corporate IT doesn't care - they are not using it. On my own systems I've long switched to alternatives.


Absolute tosh, sorry.

I don't like the Creative Cloud suite that much (FWIW I prefer Affinity, A.R.T., DxO PhotoLab, CaptureOne, any real alternative).

But Adobe's apps are pretty solidly reliable, if uninspiring in places (Affinity's layer model is better for example).


What is that alternative? How will they maintain and keep updates going, how will they add more features, how will they support non-technical customers, how will they offer cloud that a lot of customers are used to?

All of them cost money. They are ripping off Adobe to create the new Adobe.

The worst thing is that there are genuine legit open source projects that already offered an alternative but they did not need AI or ripping off Adobe as a marketing gimmick.

Vibecoded should not be an endorsement in 2026, it should be a warning.


All of them are listed as either "in development" or "early alpha", and every single person that has tried to do something even roughly resembling a task you would do with the original product can tell you that it's broken in a thousand ways.

As it stands right now, it proofs little more than it can replicate the post-boot screen of the original products.

Just because every tech news outlet was dumb enough to report it without trying it doesn't mean you have to join the echo chamber.

---

There are definitely examples out there that do use a similar relentlessly agentic development style that have produced great results. e.g. xberg[0] (formerly kreuzberg), is a great document content extractor, and in a relatively short amount of time has become one of the most robust and performant. I've reported about a dozen edge cases of documents of various types that were unextractable, and the maintainer (or their agents) were able to add a fix in maximum a day turnaround every time.

[0]: https://github.com/xberg-io/xberg


Slop clones of Adobe's apps doesn't feel "great" to me.

Moral compass/integrity stuff. Can't explain why, it just feels like absolutely the wrong direction to be heading in.


Cloning Adobe products or pirating them is the morally correct choice.


All of this recomp stuff is pretty amazing. I really don't like how AI changed my profession, but hey at least I get something good from it.


I really don't like how AI changed my profession, but hey at least I get my programming hobbies ruined too.


At least the good thing about a hobby being a hobby is that no manager tells you what you should do.


And it will make less sense for big publishers to invest in building great games if people are just going to be able to decompile and run them on their own hardware.


Big publishers have been pumping mtx riddled buggy crap for a good while now, I have no sympathy.


a big publisher just announced (today) that their new development is fully AI, from code to art. So it seems we're out of big games from them anyway.


Great, so maybe it means we are about to hit a small indie game developer renaissance!


Indeed. Programming feels so meaningless now, but at least we can replay cherished games natively. I'm doing a video game decompilation with AI as well.


There were already a couple of ways to play PS2 games though. Is it meaningful to put it in WebAssembly (especially when we were promised things like a cure for cancer [0])?

0 - https://www.theguardian.com/business/2026/sep/08/ai-cure-can...


you could have just run the rom through an emulator, and it'd be doing exactly the same process in the background. But without crashing the game several times, and then the first couple of times it doesn't crash it's declared "good enough". Because when a dynamic recompiler discovers something new (which is impossible to do statically), it recompiles and patches the new code in seamlessly.


same lol. but hey, ive been able to play the xbox 360 version of NFS most wanted perfectly on steamdeck in one press of a button due to the efforts of the fine folks working on these recomps so ill take a small win here and there. ive heard theyve also got the original forza horizon working too. so im stoked.


Here's a guy who put together this recomp of NFS the Xbox 360 version, running on the Steam Deck:

https://old.reddit.com/r/SteamDeck/comments/1x0vzyb/speedbre...

Forza Horizon recomp: https://github.com/arcanite24/pinyon-shift

More Xbox 360 projects here:

https://fangamesdb.com/consoles/xbox-360.html


No mention of AI at all in this repo.


Not explicitly but it's clearly all done using AI. Read the prose.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: