Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rtpsend: "Line ???? is invalid" #134

Open
Tratosca opened this issue Jun 21, 2020 · 2 comments
Open

rtpsend: "Line ???? is invalid" #134

Tratosca opened this issue Jun 21, 2020 · 2 comments

Comments

@Tratosca
Copy link

Using macOS Catalina, I first installed rtptools with brew.
Tried to compile it myself, same issue.
When trying to send raw PCM data to an Omnia One, an AES67 compliant broadcast audio processor (which should accept 24 bits 48k big endian stereo PCM) with rtpsend I get an error "Line {???} is invalid".
"Reverse" command to play audio directly coming from the device with rtpdump and SoX is working fine.
I tried piping SoX with same parameters to correctly encode the audio.
Capture d’écran 2020-06-21 à 23 55 40
I also got "Line {RIFF???WAVEfmt }" when I tried to send directly a 24 bits 48k 2ch wav file.
Any idea ?

@njh
Copy link
Contributor

njh commented Jun 21, 2020

Hi,

I have been using rtpdump with an AES67 compatible Dante device:
https://www.aelius.com/njh/posts/0002

The error Line {RIFF???WAVEfmt } indicates that you are trying to send a WAV file. The rtpsend command uses its own special text based file format - as output by rtpdump -F ascii. And rtpplay uses the rtpdump -F dump file format. The dump file formats contain timing and RTP packet information, not just the raw audio samples / payload.

Unfortunately the official rtptools website is offline at the moment (see #135) but there is a copy of the page documenting the file format here:
http://www.cs.cmu.edu/~./libra-demo/rtptools-1.17/rtptools.html

You would need some kind of tool to convert the WAV file into RTP packets before it could be sent by rtpplay / rtpsend.

Maybe your Omnia One will be more tolerant than my Dante device, but I suspect that you may run into trouble with getting the AES67 device to accept RTP packets generated by rtpplay because of clocking problems. You will have to make sure that your system clock is synced to the Omnia's clock (using PTPv2) and that the RTP media clock matches.

I really wish there was more Open Source tooling available for AES67. I keep meaning to spend some time on it... what is you end-goal?

nick.

@Tratosca
Copy link
Author

Tratosca commented Jun 22, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants