MMBase

Generate new stream cache for existing media

Details

  • Type: Improvement Improvement
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.9.3
  • Fix Version/s: 1.9.4
  • Component/s: Streams
  • Description:
    When you create a new configuration entry in the streamcaches.xml for a new stream format f.e. you should have an option to generate such a cache for already existing media.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
André van Toly added a comment - 2010-05-04 16:11
Updated to major since generation of new streams in existing instances depend on it.
Show
André van Toly added a comment - 2010-05-04 16:11 Updated to major since generation of new streams in existing instances depend on it.
Hide
Permalink
André van Toly added a comment - 2010-05-26 17:19
An option could be to adapt org.mmbase.streams.CreateCachesFunction not to delete already existing streamsourcescaches (and replace them with new nodes) but only recreate the belonging stream file and that only when a its configuration is changed in createcaches.xml. When done properly this would also end up with new streamsourcescaches nodes for newly added configuration entries.
Show
André van Toly added a comment - 2010-05-26 17:19 An option could be to adapt org.mmbase.streams.CreateCachesFunction not to delete already existing streamsourcescaches (and replace them with new nodes) but only recreate the belonging stream file and that only when a its configuration is changed in createcaches.xml. When done properly this would also end up with new streamsourcescaches nodes for newly added configuration entries.
Hide
Permalink
André van Toly added a comment - 2010-05-31 11:22
Just triggering this function will have it look for new configured caches and transcode them, using parameter 'all' deletes all streams files and retranscodes everything new, and giving it a node number as parameter cache wil just retranscode that cache node.
Show
André van Toly added a comment - 2010-05-31 11:22 Just triggering this function will have it look for new configured caches and transcode them, using parameter 'all' deletes all streams files and retranscodes everything new, and giving it a node number as parameter cache wil just retranscode that cache node.
Hide
Permalink
André van Toly added a comment - 2010-06-02 15:42
Note that changes to the configuration are seen as _new_ caches.
When you care to re-transcode an existing streamsourcescaches node, you must change its key (field) and re-transcode that specific cache node with that new value.
Show
André van Toly added a comment - 2010-06-02 15:42 Note that changes to the configuration are seen as _new_ caches. When you care to re-transcode an existing streamsourcescaches node, you must change its key (field) and re-transcode that specific cache node with that new value.

People

Dates

  • Created:
    2010-04-25 21:07
    Updated:
    2010-06-02 15:42
    Resolved:
    2010-05-31 11:22
Atlassian JIRA (v4.1#519) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for MMBase Foundation. Try JIRA - bug tracking software for your team.