Reconfigurable video coding - Revision history

Animalparty: bold

2019-08-10T19:20:14Z

bold

← Previous revision		Revision as of 19:20, 10 August 2019
Line 1:		Line 1:
	The Reconfigurable Video Coding (RVC) is an [[MPEG]] initiative to provide an innovative framework of video coding development. This framework offers a way to overcome the lack of interoperability between the many video codecs deployed in the market. Indeed, an RVC codec is described using the [[dataflow programming]] paradigm which permits flexibility and reusability. Two standards have been produced by the RVC working group:		The '''Reconfigurable Video Coding''' (RVC) is an [[MPEG]] initiative to provide an innovative framework of video coding development. This framework offers a way to overcome the lack of interoperability between the many video codecs deployed in the market. Indeed, an RVC codec is described using the [[dataflow programming]] paradigm which permits flexibility and reusability. Two standards have been produced by the RVC working group:
	* The codec configuration representation (ISO/IEC 23001-4 or MPEG-B pt. 4) describes the format with which an RVC decoder can be defined as a network of computational blocks, as well as a textual language for the definition of video coding blocks.		* The codec configuration representation (ISO/IEC 23001-4 or MPEG-B pt. 4) describes the format with which an RVC decoder can be defined as a network of computational blocks, as well as a textual language for the definition of video coding blocks.
	* A video tool library (ISO/IEC 23002-4 or MPEG-C pt. 4) that standardizes actors needed to describe existing video coding standards (currently MPEG-4 part 2 and MPEG-4 part 10).		* A video tool library (ISO/IEC 23002-4 or MPEG-C pt. 4) that standardizes actors needed to describe existing video coding standards (currently MPEG-4 part 2 and MPEG-4 part 10).

Edward: link multi-core processor using Find link

2013-12-08T07:37:54Z

link multi-core processor using Find link

← Previous revision		Revision as of 07:37, 8 December 2013
Line 6:		Line 6:
	RVC was motivated by the following observations:		RVC was motivated by the following observations:
	* In the last two decades, many video coding standards ([[MPEG-2]], [[MPEG-4 AVC]], [[VP8]], etc.) have been specified to meet consumers' demands. These new technologies have been using increasingly complex algorithms and many of them share some common parts (a discrete cosine transform for example). Unfortunately, there was at the time no standard way to exploit these similarities.		* In the last two decades, many video coding standards ([[MPEG-2]], [[MPEG-4 AVC]], [[VP8]], etc.) have been specified to meet consumers' demands. These new technologies have been using increasingly complex algorithms and many of them share some common parts (a discrete cosine transform for example). Unfortunately, there was at the time no standard way to exploit these similarities.
	* The specification of a video coding standard was previously provided with a textual document and reference software, without consideration for the effort needed to implement the standard on multi-core ~~processors~~ or hardware platforms.		* The specification of a video coding standard was previously provided with a textual document and reference software, without consideration for the effort needed to implement the standard on [[multi-core processor]]s or hardware platforms.

	==History==		==History==

109.190.107.82: spelling

2013-05-17T08:04:57Z

spelling

← Previous revision		Revision as of 08:04, 17 May 2013
Line 1:		Line 1:
	The Reconfigurable Video Coding (RVC) is an [[MPEG]] initiative to provide an innovative framework of video coding development. This framework offers a way to overcome the lack of interoperability between the many video codecs deployed in the market. Indeed, an RVC codec is described using the [[dataflow programming]] paradigm which permits flexibility and ~~reusibility~~. Two standards have been produced by the RVC working group:		The Reconfigurable Video Coding (RVC) is an [[MPEG]] initiative to provide an innovative framework of video coding development. This framework offers a way to overcome the lack of interoperability between the many video codecs deployed in the market. Indeed, an RVC codec is described using the [[dataflow programming]] paradigm which permits flexibility and reusability. Two standards have been produced by the RVC working group:
	* The codec configuration representation (ISO/IEC 23001-4 or MPEG-B pt. 4) describes the format with which an RVC decoder can be defined as a network of computational blocks, as well as a textual language for the definition of video coding blocks.		* The codec configuration representation (ISO/IEC 23001-4 or MPEG-B pt. 4) describes the format with which an RVC decoder can be defined as a network of computational blocks, as well as a textual language for the definition of video coding blocks.
	* A video tool library (ISO/IEC 23002-4 or MPEG-C pt. 4) that standardizes actors needed to describe existing video coding standards (currently MPEG-4 part 2 and MPEG-4 part 10).		* A video tool library (ISO/IEC 23002-4 or MPEG-C pt. 4) that standardizes actors needed to describe existing video coding standards (currently MPEG-4 part 2 and MPEG-4 part 10).

Dthomsen8: clean up, typos fixed: a innovative → an innovative using AWB

2013-03-25T00:21:16Z

clean up, typos fixed: a innovative → an innovative using AWB

← Previous revision		Revision as of 00:21, 25 March 2013
Line 1:		Line 1:
		⚫	The Reconfigurable Video Coding (RVC) is an [[MPEG]] initiative to provide an innovative framework of video coding development. This framework offers a way to overcome the lack of interoperability between the many video codecs deployed in the market. Indeed, an RVC codec is described using the [[dataflow programming]] paradigm which permits flexibility and reusibility. Two standards have been produced by the RVC working group:
	==Overview==
⚫	The Reconfigurable Video Coding (RVC) is an [[MPEG]] initiative to provide a innovative framework of video coding development. This framework offers a way to overcome the lack of interoperability between the many video codecs deployed in the market. Indeed, an RVC codec is described using the [[dataflow programming]] paradigm which permits flexibility and reusibility. Two standards have been produced by the RVC working group:
	* The codec configuration representation (ISO/IEC 23001-4 or MPEG-B pt. 4) describes the format with which an RVC decoder can be defined as a network of computational blocks, as well as a textual language for the definition of video coding blocks.		* The codec configuration representation (ISO/IEC 23001-4 or MPEG-B pt. 4) describes the format with which an RVC decoder can be defined as a network of computational blocks, as well as a textual language for the definition of video coding blocks.
	* A video tool library (ISO/IEC 23002-4 or MPEG-C pt. 4) that standardizes actors needed to describe existing video coding standards (currently MPEG-4 part 2 and MPEG-4 part 10).		* A video tool library (ISO/IEC 23002-4 or MPEG-C pt. 4) that standardizes actors needed to describe existing video coding standards (currently MPEG-4 part 2 and MPEG-4 part 10).
Line 6:		Line 5:
	==Motivations==		==Motivations==
	RVC was motivated by the following observations:		RVC was motivated by the following observations:
	* In the last two decades, many video coding standards ([[MPEG-2]], [[MPEG-4 AVC]], [[VP8]], etc.) have been specified to meet consumers' demands. These new technologies have been using increasingly complex algorithms and many of them share some common parts (a discrete cosine transform for example). Unfortunately, there was at the time no standard way to exploit these similarities.		* In the last two decades, many video coding standards ([[MPEG-2]], [[MPEG-4 AVC]], [[VP8]], etc.) have been specified to meet consumers' demands. These new technologies have been using increasingly complex algorithms and many of them share some common parts (a discrete cosine transform for example). Unfortunately, there was at the time no standard way to exploit these similarities.
	* The specification of a video coding standard was previously provided with a textual document and reference software, without consideration for the effort needed to implement the standard on multi-core processors or hardware platforms.		* The specification of a video coding standard was previously provided with a textual document and reference software, without consideration for the effort needed to implement the standard on multi-core processors or hardware platforms.

Line 21:		Line 20:
	* ISO Standards [http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=50556 23001-4] and [http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=45434 23002-4]		* ISO Standards [http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=50556 23001-4] and [http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=45434 23002-4]
	* [http://orcc.sf.net Open RVC CAL Compiler]		* [http://orcc.sf.net Open RVC CAL Compiler]

⚫	{{technology-stub}}

	[[Category:Video codecs]]		[[Category:Video codecs]]


		⚫	{{technology-stub}}

ChrisGualtieri: /* Motivations */Typo fixing, typos fixed: etc) → etc.) using AWB

2012-08-10T20:30:14Z

Motivations: Typo fixing, typos fixed: etc) → etc.) using AWB

← Previous revision		Revision as of 20:30, 10 August 2012
Line 6:		Line 6:
	==Motivations==		==Motivations==
	RVC was motivated by the following observations:		RVC was motivated by the following observations:
	* In the last two decades, many video coding standards ([[MPEG-2]], [[MPEG-4 AVC]], [[VP8]], etc) have been specified to meet consumers' demands. These new technologies have been using increasingly complex algorithms and many of them share some common parts (a discrete cosine transform for example). Unfortunately, there was at the time no standard way to exploit these similarities.		* In the last two decades, many video coding standards ([[MPEG-2]], [[MPEG-4 AVC]], [[VP8]], etc.) have been specified to meet consumers' demands. These new technologies have been using increasingly complex algorithms and many of them share some common parts (a discrete cosine transform for example). Unfortunately, there was at the time no standard way to exploit these similarities.
	* The specification of a video coding standard was previously provided with a textual document and reference software, without consideration for the effort needed to implement the standard on multi-core processors or hardware platforms.		* The specification of a video coding standard was previously provided with a textual document and reference software, without consideration for the effort needed to implement the standard on multi-core processors or hardware platforms.

Elldekaa: Remove the deletion proposal: the article was enough improved

2011-09-02T15:35:34Z

Remove the deletion proposal: the article was enough improved

← Previous revision		Revision as of 15:35, 2 September 2011
Line 1:		Line 1:
	{{Proposed deletion/dated
	\|concern = no evidence that it meets the [[WP:NOTE\|notability]] criteria
	\|timestamp = 20110827094430
	}}

	==Overview==		==Overview==
	The Reconfigurable Video Coding (RVC) is an [[MPEG]] initiative to provide a innovative framework of video coding development. This framework offers a way to overcome the lack of interoperability between the many video codecs deployed in the market. Indeed, an RVC codec is described using the [[dataflow programming]] paradigm which permits flexibility and reusibility. Two standards have been produced by the RVC working group:		The Reconfigurable Video Coding (RVC) is an [[MPEG]] initiative to provide a innovative framework of video coding development. This framework offers a way to overcome the lack of interoperability between the many video codecs deployed in the market. Indeed, an RVC codec is described using the [[dataflow programming]] paradigm which permits flexibility and reusibility. Two standards have been produced by the RVC working group:

193.52.94.40: /* Overview */

2011-09-02T15:24:23Z

Overview

← Previous revision		Revision as of 15:24, 2 September 2011
Line 6:		Line 6:
	==Overview==		==Overview==
	The Reconfigurable Video Coding (RVC) is an [[MPEG]] initiative to provide a innovative framework of video coding development. This framework offers a way to overcome the lack of interoperability between the many video codecs deployed in the market. Indeed, an RVC codec is described using the [[dataflow programming]] paradigm which permits flexibility and reusibility. Two standards have been produced by the RVC working group:		The Reconfigurable Video Coding (RVC) is an [[MPEG]] initiative to provide a innovative framework of video coding development. This framework offers a way to overcome the lack of interoperability between the many video codecs deployed in the market. Indeed, an RVC codec is described using the [[dataflow programming]] paradigm which permits flexibility and reusibility. Two standards have been produced by the RVC working group:
	* The codec configuration representation (ISO/IEC 23001-4 or MPEG-B pt. 4) describes the format with which a ~~block~~ ~~diagram~~ can be defined, as well as a textual language ~~that~~ ~~allows~~ ~~dataflow~~ ~~actors~~ to be ~~written~~.		* The codec configuration representation (ISO/IEC 23001-4 or MPEG-B pt. 4) describes the format with which an RVC decoder can be defined as a network of computational blocks, as well as a textual language for the definition of video coding blocks.
	* A video tool library (ISO/IEC 23002-4 or MPEG-C pt. 4) that standardizes actors needed to describe existing video coding standards (currently MPEG-4 part 2 and MPEG-4 part 10).		* A video tool library (ISO/IEC 23002-4 or MPEG-C pt. 4) that standardizes actors needed to describe existing video coding standards (currently MPEG-4 part 2 and MPEG-4 part 10).

193.52.94.40: /* Overview */

2011-09-02T15:22:56Z

Overview

