ASSetTitle: song logger, SIG GENERATOR, and random other improvements to boot!

[Riffraff]

EDIT: I FINALLY GOT AROUND TO ADDING SIG SUPPORT. DOWNLOAD AND READ THE README TO SEE HOW TO USE IT.

For those of you who don't know, ASSetTitle started with one simple goal: To change the title of the Audiosurf window according to what song was playing. Mincus was kind enough to write this for me, at which point I began adding a bit here and there. I may have added some nice functionality, but it's still definitely Mincus' code.

Features:
-Title bar functionality (changes the window title corresponding to what song is currently playing; this is the original scope of the project)
-Logging of *all* songs played, including score (this is probably the highlight feature)
-Enabling Usebankingcamera (Disabled by default; see readme to enable)

****ATTENTION****
THE CORE FUNCTIONALITY OF THIS PROGRAM INTERFERES WITH THE OPERATION OF VIRTUALLY ALL OTHER AUDIOSURF "ENHANCEMENT" PROGRAMS, SUCH AS AUDIOSURF MEDIA PLAYER, AND OTHERS. This cannot be avoided, as the base level at which they connect with audiosurf is through the window title, so changing it is enough to screw them up. This intereference in only within the same session; if you restart audiosurf, you can use other audiosurf programs again without trouble


**THERE IS A WAY TO DISABLE THE INTERFERING PORTION OF THIS PROGRAM, HOWEVER**
Thankfully, I do have an option to disable the "core" functionality while leaving the logging. See the readme for details on how to do this.

Sig Generation:
See the readme for the full explanation of how to set it up.

If you're wondering what I mean by logging, it'll put a listing for each song you play in a file called Played.log in the same folder as ASSetTitle.exe. Here's a short example, logging 3 songs:

[ Wed Jun 17 16:38:30 ] neutral milk hotel -- holland, 1945 51860
[ Wed Jun 17 16:42:31 ] voxtrot -- mothers, sisters, daughters and wives 76778
[ Wed Jun 17 16:45:53 ] voxtrot -- raised by wolves 85235

If you're wondering about a feature, or about specifics of it's functionality, please first try downloading it, read the readme, and try it for a song or two. I promise it won't bite.

Goals for improvement:
-Make the cfg editable by tickboxes in the UI
-Add a tray icon

Release 1.0: Jun 17 2009
Release 1.0b: wee hours of Jun 18 2009
--Fixed problems as recommended by Mincus; Not quite sure why the 8 kb difference in .exes, presumably differences between VS08 and VS10.
Release 1.1: Jul 25 2009
--Added the new sig generator feature. See readme
Release 1.11: Jul 27 2009
--Fixed crippling bug with sig generator. should work as intended now.
Release 1.12: Minutes later
--Removed some silly code I left in. sorry!
Release 1.2: Feb 11 2010
--Began work on an auto-launcher (not in yet, sorry)
--finally updated readme to explain sig feature toggle
--updated AS.cfg correspondingly
--added some more code to ensure that you can always link with audiosurf.exe, even if it's started after ASSetTitle.exe
--Fixed a bug where title would be stuck with song name if ASSetTitle terminated.


PLEASE do give feedback; What do you like, what do you hate, what features do you wish this had?

You can always find the latest version and source at: http://code.google.com/p/assettitle/

[ViRUS]

Nice program Riffraff.

One simple question though, should I include the as.cfg when I add this to AHOAA??

[Riffraff]

Nice program Riffraff.

One simple question though, should I include the as.cfg when I add this to AHOAA??

interesting question. Probably yes, although it's a shame that it'd preclude any of the original functionality =/

The alternative, of course, is worse; programs breaking because stupid riffraff wanted his pretty title bar program, and I just wanted to use it to log my tracks played. In fact, if you were to include in AHOAA at all, I'd probably use an even more barebones version, with only the logging turned on (010 in the config file), as asconfig usebankingcamera is a setting with.. limited appeal outside of those who love it to death (myself, maybe a few others), in which case you might as well call it ASLogger.

On another note, you should probably remove my controller script, as it's pretty much fully superseded by that other one some (I forget his name, too lazy to check the thread) posted.

