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 169184 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

foo_logitech_lcd

Reply #150 –
Watching: E:\Musik\Musik
Album List refreshed in: 0:00.001394
Startup time : 0:00.103982
foo_logitech_lcd.dll [Log]: Hardware acceleration enabled.
Opening track for playback: "E:\Musik\Musik\Hardstyle\Technoboy meets Ruffian - The Undersound.mp3"

That's the console.

I did turn the Hardware Acceleration off, and it did solve the problem.  But the spectrum went up side down instead.
And there are no black lines on some other, only the one i am using.

I have tried to reset the options, nothing.
And i tried all the other options to. Nothing.
On the Block spectrum, it wasnt the same, no lines.

But as i told before, Hardware Acceleration off solved it, but it went up side down.
Please help me ^^

// Mjolkspam

foo_logitech_lcd

Reply #151 –
Quote from: Mjolkspam link=msg=0 date=
I did turn the Hardware Acceleration off, and it did solve the problem.  But the spectrum went up side down instead.

Thanks for all the info - all seems fine (except the obvious problems of course). Annoyingly the upside down spectrum seems to be caused by a driver bug of some sort  - still I've implemented a fix that seems to sort it.

New version uploaded - fixes all three recently raised issues.

foo_logitech_lcd

Reply #152 –
Quote from: ectotropic link=msg=0 date=
New version uploaded - fixes all three recently raised issues.


Thanks for the update, i will try it soon enough, and report back to you

// Mjolkspam


foo_logitech_lcd

Reply #153 –
Sorry for the dubble post, i didnt find the Edit for my last post

Your uodate solved the problem    Thanks for your help etc.
I will report if i find anything more 

// Mjolkspam

foo_logitech_lcd

Reply #154 –
Hi,

Nice to see this plugin is updated, it works like a charm, I totally love it!

I found one weird bug though, when hardware acceleration is turned on the background of my display shows the area of my screen where foobar is... up-side-down. (I have a G19 now, because my G15 broke down and that orange one looks too cheap and ugly for me lol). I just turned it off and it's working flawlessly now so I guess that's not really a problem anyway... :-)

I'm just wondering though, is it possible to show the song I'm playing while watching at one of those visualisation thingies?

Thanks for bringing awesomeness!

foo_logitech_lcd

Reply #155 –
Hey so I saw this plugin and I was like SWEET!! And then I realized that my logitech keyboard isn't supported?  I have a Logitech MX5500.  Any chance you could add support for that? Thanks!

foo_logitech_lcd

Reply #156 –
After resuming from sleep there is no more anything related to plugin on lcd (G15 blue) until foobar2k is restarted. foo_g15lcd plugin is not installed.

foo_logitech_lcd

Reply #157 –
Quote from: Voe link=msg=0 date=
I found one weird bug though, when hardware acceleration is turned on the background of my display shows the area of my screen where foobar is... up-side-down. (I have a G19 now, because my G15 broke down and that orange one looks too cheap and ugly for me lol). I just turned it off and it's working flawlessly now so I guess that's not really a problem anyway... :-)

That's odd! Given that you are the first person to mention this I'm guessing that other people are not having the same issue, which would point at some OpenGL driver weirdness. Still since you can turn off hardware acceleration and it works fine it's not so much of an issue. However if it fixes itself at some point (maybe after a driver update or new version of the component) it'd be good to know.

Quote from: Voe link=msg=0 date=
I'm just wondering though, is it possible to show the song I'm playing while watching at one of those visualisation thingies?

It's certainly possible - I just need to code it  It's one of the things I've been planning to add for a while but other things have gotten in the way. Maybe the next version though...

Quote from: Voe link=msg=0 date=
Thanks for bringing awesomeness!

No problem!  Happy to help!

Quote from: henryforprez link=msg=0 date=
Hey so I saw this plugin and I was like SWEET!! And then I realized that my logitech keyboard isn't supported?  I have a Logitech MX5500.  Any chance you could add support for that? Thanks!

