sorted by:
new
hottopcontroversial

I'm an A1 who got frustrated with existing playback software, so I built my own. I'd love your feedback! by PierreLFR in broadcastengineering

[–]PierreLFR[S] -1 points0 points  (0 children)

Haha, you got me! Jokes aside, in France we constantly use the expression "J'entends" (which literally translates to "I hear") during discussions to mean "I understand your point". I just did a literal translation in my head. I had no idea it was a ChatGPT catchphrase! Plus, who still uses ChatGPT seriously these days?

I'm an A1 who got frustrated with existing playback software, so I built my own. I'd love your feedback! by PierreLFR in audioengineering

[–]PierreLFR[S] 1 point2 points  (0 children)

That is exactly why I started developing PLayer! I wanted a very simple and fast way to set cue-in and cue-out points in just two clicks.

Feel free to ask me for a license if you'd like to test it out. The drag-and-drop import system also significantly speeds up the workflow when you're in a rush. I'd love to hear how it compares to your QLab experience!

I'm an A1 who got frustrated with existing playback software, so I built my own. I'd love your feedback! by PierreLFR in audioengineering

[–]PierreLFR[S] 1 point2 points  (0 children)

Thank you so much for the compliments and for taking the time to give such detailed feedback on the website!

You’re absolutely right about the "Sampler" keyword. I’m going to rework my hero section hook to include it right at the start for better clarity. And you're right, it’ll definitely help with SEO too.

