1. 27 Apr, 2008 2 commits
  2. 25 Apr, 2008 1 commit
  3. 14 Apr, 2008 1 commit
  4. 23 Mar, 2008 1 commit
  5. 21 Mar, 2008 1 commit
  6. 20 Mar, 2008 1 commit
    • André Weber's avatar
      Fix the handling of string variable - store them as UTF-8 into the config... · 61a056a7
      André Weber authored
      Fix the handling of string variable - store them as UTF-8 into the config variables, also convert the StringList values to an UTF8 string before putting them into a QVariant - which seems not to work if created from a "char *" - because later converterd QVariant->toString() isn't UTF8 like expected.
      waveout.c forgott to convert string to UTF8 before storing in choice list
      61a056a7
  7. 19 Mar, 2008 4 commits
  8. 13 Mar, 2008 1 commit
  9. 11 Mar, 2008 2 commits
  10. 02 Mar, 2008 3 commits
    • atmo's avatar
      Bugfix for #492: Audio output on Windows useing SPDIF for AC3 / DTS · 79223aae
      atmo authored
      But its still very time critical, because paout gets sometimes empty
      so that aout_OutputNextBuffer(..) doesn't deliver new audiobuffers,
      sometimes it happens - that these buffers arrive very late for output.
      Reasons: -changed CPU load, (extra running application, also fast forward
      seeking and and jumping may lead to this situation.)
      
      Enhancement #897: added an option to let the user  choose is prefered audio device. (needs restart of VLC to get applied)
      79223aae
    • atmo's avatar
      Revert "#492 bugfix, for SPDIF audio ouput of AC3 and DTS sound on Windows" · ced125da
      atmo authored
      This reverts commit 9438646c.
      wrong file in my list I'am sorry, and wrong file modes
      ced125da
    • atmo's avatar
      #492 bugfix, for SPDIF audio ouput of AC3 and DTS sound on Windows · 9438646c
      atmo authored
      (but its still critical because it happens - aout_OutputNextBuffer(...) has no buffers
      available - sometime the output doesn't know until some ms before the last block
      has finished to play! so each little disturbtion of the CPU or load change
      leads to studdering/hickups)
      
      #897 enhancement: give the use the option to choose its prefered audio device,
      instead of useing Windows default
      9438646c
  11. 26 Feb, 2008 1 commit
    • Pierre d'Herbemont's avatar
      misc/objects.c: Don't rely on vlc_object_destroy() to destroy objects, but... · a78e273e
      Pierre d'Herbemont authored
      misc/objects.c: Don't rely on vlc_object_destroy() to destroy objects, but expects vlc_object_release to do it when the refcount goes to zero.
      * Meaning, that when created objects gets a refcount to 1.
      * Destroying is instantaneous and we don't have to poll for a few secondss or so to wait until the object's refcount reach 0.
      * We now track vlc_object_t's mem leaks when libvlc_global is released (Hard error for now, so they don't get unoticed)
      * We fail hard if an object is released with a refcount of 1 without being detached from its parent and its children, to make sure such cases don't go unoticed.
      (make test or make check still pass after that one. VLC is known to leak one object when no module is loaded, this must be fixed).
      
      a78e273e
  12. 24 Feb, 2008 1 commit
  13. 19 Feb, 2008 1 commit
  14. 28 Jan, 2008 1 commit
  15. 23 Jan, 2008 1 commit
  16. 18 Jan, 2008 1 commit
  17. 17 Jan, 2008 1 commit
  18. 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
  19. 15 Jan, 2008 1 commit
  20. 14 Jan, 2008 1 commit
  21. 11 Nov, 2007 1 commit
  22. 10 Nov, 2007 1 commit
  23. 05 Nov, 2007 4 commits
  24. 02 Oct, 2007 1 commit
  25. 18 Sep, 2007 2 commits
  26. 10 Sep, 2007 1 commit
  27. 04 Sep, 2007 1 commit