| Age | Commit message (Collapse) | Author |
|---|
|
experimental
|
|
* Jumping between marks in the movie, with "<" and ">", doesn't work
well when there are cut marks in the movie. Especially jumping
backwards will fail if there is a mark in a cut out region that is
to be jumped over. (InfoBarGenerics.py, chunks 3 and 4)
* Now when rewind works at all platforms also at low speeds, the
rewind speeds x2 and x4 should be added again to the
default. (UsageConfig.py, chunk 1)
* Cleanup some obsolete code: SeekBackHack and non-smooth
winding. None of these can be used anymore, but remnants were left
in the code and in the configuration alternatives. It is high time
to clean these out. (setup.xml, UsageConfig.py chunk 2,
InfoBarGenerics.py chunks 1 and 2, DVDPlayer)
* In the position gauge of the movie player, marks in the movie are
shown as red dots. Long time ago the last position was also shown as
a red dot, which was bad because it was confused with the marks, so
it was removed. However, jumping between marks in the movie with "<"
and ">" also stops at the last position, which is useful e.g. if you
don't automatically start playing from the last position. The code
below adds the last position back to the position gauge as a green dot,
to distinguish it from the red ones. (epositiongauge.cpp)
refs bug #570
|
|
|
|
this fixes bug #332
|
|
change action map help text for long info button press
|
|
this fixes bug #332
|
|
change action map help text for long info button press
|
|
last playing position for recorded services was stored only if between 1% and 99% of the recording's length. this lead to voodoo for the user, since long recordings naturally have a longer 1% than short ones.
so the 1% rule is gone now and we display the position of the marker in the message box, asking the user if playing should continue at this position.
|
|
last playing position for recorded services was stored only if between 1% and 99% of the recording's length. this lead to voodoo for the user, since long recordings naturally have a longer 1% than short ones.
so the 1% rule is gone now and we display the position of the marker in the message box, asking the user if playing should continue at this position.
|
|
|
|
|
|
change
|
|
the same key is pressed, small cleanup
|
|
|
|
this fixes bug #293
|
|
change
|
|
the same key is pressed, small cleanup
|
|
|
|
|
|
|
|
|
|
this fixes bug #293
|
|
|
|
|
|
|
|
|
|
|
|
for this..
|
|
|
|
requested by Tode for the AudioSync Plugin
fixes bug #305
|
|
requested by Tode for the AudioSync Plugin
fixes bug #305
|
|
solution for this.."
This reverts commit b643641e2c6288eff61d0346a3dda82bd820b3b7.
|
|
This reverts commit 1c954ba161bc3cd4b838b3c5a423d41847f0382a.
|
|
|
|
|
|
for this..
|
|
|
|
|
|
|
|
remove sleep timer from infobar blue button menu
sleep timer still accessible through powerdown menu via main menu or by holding the power button for 3 seconds
|
|
* My previous code for "slow rewind" (aka "SeekBackHack") is not
required any more. Indeed, since the change in "decoder states"
some time ago my code stopped working and is now only destructively
interfering with the new winding approach, effectively ruining the
speed accuracy for slow rewind. Similarly, the "non-smooth winding"
code ruins the accuracy for high winding speeds. The patch below
removes the "SeekBackHack", and temporarily disables the
"non-smooth winding" code until we know whether the decoder states
will allow simultaneous repeat and skip rates
again. (InfoBarGenerics.py)
* Due to a bug in 'eDVBTSTools::findNextPicture', rewind was always
at the required speed minus one. (The frame just played was counted
as one when skipping backwards.) Fixed below. (tstools.cpp)
* A piece of code to apparently increase precision in seeking, by
always aligning to an i-frame start, had exactly the opposite
effect: GOP single-stepping fails completely on DM7025 and gets
highly unreliable on DM800. The piece of code is removed.
(It destructively interferes with previous code by me to hit frames
somewhat before the GOP start. As an alternative, my previous code
can be removed instead, and the currently removed piece of code
adjusted to work. But then it has to be done differently on the two
platforms.) (dvb.cpp)
* By some reason eDVBVideo::getPTS only returns even numbers on DM800
even when it should be odd. This ruins GOP single stepping in 50%
of the cases. This is easy to compensate for by adding a margin of
1 in getAccessPoint. (pvrparse.cpp)
* After the above, when GOP single-stepping works reliable on both
platforms and on SD/HD, the correct step lengths can be
used. (InfoBarGenerics.py)
|
|
At regular intervalls there are questions in the forum (in at least
three or four different threads on only this subject) on how to
configure the recording paths so you don't have to set them to the
same thing over and over again in e.g EPG timers. People apparently
forget to set it, and miss their recordings because the harddisk is
full or not built in. They want an easy way to change the default from
/hdd/movies/ to a NAS or a USB device.
I have rebased the patch in this thread from March 23, added two minor
bugfixes, and hopefully made it less controversial by making sure that
it only affects the expert setup level. I don't think there should be
anything controversial about this patch now, and no known bugs. It
only provides functionality that several people are screaming to get.
Synopsis: The patch changes the "Timeshift path..." setup dialogue
into a "Recording paths..." dialogue where you can easily configure
both the timeshift and the other recording paths.
|
|
|
|
|
|
|
|
|
|
for one single pid
|
|
|
|
|
|
|
