In 2010, while writing a Midi file parser in C#, I needed the ability to swap the endian of the data, since Midi files are stored as Big Endian, converting them into Little Endian.

I would have thought there would be some function within the BitConverter class to be able to swap, but there didn't appear to be, so I wrote my own.

Since swapping endian is just reversing the byte order, the simplest method would be to get the bytes of a number, and reverse the array, then reconstruct the number using the reversed bytes.

Source code

//
//
using System;
 
//
//
namespace Midi
{
class Endian
{
	//
	public static UInt16 SwapUInt16( UInt16 inValue )
	{
		byte[] byteArray = BitConverter.GetBytes(inValue);
		Array.Reverse(byteArray);
		return BitConverter.ToUInt16(byteArray,0);
	}
 
	//
	public static UInt32 SwapUInt32( UInt32 inValue )
	{
		byte[] byteArray = BitConverter.GetBytes(inValue);
		Array.Reverse(byteArray);
		return BitConverter.ToUInt32(byteArray,0);
	}
}
}

But this method is slower than just using a bitshift.

Source code

//
//
using System;
 
//
//
namespace Midi
{
class Endian
{
	//
	public static UInt16 SwapUInt16( UInt16 inValue )
	{
		return (UInt16)( ((inValue & 0xff00) >> 8) |
				 ((inValue & 0x00ff) << 8) );
	}
 
	//
	public static UInt32 SwapUInt32( UInt32 inValue )
	{
		return (UInt32)( ((inValue & 0xff000000) >> 24) |
				 ((inValue & 0x00ff0000) >> 8) |
				 ((inValue & 0x0000ff00) << 8) |
				 ((inValue & 0x000000ff) << 24) );
	}
}
}

Since any the there are only 16 bit and 32 bit numbers in the Midi file format, and anything larger is of Variable Length Quantity, these are the only two required.

Eventually I got ahold of the Midi Standard 1.0 which helped me solve this riddle for when calculating it myself, and will hopefully help others who have this problem.

When calculating delta time, "Set Tempo" and "Time Signature" meta events need to be handled. Also remember that the raw denominator for "Time Signature" meta events needs to be used as the exponent for raising two to a power:

Source code

const float kTimeSignatureDenominator = powf( 2, rawTimeSignatureDenominator );

This first page will cover correctly calculating "Beats Per Minute" (BPM) correctly. And although a lot of examples seem to think you require this to convert delta time ticks to seconds or milliseconds, you don't.

What is a Beat?

In music, there is something called a Bar, which is a segment of time defined by a given number of beats of a given duration. The values which define a Bar, are called the Time Signature.

A Time Signature, is two numbers, one on top of the other. The numerator describes the number of Beats in a Bar, while the denominator describes of what note value a Beat is.

So 4/4 would be four quarter-notes per Bar, while 4/2 would be four half-notes per Bar, 4/8 would be four eighth-notes per Bar, and 2/4 would be two quarter-notes per Bar.

Calculating BPM

Now a lot of examples say to default the tempo to 120 BPM, and the time signature to 4/4, which is correct. But when handling the "Set Tempo" meta event, the same examples just use the value straight out to calculate the BPM, which is incorrect if the time signature has changed.

The "Set Tempo" meta event in midi only deals in quarter notes, so if the time signature is 4/8, a quarter-note is not a Beat since its described as an eighth-note, so using it to calculate BPM  on its own is incorrect.

Source code

const float kOneMinuteInMicroseconds = 60000000;
 
// This is wrong if the time signature is not 4/4
float BPM = kOneMinuteInMicroseconds / newMicrosecondsPerQuarterNote;

So how do we solve this? We use the new time signature to scale our BPM to the correct value.

Source code

const float kOneMinuteInMicroseconds = 60000000;
const float kTimeSignatureNumerator = 4.0f; // For show only, use the actual time signature numerator
const float kTimeSignatureDenominator = 4.0f; // For show only, use the actual time signature denominator
// This is correct
float BPM = ( kOneMinuteInMicroseconds / newMicrosecondsPerQuarterNote ) * ( kTimeSignatureDenominator / 4.0f );

In the code above, we divide the time signature denominator by four (The number four is the denominator value for quarter note), this gives us the number of notes per quarter note. Four divided by four is one, so the BPM remains the same.

If the value of kTimeSignatureDenominator was "8.0f", then eight divided by four is two (there are two eighth-notes in a quarter note).

The next page will cover the actual conversion of delta time ticks to seconds (or milliseconds).

The snippet below shows how to read to read a Variable Length Quantity (sometimes known as a Variable Length Value).

The way it works is very simple, it checks the first byte to see if the MSB is set, if it set it will keep iterating, moving along one byte and doing the same, shifting the previous value across 7 bits until the MSB isn't set.

If it isn't set on the initial test, the value from that byte will be used for the value of the VLQ.

Source code

//
//
using System;
 
//
//
namespace Midi
{
class VariableLengthQuantity
{
	//
	// Functions
	public VariableLengthQuantity( byte[] inVariableData, int inOffset )
	{
		int offset = inOffset;
 
		// At least one byte is always used
		m_value = inVariableData[offset];
		m_numBytes = 1;
		++offset;
 
		//
		if( ((m_value & 0x80) != 0) )
		{
			UInt32 c;
 
			//
			m_value &= 0x7F;
 
			//
			do
			{
				//
				c = inVariableData[offset];
 
				//
				m_value = (m_value << 7) + (c & 0x7F);
 
				//
				++m_numBytes;
				++offset;
			} while( (c & 0x80) != 0 );
		}
	}
 
	//
	public UInt32 Value
	{
		get
		{
			return m_value;
		}
	}
 
	//
	public UInt32 NumBytes
	{
		get
		{
			return m_numBytes;
		}
	}
 
	//
	// Attributes
	UInt32 m_value;
	UInt32 m_numBytes;
}
}

I found its strangely easy to setup, though I have yet to get WinForms to work from the examples, I have got console apps working. And with the console app, I have been able to use XPath.

The only downside was it took an hour to download from their website, which is quite bad for only 50MB.

This is C#, it should be simple right?

Well apparently System.IO.Path.Combine() doesn't take into account "./" or "../" and just concatenates and added an additional forward slash if needed.

After a bit of searching, and many different examples (most of which just converted absolute to relative), I found what I needed. This method used System.IO.Path.GetFullPath() with System.IO.Path.Combine() (If I used the relative path on its own with GetFullPath() I just got the relative path from the current executable directory).

I made it into a single function I can call but I was surprised that there wasn't something already to do this considering what C# has impressed me with so far for thinking ahead.

Source code

//
//
using System.IO;
 
//
//
static string GetAbsoluteFromRelative( string inBasePath, string inRelativePath )
{
	return Path.GetFullPath( Path.Combine( inBasePath, inRelativePath ) );
}

It hasn't tainted my image of C# though, I still adore it for its XML XPath node iterator library thing that has MySQL searching features.

I also found a spiffy thing I didn't know about XPath as well. If I have a set of data like so.

<FileList>

<Folder>

<File>MyFile</File>

</Folder>

<File>MyOtherFile</File>

</FileList>

I can iterate through all file nodes within file list with a double-slash before "File" within my node select call.

Source code

XPathNavigator nav;
 
// ...
 
XPathNodeIterator fileNodes = nav.Select("/FileList//File");
 
while( fileNodes.MoveNext() )
{
	Console.WriteLine( fileNodes.Current.Value );
}

I still seem to have problems with namespaces in some XML documents though (ones without them seem to make searching a hassle).