1. 01 Aug, 2011 1 commit
    • Rémi Denis-Courmont's avatar
      aout: add an optional flush/drain callback · cba93daf
      Rémi Denis-Courmont authored
      Audio output plugins can use this to expedite discarding pending
      buffers. This reduces latency upon seeking or stopping the input.
      
      This new callback also supports explicit draining, but this is not
      used for the time being.
      cba93daf
  2. 25 Jul, 2011 2 commits
  3. 08 Jul, 2011 1 commit
  4. 07 Jun, 2011 1 commit
  5. 22 Oct, 2010 4 commits
  6. 14 Oct, 2010 1 commit
  7. 12 Jun, 2010 1 commit
  8. 08 Feb, 2010 1 commit
  9. 07 Feb, 2010 2 commits
  10. 11 Jan, 2010 1 commit
  11. 23 Sep, 2009 1 commit
  12. 03 Sep, 2009 1 commit
  13. 15 May, 2009 1 commit
  14. 13 May, 2009 1 commit
  15. 25 Apr, 2009 1 commit
  16. 27 Jan, 2009 1 commit
  17. 29 Oct, 2008 1 commit
  18. 22 Sep, 2008 1 commit
  19. 14 Aug, 2008 1 commit
  20. 03 Aug, 2008 1 commit
  21. 24 Jun, 2008 1 commit
  22. 22 Jun, 2008 1 commit
  23. 31 May, 2008 1 commit
  24. 27 May, 2008 1 commit
  25. 21 May, 2008 1 commit
  26. 08 May, 2008 1 commit
  27. 14 Apr, 2008 1 commit
  28. 11 Mar, 2008 1 commit
  29. 23 Jan, 2008 1 commit
  30. 17 Jan, 2008 1 commit
  31. 16 Jan, 2008 3 commits
    • damienf's avatar
      vlc security: As i've seen very little improvement on that front, i've decided... · 658b4f83
      damienf authored
      vlc security: As i've seen very little improvement on that front, i've decided to check in my take on handling the problem of managing harmful options. I'm pretty sure this is going to be very controversial, but I think my approach is quite simple and yet very effective Anyway, my approach makes the following assumptions:
      
      - most vlc options are considered safe, only a handful are particularily unsafe and need be declared as such in their definition (they mostly deal with writing to an output file or URL)
      - unsafe options are only considered potentially harmful when used as an input option, ie. the ':option' format. Configuration options are always considered safe 'i.e --option' 
      - unsafe options are associated with a global security policy, which dictates how these are handled. At the moment, The policy can be either block, allow or prompt, and is set using the '--security-policy' option (which itself is considered unsafe ;)
      
      the policy can be set by the user at the command line or in the preferences, it curently defaults to prompt, which is the desirable state for deskop use. However, it can be overriden depending on context, for example, the activex and mozilla will force the security-policy to block regardless of preference settins.
      
      the code is a bit rough at the moment, but i will optimize/clean it up if the dev community this approach is worth keeping.
      
      try the following example, and you'll see quickly what i mean:
      
      ./vlc -vvv <a mrl> :sout=#transcode{vcodec=mp1v,vb=1024,acodec=mpga,ab=192}:standard{mux=ts,dst=vlc-output.ts,access=file}"
      
      Enjoy,
         Damien
      
      
      658b4f83
    • Rémi Denis-Courmont's avatar
    • Rafaël Carré's avatar
      806cf516
  32. 18 Sep, 2007 1 commit
  33. 20 Aug, 2007 1 commit