Unlocking the TEAC HDB850: Cheap, Cheerful, and Surprisingly Capable PVR

June 13, 2025

 

Logo

A few years ago, I picked up a budget TV tuner from Costco (Melbourne) — the TEAC HDB850. At just $40, I wasn’t expecting much more than a basic free-to-air digital tuner. But after spending some time with it, I found it to be a surprisingly handy device, especially for its USB-based PVR (Personal Video Recorder) feature.

In this post, I’ll walk through why the TEAC HDB850 caught my attention, what makes its recording feature interesting, and how you can easily join its multi-part video files into a single playable video — for free.


The Device: TEAC HDB850 PVR

At its core, the HDB850 is a digital set-top box with one job: tune in free-to-air channels. It connects to your LCD TV and acts as a digital tuner — and oddly enough, it seems to output a cleaner picture than most built-in TV tuners, particularly with our local 720p channels. This could be due to light filtering or some minor image processing, though that's just a guess.

What really sold me, though, was the recording feature.


Recording That Just Works — and Is Open

Unlike many PVRs that use proprietary or encrypted formats, the TEAC HDB850 records directly to AVCHD (MTS) format, split into ~500MB chunks. That’s roughly 15 minutes of video per file.

Better still — the files aren’t encrypted. You can drop them into Windows Media Player, VLC, or any modern video player and they’ll play without a hitch. That is, unless you're hoping to watch the full recording all at once. Then, you hit a snag.


The Problem: Chunked MTS Files

