Nexgen Output for RT+

[radiosavage]

Good Day.  I am a new user to the software and I seem to be misunderstanding a few areas that I need some assistance.  Currently I can send ASCII from Nexgen and see it all the way to the RDS Encoder but not all of the data even though I see that in the monitor for the input.  I am using a Deva 4.1 right now and I have ordered a 164.  I do plan on keeping the Deva running so I am using General UECP as the output.

Here is where I am running into an issue.  I am not sure of another way to format the output of metadata from Nexgen to Magic RDS.  Right now I export Song Title and Artist on separate lines.  What I notice is that I only get the last line.  I have looked for a guide on what the Nexgen output format should be but I am coming up short.  Anyone else using Nexgen and RT+?  Do I need to send the information on a single line?  Can I use the ability in Nexgen to prepend Item.Artist and Item.Title to be easier for Magic RDS to accept on the input? 

Let me know what other information I can provide.  I am so close.

[admin]

You're reading the Nexgen text data via Virtual port in the Magic RDS, is that true?
The setup is according to Help - m4vp.pdf, section 'Redirecting to External Text Sources'

Such feature uses a 'line separator' so two lines are like two different songs sent immediately one after another. Potential additional time separation may not be reliable so it is not used at all.

The line separator and the separator between artist and title may be any in general, they are fully configurable in the Magic RDS. But they can never be the same (or one as part of the other).

What to do next?
Establish two connections: for the Deva (Generic UECP) and for the P164 (P164)
In the Deva connection, enable the RT+ software encoder (Overview - Extensions)
Fill the RT+ template in the external text source, according to final artist/title separator
Optionally, fill the Text replacing rules if necessary.

[radiosavage]

Yes,  I am using the Virtual port and getting the information.  I noticed that the XML output from Nexgen wasn't working so I went with ASCII. 

The line separator makes sense as does the field separator. So I have adjusted accordingly and it works.  I am new to the software so it took a moment in the "External Text Sources" to realize the template was matching what I am sending.

As for the output.  I have that all setup including the extension for DEVA.  That works great.