Recherche avancée

Sur d’autres sites (7407)

• Cannot stream webcam using ffserver because of malloc error [migrated]

  21 septembre 2012, par user1509326

  I was following this tutorial RaspBerry Pi webcam and when I run the following command from root :

  $ ffserver -f /root/ffserver.conf & ffmpeg -v 2 -r 5 -s 640x480 -f video4linux2 -i /dev/video1` http://localhost:8090/webcam.ffm

  The camera is turned on and everything is fine, except it does not stream. I checked the terminal. From video 1, I get the following error :

  bind(port 8090): Address already in use
  
  *** glibc detected *** ffmpeg: malloc(): smallbin double linked list corrupted: 0x0000000000e5ac00 **

  When I use another port like 5000, I get the same result :

  $ ffserver -f /root/ffserver.conf & ffmpeg -v 2 -r 5 -s 640x480 -f video4linux2 -i /dev/video1 http://localhost:8090/webcam.ffm
  
  [2] 3795
  
  avserver version 0.8.3-4:0.8.3-0ubuntu0.12.04.1, Copyright (c) 2000-2012 the Libav developers
  
    built on Jun 12 2012 16:52:09 with gcc 4.6.3
  
  *** glibc detected *** ffmpeg: malloc(): smallbin double linked list corrupted: 0x0000000000b77c00 ***

• malloc error ubuntu ffmpeg server not streaming

  21 septembre 2012, par user1509326

  enter code hereI was following this tutorial http://jeremyblythe.blogspot.com/2012/05/raspberry-pi-webcam.html and when i run the following command from root

  ffserver -f /root/ffserver.conf & ffmpeg -v 2 -r 5 -s 640x480 -f video4linux2 -i /dev/video1` http://localhost:8090/webcam.ffm

  The camera is turned on and everything is fine, except it does not stream, i checked the terminal and it says the following.

  from video 1 i get the following error
  
  bind(port 8090): Address already in use
  
  *** glibc detected *** ffmpeg: malloc(): smallbin double linked list corrupted: 0x0000000000e5ac00 **

  when i another port like 5000 i get the same result

  ffserver -f /root/ffserver.conf & ffmpeg -v 2 -r 5 -s 640x480 -f video4linux2 -i /dev/video1 http://localhost:8090/webcam.ffm
  
  [2] 3795
  
  avserver version 0.8.3-4:0.8.3-0ubuntu0.12.04.1, Copyright (c) 2000-2012 the Libav developers
  
    built on Jun 12 2012 16:52:09 with gcc 4.6.3
  
  *** glibc detected *** ffmpeg: malloc(): smallbin double linked list corrupted: 0x0000000000b77c00 ***

• What is “interoperable TTML” ?

  19 septembre 2012, par silvia

  I’ve just tried to come to terms with the latest state of TTML, the Timed Text Markup Language.

  TTML has been specified by the W3C Timed Text Working Group and released as a RECommendation v1.0 in November 2010. Since then, several organisations have tried to adopt it as their caption file format. This includes the SMPTE, the EBU (European Broadcasting Union), and Microsoft.

  Both, Microsoft and the EBU actually looked at TTML in detail and decided that in order to make it usable for their use cases, a restriction of its functionalities is needed.

  EBU-TT

  The EBU released EBU-TT, which restricts the set of valid attributes and feature. “The EBU-TT format is intended to constrain the features provided by TTML, especially to make EBU-TT more suitable for the use with broadcast video and web video applications.” (see EBU-TT).

  In addition, EBU-specific namespaces were introduce to extend TTML with EBU-specific data types, e.g. ebuttdt:frameRateMultiplierType or ebuttdt:smpteTimingType. Similarly, a bunch of metadata elements were introduced, e.g. ebuttm:documentMetadata, ebuttm:documentEbuttVersion, or ebuttm:documentIdentifier.

  The use of namespaces as an extensibility mechanism will ascertain that EBU-TT files continue to be valid TTML files. However, any vanilla TTML parser will not know what to do with these custom extensions and will drop them on the floor.

  Simple Delivery Profile

  With the intention to make TTML ready for “internet delivery of Captions originated in the United States”, Microsoft proposed a “Simple Delivery Profile for Closed Captions (US)” (see Simple Profile). The Simple Profile is also a restriction of TTML.

  Unfortunately, the Microsoft profile is not the same as the EBU-TT profile : for example, it contains the “set” element, which is not conformant in EBU-TT. Similarly, the supported style features are different, e.g. Simple Profile supports “display-region”, while EBU-TT does not. On the other hand, EBU-TT supports monospace, sans-serif and serif fonts, while the Simple profile does not.

  Thus files created for the Simple Delivery Profile will not work on players that expect EBU-TT and the reverse.

  Fortunately, the Simple Delivery Profile does not introduce any new namespaces and new features, so at least it is an explicit subpart of TTML and not both a restriction and extension like EBU-TT.

  SMPTE-TT

  SMPTE also created a version of the TTML standard called SMPTE-TT. SMPTE did not decide on a subset of TTML for their purposes – it was simply adopted as a complete set. “This Standard provides a framework for timed text to be supported for content delivered via broadband means,…” (see SMPTE-TT).

  However, SMPTE extended TTML in SMPTE-TT with an ability to store a binary blob with captions in another format. This allows using SMPTE-TT as a transport format for any caption format and is deemed to help with “backwards compatibility”.

  Now, instead of specifying a profile, SMPTE decided to define how to convert CEA-608 captions to SMPTE-TT. Even if it’s not called a “profile”, that’s actually what it is. It even has its own namespace : “m608 :”.

  Conclusion

  With all these different versions of TTML, I ask myself what a video player that claims support for TTML will do to get something working. The only chance it has is to implement all the extensions defined in all the different profiles. I pity the player that has to deal with a SMPTE-TT file that has a binary blob in it and is expected to be able to decode this.

  Now, what is a caption author supposed to do when creating TTML ? They obviously cannot expect all players to be able to play back all TTML versions. Should they create different files depending on what platform they are targeting, i.e. a EBU-TT version, a SMPTE-TT version, a vanilla TTML version, and a Simple Delivery Profile version ? Should they by throwing all the features of all the versions into one TTML file and hope that the players will pick out the right things that they require and drop the rest on the floor ?

  Maybe the best way to progress would be to make a list of the “safe” features : those features that every TTML profile supports. That may be the best way to get an “interoperable TTML” file. Here’s me hoping that this minimal set of features doesn’t just end up being the usual (starttime, endtime, text) triple.

  UPDATE :

  I just found out that UltraViolet have their own profile of SMPTE-TT called CFF-TT (see UltraViolet FAQ and spec). They are making some SMPTE-TT fields optional, but introduce a new @forcedDisplayMode attribute under their own namespace “cff :”.