Readit News logoReadit News
haldean commented on Blackmagic Debuts $30K 3D Camera for Capturing Video for Vision Pro   macrumors.com/2024/12/16/... · Posted by u/tosh
tobyjsullivan · 9 months ago
> it’d be tough for someone to justify spending $30K on a single purpose camera

I don't think hobbyists are the target market. Isn't that price in-line with any studio-quality camera? (I have no idea if this qualifies as a studio-quality camera, but I can imagine at least a few studios would be willing to try it out).

haldean · 9 months ago
There are quite a few cine cameras that are more than 10x this amount, and there are a few that are 100x. For example, there are Panavision cameras that you can only rent direct from Panavision that require that you have half a million dollars of insurance coverage to rent. There are ARRIs that you can buy from B&H that are $100k. $30k is definitely in the range of something that individual DPs/operators could own, although it’s getting into rental territory for lots of people.
haldean commented on The data that powers AI is disappearing fast   nytimes.com/2024/07/19/te... · Posted by u/sgammon
dcow · a year ago
An AI that doesn't know the little mermaid would have trouble interfacing contextually with a society where it’s common knowledge.
haldean · a year ago
who cares
haldean commented on AI will save the world?   pmarca.substack.com/p/why... · Posted by u/kjhughes
haldean · 2 years ago
There's lots to laugh at here but my favorite dumb part is talking about wages and wealth inequality:

> But the good news doesn’t stop there. We also get higher wages. This is because, at the level of the individual worker, the marketplace sets compensation as a function of the marginal productivity of the worker. A worker in a technology-infused business will be more productive than a worker in a traditional business. The employer will either pay that worker more money as he is now more productive, or another employer will, purely out of self interest. The result is that technology introduced into an industry generally not only increases the number of jobs in the industry but also raises wages.

and later

> As it happens, this was a central claim of Marxism, that the owners of the means of production – the bourgeoisie – would inevitably steal all societal wealth from the people who do the actual work – the proletariat. This is another fallacy that simply will not die no matter how often it’s disproved by reality. But let’s drive a stake through its heart anyway.

He's just lying! There's no evidence to support this at all in the modern US economy. The gains in wealth from automation over the last 50 years have almost _exclusively_ gone to the owners of the means of production. The median US household income went up less than 20% between 1983 and 2016 while the 95th percentile more than doubled.[0] This is just VC pump-and-dump nonsense pure and simple; it seems incredibly likely that any financial gains from AI making workers more productive will flow directly to the same people who have been reaping all of the gains from our increased productivity: Andreesen and his billionaire colleagues.

[0] https://www.pewresearch.org/social-trends/2020/01/09/trends-...

haldean commented on Apple unveils new Mac Studio and brings Apple Silicon to Mac Pro   apple.com/newsroom/2023/0... · Posted by u/0xedb
USB5 · 2 years ago
Interesting. Which M2 machine are you using?
haldean · 2 years ago
Mac Mini with M2 Pro
haldean commented on Apple unveils new Mac Studio and brings Apple Silicon to Mac Pro   apple.com/newsroom/2023/0... · Posted by u/0xedb
USB5 · 2 years ago
I can't speak for cycles, but Redshift is very slow on OpenCL. I've never heard of using it on Metal. I know it was written for CUDA and didn't even support OpenCL for a long time. Do you know how it runs on Metal?

I don't think V-Ray GPU will run on anything but Nvidia, and if it will then it's definitely slow.

haldean · 2 years ago
Ah yeah forgot about V-Ray. I haven't tried Redshift on Metal, nope; all my work has been Renderman and Cycles recently. Curious to hear how well it works, people online seem to say it's pretty fast but hard to tell marketing copy from actual performance when it comes to renderers.

FWIW Cycles is definitely slower on my M2 than it was on my 3080 but it's not a huge difference -- maybe 20% slower? I still have to let the render run overnight either way haha.

