Loading...
Loading...
This video is about building a custom music player using a Raspberry Pi and mentions Raspberry Pi 5, MOOD OS, Raspberry Pi Digi Amp, USB knob, and STL file for 3D printing.
Check the Patreon for links. YT for widescreen. I've been trying to build a little player for a long time, and I kept putting it off until I found a fantastic STL @diyprojects3d , links in the Patreon. With a basic screen, Raspberry Pi, a little audio player, and not that much work, we can install a #moode , which is a music server, and build our own little digital HIFI.
Performance Category
Above Average
Score
4.2/5
Shares: 5/5
Comments: 5/5
Retention: 5/5
Views: 4/5
Likes: 5/5
Followers: 3/5
Script: 2.7/5
Total Views
6332
Likes
278
Shares
10
Comments
48
Duration
8m 44s
For You
6,028
95.2% of views
Personal Profile
133
2.1% of views
Others
82
1.3% of views
Search
70
1.1% of views
Follow
19
0.3% of views
Sound
0
0.0% of views
Views
Likes
Shares
Comments
For You Traffic
Profile Traffic
Search Traffic
Non-Followers
40.0%
2,533 views
Followers
60.0%
3,799 views
13.4% of followers reached
New Followers
5
Performance vs Median
Transcript Available
Perceived Value
54/100
Compared to Average
Average
Run the AI evaluation to identify actions and analyze their impact.
The opening does not quickly tell viewers why to stay. In the first 5 seconds, the script says, "Over the years, I've collected a lot of music..." which is slow scene-setting rather than a sharp promise. The retention data confirms the hook underperformed: retention falls from 100% at 0s to 90% at 1s, 69% at 2s, and 58% at 3s, then to 48% at 4s. Losing over half the audience by 4 seconds strongly suggests the hook was unclear and too indirect.
Open with the end result and the tension immediately. For example: "I got sick of Spotify, so I built a Raspberry Pi music player for my own library—and I'll show you the exact parts and setup." Put the audience, problem, and payoff in the first sentence.
"Over the years, I've collected a lot of music, and I've gone from hard drive to hard drive..."
The script eventually signals who this is for—people with large personal music libraries who want an alternative to Spotify—but that signal arrives late. In the first 15 seconds, the audience is still somewhat broad and unclear. Retention dropping from 100% to 43% by 5s and 30% by 14s suggests many viewers did not quickly realize this was specifically for DIY audio / Raspberry Pi / self-hosted music enthusiasts. Engagement is decent among those who stayed (121 likes and 29 comments on 2,734 views), which suggests the right niche did connect, but too late.
Name the viewer earlier and more explicitly. Try: "If you've got a big local music library and want a DIY Spotify alternative, here's how I built one with a Raspberry Pi." This filters in the right viewers immediately.
"So, of course, like everyone else, I moved over to Spotify. But I don't like Spotify..."
The problem is real and somewhat concrete: the creator has a lot of music, dislikes Spotify, and wants a dedicated player. That is more specific than generic tech talk. However, the pain is still framed loosely and conversationally instead of as one sharply stated operational problem. The retention collapse by 2-4 seconds (69% at 2s, 58% at 3s, 48% at 4s) suggests the problem was not expressed crisply enough to feel instantly compelling.
State the exact problem in one line: "I have terabytes of music on drives, but no good modern player for it, and I don't want to rely on Spotify." One concrete pain point lands faster than a nostalgic lead-in.
"kinda don't really have anything to play it with and iPods and, ah, it doesn't exist."
There is a payoff, but it is muddled and spread across multiple lines: hardware, STL file, Patreon list, MOOD install, and a build process. Viewers are asked to infer what they will actually leave with. The first-15-second retention line shows this clearly: after 10s retention is only 33%, and by 14s it is 30%. That means most people left before the value proposition became clean. The low share count (7 shares) also suggests the payoff did not feel instantly useful or easily transmissible.
Compress the payoff into one sentence: "In this video I'll show you the exact parts, software, and setup to build a Raspberry Pi music player for your own library." Keep Patreon and side mentions out of the opening.
"I'll show you the hardware I'm gonna use, the- where to get the STL file... And then I'm going to go and install MOOD."
Once the build starts, the script contains lots of practical detail: Raspberry Pi 5, Digi Amp HAT, touchscreen, MOOD setup, NAS connection, Trigger Happy, and playlist creation. That supports a mid-level to good value density. But the video is very long at 524.493 seconds, and much of the narration includes filler, repeated phrasing, and side comments. The retention trend in the opening is severe, and the modest total views suggest the content did not sustain broad interest efficiently. The engagement that did happen (121 likes, 29 comments) implies useful value exists, but it is buried in a lot of verbal padding.
Cut filler and reduce setup commentary. Group content into fast chapters: problem, parts, assembly, software setup, final demo. Remove repeated caveats and conversational loops so each 5-10 second segment delivers a distinct useful takeaway.
"I'm going a lot more jank 'cause that's how I roll... I'm trying to just make it work without too much effort."
This script is rich in concrete nouns and implementation detail: Raspberry Pi 5, Digi Amp, DAC, five-inch touchscreen, USB knob, STL, MOOD Audio, NAS, IP address, Wi-Fi, Trigger Happy, playlists, SSH. That gives the video strong operational specificity. This likely helped generate 29 comments from a relatively small 2,734 views, suggesting technically interested viewers had things to discuss. The main reason this is not a 5 is that some details are fragmented, repeated, or not always framed in the most digestible order.
Keep the specificity but organize it into clean buckets: parts list, wiring, OS install, network config, controls. On-screen labels or captions for each named component would make the specificity easier to absorb in real time.
"For this, I'm using Raspberry Pi 5... a Raspberry Pi Digi Amp... a five-inch touchscreen... install MOOD."
The creator sounds like someone who actually built the thing. The script includes firsthand troubleshooting, component choices, trade-offs, and setup decisions. Lines about failed soldering, using software volume, turning off logging, and connecting a NAS build trust. The like rate is solid for the view count, and 29 comments suggest viewers saw enough expertise to engage. This is not a 5 only because some explanations are imprecise or hesitant, which can reduce perceived mastery even when the experience is real.
Keep the firsthand process but tighten the explanations. Add quick proof points like cost, time to build, what failed, and what finally worked. That would make the expertise feel even more authoritative without losing authenticity.
"I did find that Digi Amp+ still exists... For volume type, use software. That worked for me."
The script feels highly human and honest. The creator admits mistakes, says the audio didn't work, calls the build jank, and openly says "Because I can." That kind of imperfection reads as real rather than synthetic. The comments-to-view ratio also suggests the audience likely connected with the personality and honesty. Even though retention was weak early, the people who stayed appear to have responded to the genuine voice.
Preserve the honest tone, but move the strongest authentic line earlier. For example: "I'm not paying for Spotify forever when I already own the music, so I built my own player." That keeps the humanity while sharpening the hook.
"I'm going a lot more jank 'cause that's how I roll."
Many spoken lines are long, hesitant, and packed with interruptions: "uh," "um," restarts, side notes, and unfinished thoughts. That raises the effort required to follow the content in real time. The early retention data strongly supports this: 100% to 69% by 2s and 58% by 3s is consistent with viewers struggling to parse the opening quickly enough. The technical sections also stack multiple concepts before resolving the sentence, which increases load further.
Rewrite spoken lines into short units with one idea each. Example: "I hate Spotify. I own the music already. So I built a Raspberry Pi player. Here are the parts." In the tutorial section, separate actions into step-by-step commands instead of nested explanation.
"Over the years, I've collected a lot of music, and I've gone from hard drive to hard drive, but kinda don't really have anything to play it with..."
The video does move from motivation to parts to build to software to demo, but the path is loose and repetitive. It revisits why, STL notes, jank disclaimers, troubleshooting, and setup details in a way that blurs momentum. The very long runtime of 524.493 seconds makes progression especially important, yet the script does not create frequent payoff beats. The steep early retention decline and low shares indicate that the narrative arc did not feel efficiently paced or structured for TikTok.
Use a clearer sequence: 1) what I'm building, 2) parts, 3) assembly, 4) MOOD setup, 5) final result, 6) what I'd do differently. Add explicit transitions every 15-30 seconds so the viewer feels forward motion.
"First off, uh, why? Why would you do this? Because I can."
Pishoua 🇪🇺Best would be a player that can duplicate Spotify playlists
true
thatnovaguyThis reminds me of volumio. I want to comment you on your soldering. Usually mine ends with a handful of burns and a small fire.
apart from the fire we have the same skills. burnt fingers all round!
(☞ ͡° ͜ʖ ͡°)☞winamp or nothing haha
lol
TheChriswith Jellyfin you can also manage your music 👌 (beside movies and series)
matiazI saw that project here in TikTok and I was wondering if it was really worth buying
if you want a dedicated music device, have time, and a lot of music and its maybe on a shared folder then yes, worth a crack!
matiazNice! Will give it a try, thanks dude
vintage-gayle-guyMoode is great it will quite happily run on a Pi3 a 5 is a bit overkill.
vintage-gayle-guyyou clarified this in the vid 👏
yeah, 5 is a lot. It's all I had :(
vintage-gayle-guyI nice problem to have.
lol
oxnyxwsHonestly had a Ple x lifetime pass for at least 1p years and been very happy with it glad to see people building alternatives
I wish I'd have got a pass back when they were affordable!
Best Of StupidityI self host Navidrome to play my music and I installed tailscale on it so I can use it outside my home network
solid idea, pangolin is my choice
InebriatedHedgehoglook into modded ipods and retro walkmans, its my personal preference
yeah, that was a good option, I wanted something to use my NAS though.
InebriatedHedgehogfair enough! highly recommend music brains and there is another one, if you haven't got a mass tag changer I'll send a rec but I'm assuming you have stuff for that and saying music brains for the general peeps
yeah, I'm going to play around with a lot of things now I have a player.
user9485496336213Music Assistant on a central server seems like a much better option. You can play to various remote players and with the new sendspin protocol turn esp32s into remote players that are perfectly synchronised.
I'll look into that!
WorthSalmonWatching your videos make me want to do it as well. So recently, I created my own homelab (CasaOS on a optiplex). I've been using Navidrome for my music, and I've had no problems with it. Having a blast with IoT projects. Thanks
that's awesome!
2LigmaNutswhy not just use plexamp
Plexamp instead of Moode? I stopped paying for plex and moved to jellyfin so I'm not using it anymore (its better in many ways to JF) but I was having issues.
2LigmaNutsI actually just bought the lifetime pass. as I have a lot of friends and family already setup. so the lifetime pass was a no-brainer for me. But hey, what ever works for you
It's the best way to go, I agree. if I had the pass 100% I'd be a Plex user again.
InebriatedHedgehogalways sus of those lifetime passes these days, I've seen far too many become no longer lifetime
"lifetime" *of a housefly
2LigmaNutsI feel ya, I've used Plex for years for free. So in my mind, giving them 115$ for the while it's going to last was a no brainer. we'll see how long it lasts but every technology only lasts a while.
true
Total viewers and likes aligned with spoken words.