What's the next sequence in this set?

1
11
21
1211
111221

After figuring it out, I couldn't help but want to write a solution in perl. Below is a Perl script that will carry out the progression to 16 lines. Note, this was written to be terse, not readable.

$s = '1';

BLOCK: {
     print "$s\n";

     exit() if ( length( $s ) > 100 );
     
     @nums = split( //, $s );
     @uniq = ();
     $tmp = ();
     
     foreach my $num ( @nums ){
          push( @uniq, $num ) if ( $num != $uniq[-1] );
     }
     
     foreach my $num ( @uniq ) {
          $s =~ s/^($num+)//;
          $tmp .= ( length( $1 ) . $num );
     }
     
     $s = $tmp;
     goto BLOCK;
}

Upon getting them I immediately plugged them into my iPod for a test drive. Oh no! The highs and mids sounded extremely clear, however the lows were nonexistent compared to my Sennheiser earbuds which sound wonderful for the price, with nice highs and mids, along with rich, full bass. It's amazing what kind of sound can be pushed through speakers so tiny!

I knew this couldn't be right so I did some research and I came across some articles that talked about using "headphone amps". I'd never heard of these, and frankly, using an amp with a pair of headphones sounded absurd. I continued reading about them and found that you can build you own if you're into that kind of thing, which I am, but I'm more into instant gratification at this point.

Eventually I ran across some affordable headphone amps from Headroom that got great reviews. Getting over my angst about buying something as absurd sounding as a "headphone amp", I thought I'd give a Total AirHead amp a try. I chose this one because it can be connected to an external power adapter so it doesn't have to rely on it's batteries or a USB connection as the Total BitHead does for power.

WOW! What a difference this little amp made! The low frequencies that were missing before were there in full force now, and everything sounded great across the spectrum. This bit of hardware really makes these headphones shine. I totally recommend checking out these amps if you've got a nice set of headphones, it'll be worth it.

An added benefit that I discovered about this amp is that it has two audio output jacks. So if you'd like to, you can connect two sets of headphones at the same time, however this isn't how I use it. Late last year I moved away from my desktop Linux machine and bought a MacBook Pro to use as my main computer (Love it!). The issue is that my Klipsch ProMedia set of speakers have two mini-jack connectors that plugged into my sound card. One for the front speakers, and one for the rear speakers. The MacBook Pro only has one audio output, so I could only plug in my front speakers, rendering my rear speakers useless.

Total AirHead amp to the rescue! With it's two audio outputs, I can connect the audio out from my MacBook Pro to the Audio in of the amp, and then connect the two jacks from my speakers to the audio outs of the amp! Voila! All four speakers work, albeit not in surround mode. I believe I'll be buying a second amp to leave permanently connected to my speakers. W00t!

The moral of this story is that if you've got nice headphones and love great audio, or need to connect speakers with two mini-jacks to a source with only one output, you need one of these amps....or perhaps two.

import IO
import System
import Directory

main = do
  [recDir] <- getArgs
  printDirectory recDir

printDirectory path = do
  putStrLn path
  contents <- getDirectoryContents path
  mapM_ (\f -> do
      let newPath = (path ++ "/" ++ f)
      isaDir <- doesDirectoryExist newPath
      if isaDir
           then printDirectory newPath
           else putStrLn newPath
      ) (drop 2 contents)

enum
{
     CMD_GET_VERSION, CMD_PLAYLIST_ADD, CMD_PLAY, CMD_PAUSE, CMD_STOP,
}

typedef struct
{
     guint16 version;
     guint16 command;
     guint32 data_length;
} ClientPktHeader;

typedef struct
{
     guint16 version;
     guint32 data_length;
} ServerPktHeader;

my $data = pack( 'SSI', $xmms_protocol_version, $command, $data_length );

enum
{
     CMD_GET_VERSION, CMD_PLAYLIST_ADD, CMD_PLAY, CMD_PAUSE, CMD_STOP
}

enum
{
     CMD_GET_VERSION, CMD_PLAYLIST_ADD, CMD_SOMETHING_ELSE, CMD_DIFFERENT_CMD, CMD_PLAY, CMD_PAUSE, CMD_STOP
}

#!/usr/bin/perl use strict; use warnings; printdir( $ARGV[0] ); sub printdir {      my $dir          = $_[0] ? $_[0] : '.';      my $handle      = ();      my @dirs      = ();      my $i           = ();            print "Directory: $dir\n";            opendir( $handle, $dir );      my @items = readdir( $handle );      closedir( $handle );            shift @items; #Get rid of .      shift @items; #Get rid of ..            @items = sort( @items );            while ( $i = shift( @items ) )      {           if ( -d "$dir/$i" )           {                push( @dirs, $i );                next;           }           print "$dir/$i\n";      }      printdir( "$dir/$i" ) while ( $i = shift( @dirs ) ); }

21-80

21,23,80

or even...

21-80,5900,5800 So now Yavar can scan as many ports and as many kinds of combinations as you might want. I don't know if I want to give Yavar the ability to take this kind of port argument since it seems kinda malicious, however I think it's good to have the ability to do it within the scanning engine, so whether or not this sticks around will remain to be seen.]]> tag:www.aviditysoftware.com,2007://1.11 2005-12-10T16:47:16Z 2007-04-12T17:47:52Z