This is a follow up to my tutorial about setting up a secure shell server on an iPhone. The problem with the first tutorial is that you have to type in your password everytime you want to login. This is can get annoying, especially if you connect a lot. For example, you would have to type in your password everytime you sync your iPhone over WiFi or do debugging on it (more on that later). In this tutorial, I will show you how you can set it up in a way such that you won’t have to type in the password. This tutorial should also work with any SSH server (as long as it is not explicitly disabled), not just on an iPhone.

Passwordless login is very good for convenience and it is relatively secure. It works by generating a private-public key on your Linux PC and copying the public key to the iPhone. Then when you connect, the SSH server checks your private key against the public key, and if they match, it lets you in. You cannot compare a public key with another public key, so if someone steals your iPhone, they won’t be able to get in. Heck, you can even post your public key on your website and let others download it. However if someone steals your private key, then they will be able to get in. So make sure to project your private key! To read more about private-public key authorization, read the Simple Wikipedia page.

Requirements

• Linux based PC. This guide was tested on Ubuntu Lucid. Also a Mac OS X computer might work also, I have not tried.
• iPhone with a SSH server installed. Again, follow this guide if you do not know how to install it.

Instructions

1. Make sure you have the OpenSSH client installed on your PC.

    

   sudo aptitude install openssh-client

2. Create a private/public key pair using the following command. It will ask you some questions, but just hit enter to accept the defaults. If you already have a SSH key, you can skip this step. By default, the key pair is saved into ~/.ssh/id_rsa and ~/.ssh/id_rsa.pub, where the .pub file is the public key. That is the one you want to copy. If you saved your key pair somewhere else, don’t forget to edit the location in any of the future steps.

   ssh-keygen -t rsa

3. Append the contents of the public key into the ~/.ssh/authorized_keys file on the iPhone. The following command does just that. Don’t forget to replace 192.168.1.111 with the IP address of your iPhone.

   ssh root@192.168.1.111 "mkdir -p ~/.ssh && echo `cat ~/.ssh/id_rsa.pub` >> ~/.ssh/authorized_keys"

4. Try to login to your iPhone. You shouldn’t be asked for the password if everything worked.

   ssh root@192.168.1.111

5. Repeat steps 1-4 on any additional computers that you own and will use to connect to your iPhone. For step 3, make sure that you append the contents of your public keys as a new line at the end of the authorozed_keys file.

One of the advantages of having a jailbroken iPhone is that it is possible to setup a Secure SHell server (SSH) on it. SSH gives you access to the underlying Unix system. If you do not know what that means, then probably you do not need it. However, it is a very useful tool for programmers like me. This guide goes over how to setup a OpenSSH server on the iPhone and connect to it from either a Linux, Windows or Mac OS X based computer. In the future, I plan to write a guide on how to setup passwordless login, meaning you don’t have to type in your password every time and still have a level of security.

I originally wrote this tutorial before iOS4 came out, using iPhone OS 3.1.3 running on my iPod Touch 2G. However I’ve also tested this tutorial on iOS4 and none of the steps have changed.

Warning: Make sure to change the default password after you setup the SSH server!!! The default password is ‘alpine’ and is well known. The first iPhone worm exploited the fact that people didn’t change the default password!

Requirements

• Jailbroken iPhone/iPod Touch. The SSH server is only available through Cydia, since Apple didn’t (and most likely never will) allow it into their App Store.
• Wireless Router. SSH is a network server, meaning that you need to have it connected to some network. The simplest way to do that with the iPhone is via a WiFi connection.

Setup SSH Server Instructions

