![]() I can confirm this still however removed the. ![]() My re-encoding process would remove all meta data with the exception of ".Meta Untouched". The Bitrate type, as in variable, constant or average, made no difference ![]() Unfortunately my results are a little contradictory so I feel this doesn't completely answer the problem. I created several versions of the file to determine what exactly was causing them to not work. This may or may not help.Ĭan someone flag this as it may help Blizzard diagnose the issue with their sounds. Other things to try are using constant bit rate for. Have only tested on client 1.30 and below Will inform if I do encounter an exception. I haven't had any issues with custom sounds since. Meta data removal can be quickly done by encoding files without writing meta data with some programs like LameXP. To fix my problem, I rename my files with simple letters and spaces and remove all meta data. I suspect it might have specifically been the special characters within the meta data? Audio file's meta data (artist name, track number, etc.). I did lots of research into this and I found the problem was caused by the following:ġ. The issues were present before all the new patches but became more prevalent in patch 1.29 I think? (when they introduced the new sound engine). I've had issues with custom sounds and music not playing.
0 Comments
Leave a Reply. |