Sourcefabric Development Platform

  • Log In Access more options
    • Online Help
    • GreenHopper Help
    • Agile Answers
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What’s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Agile Access more options (Alt+g)
Welcome to Sourcefabric's bug tracker. Not a member? Sign up for an account.
Liquidsoap
  • Liquidsoap
  • LS-396 Find abusive operators types
  • LS-518

source('#a,'b,'c) ?

  • Agile Board
  • More Actions
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Sub-task Sub-task
  • Status: Closed Closed
  • Priority: Important Important
  • Resolution: Fixed
  • Affects Version/s: 1.0
  • Fix Version/s: None
  • Component/s: Liquidsoap
  • Labels:
    None

Description

It may be something that I do not understand. but I think that operators like output.ao should require a source of type
  source('#a+1, 'b, 'c)
i.e. should not have to care about anything concerning video and midi..

I do not think that the current type system can express it but I may be wrong..

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
  • Source
  • Reviews
Hide
Permalink
David Baelde added a comment - 28/Apr/11 6:29 AM
The type system can express this. However, the difficulties caused by variability would apply even for an operator that only looks at the audio channel. This is because changing a content layer in a frame is a global operation for all channel types: if you want to change the video layout you need to change the global layout. So the operator would have to deal with data spread over multiple layers.

This makes me think of something trickier, related to the mismatch between local/precise types and the global/rough layer system. If you take such a source (assuming we can build one, perhaps by muxing?) and drop the video and midi channels, you get a ('#a,0,0) but I don't think that the layers will have been glued back together...

We'll have to discuss this more. I'm not sure how important this is and how we should address it.
Show
David Baelde added a comment - 28/Apr/11 6:29 AM The type system can express this. However, the difficulties caused by variability would apply even for an operator that only looks at the audio channel. This is because changing a content layer in a frame is a global operation for all channel types: if you want to change the video layout you need to change the global layout. So the operator would have to deal with data spread over multiple layers. This makes me think of something trickier, related to the mismatch between local/precise types and the global/rough layer system. If you take such a source (assuming we can build one, perhaps by muxing?) and drop the video and midi channels, you get a ('#a,0,0) but I don't think that the layers will have been glued back together... We'll have to discuss this more. I'm not sure how important this is and how we should address it.
Hide
Permalink
Romain Beauxis added a comment - 28/Apr/11 6:54 AM
Thanks for the comment, I did not realize the internal complexity..

All in all, it seems to me that variable sources will have to get converted to sources with fixed values at some point in any reasonable script..

Should I close this issue?
Show
Romain Beauxis added a comment - 28/Apr/11 6:54 AM Thanks for the comment, I did not realize the internal complexity.. All in all, it seems to me that variable sources will have to get converted to sources with fixed values at some point in any reasonable script.. Should I close this issue?
Hide
Permalink
Samuel Mimram added a comment - 28/Apr/11 8:15 AM
Shouldn't we merge with LS-396 which is a general "we should check types" bug report?
Show
Samuel Mimram added a comment - 28/Apr/11 8:15 AM Shouldn't we merge with LS-396 which is a general "we should check types" bug report?
Hide
Permalink
David Baelde added a comment - 26/Sep/11 4:09 PM
This particular point about output.ao() is not an issue, let's not accumulate sub-tickets.
Show
David Baelde added a comment - 26/Sep/11 4:09 PM This particular point about output.ao() is not an issue, let's not accumulate sub-tickets.

People

  • Assignee:
    Unassigned
    Reporter:
    Romain Beauxis
Vote (0)
Watch (0)

Dates

  • Created:
    28/Apr/11 6:18 AM
    Updated:
    26/Sep/11 4:09 PM
    Resolved:
    26/Sep/11 4:09 PM

Agile

  • View on Board
  • Atlassian JIRA (v5.2.7#850-sha1:b2af0c8)
  • Report a problem
  • Powered by a free Atlassian JIRA community license for Sourcefabric o.p.s.. Try JIRA - bug tracking software for your team.