1. Locate Cydia on your iPhone and start it.
2. Click on the Search tab.
3. Click on the search bar on top, and type in openssh. There should be only one result, as shown below.  Select it.
4. Click the Install button in top right corner.
5. Click the Confirm button and wait.
6. After the SSH server is downloaded and installed, you can click the Return to Cydia button on the bottom of the screen. Do not exist Cydia yet, because we need to install one more tool.
7. Now that we have installed the SSH server, we need to install a convenient way to turn it on and off. I prefer to use SBSettings, which is a drop-down menu that allows you to toggle SSH, WiFi and Bluetooth ON/OFF, and lists some useful informations. To install SBSettings, continue from the previous step by clicking the Search button to return to the search menu.
8. Type in SBSettings and scroll down until you see the entry that just says SBSettings, as shown in the picture below. Select it.
9. Click the Install button in the top right corner.
10. Click the Confirm button and wait.
11. After SBSettings is downloaded and installed, you need to restart your iPhone. This will start up SBSettings. Do so by clicking the Reboot Device button. (On iOS4.0, the button will say Reload SpringBoard. You do not have to reboot your device.)
12. After your iPhone starts up again, place your finger in the top left corner of the screen, and slide it from left to right. SBSettings will pop down, listing all of the information. The best thing is that you do not have to be on the home screen to do this. You can do it while running any application.
13. There are two important pieces of information that you see in the SBSettings window. The first is the SSH button in the top right corner. You can click it to toggle the SSH server on and off. Make sure it is in the On position. The second piece of information is the WiFi IP Address. This address is what you use when you connect to your iPhone, so write it down. It will be used in the next few steps.
14. You can hide the SBSettings window by clicking the X button in the top left corner. The next few steps will show you how to connect to your iPhone from a computer. When you try connecting, make sure that the iPhone is turned on or otherwise it will be disconnected from the Internet. I suggest that you turn Autolock off.

Connecting From Linux

1. Make sure that you have the SSH clients installed. On Ubuntu, type in the following command.

   sudo aptitude install openssh-client

2. Connect to the iPhone using the following command. This will connect to the iPhone at IP address 192.168.1.111 (make sure to change it to what you wrote down before) using the root account.

   ssh root@192.168.1.111

3. You will be asked for a password. If this is your first time logging in, type in alpine. This is the default password, and we’ll change it in the next step.
4. If you typed in the correct password, you should see a prompt. Any commands that you type in will be executed on your iPhone!

Connecting From Windows

None of the Windows versions come with an SSH client. However there are numerous free options that you can install. I prefer to use the PuTTY client, which is what I’ll be using in the following steps

1. Download PuTTY from the download page (direct link to 32-bit version). The latest version at this moment is 0.60-beta. The file you should download is putty.exe, which is the program itself. No installation is required.
2. Find the downloaded program (putty.exe) and double-click it. Take a look at the screenshot below to see what the icon of the program looks like, to make it easier to locate it.
3. The dialog displayed below should pop-up. Type the IP address of your iPhone into the textbox under Host name (or IP address) label. Also make sure Connection type is set to SSH (should be by default). When you are done, click the Open button to connect. The IP address I wrote into the picture below is different from that you see in the SBSettings picture, because I took this screenshot while connected to a different network. You should still use the IP address that you found via SBSettings.
4. A dialog box, displayed below, will pop-up asking you to accept a new fingerprint. Just click Yes to skip it. This just means that you haven’t connected to this server before and it wants to make sure that it is the correct one.
5. You will be asked for a username. Type in root.
6. You will be asked for a password. The default password is alpine, but make sure to change it after you login!
7. If everything went right, you should see the prompt as displayed below.
   

Connecting From Mac OS X

The instructions for connecting to the SSH server from Mac OS X are the same as for Linux. Except you don’t have to install OpenSSH (Mac OS X comes with it) and you type the commands into the Terminal application.

1. Open the Terminal application by searching for it via Spotlight.
2. Connect to the iPhone using the following command. This will connect to the iPhone at IP address 192.168.1.111 (make sure to change it to what you wrote down before) using the root account.

   ssh root@192.168.1.111

3. You will be asked for a password. If this is your first time logging in, type in alpine. This is the default password, and we’ll change it in the next step.
4. If you typed in the correct password, you should see a prompt. Any commands that you type in will be executed on your iPhone!

Changing Password

1. Connect to your iPhone following the instructions above. All of the following commands will be run on it.
2. Lets change the password. Type in the following command.

   passwd

3. You will be asked for a new password twice. Type in anything you want and hit enter to confirm it. As you type, no characters will appear on the screen, not even *. It is meant to be that way. If you make a mistake, I suggest that you hit the backspace key a lot of times and start typing over.
4. After you have changed the password, you can disconnect by typing in the following command. Next time you connect, don’t forget to use your new password instead of alpine.

   exit

A few days ago I’ve managed to stumble across another problem with using fingerprint authentication on my X61 Tablet. The screenshot below summarizes it the best.

If you run any command that asks you for your password over SSH, then it will ask you to swipe your finger. This is a problem because if you are SSH’ing into your computer, then it most likely means that you are not physically present and so you cannot swipe your finger. The good news is that you don’t have to swipe your finger to actually login via SSH, so this isn’t as big of a problem. Only if you plan to use the sudo or su commands.

