Replies: 2 comments 1 reply
-
Hi @Janix4000! If it is an output Kino (i.e. it is rendering audio/video), then I would definitely start as a separate package, this will give you more flexibility to iterate quickly. But please do share it once it is complete. Then once you consider it robust and stable enough, please ping us again. Inputs are a bit different and it is best if they are part of Livebook+Kino themselves. |
Beta Was this translation helpful? Give feedback.
1 reply
-
Just implemented such a thing here: livebook-dev/kino#311 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hey, I’m from Membrane Framework. We wanted to create interactive examples of our media pipelines in a livebook
However, as far as I checked livebook and Kino extension, there is no sufficient way to feed raw video/audio to any Kino element and show it in real-time (some type of video and audio player).
(possible workaround is to use https://hexdocs.pm/kino/Kino.html#animate/3, however
Kino.Image.new
accepts many standard image formats but raw YUV format. Additionally, converting raw frames to pictures would be overkill in the real-time pipeline)Ergo, we decided to create our own Kino element supporting manual streaming (and maybe movies from files and native streams)
Should we contribute this extension (when finished) directly to Kino or create a separate package for it? (edited)
Beta Was this translation helpful? Give feedback.
All reactions