Commit Graph

27 Commits

Author SHA1 Message Date
aler9
9f4fea8a01 change track initialization method 2022-06-23 13:13:36 +02:00
aler9
2fa3148a27 move URL into dedicated folder 2022-06-05 01:27:19 +02:00
aler9
c1b10a80be allow writing primitives to static buffers 2022-05-11 15:26:44 +02:00
aler9
edeef85e9e accept io.Writer in Write() methods 2022-05-08 14:33:29 +02:00
aler9
bfe4e8cdaa automatically remux oversized RTP/H264 packets; drop parameter ReadBufferSize 2022-04-09 20:16:14 +02:00
aler9
bc9be686d9 client: call Options() automatically 2022-02-19 22:51:54 +01:00
aler9
ad69a8957b support h264 tracks with extradata in sprop-parameter-sets 2022-01-30 15:51:49 +01:00
aler9
6d5bf0c1bb new track system 2022-01-30 15:51:49 +01:00
aler9
f3096ec102 improve write performance by
* buffering packets before sending them
* removing mutexes
2021-12-08 17:46:56 +01:00
aler9
a1de5ffdf9 add client TLS publish tests 2021-12-08 17:23:03 +01:00
aler9
9c3ee269f2 client: do not use InsecureSkipVerify by default 2021-12-03 23:11:49 +01:00
aler9
73f1c632c5 client: set ServerName when using TLS (https://github.com/aler9/rtsp-simple-server/issues/708) 2021-12-03 22:56:35 +01:00
aler9
1a62baecad add client close test 2021-11-18 10:06:36 +01:00
aler9
1411cb33f5 server: support reading with VLC and multicast 2021-11-15 17:40:17 +01:00
aler9
e13b4289ec client: simplify API, add StartReadingWait 2021-11-12 18:01:27 +01:00
aler9
d04381d787 client: allow calling Close() during a request 2021-11-12 18:01:27 +01:00
aler9
d1d766658b client: merge Client and ClientConn 2021-11-12 18:01:27 +01:00
aler9
fdb0d70870 client: remove default client 2021-11-12 18:01:27 +01:00
aler9
1d5f3c92ae add VLC authentication workaround 2021-10-30 14:47:58 +02:00
aler9
d744a2e0d3 change way tracks are initialized
A config object is now required to initialize tracks.
Config objects are provided for H264 and AAC.
This allows to pass parameters easily and treat AAC
parameters explicitly.
2021-08-25 19:16:51 +02:00
Daniel Mack
8062cfdf42 Add support for charset information in content-type header
Altough not explicitly allowed by RFC2326, some servers respond with
a `Content-Type` header field that contains charset information as
described in RFC2616 (sec 14.17).

The parser currently fails to read from such connections and bails
with

  `unsupported Content-Type header '[application/sdp; charset=utf-8]'`

Change this by ignoring everything after a semicolon.
2021-06-25 19:05:40 +02:00
aler9
dde57ee568 remove ID and BaseURL from Track 2021-06-23 23:07:55 +02:00
aler9
d073a185c2 client: allow to publish tracks with pre-existing control attribute (#48) 2021-06-23 22:03:22 +02:00
aler9
d07e93f245 auth: simplify 2021-05-30 12:52:46 +02:00
aler9
70c0dc7800 remove base.MustParseURL 2021-05-23 16:48:56 +02:00
aler9
f2f9b644c6 simplify tests 2021-05-07 23:51:23 +02:00
aler9
712432bcef client: move test files 2021-05-04 16:51:20 +02:00