Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
LCDHype 0.6.0.5 bugs
#1
1. In some conditions (20 complex scripts), when I try moving the bottom most screen upward, the first screen screws up totally (it stops working, it stops initializing and doing nothing as it supposed to). Sometimes I get an access violation error and LCDHype stops resonding. It's not the script that causes it, I've tried it many times, as soon as I move the 25-th screen to the 9-th place for example, it stops working.

2. Calling %Common.ChangeScreen(timeout, screennumber) with (timeout > 1000) doesn't execute or executes in a weird way - the next time I call it doesn't work.

3. After manually (or automatically) re-tagging an MP3 file (no matter ID3v1 or ID3v2), the fields I've edited screw up - they have 40-60 empty chars (character 0) displayed on the screen, for example:

Britney Spears#################### - Hit Me Baby###################

where the "#" is the 0 char (a square depending on the font). It's happening with all the songs I've tried, it's not depending if you use cyrillic or english fonts.

4. Winamp VU is very much sensitive to the middle frequencies (2-10KHz), it doesn't catch the bass at all, even the opposite, when the bass hits, the VU is getting smaller ?! Maybe a "respond frequency" parameter to the VU's would fix that.

5. Winamp Spectrum in FFT mode is responding much more to middle frequencies than to low and high. The other buggy thing is all the bars start responding when you play a raw 1-2KHz sound. That explains why when playing rock tracks (having more middle frequencies) all the bars start jumping like crazy.

6. Winamp Spectrum with no filtering is too unsensitive to anything. The bars move too little.

7. Winamp Spectrum in oscilloscope mode have the same bugs as in (5.) and (6.), probably it uses the same algorithm and only ads a FIR to get the curve out. I don't think its implementation is looking like a oscilloscope.

Winamp version is 5.52.
Windows XP SP2

This is tested on few machines and bugs I've just reported have been seen on all of them.
#2
Hi all. 1st post.

Agreed re: the FFT data - it's certainly not averaging frequency spectrum divided by # of bands... e.g. if you make a 10-band, I cannot tell where in the frequency range it's pulling the data even pushing 65 fps on the G2S oLED driver that Predator_MF above coded... (it's so tight, you can't tell if it's got any latency issues, either.)

In the WinAmp world, there was/is this great spectrum plugin, simply called "Classic Spectrum Analyzer", by Mike Lynch. The reason I bring this up is, why re-invent the wheel, if it's already debugged? Grab that plugin from the repository and play with it, and you'll see what I mean. The source isn't in the plugin archive, though. (email mlynch at gmail dot com.)
#3
i got the same square artist title problem. any suggestions? updates? plugins? workarounds..?
#4
QUOTE

3. After manually (or automatically) re-tagging an MP3 file (no matter ID3v1 or ID3v2), the fields I've edited screw up - they have 40-60 empty chars (character 0) displayed on the screen, for example:

Britney Spears#################### - Hit Me Baby###################

Well i have With Version 6.1.1 No Problems
and with japanes chars too
only the fonts are not coreckt but this is i mean a winamp Api problem
maybe you should try
%WinAmp.Title() - %WinAmp.Artist()
And not
%WinAmp.RawTitle()

an with the Spectrum analyser
i mean thats winamp resposns some thing wrong
this kind of problem i have too with Jalcds


Forum Jump:


Users browsing this thread: 1 Guest(s)