Analogue/digital VU

[jstraw]

Yes, with some small modifications:
1. You probably want to put your own description in extensions/details/title
2. You need to change the url element so it points to the zip on your server instead of my Google Code project
3. You can remove the <sha>...</sha> element during testing, else you will need to recalculate a new sha checksum everytime you change the zip

And you will of course need to add the url to the repository file on your server in the SBS Settings/Plugins.

If you have a server that's available always (24/7), I'll remove it from my repository. In that case, I suggest that you add your repository url to the following wiki page so users know where to find it:
http://wiki.slimdevices.com/index.ph...r_Repositories

If you add it to the above wiki page we will also add it to the list of official repositories which are available by default, this way the users doesn't have to add the url to your repository manually in SBS Settings.

If your server isn't available all the time, just point me to the zip file when you have finished tweaking it and I'll put it on my server.

It will always be available. How do I generate the sha checksum?

I'm going to develop several meter styles for the VU since that one is very bright at night. What would be nicer would be a meter style user in the UI instead of having to uninstall/install to change them.

[erland]

It will always be available. How do I generate the sha checksum?

From a command line you run:
sha1sum YellowVUMeter-1.0.zip
(Where YellowVUMeter-1.0.zip is your zip file)

The sha1sum tool is available by default on Linux, but on Windows you will have to download it from here:
ftp://ftp.gnupg.org/gcrypt/binary/

I'm going to develop several meter styles for the VU since that one is very bright at night. What would be nicer would be a meter style user in the UI instead of having to uninstall/install to change them.

Someone will have to develop a third party applet to support that.
It could probably be done by patching the standard VU Meter source code, but I think a third party applet for it is a better solution than modifying Logitech's source directly.

[jstraw]

<patch name="YellowVUMeter" target="fab4" version="1.0" minTarget="7.5" maxTarget="7.5">

Can you break down the elements of that line for me?

[erland]

<patch name="YellowVUMeter" target="fab4" version="1.0" minTarget="7.5" maxTarget="7.5">

Can you break down the elements of that line for me?

name=identity of the patch. If you make several patches they should have different values in the "name" attribute. Remember to also give them unique values in the "title" element as this is the text that is shown to the user.

target=specifies which player types it works on, possible values are:
- fab4 -> Touch
- baby -> Radio
- jive -> Controller
- squeezeplay -> SqueezePlay Desktop
You can also combined them, for example "fab4|baby" indicates that it works on both Touch and Radio. I think Touch is the only one that have visualizers, so "fab4" should be the correct value.

version=Version of the patch, preferably you should increase it if you make a new version of the same patch. It isn't used at the moment but future versions of the "Patch Installer" applet might use the version attribute to indicate to the user if the patch can be upgraded to a new version. In the current version the user have to uninstall and reinstall the patch.

minTarget=Minium version of the firmware that's required, "7.5" should be correct for visualizers since they weren't available in earlier versions

maxTarget=Maximum version of the firmware that is allowed. Possibly you might want to change this in the future, but at the moment I'd recommend that you keep "7.5" as we don't know if Logitech will change anything in the file structure in the next version.

You can have several <patch>...</patch> elements in the same repository file, look at my testing repository which I linked to in an earlier post for an example.

[jstraw]

From a command line you run:
sha1sum YellowVUMeter-1.0.zip
(Where YellowVUMeter-1.0.zip is your zip file)

The sha1sum tool is available by default on Linux, but on Windows you will have to download it from here:
ftp://ftp.gnupg.org/gcrypt/binary/


Someone will have to develop a third party applet to support that.
It could probably be done by patching the standard VU Meter source code, but I think a third party applet for it is a better solution than modifying Logitech's source directly.

I downloaded sha1sum.exe and I haven't a clue what to do with it. Is this sha thing important?

[jstraw]

name=identity of the patch. If you make several patches they should have different values in the "name" attribute. Remember to also give them unique values in the "title" element as this is the text that is shown to the user.

target=specifies which player types it works on, possible values are:
- fab4 -> Touch
- baby -> Radio
- jive -> Controller
- squeezeplay -> SqueezePlay Desktop
You can also combined them, for example "fab4|baby" indicates that it works on both Touch and Radio. I think Touch is the only one that have visualizers, so "fab4" should be the correct value.

version=Version of the patch, preferably you should increase it if you make a new version of the same patch. It isn't used at the moment but future versions of the "Patch Installer" applet might use the version attribute to indicate to the user if the patch can be upgraded to a new version. In the current version the user have to uninstall and reinstall the patch.

minTarget=Minium version of the firmware that's required, "7.5" should be correct for visualizers since they weren't available in earlier versions

maxTarget=Maximum version of the firmware that is allowed. Possibly you might want to change this in the future, but at the moment I'd recommend that you keep "7.5" as we don't know if Logitech will change anything in the file structure in the next version.

You can have several <patch>...</patch> elements in the same repository file, look at my testing repository which I linked to in an earlier post for an example.

Ok, thanks. That all made sense.

[jstraw]

Other than the sha thing, this is probably ready to roll:

http://www.smallproblem.com/touchmet...ogvumeters.xml

[maggior]

I played with this today. I want a really classic meter look. This will need tweaking after I figure out how to ssh into my Touch...that concept is eluding me.

Here's a first run at it:

This looks really really cool! I'm interested to see what you come up with for different color schemes, especially something for use in a dark room. It'd be nice to see something that would emulate that eery glow of VU meters in the dark :-).

I'm glad work is being done on a VU meter screensaver. I've used it on my SB3s since I bought them almost 3 years ago.

[jstraw]

I'm underway with the next set of meters but I need to get my testing environment sorted out. Anyone know if it's possible to get the Patch Installer applet installed on Squeezeplay? I'm not having luck.

[jstraw]

Might look something like this: