Recent Posts

Pages: 1 [2] 3 4 ... 10
11
Control Software / Magic RDS - Text replacing - Title Case
« Last post by 3mFM Tech on December 27, 2019, 06:28:03 am »
Hi, Using the latest MagicRDS V3.8e

Have a NowPlaying.xml file that has song Title, Artist, Category & Temperature. Title is all CAPITAL letters from our playback automation system.
Also have a MessageList.txt file used for a selection of station messages which appear 60s after a new song has started.
Using 'Text Replace' to replace various special station categories with fixed text such as 'Sponsor Message', using [CAT***] as suggested in a very useful Sept 2019 post.

Wish to convert the all capitals song title to Title Case (Only first letter in each word is a capital) to make long text messages fit on radio displays that use proportional text fonts. 
Yes, we could use 'External Text Sources' > More Options > Convert to Title Case, however this rule is applied to ALL text messages, independent of source; not just the song title.
Generally need words to remain as intended without forcing 'Title Case' in all instances. Otherwise text such as '3mfm.com.au', becomes '3Mfm.Com.Au'

I'm hoping to arrange a REGEXP or similar in 'External Text Sources' > 'Text Replacing' tab to find words with ALL CAPITALS & then replace that text with the 'Title Case' equivalent in this case.
The 'Text Sources' NowPlaying.xml has the Title element defined as value %2%.
Using 'Text Replacing' ordering to manage priority, we can put any Title Case manipulation after all of the other category displays cases are managed.

Thanks for any suggestions.
12
P275 FM Analyzer / Re: Measuring deviation
« Last post by beej6 on December 16, 2019, 09:30:56 pm »
Thank you Jan! As you can tell I am an amateur still at this... trying to keep learning :-)
13
P275 FM Analyzer / Re: Measuring deviation
« Last post by Jan on December 13, 2019, 09:27:58 pm »
Quote
If I get five bars on the reception, should I simply assume that my measurements are , say, 95% accurate?

No, but you may assume that there's a high probability that the results are correct.

Quote
I see where four bars reduces the accuracy, by about what percentage of tolerance?

I think it's better to say that 4 bars indicate increased probability that the results may not be correct. That sentence tells it all.

Due to highly non-linear dependencies there's no formula for calculating measurement tolerance from the signal quality rating (which is a mix of noise voltage and AM). For example the noise voltage may be affected by more than 5 influences, while each influence has a different impact on the measurements. There's no way how to detect all influences separately and plausibly. We're talking about FM which is a non-linear modulation. The noise voltage is also affected by the peak deviation but peak deviation is affected by the noise voltage. That task has no solution if the reception quality is insufficient (but in the P275, some correction algorithms expect fixed 75 kHz peak deviation so it can be said that this value is measured with best accuracy).

For reference measurements you should simply meet the general rules and official recommendations (60 dBuV, directional antenna, no interference sources) otherwise it is preferable to verify the measurement from another location, depending on the purpose.

Quote
I was measuring a station 50km away, just a 1kw station but 4-bay antenna and almost 500m AMSL. Five bars it was!

It is entirely ok, the distance is not a problem if you use directional antenna to suppress multipath and if there's no extra strong signal in your neighborhood.
14
P275 FM Analyzer / Measuring deviation
« Last post by beej6 on December 13, 2019, 06:43:34 pm »
Hi, I've had the stock P275 (and the P175 before that) for a little bit now. Notwithstanding the charts to estimate effective range of the measurements:

If I get five bars on the reception, should I simply assume that my measurements are , say, 95% accurate?

I see where four bars reduces the accuracy, by about what percentage of tolerance?

I was measuring a station 50km away, just a 1kw station but 4-bay antenna and almost 500m AMSL. Five bars it was!
15
Silence Detector / Re: Companion Software
« Last post by AndyMac on December 09, 2019, 07:12:50 pm »
This is what I want for sure.
Absolutely interested!
16
P175 FM Analyzer / Re: Pira 175 freqentie
« Last post by dasselaar68 on December 07, 2019, 11:36:46 pm »
THANKS IT,S WORKS  :) :)
17
P175 FM Analyzer / Re: Pira 175 freqentie
« Last post by Jan on December 06, 2019, 05:48:18 pm »
Using a PC and FM Scope, you may tune to a frequency outside the standard boundaries. Type in the text window:

Code: [Select]
send(085000*F)
Then you may save this frequency as a preset for later use with no more need of a PC: menu - Save Data.

The operation is however not guaranteed in that area, exact frequency limit depends on individual oscillator characteristics. A range of 84 to 110 MHz should work in almost all cases.
18
Control Software / Re: MagicRDS XML parsing with Axel DJPro
« Last post by AudioW on December 06, 2019, 03:50:22 pm »
Thank you Jan for your fast reply.
Indeed was a matter of full path notation that was incorrect

BR

19
Control Software / Re: MagicRDS XML parsing with Axel DJPro
« Last post by Jan on December 06, 2019, 02:54:38 pm »
Thank you for using this forum.

Here are correct paths to the elements:

/radio/attuale/brano/name
/radio/attuale/artista/name
20
Control Software / MagicRDS XML parsing with Axel DJPro
« Last post by AudioW on December 06, 2019, 01:43:57 pm »
Hi there.
Using version 3.8e of Magic RDS we found a valuable feature for parsing information directly from a XML file in Radiotext.
Unfortunately it seems that there is something wrong with our setup / configuration since we are unable to get any information from the file.

The attached image shows our XML file plus the configuration used in MagicRDS
We tried in 2 ways to get the data:
By element name and full path.
Both do not work.

Anyone has an idea about what's wrong?

BR
Pages: 1 [2] 3 4 ... 10