Recent Posts

Pages: [1] 2 3 ... 10
1
P175 FM Analyzer / Re: Pira 175 freqentie
« Last post by dasselaar68 on December 07, 2019, 11:36:46 pm »
THANKS IT,S WORKS  :) :)
2
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.
3
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

4
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
5
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
6
P175 FM Analyzer / Pira 175 freqentie
« Last post by dasselaar68 on December 06, 2019, 11:49:34 am »
Is it possible that the pira 175 with a firmware lower can that 87.50mhz so like to 85.00mkz to 108mhz
the pira 275 can that also     come the pira with an update for,s the 175 or is are not release any anymore ???
7
Control Software / Re: MagicRDS command line options
« Last post by Jan on November 14, 2019, 03:33:25 pm »
OK, so back to your first question. You can change the Message text from command line thru a RDS file. Create a file msg.rds:

Code: [Select]
[Messages]
MSG1=New text here

Pass the file name as a parameter to the magicrds:

magicrds.exe msg.rds
8
Control Software / Re: MagicRDS command line options
« Last post by Radiosotra_Tech on November 09, 2019, 12:49:13 pm »
Dear Jan.

Thank you for the suggestion. I dont't think this will be useful for us as we have some users (the more experienced ones) that are using the MagicRDS software and Message list to choose which messages are beeing used (and changes this often during a show) - They are using the RDS functions to maximum. The more unexperienced users are only going to set their show name and that's that (in addition to the "static" station information).

I think I will go for another approach to the "problem".
I know that magicrds will take all the RDS commands directly by using "send:" in the command line (Just that the MagicRDS software is not updating its GUI with this information), and I can update eg MSG50 (in the encoder) by using the command: "magicrds.exe send:MSG50=Some text; send:MSG50D=2" to set and enable the message and then "magicrds.exe send:MSG50D=0" when the message is not going to be used. (This will make the rds encoder able to get the information - but just not show it in the MagicRDS software).
I will just have to convince my experienced users to use only the touchpanel (instead of the software) and then give them some extra options there instead.

Thank you very much for your time and effort to look into my "problem".
9
Control Software / Re: MagicRDS command line options
« Last post by Jan on November 09, 2019, 12:13:31 pm »
I would recommend to control everything completely from the External Text tool. As I suppose you're already using this tool for the song information, you may define second text source which will read a file of predefined static text messages. That file may be updated from your Raspberry Pi. Entire process is very easy.

In short:

Disable RT2
Save the text messages to a plain text file using the MQTT, one text message per each line
Configure the text source as described here https://pira.cz/rds/show.asp?art=guide_text_5
On the External Text / Radiotext card, check both the song info source and static text source.
10
Control Software / Re: MagicRDS command line options
« Last post by Radiosotra_Tech on November 09, 2019, 11:34:44 am »
Dear Jan.

Thank you for the information. We used to do the RT1 part earlier (just by using RT2 instead since we are using RT1 for song information), but some of the shows wants more information given than just one message.

Just to clarify what we are looking for if you have any other ideas on how we could do this.

They are looking for something like (by a 0,5min switching interval from RT1 to RT2):
Radiotext1 - Song information
Radiotext2 - Message #1 (Normally information about the radio station - name, contact ++)
Radiotext1 - Song information
Radiotext2 - Message #2 (Normally information about the show - name ++)
Radiotext1 - Song information
Radiotext2 - Message #3 (Some information to the listeners)
+++
And then all over again (depending on how many Messages they want - but normally this is 2-5).


We are updating the Message1 to 99 today by making and running a .rds file using the following method:
1. Type all the texts on the raspberry pi that they wants in the rotation
2. The raspberry pi sends the information to the MagicRDS computer by using MQTT protocol.
3. The MagicRDS computer stores the information from the Raspberry PI to a file
4. The Raspberry PI runs a command on the MagicRDS machine : magicrds.exe messagefile.rds

We would like to simplify this operation if its possible by sending the information directly to MagicRDS instead of having to store it to a file, and then have MagicRDS read the file (As this will give us more control of what is given to the software as it fails sometimes if the file is not stored/closed before we run the update command. We have a small "wait" command of 0,5 sec before the command runs as this takes care of 95% of the faults - but would like to have the rate to 100% as some of the users are not technical and does not understand what to do if it fails - even if this is just pressign the same button on the touchpanel again).

Thanks in advance
Pages: [1] 2 3 ... 10