So what is the solution? I don’t think there is a good one. I did come up with a proposal for one, but it is not perfect since it doesn’t even work yet with my driver of choice (fprint). The best solution would be for the fingerprint driver to guess if it is being called from a remote machine or local machine, and fail based on that. However that is not possible yet. What I would propose instead is to prompt a user for a fingerprint, allow him to cancel it via a keyboard and then prompt him for a password.

This might not seem like a very good solution, since maybe you want your computer to be very secure and always want a biological identification. Asking for a password then defeats the purpose. If this is what you want, then I suggest you watch this video. Fingerprints readers aren’t very secure and can be bypassed. I think the purpose of having a fingerprint reader is to provide a balance between security and practicality. Swiping a finger is much faster and easier than typing a long password. This is especially true when you are using a tablet and do not have access to a keyboard. And it is relatively secure, since an average person would not probably be able to bypass it. It does require a bit of work and equipment.

Before I begin, I will go over how the fingerprint drivers plug into the standard Linux authentication framework, PAM. This background information is not very throughout, since I have just learned it myself this morning. But it should give you enough knowledge to understand why this fingerprint problem is present and maybe to come up with alternate solutions. Please leave a comment if you do.

When a program wants to authenticate a user, it talks to PAM. PAM asks the program for a username and what service to authenticate for. The reason it asks for a service is that different services might have different rules for authentication. The rules for the service are stored in the file /etc/pam.d/service-name, where service-name is the name of the service. This file contains a list of rules, one rule per line. Comments start with the # symbol and are included. Each rule has the following syntax:

type control module

The type field is the type of the rule. There are different types. For example, the auth type is used to authenticate a user by prompting him for a password. The control field determines what action should be taken if the rule fails or succeeds. For example, a required control means that the rule must succeed for the user to be authenticated. On the other had, a suffiecient control means that if the rule succeed then the user is authenticated and if it fails, then the other rules will be tested. The module field is just a reference to which module will be used to test the rule. The pam.d manpage contains a list of possible values for the type and control fields.

PAM starts by evaluating the rules in order. If the first rule tells it that the user is authenticated, then it finishes. If the first rule tells it that the user is not authenticated, then it proceeds to the next rule (or finishes) based on the value stored in the control field. A quirk is that a required rule is not always tested. For example, if the first rule is sufficient, then the user is authenticated whether any consequent required rules would fail or succeed.

If you followed my tutorial (or one of the many countless tutorials on the web) to setup your finger print reader, then you added the following set of lines to the file /etc/pam.d/common-auth. This file is the set of rules that is included in almost every service defined in the same directory.

auth sufficient pam_fprint.so
auth required pam_unix.so nullok_secure

This means that PAM first asks for a fingerprint. If that fails (wrong finger, reader not present or hardware error…), then the first rule fails. Since the rule is only sufficient, then PAM proceeds to the next rule. The next rule is the rule for standard Unix password authentication. What I would like fprint to do is to fail (causing it to proceed to password prompt) if I hit a certain key. For example according to the ThinkWiki page, the properiaty bio_api driver already does this with the Ctrl+C key combination. This way I could choose whether to use a fingerprint or proceed with typing in a password.

Of course, some people you use the keyboard more than the fingerprint reader. In that case, you can replace those two lines with the following.

auth sufficient pam_unix.so nullok_secure
auth required pam_fprint.so

This means “try password first, then fingerprint”. You can always cause the password prompt to fail by hitting Ctrl+C.

I have been using my ThinkPad X61 Tablet on Ubuntu Lucid Lynx for about a month now, so I think I am comfortable in writing an update about how well those two work together. To make a long story short, most items are unchanged since Ubuntu Karmic Koala. What worked before still works, what didn’t work before still doesn’t work. The one thing that changed is that to get the scrolling via the TrackPoint to work, you have to create a new file. Read on to see what needs to be changed.

Further documentation is available on the X61T’s Lucid ThinkWiki page and the Ubuntu Wiki. However at the time of writing, neither has been updated for Lucid.

