16 Commits

Author	SHA1	Message	Date
saxon	716a92a72c	stream/rtp/encoder.go: sendLen to sendSize and capturing error from e.Encode()	2019-02-09 19:31:15 +10:30
saxon	7f140baf22	rtp: corrected error in comment	2019-01-13 16:42:30 +10:30
saxon	cb762c04c6	rtp: set defPayloadSIze to sendLen which is 7 *188 and also commented consts	2019-01-13 16:40:25 +10:30
saxon	d5b6e91892	rtp: using 'size' instead of 'len'	2019-01-02 10:32:48 +10:30
saxon	e1dd89b348	rtp: using static memory to hold bytes of rtp pkts	2018-12-27 14:44:30 +10:30
saxon	0531b9542b	rtp: client only needs to specify padding length and then padding indicator is set based on this	2018-11-24 12:22:17 +10:30
saxon	103bd2b91c	rtp: removed exclamation marks in panics	2018-11-22 19:32:31 +10:30
saxon	efe2333683	rtp: added some commenting	2018-11-21 20:28:40 +10:30
saxon	338bc53e24	rtp: added standards information regarding padding	2018-11-21 17:30:46 +10:30
saxon	6f1515cc46	rtp: simplified addition of padding to rtp packet	2018-11-21 17:30:46 +10:30
saxon	f4d44e0c79	rtp: using = instead of |= for setting of rtp packet fields	2018-11-21 17:30:46 +10:30
saxon	5cc35a77a5	rtp: finished encoder file - wrote encode function, wrote timestamp function and sequence number function - need to test	2018-11-17 23:17:08 +10:30
saxon	ddf25e1fbe	rtp: started writing encoder for rtp. Needto work out what the packet type part of the header should be	2018-11-17 17:43:04 +10:30
saxon	1a15889522	rtp: fixed bug by actually checking to see if there is padding before adding padding size to end buf - which would mean there's actually padding	2018-11-17 17:17:54 +10:30
saxon	9f329d49b6	rtp: writing test function inside rtp_test.go	2018-11-17 16:52:57 +10:30
saxon	4e7e779de7	rtp: created rtp packet structure, wrote byte function (interprets packet structure and creates equivalent byte slice and started writing test utilities	2018-11-16 19:35:19 +10:30