Recent Posts

Pages: 1 ... 8 9 [10]
91
PIRA75/P175/P275 Control Software / Re: fm scope run in linux
« Last post by electron on December 16, 2024, 05:51:17 am »
I will answer by myshelf to this problem. First i must say that i'm running linux mint. So if someone wants to find out which com communicates with analyzer must do the tip bellow, taken from wine's site.

Serial and parallel ports are detected automatically when Wine starts. Windows serial ports follow a naming convention of the word COM followed by a number, such as COM1, COM2, etc. Similarly, parallel ports use LPT followed by a number, such as LPT1. Linux, Mac, and BSD each have their own device naming conventions, but in every case the serial or parallel device is located somewhere in /dev. You can see the mapping of Windows devices to Unix devices by looking in ~/.wine/dosdevices. For example:
$ ls -l ~/.wine/dosdevices/
total 0
lrwxrwxrwx 1 alex alex 10 May 13 21:21 c: -> ../drive_c
lrwxrwxrwx 1 alex alex 10 May 14 14:43 com1 -> /dev/ttyS0
lrwxrwxrwx 1 alex alex 10 May 14 14:43 com2 -> /dev/ttyS1
lrwxrwxrwx 1 alex alex 10 May 14 14:43 com3 -> /dev/ttyS2
lrwxrwxrwx 1 alex alex 10 May 14 14:43 com4 -> /dev/ttyS3
lrwxrwxrwx 1 alex alex 12 May 14 14:43 com5 -> /dev/ttyUSB0
lrwxrwxrwx 1 alex alex  8 May 13 21:22 d:: -> /dev/sr0
lrwxrwxrwx 1 alex alex  8 May 14 14:43 lpt1 -> /dev/lp0
lrwxrwxrwx 1 alex alex  1 May 13 21:21 z: -> /
Make sure you have the needed rights to access your computer's serial and parallel ports. On Linux, a user must typically be a member of the sys or dialout group to access serial ports, or the lp group to access parallel ports.

For me it was ttyusb35, so i configure fm scope to com35 and i was able to catch connection.
92
Silence Detector / Re: Can I get Phone Calls, perhaps from a third party service?
« Last post by cewenceslaus on December 16, 2024, 03:50:20 am »
Use Twilio or Zapier for automation: set your silence detector to send an alert email, then use these tools to trigger a phone call. Alternatively, choose professional silence detection tools like Orban or Barix that support phone alerts directly.
bitlife
93
Configuration Options and Possibilities / Re: Configuring P164 through Magic RDS 4
« Last post by Cameron Adkins on December 12, 2024, 09:59:24 pm »
Thanks for the info and education.  Just as a side question, do you have anything that will support HD pad metadata??  I have one station that is HD with an HD2 and HD3.  I have used the old Arctic Palm before for RDS and HD but since they no longer exist and Xperi has decided to do their new app as a subscription, it is out of the budget for smaller stations.

Thanks,
94
Configuration Options and Possibilities / Re: Configuring P164 through Magic RDS 4
« Last post by Jan on December 12, 2024, 09:00:30 pm »
The P164 is characterized by single TCP connection. The solution for your setup is simple - use the Magic RDS as the 'middleware'. The Magic RDS can handle all the tasks: the configuration as well as the data distribution and continuous monitoring. The 'middleware' approach is also recommended by NAB Digital Dashboard Best Practices document, rather than individual feeding of the encoders directly from the broadcast automation.

You may add more connections through the P164's feature called 'software port multiplication'. That way the Magic RDS effectively establishes a single access point for entire network of RDS encoders. See the Help - m4vp.pdf, section 'Data Splitter for RDS Encoders' or 'Redirecting to External Text Sources'.

Also you may install more instances of the Magic RDS, to distinguish between different stations and different modes of usage.
95
Configuration Options and Possibilities / Configuring P164 through Magic RDS 4
« Last post by Cameron Adkins on December 12, 2024, 08:27:27 pm »
Maybe I'm missing something or don't really understand but I have the encoders set as servers with a port number of 3000 which corresponds to the port the Wide Orbit systems are providing the metadata on. All works well except it seem the only way I can communicate with the encoder is on that port for configuration. Port 80 only works connecting to the encoder web GUI itself and you can't really setup a great number of parameters without using the Magic 4 app.  However, whenever I am connected to the encoder, all communication from the automation is interrupted and not updated until I log out of the Magic 4 app. Since I am only using the Magic 4 app for configuration, what is the trick to change configurations on the fly without it disconnecting from the the automation??  This wouldn't be such a big deal except I have other stations setup on the Magic 4 app and when I start it up, it connects to all the encoders and thus interrupts the updates on all of them.
96
Configuration Options and Possibilities / Re: 'line separator'
« Last post by radioroccella on December 08, 2024, 04:03:26 pm »
Thanks. Jan
97
Configuration Options and Possibilities / Re: 'line separator'
« Last post by Jan on December 08, 2024, 12:34:13 pm »
See our F.A.Q.:

Can the RDS encoder control graphic layout and text positioning on modern receivers?
https://pira.cz/rds/show.asp?art=rds_encoder_support#layout

Most receivers show RT+ artist and title on separate lines. There's no global instruction for the layout control.

Sending carriage return character inside the RT text is forbidden - the RDS standard defines it as the RT terminator.
98
Configuration Options and Possibilities / Re: 'line separator'
« Last post by radioroccella on December 08, 2024, 11:12:17 am »
I mean, the RT+ command was already enabled.
Is there a specific instruction to have two separate lines?
99
Configuration Options and Possibilities / Re: 'line separator'
« Last post by radioroccella on December 08, 2024, 10:57:32 am »
I've already done it
100
Configuration Options and Possibilities / Re: 'line separator'
« Last post by Jan on December 08, 2024, 10:55:50 am »
Enable the RT+ in the External Text Source.
Pages: 1 ... 8 9 [10]