Before I start talking about Ubuntu Lucid Lynx, I want to write a quick summary about the hardware. My tablet is the one with the SWGA screen and does not have finger-touch capabilities. You have to use the cheap pen, included with the tablet, for input. The tablet also has 2 GB of memory and a Core 2 Duo processor running at a maximum of 1.6 GHz. The processor also supports other frequencies, like 800 MHz and 1.2 GHz. The frequencies can be changed using the standard Linux tools right away.

Wireless

The wireless connection works out of the box. It uses the iwlagn kernel module.

Touchscreen (Pen Only)

The touch screen works out of the box using the Wacom pen. I don’t know about finger-touch support, since as I do not have that capability.

I recommend that you instal xournal for note-taking and cellwriter (my tips and tricks) for handwriting recognition. Both are available in the official Ubuntu repository, but are not installed by default.

Extra Buttons/Screen Buttons

All of the extra keyboard buttons work out of the box, with the exception of the zoom button (Fn+Space). The buttons that work are the volume buttons, the ThinkVantage button and all Fn buttons. The buttonson the screen are the rotate button, the toolbox button, the escape button and the arrow buttons.

By work, I mean they report a valid symbol to X.Org. For some of them, you have to bind them to an action to make them do something useful.

Middle Button Scrolling Using TrackPoint

You cannot use the TrackPoint as a scroll button out of the box. In Karmic, you had to create a file, such that HAL would know to enable this feature. However Lucid no longer uses HAL, instead it reverted back to X.org’s own device configuration system. So you have to create a file for X.org. The contents are still the same, only the syntax changed.

To create this file, run the following command to open a text editor:

sudo gedit /usr/lib/X11/xorg.conf.d/20-thinkpad.conf

And place the following text into it:

Section "InputClass"
Identifier "Trackpoint Wheel Emulation"
MatchProduct "TrackPoint"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
Option "EmulateWheel" "true"
Option "EmulateWheelButton" "2"
Option "Emulate3Buttons" "false"
Option "XAxisMapping" "6 7"
Option "YAxisMapping" "4 5"
EndSection

Save the file and restart X.org. After that, you can scroll by holding down the middle mouse button and moving your TrackPoint up-and-down at the same time.

I stole these instructions from Phil Sung, who stole them from Samson Yeung.

Suspend/Hibernate

Both work out of the box without any problems.

Hard Drive Accelerometer

The hard drive accelerometer STILL does not work out of the box. It will report the position (0,-3) regardless of the real position. My understanding is that there are some political problems (legal, ideal?) as to why it hasn’t been fixed yet.

To get the accelerometer to work, you have to compile it manually from the tp_smapi package. I’ve already documented how to do this for Karmic, and the same steps apply to Lucid.

Of course, you still have to install some packages to make it do something useful. I suggest that you install hdapsd, which will spin down your disk when motion is detected. This prevents it from being damaged.

sudo aptitude install hdapsd

Also my AutoRotate daemon is quite cool. It rotates your screen automatically based on orientation.

Fingerprint Scanner

The scanner does not work out of the box. And even after manual configuration, you can only go so far. While the hardware is supported, the software that uses it isn’t that great. You can configure PAM to allow you to login via fingerprints, but it cannot identify the based on the fingerprint and it always asks for a specific finger at a time.

The best software for this is fprint. I have written a tutorial on how to configure fprint. However you no longer have to add the PPA in it, since fprint is now part of the official Ubuntu repository.

Another choice is thinkfinger. I have also written a tutorial for it.

Today I took some time to update the AutoRotate daemon to work with Ubuntu Lucid. There were a few small changes that I had to make, so I decided to slightly increment the version of the package. You can download the source code here. Also Ubuntu users can install it automatically from my PPA.

Change Log

• Use xsetwacom –list to get a list of all WACOM devices

The next addition I am planning to work on next is to write a simple indicator menu to control the daemon. I’ve created a post on the Ubuntu Forums asking for suggestions.

This is the sixth installment in the Symphony of Science musical series. This one includes Robert Zubrin, Carl Sagan, Brian Cox, and Penelope Boston. The topic is the exploration … or colonization… of Mars!

The MP3 version can be downloaded from the Symphony of Science website.

kCGWindowBounds is a field in a dictionary returned by the CGWindowListCopyWindowInfo function. This fields lists the dimensions of a window displayed by the Quartz Window System (Mac OS X’s analogue of X11). I was trying to use this field to resize a NSWindow object that I was controlling, with the idea to create a window picker. The problem is that kCGWindowBounds’ coordinates are not the same ones as used by NSWindow’s frame property, and it took me a while to realize this. Which is why I am sharing what I found out.

