Post reply

Name:
Email:
Subject:
Message icon:
Verification:
Unregistered users must pass a verification:



Please enter the number from the picture above which is showing FM broadcast antenna:

shortcuts: hit alt+s to submit/post or alt+p to preview


Topic Summary

Posted by: Simon (Ben)
« on: January 22, 2023, 02:17:29 pm »

Gday Jan!

thank you so much for that, and thank you (again) for providing to the community at large such an amazing piece of software - legend, thank you

ben
4zzz
Posted by: Jan
« on: January 17, 2023, 10:29:21 pm »

It should be fixed in current version 1.08 r4  :)
Posted by: Simon (ben)
« on: January 16, 2023, 01:13:06 pm »

Thank you so much Jan!

Simon (Ben)
Posted by: Jan
« on: January 16, 2023, 10:09:54 am »

Thanks for this report. This relates to the 'Basic RDS Decoder' plugin. I'll definitely look into it.
Posted by: Simon
« on: January 15, 2023, 01:54:47 pm »

Quote from: Simon on January 15, 2023, 01:45:16 pm
Gday Mate!

Hope you are well: Firstly thank you for RDS Spy (available for free) - Legend

Just wanted to pop in a minor bug that was seen;

When a Station is Outputting a mix of Group 0A and 0B Messages (ie Block 3 as either AF or PI) RDS Spy will decode the Group 0B message as an alternative frequency message where as the PI Number is there, This give an incorrect output into the Basic RDS Decoder Screen / AF and show the PI as two frequencies

as example using a Group Sequence of 0A, 2A, 0B, 2A and a PI of 4032 (as example - if they should or not is another thing, its the decoding i'm focused on) 
with no Alt Freq we would see populated into the Alt Freq List '93.9 MHz, 92.5 Mhz' which is {Hex (40) -> Freq (93.9)}, {Hex (32) -> Freq (92.5)}
with an Alt Freq set (to anything, lets say 106.3) RDS Spy will show '#1, 106.3 MHz' <NextLine> '93.9 MHz, 92.5 Mhz'

looking into the output stream in hex the group markers are correct (Block B: Number (0-15) and Version (A vs B) its just that the Version B's PI is Ending up in the Version A Data List

Version A - [block1:PI] [Block2:Type/Pty] [Block3:AF] [Block4:PS]
Version B - [block1:PI] [Block2:Type/Pty] [Block3:PI] [Block4:PS]

Hope this all makes sense, easiest way to replicate it is send a steam of 0A / 0B Groups and hopefully it will show itself quickly!

Cheers
Simon the Seagull

I should Note the {Hex (40) -> Freq (93.9)}, {Hex (32) -> Freq (92.5)} are correct for the conversion, that is correct!
- the issue we've found is its decoding a Group 0B message using 0A Format while there is a mixture of 0A/0B groups in the stream

Thank you again!
Posted by: Simon
« on: January 15, 2023, 01:52:41 pm »

Quote from: Simon on January 15, 2023, 01:45:16 pm
Gday Mate!

Hope you are well: Firstly thank you for RDS Spy (available for free) - Legend

Just wanted to pop in a minor bug that was seen;

When a Station is Outputting a mix of Group 0A and 0B Messages (ie Block 3 as either AF or PI) RDS Spy will decode the Group 0B message as an alternative frequency message where as the PI Number is there, This give an incorrect output into the Basic RDS Decoder Screen / AF and show the PI as two frequencies

as example using a Group Sequence of 0A, 2A, 0B, 2A and a PI of 4032 (as example - if they should or not is another thing, its the decoding i'm focused on) 
with no Alt Freq we would see populated into the Alt Freq List '93.9 MHz, 92.5 Mhz' which is {Hex (40) -> Freq (93.9)}, {Hex (32) -> Freq (92.5)}
with an Alt Freq set (to anything, lets say 106.3) RDS Spy will show '#1, 106.3 MHz' <NextLine> '93.9 MHz, 92.5 Mhz'

looking into the output stream in hex the group markers are correct (Block B: Number (0-15) and Version (A vs B) its just that the Version B's PI is Ending up in the Version A Data List

Version A - [block1:PI] [Block2:Type/Pty] [Block3:AF] [Block4:PS]
Version B - [block1:PI] [Block2:Type/Pty] [Block3:PI] [Block4:PS]

Hope this all makes sense, easiest way to replicate it is send a steam of 0A / 0B Groups and hopefully it will show itself quickly!

Cheers
Simon the Seagull

I should Note the {Hex (40) -> Freq (93.9)}, {Hex (32) -> Freq (92.5)} are correct for the conversion, that is correct!
- the issue we've found is its decoding a Group 0B message using 0A Format

Thank you again!
Posted by: Simon
« on: January 15, 2023, 01:45:16 pm »

Gday Mate!

Hope you are well: Firstly thank you for RDS Spy (available for free) - Legend

Just wanted to pop in a minor bug that was seen;

When a Station is Outputting a mix of Group 0A and 0B Messages (ie Block 3 as either AF or PI) RDS Spy will decode the Group 0B message as an alternative frequency message where as the PI Number is there, This give an incorrect output into the Basic RDS Decoder Screen / AF and show the PI as two frequencies

as example using a Group Sequence of 0A, 2A, 0B, 2A and a PI of 4032 (as example - if they should or not is another thing, its the decoding i'm focused on) 
with no Alt Freq we would see populated into the Alt Freq List '93.9 MHz, 92.5 Mhz' which is {Hex (40) -> Freq (93.9)}, {Hex (32) -> Freq (92.5)}
with an Alt Freq set (to anything, lets say 106.3) RDS Spy will show '#1, 106.3 MHz' <NextLine> '93.9 MHz, 92.5 Mhz'

looking into the output stream in hex the group markers are correct (Block B: Number (0-15) and Version (A vs B) its just that the Version B's PI is Ending up in the Version A Data List

Version A - [block1:PI] [Block2:Type/Pty] [Block3:AF] [Block4:PS]
Version B - [block1:PI] [Block2:Type/Pty] [Block3:PI] [Block4:PS]

Hope this all makes sense, easiest way to replicate it is send a steam of 0A / 0B Groups and hopefully it will show itself quickly!

Cheers
sts