EnoSat Posted February 15 Share Posted February 15 Small bug when scanning TS stream (creates non-existent ONID 8916 vs 56696) Kleiner Fehler beim Scannen des TS-Streams (erstellt eine nicht vorhandene ONID 8916 vs. 56696) Quote Link to comment
Griga Posted February 16 Share Posted February 16 Here it works with a stream created by the DVBViewer Media Server: I would need the complete URL of your stream for additional tests. Does the wrong ONID 56696 appear somewhere in the SI tree? Please use the Analyzer "Find" function for a check. Quote Link to comment
EnoSat Posted May 26 Author Share Posted May 26 (edited) Edited May 26 by EnoSat Quote Link to comment
Griga Posted May 27 Share Posted May 27 Ok, now I can reproduce it. It happens because the URL http://129.168.1.19:9999/abertis/pid8001 does not indicate that the stream contains a TS. So TransEdit has to guess. The first guess is "internet radio", which is internally converted to a TS. Since internet radio has no SDT containing an ONID, TransEdit creates a fake ONID. Reading the stream as internet radio fails, of course. The next attempt is reading it as TS, which succeeds, but the fake ONID is already there This does not happen if the Analyzer is running with the same URL, while the URL is is scanned. http:// is replaced by ts:// in the URL. TransEdit understands this as "http stream containing a TS". However, this can't be done with https. the URL ends with .ts, for example .../pids800.1.ts or .../pid8001/xxx.ts. However, the server may not accept it. the URL has a query part that ends with .ts, for example .../pid8001?xxx=.ts. The server will most likely ignore it, if xxx has no special meaning for it. So there are some work-arounds... nevertheless I will try to fix it in the next release. The fake ONID should be reset to 0, if reading a stream as internet radio fails. 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.