Still sound bugs with update
solitha opened this issue · 3 comments
I'm using v4.0.17 and tried installing v4.0.17-nolib to see if it helped, but still getting errors.
3x SilverDragon\outputs\announce.lua:245: PlaySoundFile Error - Invalid fileDataID for sound. [C]: in function PlaySoundFile'
SilverDragon\outputs\announce.lua:245: in function PlaySound' SilverDragon\outputs\announce.lua:271: in function <SilverDragon\outputs\announce.lua:252> [C]: ? ...Tom\libs\CallbackHandler-1.0\CallbackHandler-1.0-7.lua:29: in function <...Tom\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:25> ...Tom\libs\CallbackHandler-1.0\CallbackHandler-1.0-7.lua:64: in function Fire'
SilverDragon\outputs\announce.lua:174: in function ?' ...Tom\libs\CallbackHandler-1.0\CallbackHandler-1.0-7.lua:119: in function <...Tom\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:119> [C]: ? ...Tom\libs\CallbackHandler-1.0\CallbackHandler-1.0-7.lua:29: in function <...Tom\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:25> ...Tom\libs\CallbackHandler-1.0\CallbackHandler-1.0-7.lua:64: in function Fire'
SilverDragon\core.lua:364: in function NotifyForMob' SilverDragon\scan\vignettes.lua:138: in function <SilverDragon\scan\vignettes.lua:127> (tail call): ? SilverDragon\scan\vignettes.lua:121: in function ?'
...Tom\libs\CallbackHandler-1.0\CallbackHandler-1.0-7.lua:119: in function <...Tom\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:119>
[C]: ?
...Tom\libs\CallbackHandler-1.0\CallbackHandler-1.0-7.lua:29: in function <...Tom\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:25>
...Tom\libs\CallbackHandler-1.0\CallbackHandler-1.0-7.lua:64: in function Fire' ...aceTomTom\libs\AceEvent-3.0\AceEvent-3.0-4.lua:120: in function <...aceTomTom\libs\AceEvent-3.0\AceEvent-3.0.lua:119>
Could you tell me what happens if you write this in the chat in-game: /dump LibStub("LibSharedMedia-3.0"):Fetch("sound", "War Drums")
If it outputs anything other than "567275", some other addon is replacing my registration of that sound with LibSharedMedia...
[1]="Sound\Event Sounds\Event_wardrum_ogre.ogg"
After lots of checking and unchecking and reloading, I seem to have pinned it down to a conflict with Omen. With Omen off, I get the message you indicate.