Need optional methods to 'processexists'

[numri]

I've written a very simple program for the Xsplit community that allows users to add a dynamical "NowPlaying" title to their justin.tv/twitch.tv streams.

Currently this program fetches information from spotify by reading the window title and dumps the title into a textfile which xsplit later on can read.

Now I want to expand the program to supporting multiple media players (winamp, foobar, etc.) but I want to keep the lightness of the application as xsplit really needs every bit of juice available.

Therefor i cannot really use "processexists" to check which media player is running, due to the page faults it seems to trigger.

I can't really read the title to determine what program it is, unless i search for the string "winamp" e.g. in the title. seems somewhat redundant, or is this the best way to go considering the way 'processexists' is working right now?

Any ideas? Below is my program in its current state. Thanks in advance.

While 1
; Fetch Title of Spotify window and remove "Spotify - " from the title
Local $title = StringTrimLeft(WinGetTitle("Spotify"), 10)

; Replace the weird "-" from spotify with a proper dash to separate Artist - Track
Local $final = StringReplace($title, " – ", " - ", 0, 0)

; Open File in overwrite mode - Place the spotify.txt in the same directory as this script.
Local $file = FileOpen("spotify.txt", 2)

; Check if file opened for writing OK
If $file = -1 Then
MsgBox(0, "Error", "Unable to open file.")
Exit
EndIf

; Write current track to file spotify.txt
FileWriteLine($file, "| " & $final & " |")

; Close file
FileClose($file)

; Sleep for 10 seconds
Sleep(10000)
WEnd

[BrewManNH]

Try it with ProcessList and then looping through the returned array to find the running player(s) by executable name.

[numri]

That's genius! However how will this affect performance running this once every 10 seconds? Should I maybe restrict it to to only do ProcessList until one of the target processes is found?

[BrewManNH]

It shouldn't affect performance all that much. Once you find one of the processes you're looking for, you can stop looking, unless you want to make sure there isn't more than one instance of it running, or more than one of the targets running at the same time (i.e. 2 WinAmps running, or WinAmp and Foobar running at the same time), then you can keep checking with ProcessExists to see if the target program has stopped running to start your scan again.

You can use ProcessExists with the PID that's returned from ProcessList to check just that window to see if it is still running, rather than just randomly looking for a process called Winamp.