Hi there!
I'm experiencing a problem that I can't find addressed in the documentation or on any of the posts on the forum.
GForce doesn't seem able to show some track info properly. Specifically letters with accents on are never shown when GForce displays the track titles.
The result is that when I play...
"Kélé Mandi" by "Rokia Traoré",
GForce displays...
"Kl Mandi" by "Rokia Traor".
I've tried changing font to see if this would help but I realised that outside GForce the fonts I was using supported these characters so I assume it's something internal?
As an aside here, tracks like
"The Box, Pt.1" by "Orbital"
becomes
"The Box, Pt" by "Orbital".
With something like this it's easy just to remove the abbreviation so the track name becomes "The Box, Part1" by "Orbital" but I'm pretty loathed to anglicise all my world music collection.
This isn’t a big thing I know, but it's irritating.
I'm sure I can't be the first to spot this.
Is there an easy fix that I'm missing?
Update...
I've just had a look to see if I have the same problem with iTunes and I don't! The track names are displayed correctly. So I'm now assuming this has got to do with how Winamp5 talks to GForce. I use Winamp5 as my default player now as MusicMatch won't pass on any track title info to GForce.
Anybody got any thoughts?
Track title info and Windows
Moderators: BTT, andy55, b.dwall, juxtiphi
Re: Track title info and Windows
In short, to my knowledge, there's no way to get the unicode name of a track in winamp. Now, if you tell me that you've seen other winamp plugins show it properly, then it looks like i need to do some digging on how to get unicode track info. But, again, last I checked it wasn't there.nuytsia wrote:Hi there!
I'm experiencing a problem that I can't find addressed in the documentation or on any of the posts on the forum.
GForce doesn't seem able to show some track info properly. Specifically letters with accents on are never shown when GForce displays the track titles.
The result is that when I play...
"Kélé Mandi" by "Rokia Traoré",
GForce displays...
"Kl Mandi" by "Rokia Traor".
I've tried changing font to see if this would help but I realised that outside GForce the fonts I was using supported these characters so I assume it's something internal?
As an aside here, tracks like
"The Box, Pt.1" by "Orbital"
becomes
"The Box, Pt" by "Orbital".
With something like this it's easy just to remove the abbreviation so the track name becomes "The Box, Part1" by "Orbital" but I'm pretty loathed to anglicise all my world music collection.
This isn’t a big thing I know, but it's irritating.
I'm sure I can't be the first to spot this.
Is there an easy fix that I'm missing?
Update...
I've just had a look to see if I have the same problem with iTunes and I don't! The track names are displayed correctly. So I'm now assuming this has got to do with how Winamp5 talks to GForce. I use Winamp5 as my default player now as MusicMatch won't pass on any track title info to GForce.
Anybody got any thoughts?
andy
Track title info and Windows
Cheers for the response Andy!
I checked out the Winamp forum and it's very much as you say.
There's an acknowledgement that unicode support is an issue, but at the present moment in time little feeling that winamp should be overhauled as this will impact on varied plug-ins.
I couldn't find any plug-ins that explicitly addressed this problem so I'm assuming at the moment it's winamp itself that needs the tinkering.
However there is one odd point though that I should mention. The Winamp forum discussion was very frank in that Winamp does not support unicode. But I happened to play the same tracks this afternoon with winamp and tried the MilkDrop visualiser to see how it faired.
Surprisingly Milkdrop did display the tracks correctly. So perhaps there is a way around this after all?
Sorry for the whingy post.
I should just say that I'm really pleased with the latest version. The new configs that have been added are brilliant!
Congratulations all round to those involved.
James
I checked out the Winamp forum and it's very much as you say.
There's an acknowledgement that unicode support is an issue, but at the present moment in time little feeling that winamp should be overhauled as this will impact on varied plug-ins.
I couldn't find any plug-ins that explicitly addressed this problem so I'm assuming at the moment it's winamp itself that needs the tinkering.
However there is one odd point though that I should mention. The Winamp forum discussion was very frank in that Winamp does not support unicode. But I happened to play the same tracks this afternoon with winamp and tried the MilkDrop visualiser to see how it faired.
Surprisingly Milkdrop did display the tracks correctly. So perhaps there is a way around this after all?
Sorry for the whingy post.
I should just say that I'm really pleased with the latest version. The new configs that have been added are brilliant!
Congratulations all round to those involved.
James
Re: Track title info and Windows
I'll look into this for something for 2.7.1. It's possible thatr because the author of milkdrop was a nullsoft employee, r. geiss used non-API methods to get a hold of the track info.nuytsia wrote:Cheers for the response Andy!
I checked out the Winamp forum and it's very much as you say.
There's an acknowledgement that unicode support is an issue, but at the present moment in time little feeling that winamp should be overhauled as this will impact on varied plug-ins.
I couldn't find any plug-ins that explicitly addressed this problem so I'm assuming at the moment it's winamp itself that needs the tinkering.
However there is one odd point though that I should mention. The Winamp forum discussion was very frank in that Winamp does not support unicode. But I happened to play the same tracks this afternoon with winamp and tried the MilkDrop visualiser to see how it faired.
Surprisingly Milkdrop did display the tracks correctly. So perhaps there is a way around this after all?
Sorry for the whingy post.
I should just say that I'm really pleased with the latest version. The new configs that have been added are brilliant!
Congratulations all round to those involved.
James
andy
Andy have a look at Ryan's VisSDK. I haven't used for a bit but I think it has track info, etc in and have the same engine as MilkDropv1.04
http://www.nullsoft.com/free/vms/
http://www.nullsoft.com/free/vms/
I've looked into things and it's still as I remember: in the mega SDK, he grabs the window title and proceeds to tear off the junk ("Paused", playlist #). the problem is that this isn't always reliable (it's a hack) and suffers the problem of not knowing that the track name is (vs. the artist name--it globs them together). i've looked around further on a lot of forms and still have yet to see any indication there's any way to get unicode track info for the current track (but I'd love to be proven wrong so I can add support).Rovastar wrote:Andy have a look at Ryan's VisSDK. I haven't used for a bit but I think it has track info, etc in and have the same engine as MilkDropv1.04
http://www.nullsoft.com/free/vms/
andy
Post subject: Track title info and Windows
Well I know this has been a long time coming, but thanks for looking into this Andy. I'm sorry it proved to be a fruitless investment of your time.
Thank you for your time.
James.
Thank you for your time.
James.
Hello people!
It's bee a while I haven't been here. I would like to say I'm really happy of this wonderful vis getting updated regularily with all these nice features.
Everything is perfect but this stingy problem of charactersupport. I would like to be informed if anything could be addressed considering this problem.
It is really odd why winamp can address unicode characters in playlist and not in plug-ins correctly. I was even trying to just simply write unicode text into the script files instead of just reading them from tags. I thought the problem was getting them out of tags but I see now reading this topic that it is sending them through Winamp plug-in handler.
Since Winamp had been sold I doubt we'll get anything from them, so I'm checking if this feature is to be added to G*Force anytime.
It's bee a while I haven't been here. I would like to say I'm really happy of this wonderful vis getting updated regularily with all these nice features.
Everything is perfect but this stingy problem of charactersupport. I would like to be informed if anything could be addressed considering this problem.
It is really odd why winamp can address unicode characters in playlist and not in plug-ins correctly. I was even trying to just simply write unicode text into the script files instead of just reading them from tags. I thought the problem was getting them out of tags but I see now reading this topic that it is sending them through Winamp plug-in handler.
Since Winamp had been sold I doubt we'll get anything from them, so I'm checking if this feature is to be added to G*Force anytime.
Just to be clear Winamp was *sold* about 5 years ago when AOL/Time Warner bought Nullsoft (I think takeover proceeding where underway in June 2000). Since then Winamp 5 came out amongest other things.Gregorius wrote:Since Winamp had been sold I doubt we'll get anything from them, so I'm checking if this feature is to be added to G*Force anytime.
Although it is true that most of the production team have left and devolpment has slowed (to a crawl at times) somewhat.
