<feed xmlns='http://www.w3.org/2005/Atom'>
<title>xine-lib, branch 1.1.16</title>
<subtitle>xine-lib git mirror
</subtitle>
<link rel='alternate' type='text/html' href='https://vdr-projects.e-tobi.net/git/xine-lib/'/>
<entry>
<title>xine-lib 1.1.16.</title>
<updated>2009-01-07T16:36:19+00:00</updated>
<author>
<name>Darren Salt</name>
<email>linux@youmustbejoking.demon.co.uk</email>
</author>
<published>2009-01-07T16:36:19+00:00</published>
<link rel='alternate' type='text/html' href='https://vdr-projects.e-tobi.net/git/xine-lib/commit/?id=20a5f2ac43666a6242dfb03a6a697692abe4b39f'/>
<id>20a5f2ac43666a6242dfb03a6a697692abe4b39f</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge security fixes.</title>
<updated>2009-01-05T14:50:58+00:00</updated>
<author>
<name>Darren Salt</name>
<email>linux@youmustbejoking.demon.co.uk</email>
</author>
<published>2009-01-05T14:50:58+00:00</published>
<link rel='alternate' type='text/html' href='https://vdr-projects.e-tobi.net/git/xine-lib/commit/?id=5347abe5764b0a0ff3ef1d357ce9934a425758fa'/>
<id>5347abe5764b0a0ff3ef1d357ce9934a425758fa</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Changelog updates.</title>
<updated>2009-01-05T14:50:15+00:00</updated>
<author>
<name>Darren Salt</name>
<email>linux@youmustbejoking.demon.co.uk</email>
</author>
<published>2009-01-05T14:50:15+00:00</published>
<link rel='alternate' type='text/html' href='https://vdr-projects.e-tobi.net/git/xine-lib/commit/?id=8f725b5644ac910294fbe28929ddc98cd1d2ad38'/>
<id>8f725b5644ac910294fbe28929ddc98cd1d2ad38</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Introduce XVMC_LOCKDISPLAY_SAFE to solve deadlocks in certain xxmc implementations.</title>
<updated>2009-01-04T17:21:11+00:00</updated>
<author>
<name>Reinhard Nißl</name>
<email>rnissl@gmx.de</email>
</author>
<published>2009-01-04T17:21:11+00:00</published>
<link rel='alternate' type='text/html' href='https://vdr-projects.e-tobi.net/git/xine-lib/commit/?id=0907a74b5fa7b8b439f1f8f5db239c7586bfb12d'/>
<id>0907a74b5fa7b8b439f1f8f5db239c7586bfb12d</id>
<content type='text'>
Some implementations are buggy and lock resources (for example the display or
internal data structures) in different order, which results in deadlocks.
As XVMC_LOCKDISPLAY_SAFE is not defined by default, most API functions will
now be guarded by a LockDisplay()/UnlockDisplay() pair, which imposes a lock
order at least for the resource display and hence avoids those deadlocks.
(transplanted from 580a2a9148618131cedfbc9058ac7979ca16f69b)

--HG--
extra : transplant_source : X%0A%2A%91Ha%811%CE%DF%BC%90X%ACyy%CA%16%F6%9B
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Some implementations are buggy and lock resources (for example the display or
internal data structures) in different order, which results in deadlocks.
As XVMC_LOCKDISPLAY_SAFE is not defined by default, most API functions will
now be guarded by a LockDisplay()/UnlockDisplay() pair, which imposes a lock
order at least for the resource display and hence avoids those deadlocks.
(transplanted from 580a2a9148618131cedfbc9058ac7979ca16f69b)

--HG--
extra : transplant_source : X%0A%2A%91Ha%811%CE%DF%BC%90X%ACyy%CA%16%F6%9B
</pre>
</div>
</content>
</entry>
<entry>
<title>FTBFS (i386 with 64bit kernel)</title>
<updated>2009-01-04T16:30:43+00:00</updated>
<author>
<name>Sven Joachim</name>
<email>svenjoac@gmx.de</email>
</author>
<published>2009-01-04T16:30:43+00:00</published>
<link rel='alternate' type='text/html' href='https://vdr-projects.e-tobi.net/git/xine-lib/commit/?id=c4ca0e127e4c3407df8268ec6320576f98c83567'/>
<id>c4ca0e127e4c3407df8268ec6320576f98c83567</id>
<content type='text'>
Am 04.01.2009 um 04:55 schrieb Adrian Bunk:

&gt; ....
&gt; In file included from ../../../src/xine-engine/xine_internal.h:33,
&gt;                  from noise.c:24:
&gt; .../../../include/xine.h:2230: warning: 'xine_tvsystem' is deprecated
&gt; noise.c: Assembler messages:
&gt; noise.c:155: Error: bad register name `%rax'
&gt; noise.c:161: Error: bad register name `%rax)'
&gt; &lt;--  snip  --&gt;

One problem is that the configure script thinks we're running a 64-bit
system:

,----
| checking build system type... x86_64-unknown-linux-gnu
| checking host system type... x86_64-unknown-linux-gnu
| checking build system type... (cached) x86_64-unknown-linux-gnu
`----

This is bad, build and host type should be passed explicitly in
debian/rules.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Am 04.01.2009 um 04:55 schrieb Adrian Bunk:

&gt; ....
&gt; In file included from ../../../src/xine-engine/xine_internal.h:33,
&gt;                  from noise.c:24:
&gt; .../../../include/xine.h:2230: warning: 'xine_tvsystem' is deprecated
&gt; noise.c: Assembler messages:
&gt; noise.c:155: Error: bad register name `%rax'
&gt; noise.c:161: Error: bad register name `%rax)'
&gt; &lt;--  snip  --&gt;

One problem is that the configure script thinks we're running a 64-bit
system:

,----
| checking build system type... x86_64-unknown-linux-gnu
| checking host system type... x86_64-unknown-linux-gnu
| checking build system type... (cached) x86_64-unknown-linux-gnu
`----

This is bad, build and host type should be passed explicitly in
debian/rules.
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix WAV demuxer to send the last frames when they don't fit perfectly into the buffer</title>
<updated>2009-01-04T12:46:08+00:00</updated>
<author>
<name>Matthias Kretz</name>
<email>kretz@kde.org</email>
</author>
<published>2009-01-04T12:46:08+00:00</published>
<link rel='alternate' type='text/html' href='https://vdr-projects.e-tobi.net/git/xine-lib/commit/?id=464ad50e25a788e900b3a0207392a689a87d745e'/>
<id>464ad50e25a788e900b3a0207392a689a87d745e</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>At discontinuity all stored PTS values need to be reset to 0, as they are now invalid.</title>
<updated>2009-01-04T14:05:04+00:00</updated>
<author>
<name>Reinhard Nißl</name>
<email>rnissl@gmx.de</email>
</author>
<published>2009-01-04T14:05:04+00:00</published>
<link rel='alternate' type='text/html' href='https://vdr-projects.e-tobi.net/git/xine-lib/commit/?id=90acd04b32de69512076b386cbb385041697e63e'/>
<id>90acd04b32de69512076b386cbb385041697e63e</id>
<content type='text'>
But as PTS values are stored in FFmpeg's decoder, there is no way to reset them to 0.
Therefore PTS tagging has been introduced. At discontinuity a tag is generated and
applied to all new PTS values. Any returned PTS value is checked for this tag and
outdated PTS values are reset to 0. When the tag appears on returned PTS values then
tagging is reset.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
But as PTS values are stored in FFmpeg's decoder, there is no way to reset them to 0.
Therefore PTS tagging has been introduced. At discontinuity a tag is generated and
applied to all new PTS values. Any returned PTS value is checked for this tag and
outdated PTS values are reset to 0. When the tag appears on returned PTS values then
tagging is reset.
</pre>
</div>
</content>
</entry>
<entry>
<title>Feed buffer PTS through FFmpeg's decoder to have them reordered to display order.</title>
<updated>2009-01-03T23:16:19+00:00</updated>
<author>
<name>Reinhard Nißl</name>
<email>rnissl@gmx.de</email>
</author>
<published>2009-01-03T23:16:19+00:00</published>
<link rel='alternate' type='text/html' href='https://vdr-projects.e-tobi.net/git/xine-lib/commit/?id=5fba2f2d170166e327beef6d743dcdbf090eb49a'/>
<id>5fba2f2d170166e327beef6d743dcdbf090eb49a</id>
<content type='text'>
Attaching buffer PTS, which are in decoding order, to decoded images is
simply wrong. FFmpeg meanwhile provides a way to pass PTS values through
its decoder too. As a result they get reordered to display order and can
be attached to the decoded frames.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Attaching buffer PTS, which are in decoding order, to decoded images is
simply wrong. FFmpeg meanwhile provides a way to pass PTS values through
its decoder too. As a result they get reordered to display order and can
be attached to the decoded frames.
</pre>
</div>
</content>
</entry>
<entry>
<title>configurable parameter for tvtime pulldown sync sensitivity</title>
<updated>2009-01-03T04:00:31+00:00</updated>
<author>
<name>Jason Tackaberry</name>
<email>tack@urandom.ca</email>
</author>
<published>2009-01-03T04:00:31+00:00</published>
<link rel='alternate' type='text/html' href='https://vdr-projects.e-tobi.net/git/xine-lib/commit/?id=f654b11f2176d71c3c0971d9a87b749225eb229c'/>
<id>f654b11f2176d71c3c0971d9a87b749225eb229c</id>
<content type='text'>
Currently, once the tvtime plugin has locked onto a telecine pattern, it
will wait PULLDOWN_ERROR_WAIT (a hardcoded #defined value) number of frames
before switching to filmmode.

This sensitivity is excessively high (i.e. the value is too low) for certain
content -- the kind of content that was shot on film but edited in video
mode, so telecine patterns are constantly breaking (examples like Buffy,
Simpsons and Family Guy are especially egregious offenders).

The attached patch turns this constant into a modifiable post plugin
parameter called pulldown_error_wait.

Xine helpfully emits a XINE_EVENT_POST_TVTIME_FILMMODE_CHANGE event when
film mode changes (a patch I submitted some years back).  With the attached
patch, a front-end can monitor the frequency of these events, and
dynamically adjust pulldown_error_wait in a sensible way.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Currently, once the tvtime plugin has locked onto a telecine pattern, it
will wait PULLDOWN_ERROR_WAIT (a hardcoded #defined value) number of frames
before switching to filmmode.

This sensitivity is excessively high (i.e. the value is too low) for certain
content -- the kind of content that was shot on film but edited in video
mode, so telecine patterns are constantly breaking (examples like Buffy,
Simpsons and Family Guy are especially egregious offenders).

The attached patch turns this constant into a modifiable post plugin
parameter called pulldown_error_wait.

Xine helpfully emits a XINE_EVENT_POST_TVTIME_FILMMODE_CHANGE event when
film mode changes (a patch I submitted some years back).  With the attached
patch, a front-end can monitor the frequency of these events, and
dynamically adjust pulldown_error_wait in a sensible way.
</pre>
</div>
</content>
</entry>
<entry>
<title>check number of bytes read by input-&gt;read in demuxing mpeg block/pes</title>
<updated>2008-12-31T22:01:54+00:00</updated>
<author>
<name>Matthias Hopf</name>
<email>mhopf@suse.de</email>
</author>
<published>2008-12-31T22:01:54+00:00</published>
<link rel='alternate' type='text/html' href='https://vdr-projects.e-tobi.net/git/xine-lib/commit/?id=82a5ac7e7ef212e08d63a8f31482548fdb3c9ba4'/>
<id>82a5ac7e7ef212e08d63a8f31482548fdb3c9ba4</id>
<content type='text'>
input-&gt;read may return negative error codes or read less than we want
so we should check for the right return value instead of just not 0
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
input-&gt;read may return negative error codes or read less than we want
so we should check for the right return value instead of just not 0
</pre>
</div>
</content>
</entry>
</feed>
