Updated Home (markdown)

Home.md

@@ -52,4 +52,23 @@ The output file is going to `/dev/shm`.  You need to be able to write the sample
 So, using that graph I was able to collect several frames with the files stored in `/dev/shm`.
 
 [2] https://github.com/osmocom/gr-osmosdr
-[3] https://github.com/osmocom/gr-fosphor
+
+[3] https://github.com/osmocom/gr-fosphor
+
+= Burst Extraction
+With a recording in hand, it's time to find when the burst starts and how long it's active for.  To view signals this way I prefer to use `baudline` [4].  It's an amazing tool considering it's free.  
+
+Heads up: The images below are going to have *tiny* font settings.  This is an issue with `baudline` on HiDPI displays and I don't have an easy fix.  So apologies in advance!
+
+Before opening the collected file, run `baudline`, right click in the main window, and select `Process` -> `Transform Size` and click `65536`.  This needs to be done if your file is over a few hundred MBytes or the app will just crash after trying to open the file. 
+
+Now right click in the main window again and select `Input` and click `Open File`.  The navigation menu is *very* old school.  The left side is directories, and the right side is files.  Navigate to where you saved the collect using the left pane, and the select the file by clicking it once in the right pane.  Then make sure that the `File Format` dropdown is `Raw` and click `Open`.  Failing to change the file format will result in an error when you click `Open`
+
+![image](https://user-images.githubusercontent.com/4240543/162873611-71b995eb-aaa1-47a3-9c98-5e504a6441d1.png)
+
+
+A new window will pop up with the signal parameters.  From top to bottom:
+- `Decompression`: `Auto Magic`
+- `Initial Byte Offset`: `0`
+- `Sample Rate`: Change to `Custom` and enter the sample rate (in Hz) of your collected file (mine was 30720000)
+- `Channels`: `2` and check both `Quadrature` and `Flip Complex`