-
Notifications
You must be signed in to change notification settings - Fork 65
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
Comments
Hi, I have been using The error 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: 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 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. |
Thanks for this detailed answer !
As a student in audio & video engineering I really like to try to achieve some pointless goals. I call this pointless because a Livewire driver does exist for Windows, linking the entire Livewire network and up to 32 virtual Windows WASAPI interfaces, however this driver is proprietary. And as a macOS/Linux user I’d love to create a way to « talk » to the Omnia both ways without having to boot a Windows VM (but as I said the main idea is to elevate my knowledge).
I talked to one of my teacher about this challenge some weeks ago and he also told me about clock issues (I achieved to send some audio using SoX and VLC ‘sout’ but audio was really stuttered, hardly audible. Vu-meters were all in red).
I will continue to experiments and will have a look into clock synchronization. Don’t know where to start, but I will start. I don’t know much how RTP does work, I guess this is where I have to come to first.
|
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.
I also got "Line {RIFF???WAVEfmt }" when I tried to send directly a 24 bits 48k 2ch wav file.
Any idea ?
The text was updated successfully, but these errors were encountered: