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.hydroge
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
--
MrSinatra
www.LION-Radio.org
Using:
Squeezebox2 (primary) / SBR (secondary) / SBC - w/SC 7.1beta - Win XP
Pro SP
iPhone;309076 Wrote:
> 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 go
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/re
Nonreality;309071 Wrote:
> 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 inde
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 se
> 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 rea
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?
--
Nonreality
*-If the rule you followed brought you to this, what good is the rule.-*
-
> 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
> 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
I was the latest in a seies 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 l
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
12 matches
Mail list logo