Both kCGWindowBounds and NSWindow’s frame property are instances of CGRect (technically, NSWindow uses a NSRect but all literature I found says it is equivalent to CGRect). This object has two attributes; a point (origin) and dimensions (size). The difference between the CGRect returned by kCGWindowBounds and NSWindow’s frame property is that:

• kCGWindowBounds measures the origin as the top-left corner of the rectangle relative to the top-left corner of the screen
• NSWindow’s frame property measures the origin as the bottom-left corner of the rectangle relative to the bottom-left corner of the screen

So if you want to convert between the two representations of the same information, you have to do the following. It is the same conversion if you are going from kCGWindowBounds to NSWindow#frame or in the other direction.

bounds.origin.y=[[NSScreen mainScreen] frame].size.height-bounds.origin.y-bounds.size.height;

My main desktop computer, tiny101, recently run out of hard disk space. Instead of clearing out everything, I decided to visit NCIX and purchase 2 new 2 TB drives (Western Digital). However when I started installing them, I realized that my previous storage disk (1 TB, Samsung) was not installed properly. It was just placed into one of the trays and connected to the motherboard. As you can imagine, this is not good for it. In this tutorial, I plan to go over how I rectified this problem by properly installing the hard drive into my Antec Nine Hundred Gaming Case.

Before I begin with the tutorial, I want to say that Antec has great customer support. The Antec 900 case requires special hard drive screws, which I did not have. But when I asked them where I can buy those screws, this was their response:

We can send the part/s out to you. Please reply back with your postal address.

They did not charge for the parts or even ask to see a receipt to prove that I own an Antec case. After this experience, I am quite glad that three years ago I chose an Antec case.

Requirements

• Antec 900 Case, but I would imagine that the other cases in the family have similar instructions.
• 4 Antec 900 hard drive screws, per disk. These are special long screws and not the standard short screws. You should have received as spare set with your case, but if you lost them you can always contact Antec support and ask for more.
• 1 SATA cable, per disk. I am assuming that your bought a SATA disk. If you have a different type of disk, you can still follow these instructions to install the disk into into the case. However you are on your own when it comes connecting the disk to the mother board.
• 1 hard disk (DUh?)
• Phillips head screw-driver, for the hard drive screws.
• A vaccum cleaner. Since your case is open, I recommend that you take some time to clean out some of the dust.

Instructions

1. Disconnect all of the external cables from the case and move the somewhere with a lot of space.
2. Remove 4 of the big, black screws on the back of the case. There are two on each side, holding down the side panels. You do not need a screw-driver for them, instead use your hands. After you remove them, place them in a place where you won’t loose them.
3. Remove the two side panels by moving them towards the back of the case for one centimeter, and then pulling them toward you.
4. Disconnect any already connected hard drives. Make sure to remember how they were connected, because you will have to reconnect them later. If you are installing your hard drive in a cage different from the current hard drive, you can skip this step. The hard drive can be put into any of the two cages located in the front (each cage holds up to 3 hard drives). A cage is just a small box that can be pulled out from the case. Take a quick look at the picture in step 8 to see what a cage looks like.
5. Disconnect the fans of the cage that you will be installing the hard drive into. Each fan is connected only to the power supply by a two thin wires. You can find those wires at the back of the case, as demonstrated in one of the pictures above. Then just follow the two wires until you reach the power cable. Both wires are connected to the power supply via the same plug. Unplug that plug, but remember which one it was! You will have to reconnect the fans after you are done!
6. Unscrew the thumb grayscrews from the cage that you will be using. There are two screws on each side of the cage (thus 4 in total). Place those screws somewhere safe, but make sure not to mix them up with the black screws from the side panels. They are different!
7. Gently pull out the cage through the front. Start by pushing it from inside the cage and end by pulling it from the outside after you can get a good grip. If for some reason you get stuck, investigate why! Maybe you forgot to unplug some wires. One more friendly warning: If you have not cleaned your computer in some time, make sure to have a vacuum cleaner turned on when you do this step. A handful of dust is guaranteed to come out.
8. Put the cage somewhere where you can see it.
9. Place your disk inside one of the free compartments inside the cage. Look at the picture above to see what a free compartment looks like.
10. Make sure you place the disk in a way such that the connectors stick out. In the picture, I placed my new disk into the second compartment from bottom.
11. Look for holes on the side of the cage. After you found them, screw the long hard drive screws into them. They should go through the cage and into the hard drive. Remember that there are 2 screws per side of the cage (4 in total). You will need a Phillips head screw driver for this.
12. Slide the cage back into the case. Make sure to put in the fan wires first. This is essentially step 7 in reverse.
13. Reconnect the fans (and any old disks) you disconnected earlier.
14. Connect the new hard drive to the motherboard. I described how to do it in the next section of this tutorial.
15. Put in the gray thumbscrews to hold the cage in place. If you forgot where they came from, then look at the picture above. They go through the wide slits.
16. Slide the two side panels back by doing step 3 in reverse. This step can be quite tricky, because there are slits in the side panels that the case has go through. After you are done, the panels should fit snuggly into the case.
17. Fasten the side panels by screwing in the black thumbscrews on the back.
18. Now you have successfully installed a hard drive in the Antec 900 case! In the next few steps, I will guide you through how to connect it to the motherboard (which you should already have done in step 14…). I assume your disk was SATA (very common for personal computers).

