Category: C#

I was having trouble getting the Google Android SDK to save screenshots for me, leaving me with the only way to save them being to open MS Paint and go through the processes there to save them. Somehow, doing this only once was enough to make me want to write a better solution, so my less than half-hour solution to the problem was writing this basic application in C#. Its not complicated or particularly intelligent, but if you click in the gray box with an image on the clipboard it will paste it and save it.

If anyone wants this overly simplified substitute pasting into Paint, you can grab it from http://users.pcfire.net/~curtis/software/ClipboardSaver.msi. It only works on Windows and will probably only install on a 64-bit Windows.

At some point over the last few hours I threw together this application, its a minor app. I needed a way to identify potentially duplicate files in a certain folder on my network, and I really didn’t want to do it manually, so here is a quick little program to take care of that task in a rather dirty fashion. I use the program to identify potentially duplicate videos that have been stored in dated folders after being downloaded.

The application is written in C# and requires .NET 3.5 to run (if you are on a modern Windows OS, you are ok). The program will take a folder you specify and treat it as the top of the tree, and from there recursively gather filenames. Once those names are gathered it compares all of the base file names as well as sizes. Not a fancy app, but thought it might be useful to someone.

For Download: http://users.pcfire.net/~curtis/software/DuplicateFinder.exe  [14KB]

I discovered last night that Mono does not contain certain parts required to make ExIf35 work on other platform, mainly, the basic parts of the Windows Presentation Foundation, which allow the metadata writing components that I use to function. At the moment I have no idea how I am going to proceed. It has crossed my mind to neuter out Form3 (the thing that writes exif to the files) and ship the application as is for other platforms, but that is somehow less than optimal. I have also considered doing everything normal, but then creating a special form3 that will write a .xmp sidecar file for each image, for later reintegration by another application. At the moment I am attempting to locate any way possible to write those values to the file that doesn’t use any part of WPF, so that there will be a chance that Mono can use it. My fear is that I will end up having to learn how to write directly to the image file in byte form to implement all of these fields. It would be neat to learn how to do that, but at the same time, quite a huge annoyance. So for now, sorry Mac users, it isn’t going to happen any time soon 🙁

I have been fighting with a problem in code for several weeks now relating to the writing of a negative exposure bias value to exif information using the .NET framework’s metadata class. The class has a set of properties and a table of what is allowed to be written to each of those properties. Unfortunately for my project, there was an oversight in that system. A variety of properties, such as System.Photo.ExposureBiasNumerator, do not accept negative values, even though they are supposed to hold signed integers. This has caused me to need to cast an absolute value on all of my exposure bias values, making them all positive. I have attempted to inquire through the MSDN forums and other sources for a reason for this, waiting for someone to point out that I’m wrong, but so far, no one has, so I must assume that there is a flaw. All other values are easy enough to write correctly with no special cases.

Tonight I have reinstated the ability to write negative values to exposure bias. Effective in ExIf 35 build 20100410 that functionality will be again functional.

I knew that there had to be a way to make it work, since those values are present in other applications and applications using the .NET Framework can read those values. I pulled some images into my diagnostic form and began reading /app1/ifd/exif/{ushort=37380} (thats ExIf 0x9204) from each of them. I found that there was an 11 digit number recorded in the space for all of them, both with positive and negative values. This got me curious, since a 32 bit integer is only 10 digits. I double checked with Visual Studio and it turns out that my two signed integers were being stored as one giant unsigned 64 bit integer. I began by trying to determine what those numbers could represent, trying to find any and all relationships between those 64 bit integers and the 2 part signed shorts I was working with (relationship between 30064771068 and –2/3 for example). Finally I gave up and decided to read the bytes.  30064771068 is 251, 255, 255, 255,6,0,0,0. I know they are supposed to be 32 bit numbers, so that takes us to 251, 255, 255, 255 and 6,0,0,0. 251 –255 = –4, and 6 = 6, making a rational of –4/6, reducing to my expected –2/3. Now it all makes sense, but I ask myself, why must I generate a 64-bit integer manually to make this work when Microsoft has created perfectly understandable way to write this crap to a file. I guess sometimes being able to do things the old way has its benefits.

So, now I present, my code:

//Assume exp.ExposureBias is a string such as -2/3
if (exp.ExposureBias.Contains("/")) //check for rational
{
double tmp = Convert.ToDouble(exp.ExposureBias.Split('/')[0]);
tmp = tmp / Convert.ToDouble(exp.ExposureBias.Split('/')[1]);
tmp = Math.Round(tmp, 1);
exp.ExposureBias = tmp.ToString();
}
//convert to a valid integer value
int exposureBias = Convert.ToInt16(Math.Floor(Convert.ToDouble(exp.ExposureBias) * 10));
//create the array to hold the 64 bits
Byte[] exposureBiasByte = new Byte[8];
if (exposureBias < 0)
{
exposureBias = 256 + exposureBias;
exposureBiasByte[1] = 255;
exposureBiasByte[2] = 255;
exposureBiasByte[3] = 255;
}
else
{
exposureBiasByte[1] = 0;
exposureBiasByte[2] = 0;
exposureBiasByte[3] = 0;
}
exposureBiasByte[0] = Convert.ToByte(exposureBias);
exposureBiasByte[4] = 10;
exposureBiasByte[5] = 0;
exposureBiasByte[6] = 0;
exposureBiasByte[7] = 0;
Int64 exposureBiasLong = BitConverter.ToInt64(exposureBiasByte, 0);