From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mx1.redhat.com (mx1.redhat.com [172.16.48.31]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n7408diO015364 for ; Mon, 3 Aug 2009 20:08:39 -0400 Received: from mail49.e.nsc.no (mail49.e.nsc.no [193.213.115.49]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n7408JdF030886 for ; Mon, 3 Aug 2009 20:08:20 -0400 To: Folkert van Heusden References: <20090717174101.GB15611@vanheusden.com> From: Esben Stien Date: Tue, 04 Aug 2009 03:08:00 +0200 In-Reply-To: <20090717174101.GB15611@vanheusden.com> (Folkert van Heusden's message of "Fri\, 17 Jul 2009 19\:41\:01 +0200") Message-ID: <87skg84c9b.fsf@quasar.esben-stien.name> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: video4linux-list@redhat.com Subject: Re: video4linux loopback device List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: video4linux-list-bounces@redhat.com Errors-To: video4linux-list-bounces@redhat.com List-ID: Folkert van Heusden writes: > Any chance that the video4linux loopback device will be integrated in > the main video4linux distribution and included in the kernel? Why don't we focus on something like JACK[0], but for video, like videojack[1]. This brings all this to userspace and we can pipe video into and out of applications as easily as we're doing with audio with JACK. This seems more like a final solution to me. [0]http://jackaudio.org/ [1]http://www.piksel.no/pwiki/VideoJack [2]http://www.linuxmao.org/tikiwiki/img/wiki_up/patchage.png -- Esben Stien is b0ef@e s a http://www. s t n m irc://irc. b - i . e/%23contact sip:b0ef@ e e jid:b0ef@ n n -- video4linux-list mailing list Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe https://www.redhat.com/mailman/listinfo/video4linux-list