Connecting A SATA Hard Drive to the Motherboard

1. Familiarize yourself with the important ports on your hard drive. I described them above.
2. Find an empty SATA power plug comming from your power supply. They look something like this. In my case, the plugs have “S-ATA 3″ written on them.
3. Connect the plug to the power port on the hard drive. The plug goes in at a specific orentation. The yellow cable should point toward the motherboard. You should have located the port in step 1.
4. Find an empty SATA plug on your motherboard. They look something like in the picture above.
5. Connect one end of the SATA cable into that plug. It does not matter which end of the cable you plug in, because both ends are the same. But there is a specific orientation at which the cable goes into the plug. Look at the shape of the plug and the cable to figure out which way it should go in. Sadly, there are no easy markings to describe it.
6. Connect the other end of the SATA cable into the SATA port on your hard disk. You should have located the port in step 1.
7. Turn on your computer and enter the BIOS. It should have detected your hard drive, if you have done everything correctly.

Further Resources

• Antec 900 Product Page
• Antec 900 Specifications
• Antec 900 Support Page
• Antec 900 Manual (English)

A while ago, I wrote a tutorial on how to get the NBC/NXC running on Linux in order to program an Mindstorm NXT brick. In the tutorial, I posted an example script that turns the robot into a dancer and plays some music. The only problem is that the music was just set of random frequencies and thus was unbearable to listen to. So I though, is there a way to make it less random without the need to make it play the same thing over and over again?

Experimenting with this idea lead me to write the libmidi library. MIDI files are a collection of notes, so it seemed as the best format to use. It allowed me to just generate random notes and tell the MIDI player to play them in some order. The library also includes an example called randommusic, but just does the same thing as the dancing robot. It just plays 128 random notes. This is what it sounds like:

I am no expert on music theory, but from what I understand most songs contain only notes in one scale. And the idea also works the other way, playing notes in a scale can result in a song. The song won’t be a masterpiece, but it will be bearable. Since I am too lazy to pre-program every possible scale, I decided that I will only limit notes to ones found in an existing song instead of a scale.

After analyzing Piano Sonata No.1, that I grabbed from Kunst der Fuge some time ago, I get the following result:

It sounds much better than before, but it still sounds like it is all over the place. To fix this, I applied one more change to how the next note is picked by looking at one more piece of information when analyzing the song; the note that was played previously. That is if note B never follows note A in the existing song, then it should never do so in the random music. Here is the result:

That was a big improvement! I think that is where I will stop working on this. But more tweaks could be done in the future:

• Add random rhythm
• Analyze multiple songs

Of course, the code still needs to be ported to NXT to make a much more improved dancer robot.

The script that I wrote to do this can be downloaded here and is released under the GPL3 license. To use it, you need to have libmidi and ROOT installed. This is how it works:

1. Analyze the song

   ./analyze input.mid output.root

2. Generate a random tune.
   • The first argument is the track of the orignal song to analyze, and should be set as track1, track2 and so on. Also you can set it to song, which uses all tracks.
   • The second argument is the ROOT file with the analyzed song created in step 1
   • The third argument is the output MIDI where the result will be saved
   • The fourth argument is optional. Specifying it will ignore any previous note conditional probability.

   ./generate track input.root output.mid [unconditional]