Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: foo_logitech_lcd (Read 168786 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

foo_logitech_lcd

Reply #125 –
Wanted to say... much love for this.  I was a bit sad when the old plugin stopped working one day. Cheers for the new one.

Visualizations are really something, even though I don't use them.

foo_logitech_lcd

Reply #126 –
EDIT:  Wow, I can't believe I missed the 'to background on play/pause'.  No problems, thanks for the awsome plugin .
 

foo_logitech_lcd

Reply #127 –
Bug: It seems that song length can sometimes be rounded up to x:60. Here's a picture. The song's length is 2:59:513.

foo_logitech_lcd

Reply #128 –
'Display track info on song change' doesnt work even with this new Version 0.4.0. It have never worked for me. I've tried to 'Rise display priority on song change' that doesnt help, but it just shows the info on screen for 1sec. Even when I've 5 seconds 'time to display' value. I have G15 v1. Please fix this or tell me how to get it work.

foo_logitech_lcd

Reply #129 –
Quote from: Ligushka on
Bug: It seems that song length can sometimes be rounded up to x:60

Yup - this is a slightly different case of something I was aware of (due to code added to prevent the skipping of seconds that used to happen, this new bug occasionally occurs). Should be fixed by next release.

Quote from: nahka on
'Display track info on song change' doesnt work even with this new Version 0.4.0. It have never worked for me.

Well, since it seems to work for others it would appear to be something to do with how things are set-up on your PC. However, from what you are saying I have a sneaking suspicion that what you want to do is currently unsupported; if you want to have something not related to foo_logitech_lcd displayed on the screen and then to be interrupted by foo_logitech_lcd when the song changes (showing the song information for 5 seconds) before returning to the other display then that is not supported currently (due to the SDK/API issues). (That is, if you want the Clock to be shown on the screen normally, but when a song changes you want the song info to be displayed briefly before returning to the Clock - this is not supported)

On the other hand, if you have the foo_logitech_lcd visualisations running and want them to be interrupted on song change with the song information then that is supported and should work, if it is this that is not working then I will look into it further though I can't think what might be breaking it.

Hope that makes sense.

foo_logitech_lcd

Reply #130 –
Oh, thats sad. I excepted it to work like with winamp, that when I have clock display and then I select next track the display will show track info for few secs. I guess I just have to wait till the SDK supports it
Thanks anyway

foo_logitech_lcd

Reply #131 –
np - sorry it's not supported yet. I am looking into getting it working (without additional SDK support) but don't know how long it might take.

foo_logitech_lcd

Reply #132 –
I found an instance where the component displays 0:60 rather than 1:00. picture

It happens with several other songs from the same concert. The files in question are FLAC files. foo_logitech_lcd is 0.4.0. Don't really know what other information to provide.

foo_logitech_lcd

Reply #133 –
First of all: loving this plugin
I use it on my G19 to display album art with the name of the artist/album/etc on top. However, sometimes that's not readable.
Also, an option for using the correct aspect ratio for images would be nice

Here are two images to illustrate my point:

Image 1

Image 2

foo_logitech_lcd

Reply #134 –
Sorry for the lack of update(s) & response(s) from me recently - Modern Warfare 2 followed by Christmas followed by a mammoth PC rebuild project (ongoing) have meant I've had little time to do anything with this plugin (and have been offline for most of the last 3 weeks!). Hopefully I'll get back to properly dealing with the plugin this week and get a new version out ASAP.

Answering the posts I have not yet responded to:

Quote from: Ligushka link=msg=0 date=
I found an instance where the component displays 0:60 rather than 1:00. picture
Fixed in my dev version - all displays of 60 secs should be gone.

Quote from: Jerre link=msg=0 date=
Also, an option for using the correct aspect ratio for images would be nice
Already added to my dev version (always intended to add it, but other things took precedence).

Quote from: Jerre link=msg=0 date=
...However, sometimes that's not readable.
This is a tough one - I had realised that this would be an issue, however I'm not sure of how to fix it. All the options I can think of have drawbacks that make them difficult to commit to. Current thoughts:
  • Add font outline support with selectable outline & fill colours (not sure how to do this - all text is rendered via GDI which I am not hugely familiar with)
  • Add a solid background to the text - where text is the background would be coloured a single colour (I doubt this would look very nice!)
  • Calculate the average colour for the image and if close to selected text colour invert text colour (potentially expensive to calculate, and would not always work)
  • Use non-additive blending (Text colour would not be as chosen, but would use chosen colour to modify image colour - may not be possible with GDI text)

If you (or anyone) has a preference let me know - or even better if anyone has an idea of how they would like it to look (and maybe a photoshop mash-up of it) that would be brilliant. Otherwise I'll continue to think about it and see what I can come up with.

Of course it could be "fixed" if you set up a secondary track info screen (copy of the 1st) with a different text colour then manually switched when there was an issue!

foo_logitech_lcd

Reply #135 –
I'm back! 

And with a bunch of goodies too

Hopefully future updates will not take so long! (No promises!)

First up the latest version is uploaded and ready for people to play with (requires foobar v1.0.0). This is a fairly major update and although not much may have appeared to change on the outside, much of the internals are new, and hopefully improved. See the first post for an indication of some of the changes.

Two of the major changes are; hardware acceleration and improved spectrum response. Although hardware acceleration is in, it requires some OpenGL extensions to work so may not be possible on all machines - if it is not available some things will be disabled, additionally if you have problems with the component, try disabling hardware acceleration. Improved spectrum response is less clear cut - there are now 4 non-linear modes that use a variety of logarithmic functions with several new associated variables to play with - if people find it overly complicated or not actually any better then I will remove it, but personally I like the results better.

As ever with such large changes, bugs are inevitable - hopefully my testing has picked up the major ones though!

As well as working on the component I've also been in touch with Logitech - which has been a somewhat fruitless endeavour. The result is this:
  • Support for Logitech LCDs that don't use the LCD Manager (e.g. the DiNovo line) will not be possible as Logitech are not going to release an SDK or support anything that I would need to do it.
  • Support for the Winamp style keyboard light changes will also not be possible, again as Logitech are not going to add it to the SDK. (It would therefore require reverse engineering, which would breach the license agreement - third party dlls breach the agreement for this reason)
  • The engineers responsible for the LCD Manager software have confirmed that users with Z-10 speakers and other older hardware which no longer has driver updates (and old versions of the LCD Manager) can happily download and install the G15 version of the software and it should work perfectly - if anyone finds any problems with this then let me know as I've been asked to forward on any such issues.

And I thanks about it for now...

Enjoy!

foo_logitech_lcd

Reply #136 –
Quote from: ectotropic on
  • Support for the Winamp style keyboard light changes will also not be possible, again as Logitech are not going to add it to the SDK. (It would therefore require reverse engineering, which would breach the license agreement - third party dlls breach the agreement for this reason)!


Ahh gutted, was really hoping you could implement this. So let me guess this right, it would be possible using third party dlls but it would be breaching license agreement?
Thanks for enquiring btw.
Anomaly.

foo_logitech_lcd

Reply #137 –
Quote
So let me guess this right, it would be possible using third party dlls but it would be breaching license agreement?

That's it precisely - I tried to present a case to the Logitech guys for them supporting it, but no dice.  I'll continue to think about it anyway - you never know, there might be a loophole somewhere, but as it stands it looks like it wont ever be possible.

Quote
Thanks for enquiring btw.

np - just sorry the result wasn't better.

foo_logitech_lcd

Reply #138 –
Hello. Nice plugin .

I have g15. The plugin shows song name and artist but when I press buttons under the screen the following happens: those animated things like Spectrum Analyzer or Oscilloscope appear on the display just for a moment and then display switches back to song/artist name. Just like if the first key is constantly pressed. But they work fine in other applications. Any ideas? Thanks.

foo_logitech_lcd

Reply #139 –
Quote
Hello. Nice plugin .

Thanks!

Quote
I have g15. The plugin shows song name and artist but when I press buttons under the screen the following happens: those animated things like Spectrum Analyzer or Oscilloscope appear on the display just for a moment and then display switches back to song/artist name. Just like if the first key is constantly pressed. But they work fine in other applications. Any ideas? Thanks.

Sounds odd - not sure what could be causing that  so some questions:
  • Can you check the console (View->Console) and let me know what it says relating to the component (relevant entries are prefixed with the component name)?
  • Do you have "Display track info on song change" selected? If so does turning it off fix things?
  • What is your track info text set to be? (Seeing all lines (even if the last is disabled) would be helpful)
  • Does it just happen with specific tracks or all you have tried? Is there anything special about the tracks it happens on? (e.g. streaming tracks, etc.)
If you could let me know the answers to them then I'll better be able to help!

foo_logitech_lcd

Reply #140 –
Quote
Sounds odd - not sure what could be causing that  so some questions:
  • Can you check the console (View->Console) and let me know what it says relating to the component (relevant entries are prefixed with the component name)?
  • Do you have "Display track info on song change" selected? If so does turning it off fix things?
  • What is your track info text set to be? (Seeing all lines (even if the last is disabled) would be helpful)
  • Does it just happen with specific tracks or all you have tried? Is there anything special about the tracks it happens on? (e.g. streaming tracks, etc.)
If you could let me know the answers to them then I'll better be able to help!


Hello. Thanks for your time and sorry for troubling you.

The problem is in my g15.
Just found out that the fourth button does not work as it should. Because first 3 buttons work fine if I disable Vis Mode 4 (track/artist names). When I enable any of VisMode4 and apply settings - after any key pressed problem reappears.
Still would be great if I could remap visualizations to different buttons (for example artist/track for 1st button).

Thanks

foo_logitech_lcd

Reply #141 –
I'm so happy that this component is still updating!

By the way, could you support MX5500?

foo_logitech_lcd

Reply #142 –
Quote from: jhjntjkf0 link=msg=0 date=
The problem is in my g15.
Just found out that the fourth button does not work as it should. Because first 3 buttons work fine if I disable Vis Mode 4 (track/artist names). When I enable any of VisMode4 and apply settings - after any key pressed problem reappears.

Are you sure it's your keyboard? Does it cause problems in any other G15 enabled applications? I wouldn't be so quick to assume the hardware is broken if it's only this component that shows up the issue. The behaviour you mention could easily still be caused by some bug in my code (assuming you have not seen it happen in other applications). If you are not sure then get me the answers to the questions I asked before and I'll see if I can see what might be happening - if you're sure it's the keyboard then that's unfortunate, and I'm sorry to hear that

Quote from: jhjntjkf0 link=msg=0 date=
Still would be great if I could remap visualizations to different buttons (for example artist/track for 1st button).

This is on the "To Do" list - just need to work out a nice way to do it and actually get round to doing it. Hopefully get it done soon.

Quote from: etonline link=msg=0 date=
I'm so happy that this component is still updating!

lol - glad to make you happy  I have no plans to stop updating any time soon! Though updates will likely be less frequent than they have been - they will still happen! (Also, if/when I do stop updating things I will be sure and make sure the source code is available so someone else can take up the reins!)

Quote from: etonline link=msg=0 date=
By the way, could you support MX5500?

Good question - from a quick look at it I think the answer is no (due to Logitech not supporting an SDK for it). I'll double check that when I have more time, but don't hold your breath. Sorry.

foo_logitech_lcd

Reply #143 –
Quote from: ectotropic on
Are you sure it's your keyboard?

Yes. Cleaned it and now it works fine 

One more thing (if not known yet):
When restarting or shutting down the PC without exiting Foobar (with hardware acceleration enabled in plugin) - a standard window popups "Waiting for program: foo_logitech_lcd_hw_window" and then another one offering to end program. This stops the shutting down process.

foo_logitech_lcd

Reply #144 –
Quote
Quote from: ectotropic on
Are you sure it's your keyboard?

Yes. Cleaned it and now it works fine 

Typical! Ah well - least it works. Computers, who needs them?

Hopefully it will all just work fine from now on!

Quote
One more thing (if not known yet):
When restarting or shutting down the PC without exiting Foobar (with hardware acceleration enabled in plugin) - a standard window popups "Waiting for program: foo_logitech_lcd_hw_window" and then another one offering to end program. This stops the shutting down process.

I wasn't aware of that, thanks for letting me know - I'll try and fix it for the next version.

foo_logitech_lcd

Reply #145 –
Hi,

I would like to report a little bug :

It's in Visualisation Options / Vis Mode 4 / Text / Left Time + Right Time

When I select TOTAL, it shows PLAYED. When I select PLAYED, it shows REMAINS, and so on.

My specs:
G15 version 1 (black n white & 18 shortcut buttons)
plugin version 0.5.1
foobar2000 v1.0
Windows 7

foo_logitech_lcd

Reply #146 –
I have a one suggestion.
When I press stop (either using the media keys or on Foobar's GUI) the progress bar doesn't reset. It acts as if the music just paused. I think it would be better if it immediately reset the position.
I would also like to know what font it is you're using in this image:

(bottom right frame)

I'm using WindowsXP and Windows7, G15 v1, version 0.5.1

Thanks for your plugin!

foo_logitech_lcd

Reply #147 –
Quote from: junkninja on
I would like to report a little bug...

Noted - thanks. Will look into it - should be fixed in the next version.

Quote from: TommySprat on
When I press stop (either using the media keys or on Foobar's GUI) the progress bar doesn't reset. It acts as if the music just paused. I think it would be better if it immediately reset the position.

That would make sense! Not sure why it doesn't already tbh - again should be fixed in the next version.

Quote from: TommySprat on
I would also like to know what font it is you're using...

I think it's Arial - but I could be wrong (I was playing around with fonts at the time to get some good looking screen-shots). Note that since that is a capture from the emulator it may not look the same as the screen, also the screen shot is from a much older version of the component - it's possible that things look differently now.

foo_logitech_lcd

Reply #148 –
Hello, i got a little problem.

[a href="http://img705.imageshack.us/i/20100309032.jpg/" target="_blank"]
And i cant get rid of them. I don't see them on the Progress & Time Bar.

So i wonder what the problem could be?   
Thanks!

// Mjolkspam

foo_logitech_lcd

Reply #149 –
Quote from: Mjolkspam on
So i wonder what the problem could be?

Good question! Sadly not one I can answer immediately.

It looks like the gaps that appear when you use the "Gap" option with the "Block Spectrum Analyser", but only affecting part of the range which is odd and I can't think of what might cause that.

It might help me work it out if you could answer some questions:
  • Can you check the console (View->Console) and let me know what it says?
  • Do you see those lines on the VU Meters or any of the other spectrum visualisations?
  • Have you tried resetting the component options? (If not then try it)
  • Can you try the following (and tell me if any change anything):
    • disable hardware acceleration and all "Expert Mode" settings
    • switch to the "Block Spectrum Analyser", set the number of blocks to 160 and all other settings to the same as your "Spectrum Analyser" and see if that looks the same (make sure "Gap" is not checked)
    • uncheck the "Gap" option on all the spectrum visualisations
    • disabling all the spectrum visualisations except "Spectrum Analyser" (i.e. the first)
Hopefully if you answer/try those then something will happen that will help me work out what is going on.