← Previous revision		Revision as of 15:22, 2 September 2011
Line 5:		Line 5:

	==Overview==		==Overview==
	The Reconfigurable Video Coding (RVC) is an [[MPEG]] initiative to provide a innovative framework of video coding development. This framework offers a way to overcome the lack of interoperability between the many video codecs deployed in the market. Indeed, an RVC codec is described using the [[dataflow programming]] paradigm which permits flexibility and reusibility. Two standards ~~was~~ ~~defined~~ to ~~described~~ ~~this~~ ~~framework~~:		The Reconfigurable Video Coding (RVC) is an [[MPEG]] initiative to provide a innovative framework of video coding development. This framework offers a way to overcome the lack of interoperability between the many video codecs deployed in the market. Indeed, an RVC codec is described using the [[dataflow programming]] paradigm which permits flexibility and reusibility. Two standards have been produced by the RVC working group:
	* The codec configuration representation (ISO/IEC 23001-4 or MPEG-B pt. 4).		* The codec configuration representation (ISO/IEC 23001-4 or MPEG-B pt. 4) describes the format with which a block diagram can be defined, as well as a textual language that allows dataflow actors to be written.
	* A video tool library (ISO/IEC 23002-4 or MPEG-C pt. 4).		* A video tool library (ISO/IEC 23002-4 or MPEG-C pt. 4) that standardizes actors needed to describe existing video coding standards (currently MPEG-4 part 2 and MPEG-4 part 10).

	==Motivations==		==Motivations==

193.52.94.40: /* Motivations */

2011-09-02T15:20:41Z

Motivations

← Previous revision		Revision as of 15:20, 2 September 2011
Line 12:		Line 12:
	RVC was motivated by the following observations:		RVC was motivated by the following observations:
	* In the last two decades, many video coding standards ([[MPEG-2]], [[MPEG-4 AVC]], [[VP8]], etc) have been specified to meet consumers' demands. These new technologies have been using increasingly complex algorithms and many of them share some common parts (a discrete cosine transform for example). Unfortunately, there was at the time no standard way to exploit these similarities.		* In the last two decades, many video coding standards ([[MPEG-2]], [[MPEG-4 AVC]], [[VP8]], etc) have been specified to meet consumers' demands. These new technologies have been using increasingly complex algorithms and many of them share some common parts (a discrete cosine transform for example). Unfortunately, there was at the time no standard way to exploit these similarities.
	* The specification of a video coding standard was ~~always~~ provided ~~using~~ textual ~~explanations~~ and reference software, ~~but~~ without ~~regard~~ for the effort needed to implement the standard on multi-core processors or hardware platforms.		* The specification of a video coding standard was previously provided with a textual document and reference software, without consideration for the effort needed to implement the standard on multi-core processors or hardware platforms.

	==History==		==History==

193.52.94.40: /* Motivations */

2011-09-02T15:17:30Z

Motivations

← Previous revision		Revision as of 15:17, 2 September 2011
Line 11:		Line 11:
	==Motivations==		==Motivations==
	RVC was motivated by the following observations:		RVC was motivated by the following observations:
	* In the last two decades, ~~a lot of new~~ video coding standards ([[MPEG-2]], [[MPEG-4 AVC]], [[VP8]], etc) ~~was~~ specified to ~~follow~~ ~~the requirement of the~~ ~~market~~. These new technologies ~~used~~ increasingly complex algorithms and many of them ~~are sharing~~ some common parts (a discrete cosine transform for example). Unfortunately, there is ~~currently~~ no standard way to exploit these similarities.		* In the last two decades, many video coding standards ([[MPEG-2]], [[MPEG-4 AVC]], [[VP8]], etc) have been specified to meet consumers' demands. These new technologies have been using increasingly complex algorithms and many of them share some common parts (a discrete cosine transform for example). Unfortunately, there was at the time no standard way to exploit these similarities.
	* The specification of video coding ~~standards~~ is always provided using ~~some~~ textual explanations and a reference software, but ~~with~~ no ~~consideration of~~ the ~~hard~~ ~~labor~~ to implement it on multi-core or~~/and~~ hardware ~~platform~~.		* The specification of a video coding standard was always provided using textual explanations and reference software, but without regard for the effort needed to implement the standard on multi-core processors or hardware platforms.

	==History==		==History==