The recordings are saved as multiple `.MTS` files:

  • `SHOW.MTS`
  • `SHOW.MTS1`
  • `SHOW.MTS2`
  • ...
  • Players don't inherently recognize these as a sequence, so they’ll stop after each chunk. Even the TEAC HDB850 itself has a slight pause between segments during playback, and fast-forwarding near the end of a chunk can cause it to lose track of where you are.

    So I went looking for a fix — a simple way to merge these MTS files into one seamless video.


    The (Free) Solution: File Joining Without Re-encoding

    As a programmer, my instinct was to dive into the file structure. But to my surprise, there was no complex wrapper or headers — you can literally just concatenate the files. No decoding, re-encoding, or special formatting needed.

    So I hunted down a free tool that could handle this kind of binary file join — and found a great one:

    👉 **IgorWare File Joiner**

    (Available in both 64-bit and 32-bit versions)


    How to Join MTS Files from the TEAC HDB850

    Here’s how to stitch your recordings into a single playable file:

    1. Download File Joiner

    Head to the IgorWare website and download the version that matches your operating system (64-bit or 32-bit). No installation needed — just extract the `.RAR` file using WinRAR or 7-Zip.

    2. Add Files in Order

    Launch the app and drag your `.MTS`, `.MTS1`, `.MTS2`, etc., into the window.

    Important: Make sure they are in the correct order! Disable the “Auto” sort option if needed.

    3. Set Output Name

    By default, the tool uses the name of the first file for the output. I recommend manually entering something like `SHOW-FULL.MTS` to avoid overwriting.

    4. Join and Enjoy

    Click Join and wait for the tool to do its magic. You’ll end up with a clean, continuous `.MTS` file that can be played back in your favorite media player with no gaps, sync issues, or pauses.


    Bonus Tip: Using Dual Tuners

    The HDB850 only has a single tuner, meaning you can't watch one channel while recording another — unless you get clever.

    By using the antenna pass-through, you can connect the HDB850 between your antenna and your TV:

    Antenna → TEAC HDB850 → TV
    

    Then, simply switch your TV input between the TEAC’s output and the TV’s built-in tuner. This way, you can:

  • Record a show on the TEAC
  • Watch another channel via your TV’s tuner
  • Do both without interrupting either stream

  • Final Thoughts

    The TEAC HDB850 may not be the flashiest gadget on the shelf, but it’s a surprisingly flexible and open device for its price. The ability to record free-to-air digital TV to open, portable formats like .MTS, and join them without specialized software or re-encoding, is rare — especially in the low-budget range.

    If you’ve got one of these lying around, or find one second-hand, it’s still a useful tool for casual recording and playback.

    Hopefully, this guide helps you make the most of yours!


    Have you used the TEAC HDB850 or a similar device? Found a better file-joining workflow? Drop a comment — I’d love to hear how others are getting the most out of these little PVRs.

    BASIC Isn't Dead. It Just Grew Up.

    June 01, 2025

     

    Logo

    1. BASIC Isn't Dead. It Just Grew Up.

    If you learned to program in the 80s or 90s, chances are your first line of code looked something like this:

    PRINT "Hello, World!"
    

    To many, BASIC feels like a relic of computing’s early days—an outdated teaching tool overshadowed by modern languages like Python or JavaScript. But that assumption couldn't be more wrong. BASIC never disappeared. It diversified. It evolved. And today, it lives on in a wide range of powerful, practical dialects still being used to build games, web tools, business systems, and more.

    2. What Made BASIC Great Then Still Matters Today

    BASIC was designed to be accessible. Its name stands for Beginner's All-purpose Symbolic Instruction Code, and its creators wanted students to focus on learning to solve problems, not memorizing syntax. That simplicity, that clarity, is what makes BASIC surprisingly relevant even now.

    Today's developers value code that is readable, quick to write, and easy to maintain. Sound familiar? That’s the same philosophy behind modern favorites like Python, Lua, and even aspects of Swift. BASIC got there decades earlier.

    3. Visual Basic: The Face Everyone Recognizes

    No conversation about BASIC is complete without mentioning Visual Basic (VB). Introduced by Microsoft in the early 90s, VB turned BASIC into a powerhouse for Windows development. Its visual form designer and event-driven model made it the go-to language for building business applications and internal tools.

    Even today, VB.NET is still supported in Visual Studio, and VBA (Visual Basic for Applications) remains deeply embedded in Microsoft Office, driving automation and macros across the business world.

    But here’s the key point: Visual Basic is just one dialect. BASIC’s legacy didn’t stop with VB—it blossomed into a wide ecosystem of modern tools, many of which continue to be actively developed.

    4. Beyond VB: The Modern BASIC Landscape

    🎮 Game Development

  • PlayBASIC: Designed for 2D game development with beginner-friendly syntax and graphics built-in.
  • BlitzBASIC / Blitz3D / BlitzMax: Known for real-time game development. Still loved by retro game coders.
  • DarkBASIC: Created to simplify 3D game creation on Windows.
  • ⚙️ General Purpose / Desktop

  • PureBASIC: Cross-platform, compiled language with full support for GUIs, DLLs, and multimedia.
  • FreeBASIC: A modern take on QBASIC with low-level access, C-like performance, and inline assembly support.
  • Oxygen BASIC: Lightweight and powerful, compiling directly to machine code.
  • 📱 Mobile and Cross-Platform

  • B4X: Formerly Basic4Android, B4X now targets Android, iOS, and desktop platforms with VB-like syntax.
  • 🌐 Web, Scripting & Automation

  • VBA: Still widely used in Excel and Access to automate reports, calculations, and workflows.
  • BasicAnywhere: A lightweight BASIC interpreter that runs in the browser.
  • 5. BASIC vs. Python: Different Names, Shared Philosophy

    Many developers praise Python for its simplicity, readability, and gentle learning curve. But that exact spirit was BASIC's mission from day one. The syntax and philosophy of BASIC have more in common with Python than most realize:

    REM BASIC
    PRINT "Hello, World!"
    
    # Python
    print("Hello, World!")
    

    Both prioritize clarity over cleverness. Both are great for beginners and prototyping. BASIC simply got there first.

    6. Why BASIC Still Deserves a Place at the Table

    Modern BASICs aren't just toys. They support features you'd expect in any serious language:

  • Compiled executables
  • GUI frameworks
  • Graphics and sound
  • Cross-platform support
  • Integration with system APIs
  • In many cases, these tools are faster to learn and deploy than bloated stacks involving multiple frameworks and languages. That makes BASIC a compelling choice for hobbyists, indie developers, and even small businesses looking for quick, effective solutions.

    7. Final Thoughts: BASIC Isn’t Just Nostalgia—It’s a Toolset That Works

    The myth that BASIC is obsolete is just that—a myth. While it may not dominate headlines, BASIC continues to evolve, empower, and enable. It never stopped being useful. It never stopped being fun.

    If you're a Python fan, or just want to create something without jumping through endless setup hoops, explore modern BASICs. There’s a whole ecosystem waiting for rediscovery.


    Where to Try Modern BASICs:

  • FreeBASIC
  • PureBASIC
  • PlayBASIC
  • B4X
  • QB64
  • BlitzMax NG
  • Oxygen BASIC

  • BASIC didn’t fade away. It just grew up quietly. And it’s still here—faster, friendlier, and more flexible than ever.



    The Vanishing Value of Software: How Free Culture Undermined Developers

    May 20, 2025

     

    Logo

    The Slow Erosion of Value

    In my experience, this shift didn’t happen overnight. It’s been more like a slow drip — a constant lowering of the barrier to entry for users, paired with rising expectations for what should be freely available. Audiences have grown to want more for less, and that change has reshaped how we, as developers, build and deliver software.

    Back in the 2000s, we used to sell a cross-section of Windows applications. These were typically released as shareware — fully functional, but with some kind of limitation. Maybe it was time-limited, or perhaps certain features were locked behind a registration key. If the user found value in the software, they could unlock the full version. Simple. Fair.

    At the time, a whole ecosystem of download sites existed to support this model. They acted as distribution hubs, allowing users to discover new software, try it out, and purchase it if it met their needs. It wasn’t perfect, but it worked. There was a clear value exchange: software solved a problem, and users paid for that solution.

    This wasn’t about open source or a “free software” movement — it was about sustainable software distribution.

    But then something started to change. Bit by bit, developers began offering more generous free editions, trimming fewer features, removing time limits, or even offering entire lite versions for free. Some split their products into different strands entirely — one version for casual users with basic needs, and a paid version for power users or professionals.

    Some argue piracy pushed developers toward these new models — forced them to adapt. Instead of relying purely on software sales, revenue started shifting to alternative strategies: paid support, in-app advertising, bundled services, or, in more cynical cases, harvesting user data. Whatever the motivation, the result was the same: the perceived value of software continued to drop, and expectations shifted with it.


    The Great Vanishing Act: Social Media and Search Engines

    While developers were adjusting to the “race to free,” another tectonic shift was quietly unfolding: the collapse of discovery.

    There was a time when building something useful and publishing it online gave you a decent chance of being seen. Early search engines, though far from perfect, prioritized relevance and freshness. Social media promised a new kind of reach — direct connection with users, fans, customers. For a while, it worked. A tweet, a blog post, a forum thread — these could ripple outward and find real people who cared.

    That era is over.

    Today, social platforms have devolved into throttled silos. You can have thousands of followers and still struggle to get a dozen views on a post unless you play the algorithm game — or pay to “boost” visibility. Engagement is driven not by merit, but by outrage, meme-ability, or timing. Even “communities” feel less like towns and more like haunted malls — full of recycled content, echo chambers, or silent scroll-bys.

    Search engines aren’t any better. Try looking up a specific kind of software or development tool today, and you’re greeted by a wall of SEO-optimized garbage: faceless blog farms, AI-generated summaries, affiliate-heavy “Top 10” lists that have no real insight — just endless noise. Organic discovery has been buried under monetization and manipulation.

    The irony? We’ve never had more content — more apps, more tools, more creativity online — yet reaching an actual human being with something honest and useful is harder than ever.

    This has huge consequences for developers. Building the software is only half the battle now. You also need to master the dark art of content marketing, navigate shifting social trends, stay in the good graces of opaque algorithms, and somehow still find the energy to keep your codebase from collapsing under constant platform churn.

    It’s exhausting. And it’s no wonder so many indie developers quietly disappear — not from lack of talent, but from a lack of reach.


    The Distorted Value of Software

    Software used to be seen as a product — a tool someone built, tested, and sold, like any crafted item. There was a clear sense of value: a developer solves a problem, and the user pays for that solution. Simple economics. But somewhere along the line, that model fractured. Platforms didn’t just disrupt the way software was distributed — they rewrote the rules of what people think software is worth.

    Take mobile apps, for example. The rise of app stores introduced convenience and global reach, but also drove prices into the ground. Suddenly, developers were competing not just with other paid apps, but with free everything. To survive, many had to shift to freemium models — giving away core features and gating the rest. But the damage was already done: users were being trained to expect entire applications for nothing.

    That expectation didn’t stay confined to mobile. Over time, it spread across platforms. “Free” became the standard — not because it made sense, but because the platforms that mediate access to users profit from volume, not value. Apple, Google, Meta, and others don’t care what your software costs — they care about engagement, data, and ad revenue. The more things people download and interact with, the better for them. Whether a developer gets paid is incidental.

    This distortion leads to absurd outcomes. A user might spend $6 on a coffee without thinking twice, but scoff at a $3 app that took six months to build. They'll binge hours of free software reviews on YouTube — funded by ads — but balk at a one-time purchase that supports a real creator directly. In this environment, even a fair price feels like a violation of some unwritten rule: “It’s digital — why should I pay?”

    And this is where the rabbit hole goes deepest: users have internalized the platform’s values. If it’s not free, it’s suspect. If it’s not viral, it’s invisible. The only way to “win” is to give away your work, and hope to monetize later — maybe through donations, maybe through volume, maybe through some yet-to-be-invented hustle.

    But real software — thoughtful, original, and well-supported — takes time. It takes energy. And when its value is constantly questioned, or ignored altogether, the system doesn’t just fail developers — it fails users too. Because eventually, good software stops getting made. Or worse: it only gets made by companies whose real product is the user, not the tool.


    Where Does This Leave Developers Now?

    For developers — especially independents — the ground has never felt more unstable. The tools have improved, the platforms have multiplied, and the audience has grown — and yet, it’s never been harder to make a living from software.

    The modern indie dev wears every hat: builder, tester, designer, marketer, customer support, social media presence, and content creator — all while contending with users who expect polished, cross-platform functionality for free. You can put in six months building something genuinely useful, only for it to be dismissed in five seconds because it’s not free, or not popular, or not ranking on some algorithmic feed.

    Worse still, the platforms themselves offer no consistency. One week your app or tool goes semi-viral and you think, Maybe this is it. The next week, your reach vanishes. No explanation. No recourse. Just silence.

    This is the new normal: developing in a vacuum, with no guarantee that effort equals outcome.

    Some developers adapt by chasing virality. Others go niche, hoping to find a small but loyal user base. A few still cling to the old model of pay-once licensing, trying to educate users about the value behind what they’re getting. But increasingly, developers are being nudged — or forced — toward models that don’t prioritize craft or utility, but engagement: ads, subscriptions, bundles, data collection, or selling their soul to platform-specific ecosystems.

    That’s not sustainability. That’s survival.

    It’s a kind of slow-burn burnout that creeps in — not because the work is hard (it always was), but because the reward structure no longer makes sense. You create something valuable, but the market’s mechanisms for recognizing that value are broken. And when developers can’t even get feedback — can’t even get seen — the silence becomes louder than criticism.

    Some quit. Some pivot. Some keep going, out of habit or hope. But nobody can honestly say the system is working for the people who build things anymore.


    What Now?

    I don’t know what the answer is — but it’s definitely not more of the same.

    The landscape we once knew has eroded, almost imperceptibly, under our feet. Choice has been quietly stripped away. The transition from independent websites to the social media monoculture wasn’t just about convenience — it was a wholesale loss of autonomy. The old ecosystem — messy, diverse, and full of personality — gave way to a handful of centralized feeds where everything looks and feels the same.

    And that’s the real tragedy: today, many developer sites aren’t homes anymore — they’re just link portals. Buttons to app stores. Embeds from Discord servers. A “community” reduced to comment threads in algorithm-driven silos. We used to build hubs that welcomed users in, that told a story, that taught people what the software was and who it was for. Now? You’re just funnelling people toward a store page and hoping they don’t bounce.

    As more of those independent sites disappear, so does our collective presence. The ripple effect kills discoverability. Search engines become even more hollow — fewer developer-run pages, fewer backlinks, less context, less authority. Everyone gets drowned in noise, and only the biggest platforms benefit.

    There is one thing we can do: keep our homes alive.

    Keep your independent site up. Keep publishing. Keep documenting your software, your thought process, your updates — even if only a handful of people read it. Link to other indie devs you respect. Drive traffic toward them. Treat your site not just as a billboard, but as a hub — something living and worth revisiting.

    It might not change the tide overnight. But every site that stays online is one more light in the dark — and if we’re going to rebuild anything, that’s where it starts.


    💬 Join the Conversation

    Have you noticed the shift in how people value software?

    Are we losing more than just revenue in this age of “free”? I’d love to hear your thoughts.

    Leave a comment below or reach out on X.com — let’s talk about where indie software goes from here.

    If this article resonated with you, consider subscribing or exploring more posts on the changing landscape of software development and digital culture.