[hpsdr] TeamSpeak audio 2013/June/29

[AA8K73 GMail]

The 29/June TeamSpeak mp3 (42 minutes) 64 kbps is available at:

< http://www.hamsdr.com/dnld.aspx?id=1410 >

or

< http://www.hamsdr.com/dnld.aspx >


Text to follow:

20:50:50>  *** You are now talking in channel: "OpenHPSDR"

21:04:16> "Greg ZL3IX": Rick, remember that version has 
implemented the option to take Tune power from the band setting. 
  It works just fine

21:04:29> "Bill - KD5TFD": Worked all Coolers @ FD here

21:05:45> "Rick - VE3MM": Hi Greg, tnx for the heads up on the 
tune power setting.  I did not know this.

21:06:01> "Rick - VE3MM": Bill, congratulation on the WAC award!

21:06:32> "Greg ZL3IX": I was always nervous about not knowing 
what the drive level was going to be before I hit the Tune button!

21:10:32> "Bill - KD5TFD": interesting ... would be interested 
to know how hard/easy it was to do the disector?

21:12:34> "Jeremy - NH6Z": It's not extremely hard.  It's just 
going to be tedious to classify the bits.

21:13:23> "Jeremy - NH6Z": And partially the protocol has some 
hinkiness that's maybe going to make it more hairy.  Like I 
guess I don't recall us using the same opcode for "start" and 
"stop."

21:13:50> "Bill - KD5TFD": That makes it hard for a disector?

21:15:11> "Jeremy - NH6Z": Only from the aspect of that I can't 
tell you whether that packet is a "start" packet or a "stop" 
packet, because they're exactly the same.

21:15:46> "Bill - KD5TFD": Label it start/stop and let the user 
sort it out from context?

21:15:56> "Jeremy - NH6Z": Yeah.  That's what I'm going to have 
to do.

21:16:15> "Jeremy - NH6Z": I'm trying to avoid the "sort out 
from context" though.  It was part of why to write the code in 
the first place. ;)

21:16:33> "Bill - KD5TFD": ya

21:16:55> "Jeremy - NH6Z": We'll see how it turns out.  Doing 
simple stuff first followed by more complex.

21:17:28> "Bill - KD5TFD": certainly will be a helpful bit .... 
something we should have done a long time ago I suspect

21:18:12> "Jeremy - NH6Z": It's one of those "not necessarily 
very fun" pieces of code that everyone puts off.

21:19:12> "Bill - KD5TFD": Ya .. I'm usually pretty good for 
writing tools to help dev't .... just never had the write combo 
of time and motivation for this one

21:19:48> "Jeremy - NH6Z": The compile-time environment isn't 
necessarily easy to get set up.  You essentially have to compile 
it from source to get the plugin compilation environment.

21:20:29> "Bill - KD5TFD": ya ... was wondering what the startup 
cost on it was ..... for linux that may not be that bad ... for 
windows I suspect it might be a bear

21:21:00> "Jeremy - NH6Z": They have some fairly detailed 
instructions in their "developers" document, so I don't think 
it's going to be that bad.  MacOS is going to be another story I 
think.

21:22:01> "Bill - KD5TFD": Wireshark as an X app or native MacOS?
I've used it as an X app on Mac ... not particularly pretty, but 
works

21:23:20> "Bill - KD5TFD": ? VFO=14.300000?

21:30:50> "Ken - N9VV": Windows 8.1 preview loaded on this Dell 
and working FB.

21:32:07> "Jeremy - NH6Z": brb

21:34:16> "Jeremy - NH6Z": back.  Realized I didn't have my 
Hermes even hooked up after I took it to FD.

21:40:12> "Jeremy - NH6Z":
http://www.nh6z.net/Files/wireshark.tiff

21:40:22> "Jeremy - NH6Z": That's what it ends up looking like 
with the "command" parsed out at least.

21:42:28> "Ken - N9VV": mITX Atom 330 fits neatly into a USPS 
envelope

21:50:21> "Bill - KD5TFD": fails for me as well