Recent Posts

Pages: 1 ... 3 4 [5] 6 7 ... 10
41
P132, P164, P232(U) and P332 RDS Encoders / Re: LIC code to P164
« Last post by Jan on April 25, 2025, 06:37:17 pm »
According to latest RDS standard release, the LIC service becomes deprecated. Regardless of that fact, we will keep it in the P164 also in future firmware versions.
If the LIC feature is not applicable or not required, set the value to 00.
42
P132, P164, P232(U) and P332 RDS Encoders / Re: 164 issue (Locks up)
« Last post by bluemax on April 25, 2025, 06:33:54 pm »
Thanks, I'll do that when on site next.

:)
43
P132, P164, P232(U) and P332 RDS Encoders / Re: 164 issue (Locks up)
« Last post by Jan on April 25, 2025, 06:19:51 pm »
According to information provided by the Ethernet chip W7500 manufacturer, current firmware version is 2.9:
https://docs.wiznet.io/img/products/w5500s2e-z1/w7500s2e-app-r1-v2.9.zip
You may use the ConfigTool for the firmware upload.

Anyway, regardless of what event occured in the network, the P164 never locks-up. This is guaranteed by design. Unlike consumer network products like routers etc., the P164 incorporates hardware watchdog and dedicated Ethernet fail-safe monitor. To be able to use this great tool, it must be enabled first. Please follow the setup procedure as described in the manual, section 6.4.2. (The same topic has been discussed about a year ago: https://pira.cz/forum/index.php?topic=970.0 )
We now added the indication also to the remote management website, which is accessible from the Magic RDS 4 central webserver (see below).

Finally, set up correct Default Radiotext, incl. the timeout: In Magic RDS 4 - RDS Content - Radiotext 1.
44
P132, P164, P232(U) and P332 RDS Encoders / 164 issue (Locks up)
« Last post by bluemax on April 25, 2025, 05:42:29 pm »
Hi,
I have a number of 164 units on our network, 10m stable connection - not 5G.

Two of which have locked up, both will ping but no web access. (Not sure if Magic will connect when they lock up)  Power cycle sorts the issue, but it happens every few weeks.
The result on air is the RT is blank on one, and the other it got stuck on one particular song. Other RDS data was ok and unaffected.

They are running v2.8 but looking online the latest I could see is v2.2

Thanks in advance! :)
45
Bug Reports / MagicRDS4, wrongly set TATMOUT parameter
« Last post by metro187 on April 25, 2025, 04:42:11 pm »
When setting up the "TA Timeout and External Control", if you choose "Level controlled", the set timeout value should be shifted by 128.
So for a "2 minute timeout, Level controlled" mode, a TATMOUT=130 should be sent and instead a TATMOUT=3 is sent.

If you read back the above saved setting from the encoder it becomes "3 minutes, Falling edge controlled"

Reproduced in the latest available 4.2.4 version.
46
P132, P164, P232(U) and P332 RDS Encoders / Re: Enabling RDS+ and station logo p232u
« Last post by Jan on April 22, 2025, 07:57:20 am »
What about trying the User manual? p232uman.pdf section 5.6

Current receivers (in 2025) still don't support RDS2. Even if you set up the logo correctly, it will not display on the receiver.
47
P132, P164, P232(U) and P332 RDS Encoders / Enabling RDS+ and station logo p232u
« Last post by drivenmedia on April 22, 2025, 07:13:04 am »
I have searched with no luck. I'm trying to get our station logo sent out and can't get it to work. I found in some directions that the RT+ must be enabled and the RDS2 mode of operation must be set to buffer but I can't find that setting. Any help would be greatly appreciated. Thanks!
48
Configuration Options and Possibilities / Re: Send metadata to TuneIn via http get URL
« Last post by Jan on April 21, 2025, 12:21:33 pm »
The sendhttp currently supports only %data% as the argument. That is a plain text single line, not separated to artist, title or anything else. In you example, MySong and MyArtist is sent as is, without substitution. A solution is on the way.

Resulting GET request can be seen in View - Debug - SendHTTP Log.

Virtual port provides data input only, it is not applicable for sending data.

49
Configuration Options and Possibilities / Send metadata to TuneIn via http get URL
« Last post by South Coast FM Tech on April 21, 2025, 11:39:46 am »
Hi Jan,

I already have Now Playing data successfully feed an RDS encoder & also internet streaming.

Now I'm trying to send metadata to TuneIn via an http get URL in the following form:

http://air.radiotime.com/Playing.ashx?partnerId=abcedfeg&partnerKey=abcdefg&id=s123456&title=MySong&artist=MyArtist&album=

Text Output Setup: 'TuneInMetadata'
Text source sequence: 'NowPlayingForStreaming'
Output purpose: Radiotext or plain text.
Destination connection: sendto "TuneInMetadataConnection"

Connection: 'TuneInMetadataConnection' . Bridge > Internal Channel.
Data distribution settings:
sendhttp url:"http://air.radiotime.com/Playing.ashx?partnerId=abcedfeg&partnerKey=abcdefg&id=s123456&title=MySong&artist=MyArtist&album="

Is a Virtual Port required?

Virtual Ports: TuneInMetadataConnection VP 1
Connection type: HTTP Server
I'm not sure what to do in this section?

Even with a TuneIn URL with fixed arguments, TuneIn doesn't seem to receive the request.

'TuneInMetadataConnection' Communication Monitor (Image 2) shows transmission of now playing Artist - Title, but not a URL string.

Using MagicRDS4 V4.2.4

thanks, Rod

50
Bug Reports / Re: Missing Numbers in Song Title
« Last post by Jan on April 17, 2025, 10:47:09 pm »
The function was originally written for situations when the player provides song file name instead of ID3 information. Various song numbering is used for the files, incl. 12. (34) 56, 78- etc. Unfortunately, some artist names violate with the numbering.
Today, the function has probably no significant reason for being used. It can be replaced by regex when necessary.
Pages: 1 ... 3 4 [5] 6 7 ... 10