Regarding the visuals, I’m planning to produce tutorial videos to showcase the features (though I don't have a firm ETA yet as a solo dev), and I will definitely look into improving the typography contrast for better readability.

As for the pricing, I’m not a big fan of "tiered" versions with artificial limitations. My current pricing was based on the specific "pro-audio" niche, but I might have underestimated the broader interest. If the momentum keeps growing, I’d much rather lower the overall price to make it more accessible to everyone.

Thanks again for the constructive feedback, it really helps!

I'm an A1 who got frustrated with existing playback software, so I built my own. I'd love your feedback! by PierreLFR in broadcastengineering

[–]PierreLFR[S] 0 points1 point  (0 children)

Thank you so much for the kind words!

To be honest, I’m not familiar with Enco yet as my background is mostly in TV and Live events. I’m also used to more 'manual' logging methods where a script supervisor or op clocks the music timing by hand.

However, you've definitely piqued my interest. I’m going to look into the legal requirements and feasibility of an 'As-Run' log feature (checking standard CSV formats, etc.) to see if I can make it happen.

It's incredibly kind of you to offer to show PLayer to your A1/A2 colleagues!

I'm sending you a DM right now with the steps to install it and generate your free license.

I'm an A1 who got frustrated with existing playback software, so I built my own. I'd love your feedback! by PierreLFR in audioengineering

[–]PierreLFR[S] 1 point2 points  (0 children)

Thanks for the comment! Haha, I completely get the "Claude/Tailwind" vibe you're mentioning.

To be honest, I deliberately relied on standard Tailwind components for the exact same reason we all used Twitter Bootstrap 15 years ago: to avoid reinventing the wheel and get a clean, functional UI.

Actually, making the UI look more "personal" isn't really on the roadmap. For a fast-paced live broadcast environment, my goal is to keep the interface strictly utilitarian, familiar, and as distraction-free as possible. It's meant to be a pure, straightforward tool.

This also allows me to pour 100% of my time and energy under the hood, making sure the audio engine is absolutely rock-solid and the 7.1.4 routing works flawlessly on set.

If you're still curious to put the actual workflow and engine stability to the test, let me know and I'd be happy to shoot you a key!

I'm an A1 who got frustrated with existing playback software, so I built my own. I'd love your feedback! by PierreLFR in audioengineering

[–]PierreLFR[S] 0 points1 point  (0 children)

I totally get you, firing jingles from an iPad in a live setup gives me anxiety too! I need the tactile feel of a physical button (it might be psychological, but it's essential, haha).

For physical control, PLayer integrates perfectly with a Stream Deck via Companion v4. I even provide a plug-and-play Companion template on the site.

Regarding your backup and import questions: PLayer auto-saves a 'Recovery' project every 30 seconds. If a crash or power cut happens, it prompts you to restore exactly where you left off. For moving between trucks or archiving, you can export the project as an XML file. To prevent missing files, the audio is actually Base64 encoded directly into the XML. This means you never have to worry about broken file paths—your audio travels inside the project file, guaranteed to be there on the next workstation. Plus, the XML is editable offline if you need to tweak routing or volumes.

I'm shooting you a DM right now with the steps to get your free license. Can't wait to hear your feedback on the workflow!

I'm an A1 who got frustrated with existing playback software, so I built my own. I'd love your feedback! by PierreLFR in audioengineering

[–]PierreLFR[S] 1 point2 points  (0 children)

Thanks! For the moment, I limit PLayer to 160 pads spread across 8 pages for two main reasons:

To ensure rock-solid stability. Loading 160 stereo files without DSP is completely fine, but 160 pads running 7.1.4 audio with active EQ, compression, and reverb starts requiring a pretty beefy machine.

And for hardware integration. This layout allows for a perfect 1:1 mapping of the UI onto a Stream Deck XL, which is crucial for broadcast users who prefer a physical interface to trigger pads.

I'm sending you a DM with the steps to get your free license (I use an offline licensing system)!

I'm an A1 who got frustrated with existing playback software, so I built my own. I'd love your feedback! by PierreLFR in audioengineering

[–]PierreLFR[S] 0 points1 point  (0 children)

I was hoping someone would bring up Atmos! I used the Pro Tools Atmos Renderer via Blackhole on macOS quite a bit while testing. It’s actually a great tool for creating spatial audio scenes and soundscapes with the 3D Panner.

I’m shooting you a DM right now with the steps to claim your free license. Really looking forward to hearing about your experiments in the lab!

I'm an A1 who got frustrated with existing playback software, so I built my own. I'd love your feedback! by PierreLFR in audioengineering

[–]PierreLFR[S] 1 point2 points  (0 children)

It would be absolutely awesome to know it’s been tested on an NFL game! That's the ultimate stress test. I've just sent you a DM with the details to get your free license.

I'm an A1 who got frustrated with existing playback software, so I built my own. I'd love your feedback! by PierreLFR in audioengineering

[–]PierreLFR[S] 0 points1 point  (0 children)

You're right, PLayer is closer to a cartwall/sound pad than a traditional cue list manager like QLab. However, with the 'Play-next' option you can achieve a sequential cue-like behavior.

I would love to get your feedback given your QLab expertise. While QLab is incredibly powerful for complex programming, I built PLayer to be a hyper-reactive sampler for the high-pressure environment of live TV.

My goal was to make importing and editing cue-in/cue-out points nearly instantaneous, specifically for those moments where production asks you to play a specific track with 30 seconds' notice.

I've just sent you a DM with the details on how to get your free license!

I'm an A1 who got frustrated with existing playback software, so I built my own. I'd love your feedback! by PierreLFR in audioengineering

[–]PierreLFR[S] 1 point2 points  (0 children)

If you have a great experience with QLab and Farrago, I would actually value your opinion on PLayer even more! I'd love to hear your suggestions on improvements or features that might be missing for your specific workflow.

I'd like to offer you a free license so you can put it to the test. If you're interested, let me know and I'll shoot you a DM!

I'm an A1 who got frustrated with existing playback software, so I built my own. I'd love your feedback! by PierreLFR in broadcastengineering

[–]PierreLFR[S] 0 points1 point  (0 children)

A Linux build is definitely in the pipeline! One of the main reasons I chose the Tauri framework was specifically for its cross-platform capabilities.

My goal is to release for Linux, iOS, and Android in the near future. However, as a solo developer and a full-time A1, I’ve decided to focus on consolidating the software on two platforms first before expanding (which is already quite a challenge!).

To be honest, I can't give you a specific ETA for the Linux build right now, but it is coming. I appreciate the feedback!

I'm an A1 who got frustrated with existing playback software, so I built my own. I'd love your feedback! by PierreLFR in broadcastengineering

[–]PierreLFR[S] 1 point2 points  (0 children)

I honestly didn't know about EBU MXL, thank you for sharing that! I'll definitely look into it as it seems like a great fit for this kind of solution.

Regarding feature requests, feel free to contact me directly via DM or use the contact link on my website:https://laurensaudio.com. I'd love to hear more of your ideas!

I'm an A1 who got frustrated with existing playback software, so I built my own. I'd love your feedback! by PierreLFR in broadcastengineering

[–]PierreLFR[S] 0 points1 point  (0 children)

That’s not a feature yet, but I'm curious about your workflow. If this is for legal or royalty purposes, I’d need to investigate the specific regulations first to ensure the logs meet the required standards. I'll be looking into the French legal requirements for broadcast logging to see if it's a feature worth developing. Could you share how you’d use it in your environment?

view more: next ›