New DVDSpy Script [Fellow DVDSpy users, I need your help!]

[Wykat]

SouthyPar,

I just played a little around with your new tool :P . I've only did some tests with zoomplayer with following results;

'old' 1.19' GML file does work but the OSD shows the wrong characters (font ?). It should display the actual playing time and total length, but in stead it shows square blocks or other not recognizable characters (Are you using a different font set ?).

With the new GML script file I can't get it to work. First of all I noticed that the last command within the group should be a simple OSD command (most groups are still on 'Variable Manipulation Script'. The problem however ist that the events are not triggered by DVDspy (which worked with 1.19 :-? ) Any idea ?

Wykat

ps: I'm using one of the oldest DVDspy on my HTPC in the living room and that works great; insert CD and the required application is started. Before I change this setup I first have to understand the new method. :oops:

EDIT= it looks like a part of Girder has crashed before. When I now load my original (copied) GML file it doesn't create events either. Will do a reboot
Yes, reboot solved the problem. However I still do not understand which event triggers the OSD ??

[Wykat]

As for the ZPLayer events not being triggered by DVDSpy...

This was resolved with a reboot... :D

Wykat

[SouthyPar]

I've just sent Ron a new "DVDSpy Information Getter" export group.

Please check out my .GML file. It offers an alternative route of handling DVDSpy's information. As you will see, it gathers all of DVDSpy Information into named variables via a Girder Variable Manipulation Script instead of 'treg's, and deletes these values once the program has been closed.

Each program has it's own variables instead of allocating a single variable for each type of information (Title, Elapsed, Duration, etc...). I find this method to be favorable, as it is more organized and concrete. While it isn't appropriate for people who use LCD displays to display the information (and do need a single constant variable for each type of data),
it may help a lot to replace the anonymous text registers with meaningfully named variables, especially for newbies.

Notice that numbers have been converted into integer variables, for easy manipulation in scripts.

Also included are examples of OSD commands for displaying the data. This method required that each application group define its own display command. I would really appreciate if anyone could test the storing of DVDSpy information and the OSD Examples, as I have only tested these with Winamp.

Please:
A) Let me know if some type of information isn't registered properly.
B) Tell me if the display format I have chosen for each multi-line OSD example is appropriate for the application. I didn't put much thought into this, and may have put useless information into the display, or set the order of things in a manner that isn't particularly smart :wink: I don't have all of these programs and don't know exactly what the information looks like.

BTW, the script doesn't get rid of PowerDVD and ShowShifter's strings yet because PowerDVD.Close and ShowShifter.Close events aren't implements in DVDSpy yet.

[SouthyPar]

Well, first off, I'm not the creator of DVDSpy (MMcM), so I can't help you with any problems you have with the 'old' GML file.


Before I change this setup I first have to understand the new method

This is in no way a new official DVDSpy change. It's merely my little suggested alternative of handling all of DVDSpy's information. If it suits you, there is no reason to change your current DVDSpy usage.


With the new GML script file I can't get it to work. First of all I noticed that the last command within the group should be a simple OSD command (most groups are still on 'Variable Manipulation Script'. The problem however ist that the events are not triggered by DVDspy (which worked with 1.19 ) Any idea ?

Damn, I forgot to double-check the OSD example thing... :o I'll send Ron a fixed version soon. As for the ZPLayer events not being triggered by DVDSpy... that's odd... I haven't tested it with ZPlayer Does anyone else have this difficulty?

Oh, and as for how to trigger the OSD. That's your choice really. You can but it on the .Elapsed event, which will cause the OSD to update itself frequently, but you would then also need a button for enabling\disabling that command. You can also simply trigger it with a button.