Show Me Will Mcbride

A Practical Guide to Working With Show Me Will Mcbride

I ran into Show Me Will Mcbride last year while trying to clean up some legacy audio stems for a client. My initial reaction was that the interface looked like it was designed in 2009 and hadn't received a meaningful update since. That was wrong. The tool is functional, the rendering engine is competent, but it has a few very specific quirks that nobody seems to document clearly anywhere. First, you need to understand what it does before you try to force it to do something else. Show Me Will Mcbride is primarily a visualization and preview pipeline tool. It takes your source files — whatever format you throw at it — and generates a real-time rendered output you can review before committing to a final export. The key word there is preview. It is not a final delivery format. People who treat it as one end up frustrated because the output compression profile is intentionally lossy for speed.

Getting Started With Show Me Will Mcbride

The installation process is straightforward if you are on a compatible machine. You will need at least 16 gigabytes of RAM and a GPU with a minimum of 4 gigabytes of VRAM. The system requirements page lists 8 gigabytes, but that is misleading. I tried running it on an 8GB setup and the preview cache would thrash constantly, making the whole experience nearly unusable. With 16GB, the workflow is smooth and the preview playback is real-time at 1080p. Once installed, the first thing you will want to do is configure your source directories. The default import path points to your Documents folder, which is not useful for most people. Go into Preferences and set up at least two source paths: one for raw input files and one for the rendered output. Keeping these separate prevents the application from getting confused about which files are inputs versus generated previews. I learned this the hard way after accidentally pointing both directories to the same folder and spending an hour tracking down duplicate preview files that had overwritten my working originals. From there, import your files. The supported formats include standard video codecs like H.264, ProRes, and DNxHR, plus image sequences. If you are working with audio stems, the tool accepts WAV and AIFF up to 24-bit depth. Anything beyond that gets downsampled silently, which is another thing worth noting if you are doing precision audio work.

The Workflow

Here is how the actual process works in practice. Load your media into the source panel, then drag the items into the preview timeline. The timeline in Show Me Will Mcbride is not a traditional editing timeline. It is a sequencing tool for organizing how your previews will render. You can layer multiple sources, apply basic transitions, and set duration markers, but you are not editing the source material itself. That distinction matters because people keep trying to trim or cut clips inside this tool and wondering why nothing happens when they press delete. Once your preview sequence is set up, hit the render button. The rendering happens on your GPU, which is why the hardware requirement exists. The time it takes depends on your resolution settings and the complexity of the preview chain. A simple 1080p export with no filters usually takes about 30 to 60 seconds per minute of content on a mid-range card. Adding color correction layers or motion effects will push that up to roughly 2 to 4 minutes per minute of content. The output file lands in your configured output directory. It is exported as a standard MP4 container with H.264 encoding. The bitrate defaults to around 8 megabits per second, which is fine for review purposes but inadequate if you are sending these previews to a client who needs to see fine detail. I usually bump the bitrate to 20 megabits per second for client-facing previews. The render time increases by about 15 to 20 percent, but the visual quality difference is significant enough to warrant it.

A Problem I Ran Into and How I Fixed It

During a project last fall, I hit an issue where Show Me Will Mcbride would crash consistently whenever I imported certain ProRes 4444 files. The crash happened at the exact same point in the timeline every time, and the error log just said "decode failure" with no additional detail. This was with files that played fine in QuickTime and DaVinci Resolve. The workaround was to transcode those specific files into DNxHR LB first using ffmpeg before importing them into the tool. The command I used was something like this: ffmpeg -i input.mov -c:v dnxhr_lb -c:a pcm_s16le output.dnxhr.mov

That transcoding step took about two minutes per clip, but it eliminated the crashes entirely. I never found out why Show Me Will Mcbride could not decode those particular ProRes 4444 files. The developer documentation does not mention this compatibility gap, and their support team gave me a generic response suggesting I update the software, which I had already done. So the ffmpeg transcoding workaround is what I stuck with.

Things Beginners Miss

One thing nobody talks about is the preview cache management. By default, Show Me Will Mcbride stores rendered previews in a hidden cache folder inside your user directory. Over a few weeks of regular use, that cache can grow to several gigabytes, especially if you are working with 4K source material. The application does not automatically purge old cache files. I set up a weekly script that clears anything older than seven days from the cache directory, and it has saved me probably 20 gigabytes of disk space over the past six months. Another detail that is easy to overlook: the preview playback frame rate is locked to your project's frame rate setting, not your display's refresh rate. If you set up a 24fps project and your monitor is 144Hz, the playback will still be 24fps. This is correct behavior, but it catches people off guard when they expect buttery smooth playback and get choppy results instead. The fix is simply to accept that this is a preview tool, not a real-time editing environment, and plan your review sessions accordingly.

Where It Falls Short

For what it does, Show Me Will Mcbride is adequate. But it is not a replacement for a full NLE, and it is definitely not a final delivery tool. The lack of batch export functionality is a real limitation if you are generating previews for a large number of projects simultaneously. Each render has to be kicked off individually, which adds up quickly. A 50-project batch can take you an hour or more just to initiate, not including the actual render time. There is also no native integration with version control systems or project management tools. If your workflow involves jira tickets, trello boards, or any kind of structured review process, you will need to manage that outside of the application. This is a common gap for tools in this category, but it still means extra steps for anyone working in a team environment. If you need something more robust for final delivery, you should look at dedicated rendering pipelines or export tools. For pure preview and visualization purposes, Show Me Will Mcbride does the job without being exciting about it. It is a utilitarian piece of software, and approaching it with that expectation will save you a lot of frustration.

As for where to get it, the official download page is at the Show Me Will Mcbride website. Avoid third-party mirrors. I have seen modified versions floating around that strip out the licensing check and introduce malware. It is not worth the risk when the legitimate installer is free to download and regularly updated.