[
http://dev.sourcefabric.org/browse/LS-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16884#action_16884
]
David Baelde commented on LS-526:
---------------------------------
Even for simple and widely used operators, seeking may be very tricky. I don't
think we'll implement it for add, not until we move away from the current
streaming/frame model. However we could perhaps do it for switches, and hence
for mksafe, so I don't close. But for users, the advice is clearly: put your
cue_cut as close as possible to the request source.
> Implement seek for mksafe and others
> ------------------------------------
>
> Key: LS-526
> URL: http://dev.sourcefabric.org/browse/LS-526
> Project: Liquidsoap
> Issue Type: Technical task
> Reporter: Samuel Mimram
>
> From the ML: "I had to remove the mksafe operator first because I was getting
> 2011/05/12 19:31:13 [mksafe:3] Seek not implemented!"
> Is it fixed? We sould really ensure that simple and widely used operators
> such as mksafe can seek.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://dev.sourcefabric.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Savonet-devl mailing list
Savonet-devl@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/savonet-devl
