Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Muse Spark 1.3

developer.meta.com

Post reply on HN
Print view View original

211–220 of 475 posts

Re: Muse Spark 1.3

#211

Post by __MatrixMan__ »

drusepth wrote: post #5
simonw wrote: post #3

llm -m meta-ai/muse-spark-1.3 "Generate an SVG of a pelican riding a bicycle" https://tools.simonwillison.net/markdown-svg-renderer?url=ht... 4.2266 cents, 38 seconds. For comparison here's Muse Spark 1.2, which animated it without me asking it to: https://tools.simonwillison.net/markdown-svg-renderer?url=ht... The 1.3 one is definitely better - better bicycle frame, better wing, better pelican hat. UPDATE: Here's an…

Is there a reason these pelicans always have roughly the same composition (side-view, 2d, biking right, flat ground beneath, etc)? I don't see any of that detailed in the prompt, yet they all seem to generate roughly the same image of differing quality.

The thing that distinguishes pelicans from other birds does so most strongly in profile. If you're looking straight at one, the throat pouch would be hidden by the beak.

I bet if it instead had something to do with black widow spiders we'd find that we're most often looking at the bottom of the spider's abdomen, regardless of whatever non-spider-like activity is supplied.

Re: Muse Spark 1.3

#212

Post by wewewedxfgdf »

simonw wrote: post #3

llm -m meta-ai/muse-spark-1.3 "Generate an SVG of a pelican riding a bicycle" https://tools.simonwillison.net/markdown-svg-renderer?url=ht... 4.2266 cents, 38 seconds. For comparison here's Muse Spark 1.2, which animated it without me asking it to: https://tools.simonwillison.net/markdown-svg-renderer?url=ht... The 1.3 one is definitely better - better bicycle frame, better wing, better pelican hat. UPDATE: Here's an…

[flagged]

Re: Muse Spark 1.3

#213

Post by nojs »

tintor wrote: post #122
hollowturtle wrote: post #117

Earlier quoted context omitted.

Is there any point anymore regarding this svg test? I would not be surprised if in the training they're fine tuned for this task too

It would be very embarrassing for any lab to benchmaxx the pelican on bicycle svg prompt, since it would be very easy to detect it by varying the prompt.

The amount of discussion around it means that the test and all the reviews of results, images, approaches etc are implicitly included in training data.

It’s not deliberate “benchmaxxing” but things that are discussed a lot online are naturally things that LLMs learn better.

Re: Muse Spark 1.3

#214

Post by HDBaseT »

tyre wrote: post #146
aftbit wrote: post #86

Earlier quoted context omitted.

Okay but Muse Glimmer 30B is one of the best small open weight models today, and IMO the best from a US lab (only real comparison is Gemma4 dense right now).

Totally fine with open weight, since other people can provide it and Meta isn’t making money. I’d use an AWS-hosted version.

Zuck said Muse Spark 1.2 should be getting open weights "soon" on a tweet from a few weeks ago.

The problem inference providers will not be able to get anywhere near the contributor pricing.

Re: Muse Spark 1.3

#215

Post by comicjk »

dakolli wrote: post #189
WASDx wrote: post #45

Earlier quoted context omitted.

With the contributor pricing being more than 10x cheaper than the standard, that would make it best and cheapest on the DeepSWE leaderboard! It feels fast in my experience too. LLMs keep improving at an insane pace.

and they're ultimately tools strictly to replace you and your labor, they can't/won't cure cancer or make your life better. Your life will get worse and worse in every aspect until they extract maximum value from all of our lives with this technology through every avenue possible. Not sure why you guys are so excited about these developments. This technology is strictly an extractive parasite on the world. Use it, bu…

My labor makes other people's lives better, so I would expect something that replaces my labor to do the same.

Re: Muse Spark 1.3

#216

Post by dakolli »

comicjk wrote: post #215
dakolli wrote: post #189

Earlier quoted context omitted.

and they're ultimately tools strictly to replace you and your labor, they can't/won't cure cancer or make your life better. Your life will get worse and worse in every aspect until they extract maximum value from all of our lives with this technology through every avenue possible. Not sure why you guys are so excited about these developments. This technology is strictly an extractive parasite on the world. Use it, bu…

My labor makes other people's lives better, so I would expect something that replaces my labor to do the same.

https://en.wikipedia.org/wiki/Commodity_fetishism

Re: Muse Spark 1.3

#217

Post by dakolli »

skybrian wrote: post #192
dakolli wrote: post #189

Earlier quoted context omitted.

and they're ultimately tools strictly to replace you and your labor, they can't/won't cure cancer or make your life better. Your life will get worse and worse in every aspect until they extract maximum value from all of our lives with this technology through every avenue possible. Not sure why you guys are so excited about these developments. This technology is strictly an extractive parasite on the world. Use it, bu…

I’m retired so it won’t be replacing my labor :)

[flagged]

Re: Muse Spark 1.3

#218

Post by labcomputer »

daemonologist wrote: post #29
postalcoder wrote: post #16

Earlier quoted context omitted.

Search Google Images for "bicycle". Almost all bicycle product shots are staged the same way: side view, going left-to-right. It makes sense to me that given that skew in the training data, the model grounds itself in the bicycle.

and furthermore, this is because the drivetrain is ~always on the right side of the bike - if you want to inspect or admire a bicycle you look at the right side, as you might look under the hood of a car. (Why the drivetrain is on the right, I don't know. But most bike parts follow open standards so it's quite entrenched.)

I can’t tell you why it’s always on the right, but it’s always on the same side because of network effects.

Bicycle frames are not fully symmetric left-right because you need things like a mount point for the derailleur hanger, and optionally affordances to keep the chain off the stays when the wheel is removed.

Those things have to be on the same side as the chain. Bikes designed for disc brakes additionally need a mount point for the brake caliper on the opposite side from the chain.

Additionally, rear wheels are not symmetric: the spokes on the chain side connect to the hub closer to the plane of the rim. That is, they are more perpendicular to the wheel’s rotational axis than spokes on the opposite side (which is why you should always mount a single pannier on the chain side). This asymmetry is to provide space for the gears.

So once the industry decided to put the chain on the ride, you can’t very well make a group set designed for a left chain if you want it to work on the vast majority of frames.

Re: Muse Spark 1.3

#219

Post by Gigachad »

polyterative wrote: post #44
vunderba wrote: post #9

Earlier quoted context omitted.

The more generic your prompt, the more generic the response. It's a regression to the "mean" of the training data aka GIGO for AI. It's like when you ask your average person off the street to draw a house - it'll almost always be square with a triangle roof, one door, and two windows. In the pelican/bike example, it's probably a bit of a self-perpetuating snowball too. If the earliest examples were bike left-to-right…

as a kid I did them like this. nobody told me to do that. are we all so similar?

It's just the simplest most recognizable form of a house. Like how a smiley face is so generic and simplistic but everyone will know what it represents. Just two dots and a line yet it's easily and unambiguously understood to represent a human face and a happy emotion.

Re: Muse Spark 1.3

#220

Post by Aurornis »

ryanschaefer wrote: post #203

For all of the comments about training: I thought that subscription plans for other models allow the same. Am I mistaken?

It's a toggle. Some will automatically enable it and you have to turn it off. People who rapidly click through setup flows can miss it and leave it enabled.
Post reply on HN