severe error SEVERE: res/missingsound.ogg

[Griffith 362]

keep getting this error in the console:

SEVERE: Input does not appear to be an Ogg bitstream.

SEVERE: res/missingsound.ogg

 

i think i should have put this on client issues, not sure. move if need be

Edited October 27, 2018 by Griffith

[Brash_Endeavors 4,735]

I am pretty sure I have been getting that for years now.

 

If it is not really a 'severe' issue -- and it certainly doesn't seem to be -- too bad they cannot change the wording to something less alarming than "SEVERE"

 

 

[Griffith 362]

ok thanks, its just i hadnt seen it before.

[Brash_Endeavors 4,735]

I googled the error to check my memory, and it seems "years" might have been an exaggeration but I can definitely find many instances dating back over a year.  This might be the first time it surfaced in wurm. 

 

As you can see from the first link, it pops up periodically and checking my own console logs, with no crashes it also shows in my own logs:

 

Writing to PlayerFiles\players\Nettles\logs\_Friends.2018-10.txt
SEVERE: Input does not appear to be an Ogg bitstream.
SEVERE: res/missingsound.ogg
Writing to PlayerFiles\players\Nettles\logs\_Skills.2018-10.txt
Initializing font texture for SansSerif (11, bold). Texture Size: 128
SEVERE: Input does not appear to be an Ogg bitstream.
SEVERE: res/missingsound.ogg
SEVERE: Input does not appear to be an Ogg bitstream.
SEVERE: res/missingsound.ogg
SEVERE: Input does not appear to be an Ogg bitstream.
SEVERE: res/missingsound.ogg
SEVERE: Input does not appear to be an Ogg bitstream.
SEVERE: res/missingsound.ogg
SEVERE: Input does not appear to be an Ogg bitstream.
SEVERE: res/missingsound.ogg
SEVERE: Input does not appear to be an Ogg bitstream.
SEVERE: res/missingsound.ogg
SEVERE: Input does not appear to be an Ogg bitstream.
SEVERE: res/missingsound.ogg
Time is Fri Oct 26 22:19:20 PDT 2018 

 

 

 

So probably not really that "severe". That's from an hour ago, and no crashing and no performance problems. I don;t know why it seemed to be "spamming" my console log, that might be new for me.

 

Might be related to running in hardware or software audio mode, or with sound cache disabled,  I dunno. Looks like we sort of discussed that a bit in the one thread I linked. 

 

 

Edited October 27, 2018 by Brash_Endeavors

[Batta 441]

9 hours ago, Griffith said:

keep getting this error in the console:

SEVERE: Input does not appear to be an Ogg bitstream.

SEVERE: res/missingsound.ogg

 

i think i should have put this on client issues, not sure. move if need be

I've been getting this lately, too.  It repeats over and over and over. Very disconcerting.

Everytime I see a cow moo soundlessly, or a dog barking with no voice, I think yep, that is a severe missing sound.  Lol

Edited October 27, 2018 by Batta

[MrCoolMan 261]

And i started to see them again after newest update again.

Dont know what missing sound is atm but something is on place

[MrCoolMan 261]

Isnt*

[Adambean 43]

I concur, also been getting this message for a very long time. (across multiple versions) 

 

Wurm overall isn't great with sounds for a variety of reasons. It's known. 

[Brash_Endeavors 4,735]

As I said above, I have gotten this for years now.  Can't be that "severe". 

 

Just ignore it? There are other issues in wurm where I'd prefer developers spend their time than hunting down one entirely random "error code" in the logs.