[ViRUS]

interesting question. Probably yes, although it's a shame that it'd preclude any of the original functionality =/

The alternative, of course, is worse; programs breaking because stupid riffraff wanted his pretty title bar program, and I just wanted to use it to log my tracks played. In fact, if you were to include in AHOAA at all, I'd probably use an even more barebones version, with only the logging turned on (010 in the config file), as asconfig usebankingcamera is a setting with.. limited appeal outside of those who love it to death (myself, maybe a few others), in which case you might as well call it ASLogger.

I'll find a way to include both options, don't worry

On another note, you should probably remove my controller script, as it's pretty much fully superseded by that other one some (I forget his name, too lazy to check the thread) posted.

Nah, I prefer not to do that, I want AHOAA to become like an addon "database", so you always find a place to search some old addon you just got used to and the developer isn't distributing it anymore (like e_-'s player, I would like to get the code again, but his homepage is down and I can't reach to him).

But anyway, it's your addon, so as stated on AHOAA's post, if you really want me to take it out, I will gladly do it

[Riffraff]

I'll find a way to include both options, don't worry

It really should be me who gets off his lazy bum and adds tickboxes, heh.

[ViRUS]

Bummer, when I try to run it, a message saying "The application couldn't be run because your configuration is incorrect. Reinstalling the application may solve the problem"



EDIT: I also noticed that both of the .cfg files have "111" inside, shouldn't they be different according to the explanation on the first post?

[Mincus]

Presumably that's the "side by side configuration" installation error?
The source needs linking in a specific manner to get round that.
IIRC you need to first switch to release mode, then go to the project properties and set "C/C++" -> "Code Generation" -> "Runtime Library" to "Multi-threaded (/MT)".

Should work, attached a copy from VS2010 with these options anyway.

Oh, two notes about the code:
Line 420 in main.cpp should be a for(size_t i = 0; as strlen() returns a size_t not an int.

To stop the following:

1>main.cpp(385): warning C4996: 'localtime': This function or variable may be unsafe. Consider using localtime_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
1>          C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\time.inl(112) : see declaration of 'localtime'
1>main.cpp(387): warning C4996: 'asctime': This function or variable may be unsafe. Consider using asctime_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details.
1>          C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\time.h(153) : see declaration of 'asctime'

You should add this to the main.h file before including windows.h

// All together now, everyone sing along o/` MS are retards who can't code for toffee o/`
// Removes warnings MS generate because they seem to think no-one can code properly.
#define _CRT_SECURE_NO_WARNINGS

With or without the daft comments works. I like them as it reminds me that MS seem to think that telling everyone that they're safe means they are (the *_s functions are no safer, they can still over-run if you pass them bad values, and the values you pass them you should be checking anyway, so the entire drive by MS for adding these functions is nonsensical -- plus it breaks compatibility with other compilers).

[Riffraff]

Bummer, when I try to run it, a message saying "The application couldn't be run because your configuration is incorrect. Reinstalling the application may solve the problem"



EDIT: I also noticed that both of the .cfg files have "111" inside, shouldn't they be different according to the explanation on the first post?

Thanks for the tip on the .cfgs; don't know how that happened, but it's fixed. I've re-built according to Mincus' suggestions; if someone could try out either his or mine, and report on whether it works or not, that'd be lovely.

edit:
It should be good to go, I've test deployed it on the only other machine I have on hand, a windows XP netbook, and it seems to be working at 100% functionality.

[Mincus]

edit:
It should be good to go, I've test deployed it on the only other machine I have on hand, a windows XP netbook, and it seems to be working at 100% functionality.

Yeah, your new build works. Since I'm using Visual Studio 2010 beta and you're using a different version (for which I don't have the runtime installed), the original build didn't work on my machine without a recompile. As to the why, it's rather boring stuff involving C runtimes and how they're linked into a program. Changing the setting I suggested links parts of the runtime into the application which fixes the problem (but makes the binary bigger).

[Riffraff]

Bumping because new version is released; sig generator is pretty spiffy, if I do say so myself. Does not depend on any community sites; uses Dropbox, a fairly established, user-friendly subversioning system.