Recent Posts

Pages: 1 ... 6 7 [8] 9 10
71
Configuration Options and Possibilities / Re: PTY NEWS
« Last post by radioroccella on August 20, 2026, 12:37:54 pm »
 :DHallo Jan, today I inserted these two lines into the "Text Conditions" page and everything seems to work!

send command:"PTY=1"send command:"PAC 0,8E=0"
send command:"PAC 0,8E=1"send command:"PTY=11"
72
Bug Reports / Re: ON AIR
« Last post by Jan on August 18, 2026, 06:06:34 pm »
Thank you for your report, but we are not aware of this issue at this time. I will need more information.

Your text source is returning empty text. This may not be a bug. Perhaps the source text is actually empty, or you are using the Text Replacing tool to change it to empty.

If you are reading a text file, then the first step I would take is to locate the file in a file explorer (e.g. Total Commander or the obscure This PC) and open it. This will give you a pretty clear idea of ​​where the problem is.
73
Bug Reports / ON AIR
« Last post by radioroccella on August 18, 2026, 05:54:06 pm »
 :(As of today, the source that's supposed to read what's being broadcast no longer works.
After a few minutes, if I try to press "TEST," it always says "magicrds."
74
Configuration Options and Possibilities / Re: Skip source if some words is found at a specific xml element
« Last post by nuno on August 18, 2026, 01:11:31 am »
Hi Jan,

Works like expected!
The solution in near future will help a lot!
Thank you for your help :)
75
Configuration Options and Possibilities / Re: Skip source if some words is found at a specific xml element
« Last post by Jan on August 17, 2026, 06:28:46 pm »
Well, if you download current build (2026-08-17), you can do following:

  • Completely remove the workaround proposed in past. Also remove the reference to the link from the Output Template.
       
  • Type following line in the Text replacing:

    Change
    %REGEXP%(?i)www.*programs

    To
    %GOTONEXT%

Explanation:
In current build, the %GOTONEXT% and %CLEAR% commands still work as you are used to. This means that even in the case of an XML/JSON source, these commands will be reflected in the resulting text. Moreover, these command now work also if matching occurs on elements which are not included in the Output Template (so they are hidden to the listener). In near future the Text replacing will include a third 'Filter' column for optinal specification of Output/Source/Element the line will apply to, so that the behaviour can be changed by the user. If you have further questions, just let me know.
76
Configuration Options and Possibilities / Re: Skip source if some words is found at a specific xml element
« Last post by Jan on August 17, 2026, 07:52:06 am »
Yes, now, in the case of XML or JSON sources, each element is processed separately, as this better reflects the logic of working with these text sources. Therefore, text replacement is no longer applied to the resulting text composed of elements according to the template.

The proposed workaround will no longer work. We will find a better solution for your specific needs.
77
Configuration Options and Possibilities / Re: Skip source if some words is found at a specific xml element
« Last post by nuno on August 16, 2026, 11:40:06 pm »
Quote from: Jan on August 16, 2022, 08:45:15 pm
  • Using the Output template, encapsulate the 'link' element into any unique substring.
    For example, if %1% is title and %2% is link:
    %1%<<%2%>>
  • Use the Text Replacing to test if the substring contains the keyword
    Change %REGEXP%<<.*programs.*>> to %GOTONEXT%
  • Remove the substring from final text
    Change %REGEXP%<<.*>> to (nothing)

Alternatively you may apply JavaScript to the same Output template, if further filtering or conditions are required.

Hi!
This is not working anymore on new versions!
How can I do this now?

Thanks
78
RDS Spy / Re: Request for lager font of PI code in RDSSpy
« Last post by SWL Tobias on August 14, 2026, 01:34:01 pm »
I fully agree, the important PI Code is displayed a bit small.

Therefore I have added a bigger separate display here, as attached.

Sorry, adding an attachment was not possible (?)

I also enjoy the signal history view (bottom curve) and a realtime AF list in the captoin of theBasic RDS decoder.

Finally, you may notice the SpectrumLab window, displaying the 'analog' view of the 57 kHz RDS traces. It gives an idea, before decoding is possible, whether there is an RDS signal and about its level above noise.
I wish some such signal indicator (not to replace the useful BER) would also be implemented into RDSspy directly.

Thanks and best regards
SWL Tobias, Bavaria
79
RDS Spy / Re: Request to change non-decoded PS Characters from '-' to '▪'
« Last post by SWL Tobias on August 14, 2026, 12:57:14 pm »
Sorry, posted before making my point...

Thanks for the great freeware RDSspy, a really superb tool for FM DX!

Since '-' is used in regular PS names, I'd suggest to change the non-decoded charcter to something not usually appearing in PS tags, e.g. the small centered 'dot', as entered via Alt+0183 (NumPad) in Windows. This allows clear distinguishing received from non-received characters.

Thank you!

Best regsrds
SWL Tobias, Bavaria
80
RDS Spy / Request to change non-decoded PS Characters from '-' to '▪'
« Last post by SWL Tobias on August 14, 2026, 12:51:08 pm »
Dear RDSspy developer
Pages: 1 ... 6 7 [8] 9 10