From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Date: Wed, 12 Aug 2009 19:06:57 -0700 From: Roman Shaposhnik In-reply-to: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-id: <9D679F98-941F-454D-8F96-E4A3C0F9E6E1@sun.com> References: Subject: Re: [9fans] audio standards -- too many to choose from Topicbox-Message-UUID: 44d73bca-ead5-11e9-9d60-3106f5b1d025 On Aug 12, 2009, at 4:18 AM, erik quanstrom wrote: >> In fact, perhaps even the page(1) command is falwed. What should've >> happened was a next layer over rio, where /dev/draw/n/data would >> be able to accept any kind of image encoding. > > i think page is a good thing. pushing data > translation to the edges makes programs like > resample much simplier. they can assume plan 9 > images. and you don't end up linking every > program to the same enormous library. Ok, I buy that -- you want a canonical format and you want multiple frontends and backends cooperating using it. But what would such an architecture look like from an FS perspective? Supposed I want resample to operate on movie frames. Thanks, Roman.