Hi On 2017-04-19 08:21:07, Daniel Kahn Gillmor wrote: > Control: tags 860555 - moreinfo > > On Wed 2017-04-19 11:40:44 +0200, Sebastian Ramacher wrote: > > On 2017-04-18 11:20:47, Daniel Kahn Gillmor wrote: > >> If i run: > >> > >> vlc rtsp://dccourt.streamguys1.com/live/streamName > > > > I'm afraid that without an actual stream that exhibits the problem or a > > sample, > > there is nothing we can do about that. > > Ah, i see why you might have thought this is a placeholder, but it is > the name of the actual stream! > > It appears to be down right now, probably because it's only running when > the Washington, DC court of appeals is in session in a particular > courtroom. It may be worth retrying around 10:30am in > TZ=America/New_York.
I'll try to catch it. > > If you'd rather have a static sample of the stream, i'm happy to provide > that but i'm not sure the best way to do so. Should i run it and grab a > .pcap on the network interface? or is there some other preferred way to > get a sample? https://wiki.videolan.org/Documentation:Streaming_HowTo/Receive_and_Save_a_Stream/ has some instructions on recording a stream. > >> then i get a series (about 1/second) of messages like this to stdout > >> or stderr: > >> > >> [h264 @ 0x7f8f58167880] mmco: unref short failure > > > > FWIW, this is a message from ffmpeg. > > thanks! should we reassign or at least CC those folks on this report? vlc currently uses an older ffmpeg version than in the archive as src:ffmpeg. So we could do that once we know that newer ffmpeg version also print the warnings. Cheers -- Sebastian Ramacher
signature.asc
Description: PGP signature
