This adds a 'Directory' node to the playlist editor so you can browse for tracks by file path. Selecting a node will add all the tracks below it to the playlist. (cherry picked from commit d7fcd89) Signed-off-by: Stuart Morgan <firstname.lastname@example.org>
On the playlist editor screen selecting the 'All tracks' node will add all the tracks below it to the playlist. (cherry picked from commit 6c6b4b8) Signed-off-by: Stuart Morgan <email@example.com>
(cherry picked from commit 91e7b1d) Signed-off-by: Stuart Morgan <firstname.lastname@example.org>
This adds some SWITCHTO* keybindings in the Music context that allows you to define keys that will switch to the chosen view rather than having to use the menu. All are unbound by default. (cherry picked from commit 0f1c4bf) Signed-off-by: Stuart Morgan <email@example.com>
(cherry picked from commit ea7a0b8) Signed-off-by: Stuart Morgan <firstname.lastname@example.org>
…er() This fixes a bug when reading the metadata from flac files with ID3 tags. (cherry picked from commit 459e806) Signed-off-by: Stuart Morgan <email@example.com>
…oving their respective related code into them. Way too many files in libmythtv, getting lost... Long way to go...
minor code cleanup...
This add full support for HTTP Live Streaming playback as per http://tools.ietf.org/html/draft-pantos-http-live-streaming-04. This includes: - Automatic fallback to lower bandwidth streams if available, the changeover will be detected according to the network bandwidth - Full support for live streaming - Seek support for video on demand stream There are few problems remaining however: -When switching to a different stream that is of a different resolution, playback will usually fail. Detection for format change should be added to myth player -When seeking with values over 2 minutes, sometimes the player will fail, detecting an EOF. No idea why. -For VOD streams, the whole downloaded content is buffered in RAM, this could get huge (as big as the file being streamed). Caching to disk should be implemented Playback of AES-128 encrypted content hasn't been tested; retrieval of the key will only work from publicly accessible web site defeating the whole purpose of encryption
The default-valued "next" and "prev" arguments are never deliberately set, and were actually getting in the way of the "timeout" argument.
OSDCC708TextZoom is removed from the frontend OSD setup screen and added as a "live setting" to the Subtitles menu of the playback OSD. This brings up an adjustment dialog similar to adjusting audio sync or timestretch. The menu item is only offered when subtitles are currently enabled. For text and CEA-708 subtitles, adjustments take effect immediately. For CEA-608, the adjustment takes effect only when the next caption is displayed, due to the way the 608 reader is structured. For now, only the Subtitles menu entry is provided, but if needed, it would be practical to add a wider set of actions and keybindings to match the implementation of audio sync and timestretch adjustment.
Using native aac support will require converting audio to floats, so put in a comment letting users enable AAC encoding for now if they want to test AAC. libfaac seems to work fine for generating streams playable on my iOS devices and Roku player.
The spec does not require path names, so remove them so that all files are found relative to the playlist itself. The path was only originally supplied in the playlist due to the fact that we had to use URIs of the form /Content/GetFile?StorageGroup=blah&FileName=bleh. Now that we can use /StorageGroup/blah/bleh we no longer need to use paths in the files since clients can follow the new URI format.
This reverts commit db12303. Conflicts: mythtv/programs/mythfrontend/scheduleeditor.cpp
The 1299 upgrade modifies DeletedMaxAge for its new meaning, now that AutoExpireInsteadOfDelete is always enabled. Previously, 0 meant "expire when out of disk space" and was the default value; but after f78f999 , 0 means "expire immediately" and -1 means "expire when out of disk space." Both before and after f78f999, any positive value means to expire recording files that many days after deletion. However, the setting DeletedMaxAge was only ever written to the database if the user enabled AutoExpireInsteadOfDelete (triggering the DeletedExpireOptions TriggeredConfigurationGroup) and modified DeletedMaxAge to some value other than its default of 0. Therefore, most users did not actually have a value for DeletedMaxAge in their databases--whether they had enabled AutoExpireInsteadOfDelete or not. The DB upgrade needs to change DeletedMaxAge to -1 if and only if AutoExpireInsteadOfDelete is enabled and DeletedMaxAge has a value of 0 (or is still using the default). Because of the condition on the update, it did nothing for users with AutoExpireInsteadOfDelete enabled but without a value for DeletedMaxAge in the database. This resulted in their systems changing from "expire when out of space" to "expire immediately". Thanks to Thomas Boehm and Peter on the mythtv-users mailing list for noticing that their settings didn't carry over through the update.
I'm planning a more comprehensive fix, but this will allow these scripts to work until it's ready. The scripts remain version independent and will work with any version of MythTV (and any version of config.xml)--unstable/development, 0.25-fixes, 0.24-fixes, or older versions.