Unavoidable HDMI recording audio glitches and their fix

Been noticing some unavoidable noise when capturing from a certain HDMI source. It always sounds like scrunching up a newspaper, happens about once per 20 minutes (if at all), and looks like this in Audacity:

I don't ever hear it watching it live; it's just in the recording. I've found ripping the raw wav and loading it in Audacity is both the best way to find the glitch at all, as well as the only way to fix it. So at this point I recapture and get a clip of the audio without the glitch, and replace this audio. 

This is already zoomed in, but I like to zoom in even further, to the point where the thin lines of the waveform become thick again. Then I just line up the audio and mute out the bad portion. It's sort of touch-and-go at this point; it's not as easy as it should be. I try to find an identifiable peak, trim the clean audio, move the cursor to the top (bad audio), and mute. Maybe not even that order. 

In AviSynth, I load like this: 

rawfile1v=LWLibavVideoSource("Untitled 115.avi")
rawfile1a=LWLibavAudioSource("Untitled 115 fixed.wav")
AudioDubEx(rawfile1v, rawfile1a)
stream1=last
rawfile1=last

Another problem I had was Blackmagic Media Express not recognizing audio from certain sources, such as:

• RetroTINK-5X Pro into OSSC Pro (individually, both scalers would work fine)

• EZCOO 4K splitter with manual downscaling

• RetroTINK-4K Pro with HDMI input, e.g. PSTV + splitter (even if I would get audio from a component source just fine)

My solution was to run the HDMI output into an HDMI + Audio Converter box, connect that to an HDMI Audio Embedder using a S/PDIF optical cable, and then finally to the capture card. 

My equipment chain, for the curious. And might I add, Google Drawings was plenty enough for this. Just had to set the canvas to a reasonable size in File > Page Setup (I chose 4K resolution, or 3840 × 2160) and set the measurements to pixels instead of inches, and everything else was easy to understand. I can't believe I wasted time dabbling with Lucidchart which limited the number of shapes I could use and wanted me to pay per month... and they wanted me to pay more per month if I wanted to pay for a whole year! Got rid of that app's permission real fast. 

New final best firmware setups for PSP and Vita in 2026

PSP:

On any model, it's ARK-4. Grab your official 6.61 firmware, remove any trace of former CFW, update to OFW, and add your new ARK-4 CFW. It's even updateable right from the console itself. The firmware even allows for WPA2 (something the PSP didn't originally support), which is absolutely nuts. 

https://github.com/PSP-Archive/ARK-4 Main link

https://github.com/PSP-Archive/ARK-4/wiki/Recommended-Plugins Recommended Plugins, though I don't use all of them myself. 

Vita and PSTV

First things first: it's best to completely eliminate all dependency on Sony's crappy proprietary Vita memory cards. This tutorial shows how to add internal storage on a Vita 1000 without any memory card or PC at all:

1. Run HENlo jailbreak, install Henkaku, and without exiting, replace NEAR with VitaDeploy. System reboots. 
2. Run HENlo jailbreak, install Henkaku, exit, then go to Settings > Henkaku Settings, Enable Unsafe Homebrew. 
3. Run VitaDeploy > Miscellaneous > Create an internal memory card > choose Default 2xxx storage configuration. System reboots.
4. Go to Settings >  Format > Format Memory Card > check Internal Memory Card and format. System reboots. You now have just enough space to Download everything VitaDeploy offers, including Enso if you need to downgrade
• Side note: If you're on the latest official firmware (3.74) and had to downgrade to 3.65 in the first place, you won't be able to fully replace Near when you're on 3.65, if you care about that at all. In my case, the icon was restored but the icon name (unchangeable) still said vdep. The devs recommend disabling firmware spoofing and going back up to 3.74 (which is safe and fine because the internal memory card partition persists across firmware updates). At this point Near should be restored.  You can use that internal memory on your HENlo'd 3.74 to download the version of VitaDeploy that doesn't remove Near, download Enso along with other apps you want from the Downloads menu within VitaDeploy, and you're good. 
5. Use ITLS-Enso (from VitaDeploy) to uninstall and then reinstall the full certificate to regain access to the PS Store.

Reading around, the new partition really is the same "extra memory" that the Vita 2000 and PSTV have, so you're not really losing anything. And the most risky thing (moving across firmwares) has proven to be no issue at all. 

If you're like me and you already had a working homebrew setup with a 4 GB memory card and an SD2Vita, and you wanted to go completely Vita memory card-less, first take note of your bubble layout with a video (none of the bubble manager apps have ever worked for me).. Then you just need to do the following... although this is from memory, so I may be including steps I don't need or missing steps I do need because I was figuring it out as I went along:

1. Shut down Vita and remove original Vita memory card and SD2Vita. 
2. Run HENlo jailbreak, install Henkaku, and without exiting, replace NEAR with VitaDeploy. System reboots.
3. Run HENlo jailbreak, install Henkaku, exit, then go to Settings > Henkaku Settings, Enable Unsafe Homebrew. 
4. Run VitaDeploy > Miscellaneous > Create an internal memory card > choose Default 2xxx storage configuration. System reboots.
5. Go to Settings >  Format > Format Memory Card > check Internal Memory Card and format. System reboots. 
6. Run HENlo jailbreak, install Henkaku, and without exiting, replace NEAR with VitaDeploy. System reboots (but this time, choose to restore). 
7. Shut down Vita, reinsert SD2Vita, and power on. You should have your games again (though need of organizing), while no longer relying on that ticking time bomb that is the proprietary Vita memory card. 

Anyway, on the Vita/PSTV side, you still want 3.65 Enso, which you can downgrade to painlessly straight from the browser. Get started with Henkaku in the browser and click Install. Downgrade to 3.65 and make it permanent with Enso. From there, check my older posts about things you definitely need.

(Jailbreak link again. Why are there so many? https://henkaku.xyz/ or  http://deploy.psp2.dev/ or jailbreak.psp2.dev )

On the PSP side, you want to use Isage's fork for Adrenaline. Stepping back for a bit, although you can apply ARK-4 to the regular Adrenaline, it's only Isage's fork of it that fixes the PSP's recovery mode's autoboot. And having it autoboot the ARK-4 loader is the preferred way to load ARK-4 now because, as the ARK-4 github states, the Adrenaline Bubbles Manager method installs an older version of Adrenaline. That means you don't want to use Adrenaline Bubbles Manager at all anymore. 

Continuing, you want to use Game Categories Lite v1.7-js1 by Ticky, making sure to add and enable it in VSH.text and PLUGINS.txt, then going into the XMB Settings (and ARK-4 Plugin Manager) to make sure it's on. This fork is the version recommended by the ARK-4 team (linked above). 

https://github.com/isage/Adrenaline/releases/tag/v7.1.7

https://github.com/ticky/game-categories-lite/releases/tag/1.7-js1