PDA

View Full Version : Anyone who is a bit bored.



Nonreality
2008-06-05, 04:47
If someone has the time could you look at this scan log. These keep bugging me as it looks like everything is going wrong but I don't seem to have any problems. Yeah I know quit looking at the scan logs. It's too late though, I'd just like to have a clue on what some of it means.
Is it just me or is there a reason that an attachment can be .doc 195kb .zip 195kb but the evil txt file only 19.5 kb ??? So anyway I hope this works, its a 95kb txt file in a zip. :)
Oh and thanks in advance.

ModelCitizen
2008-06-05, 05:48
I was the latest in a series of people who have asked on this forum why my log file fills up with loads of errors like this:

[08-06-05 02:25:03.1289] MPEG::Audio::Frame::broken (621) Warning: Use of uninitialized value in right bitshift (>>) at C:\PROGRA~1\SQUEEZ~1\server\lib/MPEG/Audio/Frame.pm line 621, <$mpeg> chunk 20107.

None of the enquiries ever got a reply.... so I guess no one knows. But anyway, as you say... the error doesn't appear to cause any problems.

MC

mherger
2008-06-05, 05:54
> None of the enquiries ever got a reply.... so I guess no one knows. But
> anyway, as you say... the error doesn't appear to cause any problems.

I really have no clue. But you might try to verify whether it's all files failing there or whether it's only a few of them. Reduce your collection to some subfolder, try again etc.

--

Michael

mherger
2008-06-05, 05:56
> If someone has the time could you look at this scan log. These keep
> bugging me as it looks like everything is going wrong but I don't seem
> to have any problems

Good news is it's only warnings, not errors. Lower the logging level to errors, and they should disappear.


--

Michael

Nonreality
2008-06-05, 07:26
haha It's only a warning. That almost bothers me more. Is it a warning like the oil light on my car or the gas caps loose. Big diff. :) And if it's a warning should I duck and cover or fix something?

mherger
2008-06-05, 07:35
> haha It's only a warning

Oh, I feared that reaction... but please see my first answer, too.

> if it's a warning should I duck and cover or fix something?

If your concern is fixing the issue, see my first posting. If you fear your disk filling up, then set the log level differently. If you really like to worry a lot, set it to debug. There will be even more confusing messages.

There's nothing to worry about in a warning, unless we understand what it's about.

--

Michael

Nonreality
2008-06-05, 08:59
Actually not too worried, just kept seeing that and kept wondering what the hell it's trying to tell me. Must be messages to the creators and not the congregation. They probably shouldn't put such a tempting, clickable line with choices of how many lines of indecipherable warnings you want to see. I'll just try my best not to click. tempting tempting aaaggghhhh 500 lines must be better than 100, oh but a 1000 lines maybe maybe I'll understand if I ....just ...click....

iPhone
2008-06-05, 09:14
Actually not too worried, just kept seeing that and kept wondering what the hell it's trying to tell me. Must be messages to the creators and not the congregation. They probably shouldn't put such a tempting, clickable line with choices of how many lines of indecipherable warnings you want to see. I'll just try my best not to click. tempting tempting aaaggghhhh 500 lines must be better than 100, oh but a 1000 lines maybe maybe I'll understand if I ....just ...click....

What is that old saying, "There is nothing to worry about until there is something to worry about......."

Another good saying is, "If it isn't broken, don't fix it!"

Then there is always, "Don't ask, Don't tell" oh that was for something else and the stupid government was involved. Nevermind.

As mherger said, they are only warnings not errors. When you hear this from your speakers:
Danger, Will Robinson, Danger
then it is time to duck and cover!
I am changing my logging setting to reduce the file size as I type.....

schiegl
2008-07-17, 06:04
Hi,

while "polishing" my music library - and hence my SC installation - i stumbled across this "Use of uninitialized value in right bitshift" error message when scanning.

I've narrowed it down to three problem mp3 tracks (creating 74 warning entries!!!). I tried various methods to rewrite/fix/repair the mp3 header using foobar->utils->rebuild-mp3-stream, mp3trim, and a few more.
This fixed 2 of the 3 files, one track remains which responsible for 66 lines of log alone (priority "warning" despite the fact scanner.* is set to output only error messages)

Did anybody find a working solution to get rid of those messages - or even better to fix the problem (mp3-frame-tags)?

thanks!

I'll attach my track to Bug 8070 (http://bugs.slimdevices.com/show_bug.cgi?id=8070)

kind regards,
Markus

autopilot
2008-07-17, 07:05
What is that old saying, "There is nothing to worry about until there is something to worry about......."

Another good saying is, "If it isn't broken, don't fix it!"

Then there is always, "Don't ask, Don't tell" oh that was for something else and the stupid government was involved. Nevermind.

As mherger said, they are only warnings not errors. When you hear this from your speakers:
Danger, Will Robinson, Danger
then it is time to duck and cover!
I am changing my logging setting to reduce the file size as I type.....

There is also a saying that goes "There is no smoke without fire" :p

MrSinatra
2008-07-17, 18:54
here's a great tool to help you examine your lame headers:

http://www.thelion.fm/mp3tools/LameTag/

u can find more info on it by just searching the forum here for: lame tag gui

schiegl
2008-07-18, 05:29
Hi,

thanks! i tried this one (LameTag) too, unfortunately without success.

Those CBR-mp3's don't have lame-tags at all - i probably have encoded them in the pre-lame-days with something like bladeenc.
The tool which finally was able to "repair" those tracks was MP3 repacker (http://www.hydrogenaudio.org/forums/index.php?showtopic=32379) and it's GUI WinMP3Packer (http://www.hydrogenaudio.org/forums/index.php?showtopic=40780&hl=). It even preserved all ID3-Tags.

the steps i've done to get rid of these messages:

disable mip for the time (to reduce the scanning time)
set scan, scan.import & scan.scanner to debug
perform a full scan and identify those mp3 tracks
use WinMP3Packer with default-options to re-package those tracks - sometimes converts CBR to VBR (!!! this overwrites the source !!! make a backup before and somehow save/note the timestamp if you'd later want to restore it)
enable MIP & disable debug log for scanner & perform another full-scan
no more warnings


kind regards,
Markus