Bugs in 1.2.4

Is Virtual Radar Server not behaving itself? If so then please report it here.
agw
Posts: 2241
Joined: Fri Feb 17, 2012 3:20 am

Bugs in 1.2.4

Post by agw » Wed May 08, 2013 1:41 am

If you find them then please let me know :)

Gyzmok
Posts: 7
Joined: Mon Apr 15, 2013 12:14 pm

Re: Bugs in 1.2.4

Post by Gyzmok » Sun May 12, 2013 10:57 am

Thanks for this great application !
no bugs seen sofar.

Jester
Posts: 54
Joined: Tue Apr 09, 2013 6:23 pm

Re: Bugs in 1.2.4

Post by Jester » Tue Jun 04, 2013 5:17 pm

Not really a bug, but could you please post your source code for 1.2.4 ?
I'm building against it with my local changes (see the 1.2.3 display issues) but it seems the source code is still the 1.2.3 one.

Thanks !

agw
Posts: 2241
Joined: Fri Feb 17, 2012 3:20 am

Re: Bugs in 1.2.4

Post by agw » Wed Jun 05, 2013 12:10 am

I've just checked and the source code for 1.2.4 is already up on the site.

Jester
Posts: 54
Joined: Tue Apr 09, 2013 6:23 pm

Re: Bugs in 1.2.4

Post by Jester » Wed Jun 05, 2013 6:48 pm

agw wrote:I've just checked and the source code for 1.2.4 is already up on the site.
weird,

Redownloaded, now its ok, but a cache issue.

Thanks !

Aardvark
Posts: 30
Joined: Mon Jun 17, 2013 11:16 pm

Re: Bugs in 1.2.4

Post by Aardvark » Tue Jun 18, 2013 2:30 pm

I just installed this software for the first time in conjunction with ADBSharp and have been having a ball with this software. Especially after I got the Kinetics SBS databases loaded. However, I have noticed a rather strange bug in the speech feature. I have only tested it with Firefox on Mountain Lion and Windows. Basically a "2" is getting inserted into various strings. For example:

Callsign N148CZ is spoken as N1248CZ

Callsign DHK971 is spoken as DHK9271

Registration 4067A2 is spoken as 42067A2

Callsign UPS219 is spoken as UPS2219

Model A320 is spoken A3220

I imagine there is a probably a formatting character stuck somewhere in the code that placing this extra numeric two in the string. The displayed text is fine. I am a programmer by trade (and an amateur radio operator too) but I have not had a chance to download the code and search this out myself. I figured I would drop it here and see if maybe this is already a known issue. A cursory search of the forums did not turn anything up.

EDIT: Checked Safari too and the problem is there so it is not Firefox specific.

agw
Posts: 2241
Joined: Fri Feb 17, 2012 3:20 am

Re: Bugs in 1.2.4

Post by agw » Wed Jun 19, 2013 12:50 am

Ha, excellent! I hope that is a bug, I'd be quite proud of that if I managed to stick random "2"s into the text :) Well, almost random - in your selection it was always the 2nd digit in a run of digits where the 2 gets added. Unfortunately I've not been able to reproduce it so far.

You can send your own text strings to VRS to get read back to you - if the address of the server is http://127.0.0.1/VirtualRadar then the address to play back "123456", with each digit pronounced separately, is http://127.0.0.1/VirtualRadar/audio?cmd ... -2-3-4-5-6. It would be interesting to know whether the extra two is spoken back to you when you send a request like that.

Alternatively if you open up Firefox's web console (Ctrl+Shift+K on windows), then switch on the Net logging and switch off CSS, JS and Logging then it'll show you the messages going to the server. If you wait for the audio to be played with an extraneous "2" then you should be able to see the corresponding audio request to the server. If the extra "2" is showing in the request that went to the server then it's the javascript, otherwise it's the server. I don't think the server does all that much with the text, from what I remember it just hands it over to .NET's speech synthesis to generate the audio and all that does is hand it over to Windows - but the javascript does do a bit of mangling of the text so that's a good candidate for it. I would have thought it would be happening all the time though.

Aardvark
Posts: 30
Joined: Mon Jun 17, 2013 11:16 pm

Re: Bugs in 1.2.4

Post by Aardvark » Wed Jun 19, 2013 2:29 am

I did the test using the local URL above to try 123456 and it spoke fine. I then went into the diagnostic console and captured a URL that misspoke. That URL is:

http://168.100.196.84/VirtualRadar/Audi ... C%20Turkey.

Note that the string does in fact say "type B - 7 - 7 - 3" but when it speaks, it says "type B7273". I even shortened it to:

http://168.100.196.84/VirtualRadar/Audi ... 0-%203%20-

and

http://168.100.196.84/VirtualRadar/Audi ... 0-%207%203

and it still misspeaks. Remove the hyphen and it is fine. I think I know what it is saying. It isn't saying "B 7 2 7 3" but "B 7 to 7 3" as in the range "7 - 73". Just a theory. If it is the hyphen, an alternative to create a pause would be to use commas. I have done some speech synthesis work in the past with a Winamp plugin I developed and that was how I got it to pause when speaking as well as break up numbers. I did test with commas and it is slower so that may not be an option. Simply leaving the hyphens out and using spaces seems to work fine for me. I actually had a call come in this morning, N1454H, that had two "to's": November one to four five to four H.

I should note the system running VirtualRadar is on Windows 8. I am not sure if this may be an issue with the speech engine on that platform alone.

agw
Posts: 2241
Joined: Fri Feb 17, 2012 3:20 am

Re: Bugs in 1.2.4

Post by agw » Wed Jun 19, 2013 2:13 pm

.NET just hands the whole speech synthesis thing over to Windows so I guess it probably is a change to how Windows is dealing with hyphens in the text in W8. I'm currently rewriting the website side of things, I'll get rid of the hyphens in the next big release.

Aardvark
Posts: 30
Joined: Mon Jun 17, 2013 11:16 pm

Re: Bugs in 1.2.4

Post by Aardvark » Wed Jun 19, 2013 2:41 pm

It figures they would change something. When I was working with the speech synthesis API a few years ago I wrote it to support both the Windows engine and the AT&T Real Voices engine (which I definitely prefer for its more natural sounding voices). AT&T had a few quirks for how it pronounced things that I needed to add exceptions for (For example: Windows would pronounce the year 1998 as nineteen ninety eight but Real Voices would say nineteen hundred ninety eight - had to split the year into 19 and 98). One thing I really like about Real Voices is its support for customized pronunciation through a customized dictionary file. I had created an automated DJ that announced the titles of songs as they would start to play in Winamp. I wound up adding about two dozen corrections for various words it just could not handle in song titles and artist names.

Overall, I am very impressed with this software. It must be nightmare to maintain!

Locked