El 27/01/2017 a las 3:52, fredvs escribió:
Hello Silvio:
Yes, we are on the good way.
Following your advice, here from https-url-opus the result of :
Hello,
The first thing to debug this problems is to determine the expected data
for opus_test_memory. Usually streams (audio, video, etc...) are
composed by two pieces the raw data and the transport envelope. In this
case opus usually uses Ogg as transport envelope but it could be
streamed in another container like MP4, MKV, etc.
Opus library should provide a play engine that decodes raw streams,
extracted from its transport layer and maybe another series of APIs for
the default transport layer, Ogg in this case. This last job seems to be
done by the OpusFile API.
So to resume, you file is a raw opus audio or an Ogg file ?
Before using pipes with http try pipes with a local file. If your pipes
on local file works but http does not maybe you are receiving the http
headers, or any other unexpected situation, so dump the piped data to a
local file and match it against the remote one.
Said that, I had never touched opus in my life :) so take my comments
with care.
--
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
