Rafaël Carré

Results 12 comments of Rafaël Carré

We are still keeping a uref, it's just the first of N urefs until a buffer is getting output. I don't see how a regression is possible as after we...

Works with clang-4.0 from http://apt.llvm.org/ ``` CFLAGS="-fsanitize=thread -O2 -g -fno-omit-frame-pointer"; ../configure CFLAGS="$CFLAGS" CXXFLAGS="$CFLAGS" LDFLAGS=-fsanitize=thread CC=clang-4.0 CXX=clang++-4.0 ```

I hacked rist_ts and rist_rx changes to test quickly Not sure if I should remove the changes completely or add new programs

This depends on https://github.com/funman/bitstream/tree/srt

> @funman [srth: no need to update flow def immediately](https://github.com/Upipe/upipe/pull/947/commits/15e3534afd7686d6573114f959e29d115fabead4) breaks data transmission This seems to break rist_tx caller

> There are still some indentation changes left in `rist_rx` and `rist_tx`. Sorry I think I used git diff -w

> What about adding `upipe_srt_source` and `upipe_srt_sink` pipes which could be used as replacement of `upipe_udp_source`/`upipe_rtp_source` and `upipe_udp_sink`? These would make `srt_tx`/`srt_rx` much simpler, and srt usage in client applications...

> > I don't understand what they would replace exactly, why does udpsink need to be replaced? > > The same way you could replace `upipe_udp_source` with `upipe_rtp_source` to use...

It's not simpler for me since they are done already :)

> Yes, it encapsulates everything, which is why `srt_tx` and `srt_rx` will be much simpler afterwards. Also wouldn't we be missing events between internal pipes that could be useful?