haldean commented on Apple unveils new Mac Studio and brings Apple Silicon to Mac Pro   apple.com/newsroom/2023/0... · Posted by u/0xedb
USB5 · 2 years ago
>3D animation

Disagree. All the good GPU-based rendering engines need CUDA, and none of them are optimized for Apple silicon. Octane (the one in the demo) is trash, only good for fancy titles and that sort of thing.

haldean · 2 years ago
Octane, Redshift, and eevee/Cycles all work on Metal, and Renderman and Mantra are CPU-only for now -- RM/Mantra have beta-versions that are GPU enabled, and Karma is nvidia-only and RM XPU doesn't work on macs at all yet, but I don't think many people are using either in production very much yet. I think the only GPU renderer people are using in production pipelines that's really locked to NVIDIA chips is Arnold, right?
haldean commented on Please stop sending me emails written by GPT   mkbaio.substack.com/p/ple... · Posted by u/HumanReadable
kelseyfrog · 2 years ago
The author seems unaware or at least uninterested in the fact that writing style can have a dramatic impact on output. It's unclear if they wish to not be emailed "by ChatGPT" or if they wish to not have to sift through unnecessary and flowery pose.

I'll spare you the details, but a follow up "That's great. However, please rewrite it in the style of Ernest Hemingway." delivers concise, yet obviously Hemingway-esque emails. Example here: https://pastebin.com/rrkCMd8c It works much better in a two-step process. If "Write this email in the style of Ernest Hemingway" is affixed to the original prompt, the model will generate prose at length, defeating the purpose of being concise.

"That's great. However, please rewrite it in the concise style of Paul Graham," of course, works even better.

haldean · 2 years ago
If I received the second email there I would think the sender was a psychopath
haldean commented on Google I/O 2023   io.google/2023/... · Posted by u/skilled
elliotec · 2 years ago
What is? Adobe? Davinci? My assumption was also that Final Cut Pro was _the_ one.
haldean · 2 years ago
Most big-budget feature films are cut on Avid and that's been the case for a while now; for indies my impression is that it's 50/50 Premiere and Resolve, yup.
haldean commented on DaVinci Resolve for iPad   blackmagicdesign.com/medi... · Posted by u/dagmx
bitL · 3 years ago
How is iPad going to handle RAW 8k video? Its highest storage is small, good only for a scratch disk at best or for very short movies.
haldean · 3 years ago
The workflow many post-production studios use for editing/grading is to keep files on a NAS with proxies (i.e., lower-quality transcodes of the video clips in the edit) on a local disk -- that's the workflow I use even with my desktop machine, and I bet it'll work well with this too.
haldean commented on My favourite C++ footgun   dustri.org/b/my-favourite... · Posted by u/pabs3
eklitzke · 4 years ago
The author writes "this might be why there is std::make_shared", but that's not really why it exists. When you create a std::shared_ptr it needs to allocate memory for a control block structure (which tracks the reference count) as well as the memory for the object itself. If you write std::shared_ptr<Foo>(new Foo) this will result in two memory allocations, one for the Foo object and the other for the std::shared_ptr control block. If you write std::make_shared<Foo>() then a single allocation will happen which has enough space for both the control block and the Foo object, and then placement new is used to initialize the memory for both structures. So std::make_shared exists to reduce the number of memory allocations that are being made, not for the reason suggested here.
haldean · 4 years ago
There's a crazy downside to make_shared that I learned recently because of this: if you have a weak pointer to a shared thing, and the refcount for the shared thing drops to zero, the weak pointers will keep the allocation for the object "alive", because they still need access to the remnant and the remnant was created in the same allocation as the object so they can't be freed separately. So now I only use make_shared if I know for sure there won't be a weak_ptr pointing at it (or if the base object has a relatively small memory footprint after it's been destructed).

u/haldean

KarmaCake day1170November 3, 2010
About
http://haldean.org

[ my public key: https://keybase.io/haldean; my proof: https://keybase.io/haldean/sigs/b8iMYgBztqHNxdzpE22mUbizveJMjo8AbBnxJimUpIU ]

View Original