Hi Gogs...
I can remmber having some problems with sound too, although in my case is was only
some sounds, not all of them. Here are some things that you may like to look at:
First of all, here is a snapshot of some extacts from the begining and end of the main sound section of the descripton.ext file for a (rather over ambitious) mission that I will have to finish sometime, when I get the chance. I have taken a snaphot of it and uploaded it to my site, as I got fed up with it not displaying properly when trying to use the "code" tags, and inserting the image in my post does not work either (unfortunatly, the forum seems to agressively limit dimentions of any larger images posted so that they are distorted and unreadable.
Please right-click this URL and open it in a new tab or window...
http://www.richuk.net/ofpecpics/mysound01.jpgHere are some small extracts, without the indent, as code:
class say_shhh
{
name = "shhh";
sound[] = {"\sound\shhh.ogg", db+0,1};
titles[] = { };
};
class ggv01
{
name = "ggv01";
sound[] = { "\sound\ggv01.ogg",db+0,1 };
forceTitles = true;
titles[] = { 0,$STRggv01 };
};
//
//
//
class s10toofar
{
name = "s10toofar";
sound[] = {"\userscud\SCUDsound\s10toofar.ogg",db+20,1.0};
titles[] = {};
};
Here are some points, that I would like to make:
1. I Use a "declaration" section at the top (which you can see in the snapshot), which has a LOT of items in it, in the form:
sounds[] = {sound1,sound2,sound3};
I understand that that is not stictly necessary anymore, but I started doing it for a much earlier version of OFP (v1.46 or older), where this was necessary, so I carried on with it. You just have white space between the backets, which should be OK.
2. You will see that I sometimes have string defined in the titles section (when I want to display text in my stringtable.csv) where other times I do not, or do not include titles[] at all! One thing is that when I am using a title, my statement is like this:
titles[] = { 0,$STRggv01 };
..whereas you are not using the curly backets, or the "0," prefix. I wonder if that could be a problem (?), although quite probably not, if there was anything going wrong here, I expect the title stuff would not display. That brings a question to mind, when you try to play the sound, do you see a title that you have defined in your stringtable.csv displayed or not when you get the "Radio file filename not found" dialog box.
3. Even though when sounds are in a "sound" sub-directory, you should not need to specify it under the sound[] section, but I used to have problems at one time, so I always now include the sub-path. You could try doing this, just in case, although that may be unlikely to be your problem. Of course, you may have named your directory "sounds" instead of "sound" which could well stop thing working, without the path included. You will see that I have used sub-sub-directories too, and everything works fine. [edit] but see my edit at the bottom [/edit]
4. Although it is not clear from the extracts I have shown, I found about 10 of my .ogg souns refused to play at all under OFP, even though they were sampled at the same rate and number of bits as others that did work. I just converted them to .wss files and now they play fine!
5. I previously found that there seemed to be a problem if a sound file was too small. I cannot remember the figure, but when it was only a few KB, then OFP seemed to have problems with it as an .ogg, so that could be why the .wss ones worked, but I am not sure that that is true, or I probably would have remembered that.
6. I can remember that I experience problems with sound files with a name of less than 3 or 4 characters (I think for the class name, rather than the name before the file extension, although it could have been for the name ="xxxx") section. In spite of karantan using your file without problems, it may still be a problem on your machine due to a different versiion of OFP, or some configuration problem.
7. Sampling rates, etc. when producing the .ogg files can be a problem, but you have already stated that you have been using 16-bit Mono at 16 KHz, which should be fine.
8. You are using db+40 with all of your sounds, which is a very high figure. Perhaps OFP does not like that? Could it be out of range, causing no sound at all? ... I would try db+20, you never know it may work.
9. How about trying a sound that you
know works OK from another mission? I would put it in twice, once under its original name (with the corresponding description.ext entry) and once renamed to one of the sound file names you are using (to replace your normal file). If it works in both cases, you know that it is your normal sound file that hs the problem. Conversely, you could put your renamed normal sound file into the other mission to try it... you ge the idea...
Of all of the above, number 3 looks the most likely problem, as with the path not overtly stated, any other name but "sound" as a sub-directory with your sounds in (if not in the root of your mission folder) would not work and be likely to give the "Radio file filename not found" error you are seeing (although I have not tested that)... it could be just an unwanted "s" after sound!
[edit]
I missed that you had already stated that your sound folder was called "sound", not "sounds" or something, bu you could still try putting the path in, like I do, just in case. What version of OFP are you running? v1.96?
[/edit]
Hope some of this helps others, if not yourself...
Rich.
Topic: Radio sounds not found.... (Read 1333 times)
