Jump to content
Hak5 Forums

Digitally Colourful Mistifier

  • Content count

  • Joined

  • Last visited

About Digitally Colourful Mistifier

  • Rank
  1. SDR Noob alert: choppy audio output

    Correct, that was the answer. When playing with SDR on a VM you can get messed up results. This is caused by the virtualisation layer, it slows down a whole number of things including USB-connections and audio-output. It was the latter which caused the error in my case. I discoverd I could fidle a little bit with the output sample rate (make it a little higher than 48Khz) which solved the audio-underrun problem, but which then in effect caused CPU-overrun :-). So yes, the solution to my problem was installation on a bare metal box.
  2. SDR Noob alert: choppy audio output

    Hi, I just got started with the HackRF One and it's really fun. I'm following the lessons at greatscottgadgets.com but with lesson 1 I'm already facing some issues I just can't seem to get solved on my own. The problem I'm facing is the classical 'choppy output' of the audio when demodulating FM radio. The schema that we're supposed to build is explained in great detail at https://greatscottgadgets.com/sdr/1/. I followed all the steps, I think my schema is exactly as what he told me to build, but still I'm getting choppy output, for as far as my googling learned me anything this means that I've messed up the sample rates at some point. It's not that my hardware can't keep up with the rate, already checked that by lowering the rate to ridiculously low levels but that didn't help to solve the choppy output. Anyone having some hints for me? I've included a screenshot of my workflow: My setup looks like this: - Physical machine is a recent macbook pro with 8GB RAM and 4 cpu-cores running OSX Sierra - Virtual Machine is a Debian 9 with 3GB RAM and 1 cpu-core
  3. Mapping a keyboard to a new propperties-file

    Hi, I'm trying to use a ducky to automate some stuff on a macbook :-) But it has this funky Azerty layout (see image). I encoded it with "-l resources/be.properties" and that worked fine, except for one character: the at-sign "@", this renders as "ë". So I was thinking, maybe I should create a properties-file for this keyboard layout. But how do I do this? Any thoughts?