A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2017; you can also visit <a rel="external noopener" href="https://infoscience.epfl.ch/record/153935/files/S4.3.pdf">the original URL</a>. The file type is <code>application/pdf</code>.
High level design space exploration of RVC codec specifications for multi-core heterogeneous platforms
<span title="">2010</span>
<i title="IEEE">
<a target="_blank" rel="noopener" href="https://fatcat.wiki/container/nq3a3wrr3ja27nres7uhrlmdfi" style="color: black;">2010 Conference on Design and Architectures for Signal and Image Processing (DASIP)</a>
</i>
Preserved Fulltext
Nowadays, the design flow of complex signal processing embedded systems starts with a specification of the application by means of a large and sequential program (usually in C/C++). As we are entering in the multicore era, sequential programs are no longer the most appropriate way to specify algorithms targeted to run on several processing units. The new ISO/MPEG Reconfigurable Video Coding (RVC) standard is proposing a new paradigm for specifying and designing complex signal processing
<span class="external-identifiers">
<a target="_blank" rel="external noopener noreferrer" href="https://doi.org/10.1109/dasip.2010.5706264">doi:10.1109/dasip.2010.5706264</a>
<a target="_blank" rel="external noopener" href="https://dblp.org/rec/conf/dasip/LucarzRM10.html">dblp:conf/dasip/LucarzRM10</a>
<a target="_blank" rel="external noopener" href="https://fatcat.wiki/release/ufblw2ft6rh3flznr3rh2hs4ry">fatcat:ufblw2ft6rh3flznr3rh2hs4ry</a>
</span>
more »
... The RVC standard enables specifying new codecs by assembling blocks, or so called Functional Units (FUs) from a standard Video Tool Library (VTL). Flexibility, reusability, and modularity are the key features of RVC. This new way of specifying algorithms clearly simplifies the task of designing future video coding applications by allowing software and hardware reuse across multiple video coding standards. Specifications are provided in the form of an actor and dataflow-based language called CAL. Although the RVC standard does not imply any specific implementation design flow, it is an appropriate starting point for targeting multiple processing units platforms. This paper describes a new model-driven design flow which considers both algorithm and architecture to map RVC codec specifications onto heterogeneous and multi-core systems.
<a target="_blank" rel="noopener" href="https://web.archive.org/web/20170818065636/https://infoscience.epfl.ch/record/153935/files/S4.3.pdf" title="fulltext PDF download" data-goatcounter-click="serp-fulltext" data-goatcounter-title="serp-fulltext">
<button class="ui simple right pointing dropdown compact black labeled icon button serp-button">
<i class="icon ia-icon"></i>
Web Archive
[PDF]
<div class="menu fulltext-thumbnail">
<img src="https://blobs.fatcat.wiki/thumbnail/pdf/95/61/95614d2c6055c0de54806086db3102f466df3746.180px.jpg" alt="fulltext thumbnail" loading="lazy">
</div>
</button>
</a>
<a target="_blank" rel="external noopener noreferrer" href="https://doi.org/10.1109/dasip.2010.5706264">
<button class="ui left aligned compact blue labeled icon button serp-button">
<i class="external alternate icon"></i>
ieee.com
</button>
</a>