The short answer is no. Sorry.  The long answer is that until Logitech release an SDK for their other LCD products there is nothing I can (legally) do about this (any software that does support the other Logitech LCD products either has parts written by Logitech themselves or has used reverse engineering - which is prohibited by the EULA). The only thing I can suggest is that you contact Logitech and tell them you would like an SDK - maybe if enough people do that they might listen. (Though given my own contact with them I wouldn't count on it.)

Sorry it's not better news - but if an SDK does appear (or someone can provide a legal alternative) I will certainly support it.

Quote from: Lorond link=msg=0 date=
After resuming from sleep there is no more anything related to plugin on lcd (G15 blue) until foobar2k is restarted. foo_g15lcd plugin is not installed.

Thanks for the error report. Hmmm. Not sure how to fix that - I'm not sure if there is any way for the component to know anything about sleep mode. Can you check the console (View -> Console) after waking from sleep and let me know what it says relating to the component (relative entries will be prefixed with foo_logitech_lcd).

Unfortunately it's pretty difficult to debug anything that involves the PC effectively turning off!

foo_logitech_lcd

Reply #158 –
I would be very happy if you made it possible to show what I'm playing together with my viz in one picture.

Other than that, I already love you for making this comp. Beats the logitech default one by a quarter of a million.

foo_logitech_lcd

Reply #159 –
Hi, it's me again! lol

I also have the problem of the plugin dissapearing from my display, but it happens when my computer resumes from standby (windows xp).

I did the console thingy you mentioned and this is the message it showed:
foo_logitech_lcd.dll [Error] (.\LCDWrapper.cpp, NLCD::CConnection::Update, 218): Update bitmap not valid

I hope it's helpful

Also a quick question: Could someone tell me how to subscribe to this topic? tia

foo_logitech_lcd

Reply #160 –
Quote from: Habitats link=msg=0 date=
I would be very happy if you made it possible to show what I'm playing together with my viz in one picture.

Sorry for delayed response - this is likely to make into the next major release, but could be a while before I can get that done; unfortunately I've not been able to spend much time on the component recently

Quote from: Voe link=msg=0 date=
I also have the problem of the plugin dissapearing from my display, but it happens when my computer resumes from standby (windows xp).

I did the console thingy you mentioned and this is the message it showed:
foo_logitech_lcd.dll [Error] (.\LCDWrapper.cpp, NLCD::CConnection::Update, 218): Update bitmap not valid

I hope it's helpful

Ahhh - very useful - thanks. Could be a couple of things - but at least I have an idea of where to look. I'll try some things for the next version and hopefully at least one of them will work!

Quote from: Voe link=msg=0 date=
Also a quick question: Could someone tell me how to subscribe to this topic? tia

There is a button labelled "Options" on the first post on any page of a topic. Click it and select "Track this topic" - and you will be asked you you want to hear about posts, make you choice and you will be subscribed. (You can check it worked and make changes to your choice by looking at the the Subscriptions -> View Topics section of your control panel). HTH.

foo_logitech_lcd

Reply #162 –
Quote from: IronFly link=msg=0 date=
on foo_wlm the author add %streamname% as string to display web streaming name, can be nice to have this on track info visualisation option.

I don't listen to streams, so I'm probably missing something, but I'm really don't understand what "%streamname%" adds to foobar; how is it different from any of the existing meta-data available? (That is, can you not get the same information from %title% or %album% or use $meta(name) to get this information?) If you look at the meta-data of the stream (right click -> properties) if the information appears there then it is already available using either the built in %name% style tags or by using $meta(name) for tags that are non-standard (like URL).

Besides, as I understand it, I think that if a component provides title formatting correctly (via a metadb hook) then any formatting it allows is available to all components automatically; i.e. assuming (I understand the SDK correctly) if foo_wlm uses the metadb hook to provide the formatting then, if you have foo_wlm installed, you should be able to use %streamname% anywhere in foobar where title formatting is allowed - without any support from other developers. Having said that I would not be surprised if I had got the wrong end of the stick with the SDK, wouldn't be the first time (and documentation in this area is sketchy at best). Anyone else know for sure?

Anyway - if the the tag does add something new, and I am wrong about the metadb hook stuff (I'll investigate), then I'll happily add it - otherwise I don't think foo_logitech_lcd is the right place for that code.

foo_logitech_lcd

Reply #163 –
Quote from: ectotropic on
Besides, as I understand it, I think that if a component provides title formatting correctly (via a metadb hook) then any formatting it allows is available to all components automatically; i.e. assuming (I understand the SDK correctly) if foo_wlm uses the metadb hook to provide the formatting then, if you have foo_wlm installed, you should be able to use %streamname% anywhere in foobar where title formatting is allowed - without any support from other developers. Having said that I would not be surprised if I had got the wrong end of the stick with the SDK, wouldn't be the first time (and documentation in this area is sketchy at best). Anyone else know for sure?
The recommended way is to provide custom %fields% only in the context where they are relevant (or possible to provide, like %now%), i.e. passing the hook as the first parameter to the individual call to metadb_handle::format_title() or whatever function only.
Full-quoting makes you scroll past the same junk over and over.

foo_logitech_lcd

Reply #164 –
Quote from: Yirkha link=msg=0 date=
i.e. passing the hook as the first parameter to the individual call to metadb_handle::format_title() or whatever function only.

So, if I don't have the hook (because it is defined in another component) I have to write the same hook again myself? Or maybe look it up in a list of registered hooks? Or is there a third way?

Anyway, for now I'm less interested in the general, more interested in the specifics of this request - what is the right way to provide custom track formatting information in my component if another component already provides that formatting?

Sorry if I'm being a bit thick - just one of those days!

foo_logitech_lcd

Reply #165 –
Each [font= "Courier New"]metadb_handle::format_title()[/font] or similar function works like this: If a [font= "Courier New"]%field%[/font] is parsed, try to find a metadata field named as such for the current track, if not found, try the passed [font= "Courier New"]titleformat_hook[/font] (unless NULL), if still not found, try the [font= "Courier New"]global metadb_display_field_provider[/font]s.

An [font= "Courier New"]titleformat_hook[/font] object is something you can add to any such title formatting function (and you can supply even custom [font= "Courier New"]$functions()[/font], which the global hooks do not allow) and extend the information available to the user.

On the other hand, if you create a [font= "Courier New"]metadb_display_field_provider[/font] service, your fields are available during all title formatting in the whole application.

Now, I don't know what %streamname% is as well, but I assume it's the Winamp's %streamname% and I think you can't really add support for it neither way.
Full-quoting makes you scroll past the same junk over and over.

foo_logitech_lcd

Reply #166 –
Thanks so much! I can confirm that this works using a Logitech G13 Gamepad on Windows 7 x64 and Logitech LCD Manager 3.04.143.
-CyberInferno

foo_logitech_lcd

Reply #167 –
Quote
Thanks so much!

Not a problem

Quote
I can confirm that this works using a Logitech G13 Gamepad...

Excellent! I expected it would, but you never really know. Thanks for the info - much appreciated. A bit off topic, but what is the G13 like? Any good? Better than using the keyboard?

In other component related news - apologies to everyone for the lack of updates, it's been way too long since the last one, but as you can probably imagine it's not always easy to find the time to work on the component. However, rest assured that I'm still working on it and updates are coming (though as ever it could be a while). Just thought I'd let you all know that it's not dead quite yet

foo_logitech_lcd

Reply #168 –
Hey,

I've used this component since its release, it's really great and I appreciate all the work you've put into it.

But after a new installation of Windows 7 Ultimate 64-bit it seems to be struggling, sadly.

I'm using the latest version of the component, the version of Logitech LCD Manager is 3.04.143 and the keyboard I've got it the first version of G15. And I'm using the latest version of foobar2000 too, which is 1.1 (not beta!).

This is what the console is saying when I start foobar:

Quote
[17:02:05] foo_logitech_lcd.dll [Error] (.\LCDWrapper.cpp, NLCD::CConnection::OpenDevice, 111): Could not open supported LCD screen (last error: Invalid type context structure)
[17:02:05] foo_logitech_lcd.dll [Error] (.\LCDWrapper.cpp, NLCD::CConnection::NewConnection, 643): Failed to open LCD device
[17:02:05] foo_logitech_lcd.dll [Error] (.\LCDDisplay.cpp, CLCDDisplay::Initialise, 61): Failed to create LCD object. Plugin will be unavailable.
[17:02:05] foo_logitech_lcd.dll [Error] (.\foobarDLL.cpp, CFoobarDLL::threadProc, 129): Could not initialise LCD. Plugin will be unavailable.

Does anyone have an idea what it could be, causing it?

Thanks in advance!
 

foo_logitech_lcd

Reply #169 –
Quote
But after a new installation of Windows 7 Ultimate 64-bit it seems to be struggling, sadly.

I'm using the latest version of the component, the version of Logitech LCD Manager is 3.04.143 and the keyboard I've got it the first version of G15. And I'm using the latest version of foobar2000 too, which is 1.1 (not beta!).

...

That is very odd indeed - the Invalid type context structure message is coming from the Logitech software and is saying that the data the component is passing to the API is somehow wrong - but I can't see how that could be. Apart from anything else, your set-up looks almost exactly like mine.

In order to try to figure this out I'm going to need more information, so:
  • What has changed in terms of your set-up since it worked? (Windows version?)
  • Are you using the 64-bit version of the LCD software?
  • Do any other (non-Logitech) LCD components work?
  • Have you tried re-downloading the component and re-installing?
  • Have you tried re-installing the LCD software? (Uninstalling first)
Sorry there's no answer as such yet, but I'm sure we can figure it out!

foo_logitech_lcd

Reply #170 –
Quote from: ectotropic on
Quote
But after a new installation of Windows 7 Ultimate 64-bit it seems to be struggling, sadly.

I'm using the latest version of the component, the version of Logitech LCD Manager is 3.04.143 and the keyboard I've got it the first version of G15. And I'm using the latest version of foobar2000 too, which is 1.1 (not beta!).

...

That is very odd indeed - the Invalid type context structure message is coming from the Logitech software and is saying that the data the component is passing to the API is somehow wrong - but I can't see how that could be. Apart from anything else, your set-up looks almost exactly like mine.

In order to try to figure this out I'm going to need more information, so:
  • What has changed in terms of your set-up since it worked? (Windows version?)
  • Are you using the 64-bit version of the LCD software?
  • Do any other (non-Logitech) LCD components work?
  • Have you tried re-downloading the component and re-installing?
  • Have you tried re-installing the LCD software? (Uninstalling first)
Sorry there's no answer as such yet, but I'm sure we can figure it out!

Thanks a lot for the help, man. I'll definitely try it out as soon as I'll find the time for it (and I'll come back telling you how it went), it'll be in the next couple of days for sure!

Thanks a lot again.

foo_logitech_lcd

Reply #171 –
New version released!

As ever details on first post along with a link to the latest version. (Component DB version uploaded but not yet available via the new foobar update facility.)

Primarily a bug fix release in order to get the component removed from the troubleshooter  but also added a few minor things (mainly for colour LCD users).

On the troubleshooter thing, it seems like the component was crashing quite a bit for people who had colour LCDs and were using the album art functionality (particularly if you were using foobars random play mode) - this should be fixed, but if anyone has any further problems with this could they let me know? (It's a little difficult to test the G19 since I don't actually have one!)

Enjoy!

foo_logitech_lcd

Reply #172 –
Quote from: ectotropic on
Sorry there's no answer as such yet, but I'm sure we can figure it out!

God, you won't believe it. I started out by uninstalling foobar2000, removing every component (but I backed it up, of course), tried foobar2000 with only your component, no luck there. No other component was causing it.

Okay, so I uninstalled the driver and installed the latest version again, but you know what the real problem was? I didn't have Foobar2000 LCD Display & Visualizations enabled under Programs in the Logitech LCD Manager. Which I eventually found out when I just installed it and opened up the manager (your component wasn't enabled). Face meets palm once again on me. 

So that was THE real problem I guess, nothing was wrong! Awesome component in other words, just me that didn't have the obvious settings enabled. How could I even forget that? That answer will probably never become available, haha.

Thanks again for the help, and once again, I can finally enjoy it. Great update by the way!

foo_logitech_lcd

Reply #173 –
Quote from: Cyphe link=msg=0 date=
God, you won't believe it.

...

D'oh!

Quote from: Cyphe link=msg=0 date=
So that was THE real problem I guess, nothing was wrong!

That's the kind of bug I like! Ah well - least it got sorted, that's all that matters, right? I'm just glad it's not another issue for me to fix!

Quote from: Cyphe link=msg=0 date=
Thanks again for the help

No problem - thanks for letting me know what the issue was.

On the bright side now I can make sure other people check that before doing anything else - you might save others some pain

If you have any other problems just let me know (might want to check your settings first though )

foo_logitech_lcd

Reply #174 –
Just posting to say that you can add the G510 to the list of compatible devices, this works great on mine.