OnCourse Software

One more vote here for a little update on airline names in the future. There is still a typo mistake which is inherited from PFE. In the airlines dropdown list there is "AT Yugoslav Airlines" instead of "JAT Yugoslav Airlines". The ATC pronunciation is good.

How then do you add the new callsigns, created by cutting and joining existing wav files, to the PF3 database? I open captions.ini to locate the wav files needed and use a wav editor to join them (with a good wav editor you can even copy and paste individual syllables to make new words) to make a new wav file. But I can't find any instruction on how to add the new callsign to the pf3_callsigns.dat file. That file has all the callsigns and then two numbers separated by commas...

For instance, South American airlines TAM and LAN Airlines are now amalgamated to LATAM. But of course 'LATAM' doesn't exist in PF3. Having to create so many versions, for all the voice combinations, may well prove a big disincentive, but if I did have a go, on a day I have nothing better to do!, after adding LATAM to the pf3_callsigns.dat file, how do I work out what numbers I would use - and what, if anything, would I add to the captions.ini file - for PF3 to recognise and use the newly created wave file? What do the two numbers refer to?

Thanks.

BTW....

Quote:

In the airlines dropdown list there is "AT Yugoslav Airlines" instead of "JAT Yugoslav Airlines".

You can change the mistake yourself by opening pf3_callsigns.dat with a text editor, like notepad, adding the initial 'J' and saving the file. (I keep a backup of the original file, just in case).

.. and where exactly in PF3/wav would I place my created files?

(I already made a dozen or so - it's actually pretty fast, I could do all 238 in an afternoon, but it needs to be a callsign that you'd use often enough to make the effort worthwhile! I can upload all my LANTAM files if I get them installed and working, assuming no copyright issues Dave???...)

(Can't edit the posts, so have to keep adding new replies...).
Ok, I understand the first number in the callsigns dat file (refers to the callsign no. in the captions.ini file of course) and can probably work out all the rest, folders etc. with no problem: but I still can't work out what the second number refers to in the callsign dat file. Probably I am being a bit dense, but a heads up would be good....

The second number is the region.

I think this has been already written somewhere, but here's a summary:

captions.ini: Pfac105=Air Berlin (this maps Pfac wav file number to displayed captions)
Data/pf3_callsigns.dat: Air Berlin,105,10 (this populates the dropdown for VCP voice)
Data/Callsigns_Map.dat: Air Berlin,105,10 (this maps AI airline names to Pfac wav file number and region)

Regions are:

Code: Select all Folder A - African - Voices: 6 Folder B - Arabian - Voices: 2 Folder C - Asian - Voices: 7 Folder D - Australian - Voices: 5 Folder E - British - Voices: 25 Folder F - Canadian - Voices: 3 Folder G - Caribbean - Voices: 1 Folder H - Dutch - Voices: 4 Folder I - French - Voices: 2 Folder J - French Canadian - Voices: 0 Folder K - German - Voices: 5 Folder L - Greek - Voices: 1 Folder M - Hindi - Voices: 7 Folder N - Hungarian - Voices: 1 Folder O - Indonesian - Voices: 0 Folder P - Irish - Voices: 2 Folder Q - Italian - Voices: 3 Folder R - Latin American - Voices: 2 Folder S - Nordic - Voices: 0 Folder T - Portuguese - Voices: 0 Folder U - Russian - Voices: 0 Folder V - Spanish - Voices: 1 Folder W - US Generic - Voices: 26 Folder X - US MidWestern - Voices: 4 Folder Y - US Northern - Voices: 7 Folder Z - US Southern - Voices: 5

If you read A as 0, B as 1, ..., K as 10, you get the region numbers above, so 10 is German.

Quote:

The second number is the region.

Thanks Thomas.. I'll give one a try at some stage soon and post how I get on. It's a lot of work making/editing all those new wav files (I think 238?), so it may take a while!

(I wanted to start with 'LATAM Columbia', but the word 'Colombia' doesn't exist in PF3 voice folders (apart from ATIS, which is no good for making callsigns), so unless I can be bothered to copy and paste 'Col', 'Um' and 'Bia' from existing files into one new one - and do it 238 times! (highly unlikely!!) - my current project won't happen! Still, I can use this to create and install other missing callsigns, I am sure).

Martin

I've wasted several hours this week trying this out, cutting and pasting wav files into new ones: I should have remembered an earlier post in which I discussed this with Dave M, when it became clear that editing and saving any of the wav files in PF3 or PFE renders them unusable - I just get a screeching noise instead of the call sign in FS9 (though they sound fine in any wav player). Seems that isn't fixable, unless Dave has come up with a way around it since that thread (several months ago I think).

The best you can do is find a close approximation to the missing callsign and use that, by adding it to the callsigns .dat file. So, I now have, for example "Aero Asia" instead of "Air Asia" for AirAsia (new entry) - better than nothing I guess! (Yes, I back up the original files BTW )

martinlest wrote: *

Sat Mar 11, 2017 9:41 pm

I've wasted several hours this week trying this out, cutting and pasting wav files into new ones: I should have remembered an earlier post in which I discussed this with Dave M, when it became clear that editing and saving any of the wav files in PF3 or PFE renders them unusable - I just get a screeching noise instead of the call sign in FS9 (though they sound fine in any wav player). Seems that isn't fixable, unless Dave has come up with a way around it since that thread (several months ago I think).

The best you can do is find a close approximation to the missing callsign and use that, by adding it to the callsigns .dat file. So, I now have, for example "Aero Asia" instead of "Air Asia" for AirAsia (new entry) - better than nothing I guess! (Yes, I back up the original files BTW )

Strange, I have edited a bunch of files and did not have such problems. Just make sure to save them in the same format (8bit mono 11025 Hz).
But yes, using something similar as a proxy might be the easiest way.