From gautam noida.hcltech.com Sat Sep 1 10:22:43 2001 From: gautam noida.hcltech.com (Gautam Kumar) Date: Wed Jul 30 14:06:48 2003 Subject: [M4IF Technotes] Queries!!!! Message-ID: <1BD957F48464D5118CD500508BBB212198AC58@exch-01.noida.hcltech.com> Dear Rob, Thanks for clearing the doubts. Kind Regards Gautam -----Original Message----- From: Rob Koenen [mailto:rkoenen@intertrust.com] Sent: Saturday, September 01, 2023 1:35 AM To: 'Gautam Kumar'; technotes@lists.m4if.org Subject: RE: [M4IF Technotes] Queries!!!! Gautam, > 1. i want to download initial draft of streaming video > profile which is in > amendment4. can anyone guide me where is it available? MPEG cannot make it available for download now that it is at Final Draft International Standard Stage. ISO will start selling the FDIS text as of 20 Sept. Check here: http://www.iso.ch/iso/en/CatalogueListPage.CatalogueList?ICS1=35&ICS2=40&ICS 3= and look for 14496-2, then look for "Streaming Video Profiles" > 2.I need the mpeg4 reference code which is supposed to be at > http://isotc.iso.ch/livelink/livelink/fetch/2000/2489/Ittf_Home/ITTF.htm . but it is not functional for last 10 to 15 days. you can go to it thought http://www.cselt.it/mpeg/ them "Hot news" then there is a link "ISO Site" then there is a link for FCD (Final Committee Draft) and all. can anyone suggest alternative source for it. The website works fine. Try the link that is on the M4IF page, http://isotc.iso.ch/livelink/livelink/fetch/2000/2489/Ittf_Home/PubliclyAvai lableStandards.htm/ (make sure not to break it in pieces) > 3. For the transmission of the mpeg4 stream in network besides encoder and > decoder what else we need to have??? > where this DMIF and RTP/RTSP come in picture??? > does DMIF sits at the top of RTP/RTSP?? Please be elaborative for this > perticular query. DMIF sits between the application and the transport. It abstracts the transport layer from the application, so that the app only needs to have one interface to the tranport layer. THen through DMIF instances, the app can talk to e.g. RTP, local disk, broadcast transparently. See http://www.m4if.org/public/MPEG-4Overview.zip Best, Rob From fakl gmx.de Tue Sep 4 20:43:44 2001 From: fakl gmx.de (Falk Dobermann) Date: Wed Jul 30 14:06:48 2003 Subject: [M4IF Technotes] Objects Message-ID: <005901c13569$24e37850$9faa66c0@rostock.igd.fhg.de> Hi All, I have a question about mpeg-4 systems. Is it possible to use one ObjectID in more than one node, e.g. if I want to use one backchannel object for multiple ServerCommand nodes? Or must this be a 1:1 relationship. I couldn't find it in the standard. Thanks four your help Falk Dobermann -------------- next part -------------- An HTML attachment was scrubbed... URL: /pipermail/mp4-tech/attachments/20010904/04401eb4/attachment.html From lkerogues gerpi.fr Mon Sep 10 15:37:57 2001 From: lkerogues gerpi.fr (Lionel KEROGUES) Date: Wed Jul 30 14:06:48 2003 Subject: [M4IF Technotes] MPEG4Decoder.dll Message-ID: <200109101237.OAA01561@venus.gerpi.fr> Hi all, Has someone succeeded in running the MPEG4Decoder.dll of the player3D of the reference software ? Thanks in advance for comments. Lionel KEROGUES Consultant --------------- GERPI S.A. "Alma City" 3, rue du Bosphore 35 074 - Rennes Cedex (FRANCE) Standard T?l : +33 (0) 2 99 51 17 18 Fax : +33 (0) 2 99 32 19 80 Email : mailto:lkerogues@gerpi.fr Web : http://www.gerpi.fr ----------------------------------------------------- From manish.singhal ittiam.com Tue Sep 11 11:21:16 2001 From: manish.singhal ittiam.com (Manish Singhal) Date: Wed Jul 30 14:06:48 2003 Subject: [M4IF Technotes] CIF raw sequences Message-ID: <45A1F95BB9D7D84FAB0A1EB4D67EEF9611341E@IS01EX01.ittiam.com> Hello there I am looking for some CIF size raw sequences especially foreman, silent and akiyo. Can any kind soul tell me from where I can get these. I do not mind buying them as well Rgds Manish Singhal Manager, Video and Imaging Ittiam Systems Bangalore, India. From gchandra tataelxsi.co.in Tue Sep 11 11:41:01 2001 From: gchandra tataelxsi.co.in (G Chandra Sekhar Reddy) Date: Wed Jul 30 14:06:48 2003 Subject: [M4IF Technotes] CIF raw sequences References: <45A1F95BB9D7D84FAB0A1EB4D67EEF9611341E@IS01EX01.ittiam.com> Message-ID: <000f01c13a80$27e7c490$cc14010a@tataelxsi.co.in> Hi, You can find them at these places: http://kbs.cs.tu-berlin.de/~stewe/vceg/sequences.htm http://standard.pictel.com/ftp/video-site/sequences Chandra Sekhar Reddy G. TATA ELXSI LTD., BANGALORE, INDIA. ----- Original Message ----- From: Manish Singhal To: Sent: Tuesday, September 11, 2023 10:21 AM Subject: [M4IF Technotes] CIF raw sequences > > Hello there > > I am looking for some CIF size raw sequences especially foreman, silent > and akiyo. > > Can any kind soul tell me from where I can get these. I do not mind > buying them as well > > Rgds > Manish Singhal > Manager, Video and Imaging > Ittiam Systems > Bangalore, India. > > _______________________________________________ > Technotes mailing list > Technotes@lists.m4if.org > http://lists.m4if.org/mailman/listinfo/technotes From manish.singhal ittiam.com Tue Sep 11 11:41:17 2001 From: manish.singhal ittiam.com (Manish Singhal) Date: Wed Jul 30 14:06:49 2003 Subject: [M4IF Technotes] CIF raw sequences Message-ID: <45A1F95BB9D7D84FAB0A1EB4D67EEF9611341F@IS01EX01.ittiam.com> Yes I tried those two sites. The first one does not have foreman, silent or akiyo in CIF and I am not able to access the second site. RGds Manish > -----Original Message----- > From: G Chandra Sekhar Reddy [mailto:gchandra@tataelxsi.co.in] > Sent: Tuesday, September 11, 2023 10:41 AM > To: Manish Singhal; technotes@lists.m4if.org > Subject: Re: [M4IF Technotes] CIF raw sequences > > > Hi, > > You can find them at these places: > > http://kbs.cs.tu-berlin.de/~stewe/vceg/sequences.htm > http://standard.pictel.com/ftp/video-site/sequences > > Chandra Sekhar Reddy G. > TATA ELXSI LTD., > BANGALORE, INDIA. > > > > ----- Original Message ----- > From: Manish Singhal > To: > Sent: Tuesday, September 11, 2023 10:21 AM > Subject: [M4IF Technotes] CIF raw sequences > > > > > > Hello there > > > > I am looking for some CIF size raw sequences especially > foreman, silent > > and akiyo. > > > > Can any kind soul tell me from where I can get these. I do not mind > > buying them as well > > > > Rgds > > Manish Singhal > > Manager, Video and Imaging > > Ittiam Systems > > Bangalore, India. > > > > _______________________________________________ > > Technotes mailing list > > Technotes@lists.m4if.org > > http://lists.m4if.org/mailman/listinfo/technotes > > From sundar tataelxsi.co.in Tue Sep 11 12:18:48 2001 From: sundar tataelxsi.co.in (T Sundar Murthy) Date: Wed Jul 30 14:06:49 2003 Subject: [M4IF Technotes] CIF raw sequences References: <45A1F95BB9D7D84FAB0A1EB4D67EEF9611341F@IS01EX01.ittiam.com> Message-ID: <000c01c13a85$6e59e110$0d14010a@tataelxsi.co.in> You can try someother sequences from the following site: http://ftp.crc.ca/test/pub/crc/vqeg/TestSequences/ sundar ----- Original Message ----- From: "Manish Singhal" To: "G Chandra Sekhar Reddy" ; Sent: Tuesday, September 11, 2023 10:41 AM Subject: RE: [M4IF Technotes] CIF raw sequences > > Yes I tried those two sites. > > The first one does not have foreman, silent or akiyo in CIF > and I am not able to access the second site. > > RGds > Manish > > > -----Original Message----- > > From: G Chandra Sekhar Reddy [mailto:gchandra@tataelxsi.co.in] > > Sent: Tuesday, September 11, 2023 10:41 AM > > To: Manish Singhal; technotes@lists.m4if.org > > Subject: Re: [M4IF Technotes] CIF raw sequences > > > > > > Hi, > > > > You can find them at these places: > > > > http://kbs.cs.tu-berlin.de/~stewe/vceg/sequences.htm > > http://standard.pictel.com/ftp/video-site/sequences > > > > Chandra Sekhar Reddy G. > > TATA ELXSI LTD., > > BANGALORE, INDIA. > > > > > > > > ----- Original Message ----- > > From: Manish Singhal > > To: > > Sent: Tuesday, September 11, 2023 10:21 AM > > Subject: [M4IF Technotes] CIF raw sequences > > > > > > > > > > Hello there > > > > > > I am looking for some CIF size raw sequences especially > > foreman, silent > > > and akiyo. > > > > > > Can any kind soul tell me from where I can get these. I do not mind > > > buying them as well > > > > > > Rgds > > > Manish Singhal > > > Manager, Video and Imaging > > > Ittiam Systems > > > Bangalore, India. > > > > > > _______________________________________________ > > > Technotes mailing list > > > Technotes@lists.m4if.org > > > http://lists.m4if.org/mailman/listinfo/technotes > > > > > _______________________________________________ > Technotes mailing list > Technotes@lists.m4if.org > http://lists.m4if.org/mailman/listinfo/technotes > From vivek_iitg yahoo.com Tue Sep 11 10:51:28 2001 From: vivek_iitg yahoo.com (=?iso-8859-1?q?Vivek=20Singhal?=) Date: Wed Jul 30 14:06:49 2003 Subject: [M4IF Technotes] MPEG-4 and VIdeo Segmentation.... Message-ID: <20010911085128.32094.qmail@web13302.mail.yahoo.com> hi everybody!!! I wanted some information on Video Segmentation and it's application in MPEG-4. I am looking forward to do my B.Tech Project on the same. thankx Vivek Singhal B.Tech 4th Year Electronics and Comm. Engg. IIT Guwahati. ____________________________________________________________ Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie From sudhakar cradle.com Thu Sep 13 16:37:08 2001 From: sudhakar cradle.com (Sudhakar Rao Kimidi) Date: Wed Jul 30 14:06:49 2003 Subject: [M4IF Technotes] hi Message-ID: <3BA0854B.81649880@cradle.com> Dear all, Can somebody help me with the answers for the following. 1. Which method of Quantization is used in MPEG-4 video simple profile? Are both methods of Quantizations used in MPEG-4 Video simple profile? 2. Is fixed interval synchronization supported in simple profile? Is it compulsory to use the method? Is there any mentioning about it in syntax?(This method requires that VOP start codes and resynchronization markers appear only at legal fixed interval locations in the bitstream) Thanks, Sudhakar K. From gmar cvs.agilent.com Wed Sep 12 16:07:46 2001 From: gmar cvs.agilent.com (Eugene Mar) Date: Wed Jul 30 14:06:49 2003 Subject: [M4IF Technotes] Question on inverse Quantization Message-ID: <3B9FDCB2.20C0D922@cvs.agilent.com> Hello, I have a question concerning an apparent discrepency between the ISO/IEC 14496-2 Standards Document, the ISO/IEC JTC1/SC29/WG11 N3908 VM Document, and the reference software from MoMuSys and Microsoft. On section 7.4.4.1.2 of the ISO/IEC 14496-2 Standards Document, the equation for F''[v][u] is shown with a divisor of 16 if QF[v][u] != 0. On section 7.4.4.6 of the ISO/IEC 14496-2 Standards Document, the sample c-code shows F''[v][u] with a divisor of 32. On section 3.4.5.4.1 of the N3908 VM Document, the equation for F''[v][u] is shown to be divided by 32. On section 3.4.5.7 of the N3908 VM Document, the sample c-code shows F''[v][u] with a divisor of 32. Both reference c-code from MoMySys and Microsoft shows F''[v][u] with a divisor of 16. On MoMuSys the code comes from vm_common\src\text_quant.c. On Microsoft the code comes from sys\encoder\blkenc.cpp. My question is, is the divisor for F''[v][u] 16 or 32? Sincerely, Gene Mar From Jani.Huoponen hantro.com Thu Sep 13 19:55:17 2001 From: Jani.Huoponen hantro.com (Jani Huoponen) Date: Wed Jul 30 14:06:49 2003 Subject: [M4IF Technotes] hi Message-ID: Dear Sudhakar, > Dear all, > > Can somebody help me with the answers for the following. > > 1. Which method of Quantization is used in MPEG-4 video > simple profile? Type 2. > Are both methods of Quantizations used in MPEG-4 Video simple profile? No. Type 1 (quantization matrices) is not used in Simple profile. > 2. Is fixed interval synchronization supported in simple > profile? Is it > compulsory to use the method? Is there any mentioning about it in > syntax?(This method requires that VOP start codes and > resynchronization > markers appear only at legal fixed interval locations in the > bitstream) If you mean that should encoded VOPs have a fixed time interval between them then the answer is yes. Simple profile supports this. See section 6.3.3. in the 14496-2 standard, the field called "fixed_vop_rate" explains how this works. It is not a compulsory method, i.e., VOPs can have variable time intervals between them. BR, Jani ------------------------------------------------------------ Jani Huoponen Engineering Manager, System Design Hantro Products Oy Nahkatehtaankatu 2, 90100 Oulu, Finland +358-40-5272676 ------------------------------------------------------------ From Jani.Huoponen hantro.com Thu Sep 13 20:05:41 2001 From: Jani.Huoponen hantro.com (Jani Huoponen) Date: Wed Jul 30 14:06:49 2003 Subject: [M4IF Technotes] Question on inverse Quantization Message-ID: Dear Gene Mar, Divisor is 16. The correction can be found from N336, Technical Correigendum 2. It is also updated to N4350, the 2001 edition of 14496-2 Visual standard. BR, Jani > -----Original Message----- > From: Eugene Mar [mailto:gmar@cvs.agilent.com] > Sent: 13. syyskuuta 2001 1:08 > To: technotes@lists.m4if.org > Subject: [M4IF Technotes] Question on inverse Quantization > > > Hello, > > I have a question concerning an apparent discrepency between > the ISO/IEC > 14496-2 Standards Document, the ISO/IEC JTC1/SC29/WG11 N3908 VM > Document, and the reference software from MoMuSys and Microsoft. > > On section 7.4.4.1.2 of the ISO/IEC 14496-2 Standards Document, the > equation for F''[v][u] is shown with a divisor of 16 if > QF[v][u] != 0. > > On section 7.4.4.6 of the ISO/IEC 14496-2 Standards Document, > the sample > c-code shows F''[v][u] with a divisor of 32. > > On section 3.4.5.4.1 of the N3908 VM Document, the equation for > F''[v][u] is shown to be divided by 32. > > On section 3.4.5.7 of the N3908 VM Document, the sample c-code shows > F''[v][u] with a divisor of 32. > > Both reference c-code from MoMySys and Microsoft shows > F''[v][u] with a > divisor of 16. On MoMuSys the code comes from > vm_common\src\text_quant.c. On Microsoft the code comes from > sys\encoder\blkenc.cpp. > > My question is, is the divisor for F''[v][u] 16 or 32? > > > Sincerely, > > Gene Mar > _______________________________________________ > Technotes mailing list > Technotes@lists.m4if.org > http://lists.m4if.org/mailman/listinfo/technotes > From yossi neomagic.co.il Thu Sep 13 21:01:23 2001 From: yossi neomagic.co.il (Yossi) Date: Wed Jul 30 14:06:49 2003 Subject: [M4IF Technotes] Simple Profile Quantisation In-Reply-To: <200109131605.f8DG5TJ09633@mx3.magma.ca> Message-ID: <006c01c13c7e$1af4c800$64f95ac2@asp.co.il> ********************************************************* Trend InterScan has scanned this mail for viruses, vandals and suspicious attachments and has found it to be CLEAN. ********************************************************* -------------- next part -------------- Hello Sudhakar, As to your first question, Simple Profile allows only the Second method for quantisation (quant_type == 0). See Table 9-1 "Tools for Version 1 Visual Object Types." Regards, Yossi Date: Thu, 13 Sep 2023 15:37:08 +0530 From: Sudhakar Rao Kimidi Organization: cradle To: "'technotes@lists.m4if.org'" Subject: [M4IF Technotes] hi Dear all, Can somebody help me with the answers for the following. 1. Which method of Quantization is used in MPEG-4 video simple profile? Are both methods of Quantizations used in MPEG-4 Video simple profile? 2. Is fixed interval synchronization supported in simple profile? Is it compulsory to use the method? Is there any mentioning about it in syntax?(This method requires that VOP start codes and resynchronization markers appear only at legal fixed interval locations in the bitstream) Thanks, Sudhakar K. --__--__-- Message: 2 Date: Wed, 12 Sep 2023 15:07:46 -0700 From: Eugene Mar Organization: Agilent Technologies To: technotes@lists.m4if.org Subject: [M4IF Technotes] Question on inverse Quantization Hello, I have a question concerning an apparent discrepency between the ISO/IEC 14496-2 Standards Document, the ISO/IEC JTC1/SC29/WG11 N3908 VM Document, and the reference software from MoMuSys and Microsoft. On section 7.4.4.1.2 of the ISO/IEC 14496-2 Standards Document, the equation for F''[v][u] is shown with a divisor of 16 if QF[v][u] != 0. On section 7.4.4.6 of the ISO/IEC 14496-2 Standards Document, the sample c-code shows F''[v][u] with a divisor of 32. On section 3.4.5.4.1 of the N3908 VM Document, the equation for F''[v][u] is shown to be divided by 32. On section 3.4.5.7 of the N3908 VM Document, the sample c-code shows F''[v][u] with a divisor of 32. Both reference c-code from MoMySys and Microsoft shows F''[v][u] with a divisor of 16. On MoMuSys the code comes from vm_common\src\text_quant.c. On Microsoft the code comes from sys\encoder\blkenc.cpp. My question is, is the divisor for F''[v][u] 16 or 32? Sincerely, Gene Mar --__--__-- _______________________________________________ Technotes mailing list Technotes@lists.m4if.org http://lists.m4if.org/mailman/listinfo/technotes End of Technotes Digest From gmar cvs.agilent.com Thu Sep 13 17:04:16 2001 From: gmar cvs.agilent.com (Eugene Mar) Date: Wed Jul 30 14:06:49 2003 Subject: [M4IF Technotes] Where is error_resilient_disable_flag? Message-ID: <3BA13B70.AD4C336F@cvs.agilent.com> Hello, In ISO/IEC JTC1/SC29/WG11 N3908 VM Document, section 3.3.2.7, reference is made to an "error_resilient_disable_flag". Where is this set? I could not find further references to it in neither the VM Document nor the 14496-2 Standards Document. - Gene Mar From ramki emuzed.com Fri Sep 14 11:22:03 2001 From: ramki emuzed.com (Ramkishor Korada) Date: Wed Jul 30 14:06:49 2003 Subject: [M4IF Technotes] Where is error_resilient_disable_flag? References: <3BA13B70.AD4C336F@cvs.agilent.com> Message-ID: <012101c13cd9$024c9e30$0d0aa8c0@blr.emuzed.com> Hi, It looks like a mistake in the VM. It is there even in older version of VM(8.0, 13.0, 13.3, 16.0 etc) also. Standard does not propose two different ways of motion vector prediction. Otherwise, one can find error_resilience_disable_flag in control file. Control file is the parameter file for Momusys decoder/encoder. In the control file, error_resilience_disable_flag can be either enabled or disabled. Disabling this flag means that data partitioning and RVLC are enabled. regards, ramkishor Architect - Video Digital Media Technology Division Emuzed Bangalore Division IndiraNagar,Bangalore www.emuzed.com ----- Original Message ----- From: "Eugene Mar" To: Sent: Friday, September 14, 2023 4:34 AM Subject: [M4IF Technotes] Where is error_resilient_disable_flag? > Hello, > > In ISO/IEC JTC1/SC29/WG11 N3908 VM Document, section 3.3.2.7, reference > is made to an > "error_resilient_disable_flag". Where is this set? I could not find > further references > to it in neither the VM Document nor the 14496-2 Standards Document. > > - Gene Mar > _______________________________________________ > Technotes mailing list > Technotes@lists.m4if.org > http://lists.m4if.org/mailman/listinfo/technotes > > From gchandra tataelxsi.co.in Fri Sep 14 13:00:27 2001 From: gchandra tataelxsi.co.in (G Chandra Sekhar Reddy) Date: Wed Jul 30 14:06:49 2003 Subject: [M4IF Technotes] hi References: Message-ID: <00bb01c13ce6$beb45b00$cc14010a@tataelxsi.co.in> Dear All, > > 2. Is fixed interval synchronization supported in simple > > profile? Is it > > compulsory to use the method? Is there any mentioning about it in > > syntax?(This method requires that VOP start codes and > > resynchronization > > markers appear only at legal fixed interval locations in the > > bitstream) As I understand your question, you are talking about VOP sizes (size in number of bits) and VideoPacket sizes (size in number of bits) being constant. The Levels restrict maximum number of bits per VideoPacket, making these synchronization points appear within some fixed interval (interval in bits, in bitstream). This is only restriction on the maximum size. The actual sizes (thereby synchronization intervals) can be less than this maximum size. If you want fixed size (thereby fixed synchronization intervals), you can use stuffing. About the legal interval you are taking about, I think only restriction is that they shall be at BYTE-Boundaries. Does the standard restrict VOP size in bits to some maximum value in any Profile / Level? Chandra ********************************************************************** Chandra Sekhar Reddy G., TATA ELXSI Ltd., WhiteField Road, Hoody, BANGALORE, INDIA - 560048. TEL: +91-80-8410148, 8411811, 8411812 (Ext:254), FAX: +91-80-8410152, 8411813. EMAIL: gchandra@tataelxsi.co.in WEB: www.tataelxsi.com ********************************************************************** ----- Original Message ----- From: Jani Huoponen To: Sudhakar Rao Kimidi ; Sent: Thursday, September 13, 2023 9:25 PM Subject: RE: [M4IF Technotes] hi > Dear Sudhakar, > > > Dear all, > > > > Can somebody help me with the answers for the following. > > > > 1. Which method of Quantization is used in MPEG-4 video > > simple profile? > > Type 2. > > > Are both methods of Quantizations used in MPEG-4 Video simple profile? > > No. Type 1 (quantization matrices) is not used in Simple profile. > > > 2. Is fixed interval synchronization supported in simple > > profile? Is it > > compulsory to use the method? Is there any mentioning about it in > > syntax?(This method requires that VOP start codes and > > resynchronization > > markers appear only at legal fixed interval locations in the > > bitstream) > > If you mean that should encoded VOPs have a fixed time interval between them > then the answer is yes. Simple profile supports this. See section 6.3.3. in > the 14496-2 standard, the field called "fixed_vop_rate" explains how this > works. It is not a compulsory method, i.e., VOPs can have variable time > intervals between them. > > BR, Jani > > ------------------------------------------------------------ > Jani Huoponen > Engineering Manager, System Design > Hantro Products Oy > Nahkatehtaankatu 2, 90100 Oulu, Finland > +358-40-5272676 > ------------------------------------------------------------ > > _______________________________________________ > Technotes mailing list > Technotes@lists.m4if.org > http://lists.m4if.org/mailman/listinfo/technotes From garysull microsoft.com Fri Sep 14 01:21:30 2001 From: garysull microsoft.com (Gary Sullivan) Date: Wed Jul 30 14:06:49 2003 Subject: [M4IF Technotes] hi Message-ID: <0170DDAD0BADFA4CBEC3B55A0748DCCC040C1BD7@red-msg-02.redmond.corp.microsoft.com> Reply interspersed (a response from memory -- I have not double-checked the text) +> -----Original Message----- +> From: Sudhakar Rao Kimidi [mailto:sudhakar@cradle.com] +> Sent: Thursday, September 13, 2023 3:07 AM +> To: 'technotes@lists.m4if.org' +> Subject: [M4IF Technotes] hi +> +> +> Dear all, +> +> Can somebody help me with the answers for the following. +> +> 1. Which method of Quantization is used in MPEG-4 video +> simple profile? +> Are both methods of Quantizations used in MPEG-4 Video +> simple profile? I believe the Simple profile only includes H.263-style quantization. +> 2. Is fixed interval synchronization supported in simple +> profile? Is it +> compulsory to use the method? Is there any mentioning about it in +> syntax?(This method requires that VOP start codes and +> resynchronization +> markers appear only at legal fixed interval locations in the +> bitstream) I believe that is an encoding-only issue. It is not a normative part of the standard. Also, I believe that it is not really possible to achieve precisely fixed spacing of resync markers. +> +> Thanks, +> Sudhakar K. +> +> +> +> _______________________________________________ +> Technotes mailing list +> Technotes@lists.m4if.org +> http://lists.m4if.org/mailman/listinfo/technotes +> From garysull microsoft.com Fri Sep 14 01:21:34 2001 From: garysull microsoft.com (Gary Sullivan) Date: Wed Jul 30 14:06:49 2003 Subject: [M4IF Technotes] Where is error_resilient_disable_flag? Message-ID: <0170DDAD0BADFA4CBEC3B55A0748DCCC040C1BDD@red-msg-02.redmond.corp.microsoft.com> I found one isolated mention of that flag in 7.5.4.14 of the MPEG-4 Visual spec. However, that flag is not defined anywhere. I suspect it is referring to something that was later changed to data_partitioned or resync_marker_disable. We will add error_resilient_disable to the list of problems in MPEG-4 Visual that we are tracking for correction. Best Regards, -Gary Sullivan +> -----Original Message----- +> From: Eugene Mar [mailto:gmar@cvs.agilent.com] +> Sent: Thursday, September 13, 2023 4:04 PM +> To: technotes@lists.m4if.org +> Subject: [M4IF Technotes] Where is error_resilient_disable_flag? +> +> +> Hello, +> +> In ISO/IEC JTC1/SC29/WG11 N3908 VM Document, section +> 3.3.2.7, reference +> is made to an +> "error_resilient_disable_flag". Where is this set? I could not find +> further references +> to it in neither the VM Document nor the 14496-2 Standards Document. +> +> - Gene Mar +> _______________________________________________ +> Technotes mailing list +> Technotes@lists.m4if.org +> http://lists.m4if.org/mailman/listinfo/technotes +> From Klaus.Diepold dynapel.de Fri Sep 14 13:39:21 2001 From: Klaus.Diepold dynapel.de (Klaus Diepold) Date: Wed Jul 30 14:06:49 2003 Subject: [M4IF Technotes] Where is error_resilient_disable_flag? In-Reply-To: <0170DDAD0BADFA4CBEC3B55A0748DCCC040C1BDD@red-msg-02.redmond.corp.microsoft.com> Message-ID: Gary, friends and collegues, concerning the reported problems found in either the Visual specification or the rference software I would like to make you aware of document w4349.doc from the Sydney meeting that collects a number of issues already found. I think we should continue to collect, investigate and confirm reported problems to update the document in order to be able to issue corrigenda in the future. Thanks Klaus +-----Original Message----- +From: technotes-admin@lists.m4if.org +[mailto:technotes-admin@lists.m4if.org]On Behalf Of Gary Sullivan +Sent: Friday, September 14, 2023 9:22 AM +To: Eugene Mar; technotes@lists.m4if.org +Cc: Klaus Diepold (Dynapel +Subject: RE: [M4IF Technotes] Where is error_resilient_disable_flag? + + + +I found one isolated mention of that flag in 7.5.4.14 of +the MPEG-4 Visual spec. However, that flag is not defined +anywhere. I suspect it is referring to something that +was later changed to data_partitioned or resync_marker_disable. + +We will add error_resilient_disable to the list of problems +in MPEG-4 Visual that we are tracking for correction. + +Best Regards, + +-Gary Sullivan + ++> -----Original Message----- ++> From: Eugene Mar [mailto:gmar@cvs.agilent.com] ++> Sent: Thursday, September 13, 2023 4:04 PM ++> To: technotes@lists.m4if.org ++> Subject: [M4IF Technotes] Where is error_resilient_disable_flag? ++> ++> ++> Hello, ++> ++> In ISO/IEC JTC1/SC29/WG11 N3908 VM Document, section ++> 3.3.2.7, reference ++> is made to an ++> "error_resilient_disable_flag". Where is this set? I could not find ++> further references ++> to it in neither the VM Document nor the 14496-2 Standards Document. ++> ++> - Gene Mar ++> _______________________________________________ ++> Technotes mailing list ++> Technotes@lists.m4if.org ++> http://lists.m4if.org/mailman/listinfo/technotes ++> +_______________________________________________ +Technotes mailing list +Technotes@lists.m4if.org +http://lists.m4if.org/mailman/listinfo/technotes + + From garysull microsoft.com Fri Sep 14 08:10:36 2001 From: garysull microsoft.com (Gary Sullivan) Date: Wed Jul 30 14:06:50 2003 Subject: [M4IF Technotes] hi Message-ID: <0170DDAD0BADFA4CBEC3B55A0748DCCC040C1BE3@red-msg-02.redmond.corp.microsoft.com> Reply interspersed: +> -----Original Message----- +> From: G Chandra Sekhar Reddy [mailto:gchandra@tataelxsi.co.in] +> Sent: Thursday, September 13, 2023 11:30 PM +> To: Jani Huoponen; Sudhakar Rao Kimidi; technotes@lists.m4if.org +> Subject: Re: [M4IF Technotes] hi +> +> [snip] +> The Levels restrict maximum number of bits per VideoPacket, +> making these +> synchronization points appear within some fixed interval +> (interval in bits, +> in bitstream). Are you sure about that statement? I don't think it's true. Can you point to where such a restriction can be found? +> This is only restriction on the maximum size. The actual +> sizes (thereby +> synchronization intervals) can be less than this maximum size. +> If you want fixed size (thereby fixed synchronization +> intervals), you can +> use stuffing. I think you're right. I guess some combination of MCBPC stuffing and bit stuffing can enable the encoder to hit any desired reasonably-large packet size. +> About the legal interval you are taking about, I think only +> restriction is +> that they shall be at BYTE-Boundaries. They also must start at macroblock boundaries. Each packet must contain the bits to represent an integer number of macroblocks. +> +> Does the standard restrict VOP size in bits to some maximum +> value in any +> Profile / Level? Not that I'm aware of. +> +> Chandra +> ************************************************************* +> ********* +> Chandra Sekhar Reddy G., +> TATA ELXSI Ltd., +> WhiteField Road, Hoody, +> BANGALORE, INDIA - 560048. +> TEL: +91-80-8410148, 8411811, 8411812 (Ext:254), +> FAX: +91-80-8410152, 8411813. +> EMAIL: gchandra@tataelxsi.co.in +> WEB: www.tataelxsi.com +> ************************************************************* +> ********* +> +> ----- Original Message ----- +> From: Jani Huoponen +> To: Sudhakar Rao Kimidi ; +> +> Sent: Thursday, September 13, 2023 9:25 PM +> Subject: RE: [M4IF Technotes] hi +> +> +> > Dear Sudhakar, +> > +> > > Dear all, +> > > +> > > Can somebody help me with the answers for the following. +> > > +> > > 1. Which method of Quantization is used in MPEG-4 video +> > > simple profile? +> > +> > Type 2. +> > +> > > Are both methods of Quantizations used in MPEG-4 Video +> simple profile? +> > +> > No. Type 1 (quantization matrices) is not used in Simple profile. +> > +> > > 2. Is fixed interval synchronization supported in simple +> > > profile? Is it +> > > compulsory to use the method? Is there any mentioning about it in +> > > syntax?(This method requires that VOP start codes and +> > > resynchronization +> > > markers appear only at legal fixed interval locations in the +> > > bitstream) +> > +> > If you mean that should encoded VOPs have a fixed time +> interval between +> them +> > then the answer is yes. Simple profile supports this. See +> section 6.3.3. +> in +> > the 14496-2 standard, the field called "fixed_vop_rate" +> explains how this +> > works. It is not a compulsory method, i.e., VOPs can have +> variable time +> > intervals between them. +> > +> > BR, Jani +> > +> > ------------------------------------------------------------ +> > Jani Huoponen +> > Engineering Manager, System Design +> > Hantro Products Oy +> > Nahkatehtaankatu 2, 90100 Oulu, Finland +> > +358-40-5272676 +> > ------------------------------------------------------------ +> > +> > _______________________________________________ +> > Technotes mailing list +> > Technotes@lists.m4if.org +> > http://lists.m4if.org/mailman/listinfo/technotes +> +> _______________________________________________ +> Technotes mailing list +> Technotes@lists.m4if.org +> http://lists.m4if.org/mailman/listinfo/technotes +> From gchandra tataelxsi.co.in Fri Sep 14 21:04:14 2001 From: gchandra tataelxsi.co.in (G Chandra Sekhar Reddy) Date: Wed Jul 30 14:06:50 2003 Subject: [M4IF Technotes] hi References: <0170DDAD0BADFA4CBEC3B55A0748DCCC040C1BE3@red-msg-02.redmond.corp.microsoft.com> Message-ID: <00ac01c13d2a$53d567e0$cc14010a@tataelxsi.co.in> "Max. video packet length" in the video standard, is it not? please let me know, if this restriction has been removed from the standard. > +> The Levels restrict maximum number of bits per VideoPacket, > +> making these > +> synchronization points appear within some fixed interval > +> (interval in bits, > +> in bitstream). > > > Are you sure about that statement? I don't think it's true. > Can you point to where such a restriction can be found? Chandra From ramki emuzed.com Fri Sep 14 21:06:03 2001 From: ramki emuzed.com (Ramkishor Korada) Date: Wed Jul 30 14:06:50 2003 Subject: [M4IF Technotes] hi References: <0170DDAD0BADFA4CBEC3B55A0748DCCC040C1BE3@red-msg-02.redmond.corp.microsoft.com> <00ac01c13d2a$53d567e0$cc14010a@tataelxsi.co.in> Message-ID: <036501c13d2a$9a4e5470$0d0aa8c0@blr.emuzed.com> Hi, Max. video packet length based on level applies only and when data partitioning is enabled. Refer to Annex N (normative ) section on visual profiles and levels. regards, ramkishor Architect - Video Multimedia Technology Divn, Emuzed Bangalore IndiraNagar,Bangalore www.emuzed.com ----- Original Message ----- From: "G Chandra Sekhar Reddy" To: "Gary Sullivan" ; "Jani Huoponen" ; "Sudhakar Rao Kimidi" ; Sent: Friday, September 14, 2023 8:04 PM Subject: Re: [M4IF Technotes] hi > "Max. video packet length" in the video standard, is it not? > please let me know, if this restriction has been removed from the standard. > > > > +> The Levels restrict maximum number of bits per VideoPacket, > > +> making these > > +> synchronization points appear within some fixed interval > > +> (interval in bits, > > +> in bitstream). > > > > > > Are you sure about that statement? I don't think it's true. > > Can you point to where such a restriction can be found? > > > Chandra > > > _______________________________________________ > Technotes mailing list > Technotes@lists.m4if.org > http://lists.m4if.org/mailman/listinfo/technotes > > From sudhakar cradle.com Fri Sep 14 21:24:58 2001 From: sudhakar cradle.com (Sudhakar Rao Kimidi) Date: Wed Jul 30 14:06:50 2003 Subject: [M4IF Technotes] hi References: <0170DDAD0BADFA4CBEC3B55A0748DCCC040C1BE3@red-msg-02.redmond.corp.microsoft.com> Message-ID: <3BA21A41.104D6406@cradle.com> Hi all, With respect to discussions below about fixed interval synchronization .... Gary,... you can find the maximum video packet size specified on the last page on either of versions the satnadards ISO 14496-1 or 14496-2. Now I have a doubt regarding the following line: If the number of bits contained in the current video packet exceeds a predetermined threshold, then a new video packet is created at the start of the next macroblock. =================================================== What is the value of the threshold? Has it been mentioned in the standard? Or is this threshhold same as maximum video packet size. ==================================================== Gary Sullivan wrote: > Reply interspersed: > > +> -----Original Message----- > +> From: G Chandra Sekhar Reddy [mailto:gchandra@tataelxsi.co.in] > +> Sent: Thursday, September 13, 2023 11:30 PM > +> To: Jani Huoponen; Sudhakar Rao Kimidi; technotes@lists.m4if.org > +> Subject: Re: [M4IF Technotes] hi > +> > +> > [snip] > +> The Levels restrict maximum number of bits per VideoPacket, > +> making these > +> synchronization points appear within some fixed interval > +> (interval in bits, > +> in bitstream). > > Are you sure about that statement? I don't think it's true. > Can you point to where such a restriction can be found? > > +> This is only restriction on the maximum size. The actual > +> sizes (thereby > +> synchronization intervals) can be less than this maximum size. > +> If you want fixed size (thereby fixed synchronization > +> intervals), you can > +> use stuffing. > > I think you're right. I guess some combination of MCBPC stuffing and > bit stuffing can enable the encoder to hit any desired > reasonably-large packet size. > > +> About the legal interval you are taking about, I think only > +> restriction is > +> that they shall be at BYTE-Boundaries. > > They also must start at macroblock boundaries. Each packet must > contain the bits to represent an integer number of macroblocks. > > +> > +> Does the standard restrict VOP size in bits to some maximum > +> value in any > +> Profile / Level? > > Not that I'm aware of. > > +> > +> Chandra > +> ************************************************************* > +> ********* > +> Chandra Sekhar Reddy G., > +> TATA ELXSI Ltd., > +> WhiteField Road, Hoody, > +> BANGALORE, INDIA - 560048. > +> TEL: +91-80-8410148, 8411811, 8411812 (Ext:254), > +> FAX: +91-80-8410152, 8411813. > +> EMAIL: gchandra@tataelxsi.co.in > +> WEB: www.tataelxsi.com > +> ************************************************************* > +> ********* > +> > +> ----- Original Message ----- > +> From: Jani Huoponen > +> To: Sudhakar Rao Kimidi ; > +> > +> Sent: Thursday, September 13, 2023 9:25 PM > +> Subject: RE: [M4IF Technotes] hi > +> > +> > +> > Dear Sudhakar, > +> > > +> > > Dear all, > +> > > > +> > > Can somebody help me with the answers for the following. > +> > > > +> > > 1. Which method of Quantization is used in MPEG-4 video > +> > > simple profile? > +> > > +> > Type 2. > +> > > +> > > Are both methods of Quantizations used in MPEG-4 Video > +> simple profile? > +> > > +> > No. Type 1 (quantization matrices) is not used in Simple profile. > +> > > +> > > 2. Is fixed interval synchronization supported in simple > +> > > profile? Is it > +> > > compulsory to use the method? Is there any mentioning about it in > +> > > syntax?(This method requires that VOP start codes and > +> > > resynchronization > +> > > markers appear only at legal fixed interval locations in the > +> > > bitstream) > +> > > +> > If you mean that should encoded VOPs have a fixed time > +> interval between > +> them > +> > then the answer is yes. Simple profile supports this. See > +> section 6.3.3. > +> in > +> > the 14496-2 standard, the field called "fixed_vop_rate" > +> explains how this > +> > works. It is not a compulsory method, i.e., VOPs can have > +> variable time > +> > intervals between them. > +> > > +> > BR, Jani > +> > > +> > ------------------------------------------------------------ > +> > Jani Huoponen > +> > Engineering Manager, System Design > +> > Hantro Products Oy > +> > Nahkatehtaankatu 2, 90100 Oulu, Finland > +> > +358-40-5272676 > +> > ------------------------------------------------------------ > +> > > +> > _______________________________________________ > +> > Technotes mailing list > +> > Technotes@lists.m4if.org > +> > http://lists.m4if.org/mailman/listinfo/technotes > +> > +> _______________________________________________ > +> Technotes mailing list > +> Technotes@lists.m4if.org > +> http://lists.m4if.org/mailman/listinfo/technotes > +> > _______________________________________________ > Technotes mailing list > Technotes@lists.m4if.org > http://lists.m4if.org/mailman/listinfo/technotes Thanks&Regards, Sudhakar. From Prabhudev_Hosur objectvideo.com Fri Sep 14 13:31:53 2001 From: Prabhudev_Hosur objectvideo.com (Prabhudev Hosur) Date: Wed Jul 30 14:06:50 2003 Subject: [M4IF Technotes] RE: Technotes digest, Vol 1 #60 - 1 msg In-Reply-To: <200109141600.f8EG0rJ11713@mx3.magma.ca> Message-ID: <000e01c13d3a$c396ec10$1e10a8c0@atom.dbvision.net> Hi Sudhakar Rao Kimidi The table of Suggested Resynchronization Marker Spacing in the VM document may help you in determining the threshold -Prabhu -----Original Message----- From: technotes-admin@lists.m4if.org [mailto:technotes-admin@lists.m4if.org]On Behalf Of technotes-request@lists.m4if.org Sent: Friday, September 14, 2023 12:01 PM To: technotes@lists.m4if.org Subject: Technotes digest, Vol 1 #60 - 1 msg Send Technotes mailing list submissions to technotes@lists.m4if.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.m4if.org/mailman/listinfo/technotes or, via email, send a message with subject or body 'help' to technotes-request@lists.m4if.org You can reach the person managing the list at technotes-admin@lists.m4if.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Technotes digest..." Today's Topics: 1. Re: hi (Sudhakar Rao Kimidi) --__--__-- Message: 1 Date: Fri, 14 Sep 2023 20:24:58 +0530 From: Sudhakar Rao Kimidi Organization: cradle To: Gary Sullivan CC: G Chandra Sekhar Reddy , Jani Huoponen , technotes@lists.m4if.org Subject: Re: [M4IF Technotes] hi Hi all, With respect to discussions below about fixed interval synchronization .... Gary,... you can find the maximum video packet size specified on the last page on either of versions the satnadards ISO 14496-1 or 14496-2. Now I have a doubt regarding the following line: If the number of bits contained in the current video packet exceeds a predetermined threshold, then a new video packet is created at the start of the next macroblock. =================================================== What is the value of the threshold? Has it been mentioned in the standard? Or is this threshhold same as maximum video packet size. ==================================================== Gary Sullivan wrote: > Reply interspersed: > > +> -----Original Message----- > +> From: G Chandra Sekhar Reddy [mailto:gchandra@tataelxsi.co.in] > +> Sent: Thursday, September 13, 2023 11:30 PM > +> To: Jani Huoponen; Sudhakar Rao Kimidi; technotes@lists.m4if.org > +> Subject: Re: [M4IF Technotes] hi > +> > +> > [snip] > +> The Levels restrict maximum number of bits per VideoPacket, > +> making these > +> synchronization points appear within some fixed interval > +> (interval in bits, > +> in bitstream). > > Are you sure about that statement? I don't think it's true. > Can you point to where such a restriction can be found? > > +> This is only restriction on the maximum size. The actual > +> sizes (thereby > +> synchronization intervals) can be less than this maximum size. > +> If you want fixed size (thereby fixed synchronization > +> intervals), you can > +> use stuffing. > > I think you're right. I guess some combination of MCBPC stuffing and > bit stuffing can enable the encoder to hit any desired > reasonably-large packet size. > > +> About the legal interval you are taking about, I think only > +> restriction is > +> that they shall be at BYTE-Boundaries. > > They also must start at macroblock boundaries. Each packet must > contain the bits to represent an integer number of macroblocks. > > +> > +> Does the standard restrict VOP size in bits to some maximum > +> value in any > +> Profile / Level? > > Not that I'm aware of. > > +> > +> Chandra > +> ************************************************************* > +> ********* > +> Chandra Sekhar Reddy G., > +> TATA ELXSI Ltd., > +> WhiteField Road, Hoody, > +> BANGALORE, INDIA - 560048. > +> TEL: +91-80-8410148, 8411811, 8411812 (Ext:254), > +> FAX: +91-80-8410152, 8411813. > +> EMAIL: gchandra@tataelxsi.co.in > +> WEB: www.tataelxsi.com > +> ************************************************************* > +> ********* > +> > +> ----- Original Message ----- > +> From: Jani Huoponen > +> To: Sudhakar Rao Kimidi ; > +> > +> Sent: Thursday, September 13, 2023 9:25 PM > +> Subject: RE: [M4IF Technotes] hi > +> > +> > +> > Dear Sudhakar, > +> > > +> > > Dear all, > +> > > > +> > > Can somebody help me with the answers for the following. > +> > > > +> > > 1. Which method of Quantization is used in MPEG-4 video > +> > > simple profile? > +> > > +> > Type 2. > +> > > +> > > Are both methods of Quantizations used in MPEG-4 Video > +> simple profile? > +> > > +> > No. Type 1 (quantization matrices) is not used in Simple profile. > +> > > +> > > 2. Is fixed interval synchronization supported in simple > +> > > profile? Is it > +> > > compulsory to use the method? Is there any mentioning about it in > +> > > syntax?(This method requires that VOP start codes and > +> > > resynchronization > +> > > markers appear only at legal fixed interval locations in the > +> > > bitstream) > +> > > +> > If you mean that should encoded VOPs have a fixed time > +> interval between > +> them > +> > then the answer is yes. Simple profile supports this. See > +> section 6.3.3. > +> in > +> > the 14496-2 standard, the field called "fixed_vop_rate" > +> explains how this > +> > works. It is not a compulsory method, i.e., VOPs can have > +> variable time > +> > intervals between them. > +> > > +> > BR, Jani > +> > > +> > ------------------------------------------------------------ > +> > Jani Huoponen > +> > Engineering Manager, System Design > +> > Hantro Products Oy > +> > Nahkatehtaankatu 2, 90100 Oulu, Finland > +> > +358-40-5272676 > +> > ------------------------------------------------------------ > +> > > +> > _______________________________________________ > +> > Technotes mailing list > +> > Technotes@lists.m4if.org > +> > http://lists.m4if.org/mailman/listinfo/technotes > +> > +> _______________________________________________ > +> Technotes mailing list > +> Technotes@lists.m4if.org > +> http://lists.m4if.org/mailman/listinfo/technotes > +> > _______________________________________________ > Technotes mailing list > Technotes@lists.m4if.org > http://lists.m4if.org/mailman/listinfo/technotes Thanks&Regards, Sudhakar. --__--__-- _______________________________________________ Technotes mailing list Technotes@lists.m4if.org http://lists.m4if.org/mailman/listinfo/technotes End of Technotes Digest From Prabhudev_Hosur objectvideo.com Fri Sep 14 13:52:44 2001 From: Prabhudev_Hosur objectvideo.com (Prabhudev Hosur) Date: Wed Jul 30 14:06:50 2003 Subject: [M4IF Technotes] hi Message-ID: <000f01c13d3d$adad4e00$1e10a8c0@atom.dbvision.net> Hi Sudhakar Rao Kimidi The table of Suggested Resynchronization Marker Spacing in the VM document may help you in determining the threshold -Prabhu -----Original Message----- From: technotes-admin@lists.m4if.org [mailto:technotes-admin@lists.m4if.org]On Behalf Of technotes-request@lists.m4if.org Sent: Friday, September 14, 2023 12:01 PM To: technotes@lists.m4if.org Subject: Technotes digest, Vol 1 #60 - 1 msg Send Technotes mailing list submissions to technotes@lists.m4if.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.m4if.org/mailman/listinfo/technotes or, via email, send a message with subject or body 'help' to technotes-request@lists.m4if.org You can reach the person managing the list at technotes-admin@lists.m4if.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Technotes digest..." Today's Topics: 1. Re: hi (Sudhakar Rao Kimidi) --__--__-- Message: 1 Date: Fri, 14 Sep 2023 20:24:58 +0530 From: Sudhakar Rao Kimidi Organization: cradle To: Gary Sullivan CC: G Chandra Sekhar Reddy , Jani Huoponen , technotes@lists.m4if.org Subject: Re: [M4IF Technotes] hi Hi all, With respect to discussions below about fixed interval synchronization .... Gary,... you can find the maximum video packet size specified on the last page on either of versions the satnadards ISO 14496-1 or 14496-2. Now I have a doubt regarding the following line: If the number of bits contained in the current video packet exceeds a predetermined threshold, then a new video packet is created at the start of the next macroblock. =================================================== What is the value of the threshold? Has it been mentioned in the standard? Or is this threshhold same as maximum video packet size. ==================================================== Gary Sullivan wrote: > Reply interspersed: > > +> -----Original Message----- > +> From: G Chandra Sekhar Reddy [mailto:gchandra@tataelxsi.co.in] > +> Sent: Thursday, September 13, 2023 11:30 PM > +> To: Jani Huoponen; Sudhakar Rao Kimidi; technotes@lists.m4if.org > +> Subject: Re: [M4IF Technotes] hi > +> > +> > [snip] > +> The Levels restrict maximum number of bits per VideoPacket, > +> making these > +> synchronization points appear within some fixed interval > +> (interval in bits, > +> in bitstream). > > Are you sure about that statement? I don't think it's true. > Can you point to where such a restriction can be found? > > +> This is only restriction on the maximum size. The actual > +> sizes (thereby > +> synchronization intervals) can be less than this maximum size. > +> If you want fixed size (thereby fixed synchronization > +> intervals), you can > +> use stuffing. > > I think you're right. I guess some combination of MCBPC stuffing and > bit stuffing can enable the encoder to hit any desired > reasonably-large packet size. > > +> About the legal interval you are taking about, I think only > +> restriction is > +> that they shall be at BYTE-Boundaries. > > They also must start at macroblock boundaries. Each packet must > contain the bits to represent an integer number of macroblocks. > > +> > +> Does the standard restrict VOP size in bits to some maximum > +> value in any > +> Profile / Level? > > Not that I'm aware of. > > +> > +> Chandra > +> ************************************************************* > +> ********* > +> Chandra Sekhar Reddy G., > +> TATA ELXSI Ltd., > +> WhiteField Road, Hoody, > +> BANGALORE, INDIA - 560048. > +> TEL: +91-80-8410148, 8411811, 8411812 (Ext:254), > +> FAX: +91-80-8410152, 8411813. > +> EMAIL: gchandra@tataelxsi.co.in > +> WEB: www.tataelxsi.com > +> ************************************************************* > +> ********* > +> > +> ----- Original Message ----- > +> From: Jani Huoponen > +> To: Sudhakar Rao Kimidi ; > +> > +> Sent: Thursday, September 13, 2023 9:25 PM > +> Subject: RE: [M4IF Technotes] hi > +> > +> > +> > Dear Sudhakar, > +> > > +> > > Dear all, > +> > > > +> > > Can somebody help me with the answers for the following. > +> > > > +> > > 1. Which method of Quantization is used in MPEG-4 video > +> > > simple profile? > +> > > +> > Type 2. > +> > > +> > > Are both methods of Quantizations used in MPEG-4 Video > +> simple profile? > +> > > +> > No. Type 1 (quantization matrices) is not used in Simple profile. > +> > > +> > > 2. Is fixed interval synchronization supported in simple > +> > > profile? Is it > +> > > compulsory to use the method? Is there any mentioning about it in > +> > > syntax?(This method requires that VOP start codes and > +> > > resynchronization > +> > > markers appear only at legal fixed interval locations in the > +> > > bitstream) > +> > > +> > If you mean that should encoded VOPs have a fixed time > +> interval between > +> them > +> > then the answer is yes. Simple profile supports this. See > +> section 6.3.3. > +> in > +> > the 14496-2 standard, the field called "fixed_vop_rate" > +> explains how this > +> > works. It is not a compulsory method, i.e., VOPs can have > +> variable time > +> > intervals between them. > +> > > +> > BR, Jani > +> > > +> > ------------------------------------------------------------ > +> > Jani Huoponen > +> > Engineering Manager, System Design > +> > Hantro Products Oy > +> > Nahkatehtaankatu 2, 90100 Oulu, Finland > +> > +358-40-5272676 > +> > ------------------------------------------------------------ > +> > > +> > _______________________________________________ > +> > Technotes mailing list > +> > Technotes@lists.m4if.org > +> > http://lists.m4if.org/mailman/listinfo/technotes > +> > +> _______________________________________________ > +> Technotes mailing list > +> Technotes@lists.m4if.org > +> http://lists.m4if.org/mailman/listinfo/technotes > +> > _______________________________________________ > Technotes mailing list > Technotes@lists.m4if.org > http://lists.m4if.org/mailman/listinfo/technotes Thanks&Regards, Sudhakar. --__--__-- _______________________________________________ Technotes mailing list Technotes@lists.m4if.org http://lists.m4if.org/mailman/listinfo/technotes End of Technotes Digest From olivier.avaro francetelecom.com Mon Sep 17 10:21:39 2001 From: olivier.avaro francetelecom.com (Olivier Avaro) Date: Wed Jul 30 14:06:50 2003 Subject: [M4IF Technotes] Objects In-Reply-To: <005901c13569$24e37850$9faa66c0@rostock.igd.fhg.de> Message-ID: <002201c13f4e$22d72a90$3c4b6a20@rd.francetelecom.fr> I have a question about mpeg-4 systems. Is it possible to use one ObjectID in more than one node, e.g. if I want to use one backchannel object for multiple ServerCommand nodes? Or must this be a 1:1 relationship. I couldn't find it in the standard. To my knowledge, nothing prevent you from doing it this. It has been used many times with downstreams. You should be able to do it with upstreams as well. Kind regards, Olivier -------------- next part -------------- An HTML attachment was scrubbed... URL: /pipermail/mp4-tech/attachments/20010917/698aaefc/attachment.html From shivakumar asu.edu Mon Sep 17 10:04:11 2001 From: shivakumar asu.edu (Shivakumar Narayanan) Date: Wed Jul 30 14:06:50 2003 Subject: [M4IF Technotes] Query Message-ID: Hi all, I am a grad student and we are working in layered encoding of MPEG-4 for wireless. In the MPEG-4 document N2552, they give a brief picture about the scalable encoding codec structure and its working. Where can I get more information in depth about each building block. Can anyone help me in this regard or which section of the MoMuSys code this is implemented. Thankyou, Regards Shivakumar -------------------------------------------- Shivakumar K Narayanan Department of Electrical Engineering Arizona State University Tempe, AZ 85281 Ph.No: 480 731 4975(home) 480 965 2153(lab) From steve.mcrobert amd.com Mon Sep 17 16:13:50 2001 From: steve.mcrobert amd.com (steve.mcrobert@amd.com) Date: Wed Jul 30 14:06:51 2003 Subject: [M4IF Technotes] RE: implementation of SL/DMIF Message-ID: <4201B90278FBD111B95100805F8516BD0565AD55@caexmta4.amd.com> Guido: Thanks for your most helpful reply. You comment that "the DMIF spec as such is not being extended, and the "bits on the wire" are being defined in a separate MPEG4 document (part 8)". What does "not being extended" mean? That it will be used as currently defined? Or that in practice it will be bypassed? Will the great flexibility in combining different types of object described in part 1 (systems) of the MPEG-4 Standard be fully supported? How can I get access to part 8 of the standard? The ISO Web site lists only parts 1-6. I purchased ISO/IEC 14496 parts 1-6 earlier this year (part 1 is dated 2023-12-15) Regards, Steve > -----Original Message----- > From: Franceschini Guido [mailto:Guido.Franceschini@TILAB.COM] > Sent: Friday, September 14, 2023 1:20 AM > To: McRobert, Steve; Guido.Franceschini@cselt.it > Cc: rkoenen@intertrust.com > Subject: RE: implementation of SL/DMIF > > > Hi Steve, > > RTP and Sync Layer partly overlap indeed, and that's the reason why a > few fields of the SL (namely: AU_EndFlag <-> Marker bit in some case; > timestamps) are mapped into field of the RTP header. > Apart from that, the I-D for RTP over MPEG4 addresses optimization > issues, and defines a mechanism to aggregate/interleave multiple SL > packets into a single RTP packet. > > What's DMIF role in all this ? How to implement this in practice ? > > Well, I have largely contributed to the DMIF spec, to the reference > software dealing with DMIF and SL, and, internally to TILAB, to a vast > number of what we call "DMIF Instances". I try to shed some light on > this. > > The basic concept is that a multimedia application, and namely MPEG-4 > Systems, should be implementable independently of how the content is > retrieved, in order to easily add new transport solutions in > the future > (both from a standard and implementation perspective). This > idea lead to > the definition of a simple but accurate semantic interface, the DAI > (DMIF-Application Interface) > Below the DAI you have to deal with the peculiarities of your > transport, > on top of the DAI you only deal with a single content representation. > After the initial specification in 1998, we amended the DAI > and the ref. > sw. to take into account the fact that different transport mechanisms > represent the same semantic information (timestamp, AU boundaries, > Random Access Flag, sequence numbers ...) with different sintax. > Examples are RTP, MPEG2-TS, MP4 files. To cope with this, the exchange > of data across the DAI goes in tuples , where the > payload represents the pure content, and the metainfo semantically > carries a complete representation of the SL info. Each transport > mechanism defines headers, which include information such as > timestamps. > Therefore the implementation of a DMIF Instance, dealing with > a specific > transport stack, and knowing the format of those header, can transform > the information contained herein into a uniform metainfo > representation > to be carried across the uniform DAI. > What I am stating above is proved in reality: using this technique, we > have developed in TILAB "DMIF Instances" to get content from: > > - MP4 files > - the Internet with Unicast and Multicast using > UDP/RTP/TCP(unicast), or > with HTTP > - MPEG2 Transport Streams > - Fixed and Mobile phone lines > > Note that the SL information is represented in very different syntaxes > in all the above cases > On top of any of those DMIF Instances we run Players, Recorders, > Recasters and Servers, all using a single interface. > > As far as the AVT efforts are concerned: DMIF defines the DAI and the > architectural model. It also specifies "bits on the wire" for a few > cases, by means of the so-called "Default DMIF Signalling Protocol" (a > protocol for peer-to-peer communication that fully supports all MPEG-4 > Systems requirements. However it overlaps with Hxxx and RTSP, that > -although unable to support all MPEG4 Systems options- are more > appealing for developers) In the initial intentions, it was > the box into > which the details of the various transports were to be defined. > Real-life however indicates that many people do not care about DAI or > architecture, which are believed to be sort of > "implementation issues", > and wanted to avoid mixing the details of a particular transport with > the DMIF specification. Therefore, the DMIF spec as such is not being > extended, and the "bits on the wire" are being defined in a separate > MPEG4 document (part 8): this document reflects the AVT work and > "imports" it in MPEG4 > > I hope I cleared your doubts. > > Best regards > > Guido Franceschini > > Telecom Italia Labs > TILAB - Multimedia Division > Via G.Reiss Romoli 274 > I-10148 Torino, Italy > tel + 39 011 228 6137 > fax + 39 011 228 6299 > > -----Original Message----- > From: steve.mcrobert@amd.com [mailto:steve.mcrobert@amd.com] > Sent: Thursday, September 13, 2023 9:21 PM > To: Guido.Franceschini@cselt.it > Cc: rkoenen@intertrust.com > Subject: implementation of SL/DMIF > > > Guido: > > I'm having trouble understanding how the Synchronization > Layer and the DMIF > are being implementated in practice. > > The work going on in the AVT group of IETF is focussed on RTP, & seems > largely to view the Synchronization Layer as overlapping with RTP & > therefore redundant. > > I can't find any work on the DMIF at all. > > Can you point me in the right direction? > > Thanks, Steve > > The reasonable man adapts himself to the world; the unreasonable one > persists to adapt the world to himself. Therefore all progress depends > on > the unreasonable man. -George Bernard Shaw, writer, Nobel laureate > (1856-1950) > > <> > From sudhakar cradle.com Tue Sep 18 12:41:20 2001 From: sudhakar cradle.com (Sudhakar Rao Kimidi) Date: Wed Jul 30 14:06:51 2003 Subject: [M4IF Technotes] Hi Message-ID: <3BA6E586.4093F8F0@cradle.com> Hi all, Can somebody, who is experienced in MPEG-4 video coding, help me. How many video packets do you usually find per video object of size CIF when coded at rate 384kbps using Simple Profile?. What is the minimum number of video packets of the same case? I need this as a part of looking for parallelization in coding Thanks&Regards, Sudhakar K. From ramki emuzed.com Tue Sep 18 13:32:15 2001 From: ramki emuzed.com (Ramkishor Korada) Date: Wed Jul 30 14:06:51 2003 Subject: [M4IF Technotes] Hi References: <3BA6E586.4093F8F0@cradle.com> Message-ID: <020801c1400f$dbf3ce40$0d0aa8c0@blr.emuzed.com> Hi, Reg. video packets, already it has been discussed here. Unless data partitioning is enabled, there is no limitation on packet size. Parallelization at macroblock decoding level can be tried out i.e., IQ & IDCT can be done on one PE (Processing Element) and MC can be done on another PE. Parallelization within the packet can be also tried out i.e., if four PEs are available then four macroblocks can be decoded simultaneously on four PEs. In this method, if the number of available PEs is more than the number of macroblocks in the packet, then some PEs are under utilized. But, usually this won't happen unless the processor has PEs in the order of 30-40. regards, ramkishor Architect - Video Multimedia Technologies Division Emuzed India Bangalore www.emuzed.com ----- Original Message ----- From: "Sudhakar Rao Kimidi" To: < > Sent: Tuesday, September 18, 2023 11:41 AM Subject: [M4IF Technotes] Hi > Hi all, > > Can somebody, who is experienced in MPEG-4 video coding, help me. > > How many video packets do you usually find per video object of size CIF > when coded at rate 384kbps using Simple Profile?. What is the minimum > number of video packets of the same case? > I need this as a part of looking for parallelization in coding > > Thanks&Regards, > Sudhakar K. > > _______________________________________________ > Technotes mailing list > Technotes@lists.m4if.org > http://lists.m4if.org/mailman/listinfo/technotes > > From sudhakar cradle.com Wed Sep 19 11:14:34 2001 From: sudhakar cradle.com (Sudhakar Rao Kimidi) Date: Wed Jul 30 14:06:51 2003 Subject: [M4IF Technotes] Hi References: <3BA6E586.4093F8F0@cradle.com> <020801c1400f$dbf3ce40$0d0aa8c0@blr.emuzed.com> Message-ID: <3BA822B1.2A6758FE@cradle.com> Hil, The problem with going for parallelization at macro block level : In case of Intra macro blocks...If AC prediction is to be done from the macroblock just before the present macroblock :::: the present macroblock decoding has to wait till it gets the quantized AC fist column coefficients of previous macroblocks ====================================================. And I think thresholds for video packets are suggested in verification model even for no data-partioning. If encoders follow that threshold we may get some number of video packets per VOP ( That helps to go for parallelization at Video packet level) regards, sudhakar k. Ramkishor Korada wrote: > Hi, > Reg. video packets, already it has been discussed here. Unless data > partitioning is enabled, there is no limitation on packet size. > > Parallelization at macroblock decoding level can be tried out i.e., IQ & > IDCT can be done on one PE (Processing Element) and MC can be done on > another PE. > Parallelization within the packet can be also tried out i.e., if four PEs > are available then four macroblocks can be decoded simultaneously on four > PEs. In this method, if the number of available PEs is more than the number > of macroblocks in the packet, then some PEs are under utilized. But, usually > this won't happen unless the processor has PEs in the order of 30-40. > > regards, > ramkishor > > Architect - Video > Multimedia Technologies Division > Emuzed India > Bangalore > www.emuzed.com > > ----- Original Message ----- > From: "Sudhakar Rao Kimidi" > To: < > > Sent: Tuesday, September 18, 2023 11:41 AM > Subject: [M4IF Technotes] Hi > > > Hi all, > > > > Can somebody, who is experienced in MPEG-4 video coding, help me. > > > > How many video packets do you usually find per video object of size CIF > > when coded at rate 384kbps using Simple Profile?. What is the minimum > > number of video packets of the same case? > > I need this as a part of looking for parallelization in coding > > > > Thanks&Regards, > > Sudhakar K. > > > > _______________________________________________ > > Technotes mailing list > > Technotes@lists.m4if.org > > http://lists.m4if.org/mailman/listinfo/technotes > > > > From Guido.Franceschini TILAB.COM Wed Sep 19 14:50:14 2001 From: Guido.Franceschini TILAB.COM (Franceschini Guido) Date: Wed Jul 30 14:06:51 2003 Subject: [M4IF Technotes] RE: implementation of SL/DMIF Message-ID: Steve, see below -----Original Message----- From: steve.mcrobert@amd.com [mailto:steve.mcrobert@amd.com] Sent: Tuesday, September 18, 2023 12:14 AM To: Franceschini Guido Cc: technotes@lists.m4if.org Subject: RE: implementation of SL/DMIF Guido: Thanks for your most helpful reply. You comment that "the DMIF spec as such is not being extended, and the "bits on the wire" are being defined in a separate MPEG4 document (part 8)". What does "not being extended" mean? That it will be used as currently defined? Or that in practice it will be bypassed? [guido] DMIF provides you with an architecture and APIs that you can very well ignore in your own implementation, and with the specification of "the bits on the wire" for a few transport solutions. The "bits on the wire" for delivering MPEG-4 over RTP however are defined somewhere else (part 8, which in turn refers to AVT work). To my knowledge further related issues concerning the control plane -in particular RTSP, SDP- are being addressed in ISMA. In principle all of this could have been dealt with within part 6 (DMIF), but it has been decided differently. Will the great flexibility in combining different types of object described in part 1 (systems) of the MPEG-4 Standard be fully supported? [guido] To my knowledge, not all of the combinations allowed in part 1 can be supported in the control plane by RTSP in its current version. Those combinations are probably not very significant, nevertheless the inadeguacy of RTSP was one of the reasons why DMIF specified a somehow equivalent protocol, which fully supports MPEG-4 Systems: the "DMIF Default Signaling Protocol". How can I get access to part 8 of the standard? The ISO Web site lists only parts 1-6. I purchased ISO/IEC 14496 parts 1-6 earlier this year (part 1 is dated 2023-12-15) [guido] Part 8 is not yet at its final stage. You can only get it -in its current form- by being part of your National Body within ISO Bye Guido Regards, Steve > -----Original Message----- > From: Franceschini Guido [mailto:Guido.Franceschini@TILAB.COM] > Sent: Friday, September 14, 2023 1:20 AM > To: McRobert, Steve; Guido.Franceschini@cselt.it > Cc: rkoenen@intertrust.com > Subject: RE: implementation of SL/DMIF > > > Hi Steve, > > RTP and Sync Layer partly overlap indeed, and that's the reason why a > few fields of the SL (namely: AU_EndFlag <-> Marker bit in some case; > timestamps) are mapped into field of the RTP header. > Apart from that, the I-D for RTP over MPEG4 addresses optimization > issues, and defines a mechanism to aggregate/interleave multiple SL > packets into a single RTP packet. > > What's DMIF role in all this ? How to implement this in practice ? > > Well, I have largely contributed to the DMIF spec, to the reference > software dealing with DMIF and SL, and, internally to TILAB, to a vast > number of what we call "DMIF Instances". I try to shed some light on > this. > > The basic concept is that a multimedia application, and namely MPEG-4 > Systems, should be implementable independently of how the content is > retrieved, in order to easily add new transport solutions in > the future > (both from a standard and implementation perspective). This > idea lead to > the definition of a simple but accurate semantic interface, the DAI > (DMIF-Application Interface) > Below the DAI you have to deal with the peculiarities of your > transport, > on top of the DAI you only deal with a single content representation. > After the initial specification in 1998, we amended the DAI > and the ref. > sw. to take into account the fact that different transport mechanisms > represent the same semantic information (timestamp, AU boundaries, > Random Access Flag, sequence numbers ...) with different sintax. > Examples are RTP, MPEG2-TS, MP4 files. To cope with this, the exchange > of data across the DAI goes in tuples , where the > payload represents the pure content, and the metainfo semantically > carries a complete representation of the SL info. Each transport > mechanism defines headers, which include information such as > timestamps. > Therefore the implementation of a DMIF Instance, dealing with > a specific > transport stack, and knowing the format of those header, can transform > the information contained herein into a uniform metainfo > representation > to be carried across the uniform DAI. > What I am stating above is proved in reality: using this technique, we > have developed in TILAB "DMIF Instances" to get content from: > > - MP4 files > - the Internet with Unicast and Multicast using > UDP/RTP/TCP(unicast), or > with HTTP > - MPEG2 Transport Streams > - Fixed and Mobile phone lines > > Note that the SL information is represented in very different syntaxes > in all the above cases > On top of any of those DMIF Instances we run Players, Recorders, > Recasters and Servers, all using a single interface. > > As far as the AVT efforts are concerned: DMIF defines the DAI and the > architectural model. It also specifies "bits on the wire" for a few > cases, by means of the so-called "Default DMIF Signalling Protocol" (a > protocol for peer-to-peer communication that fully supports all MPEG-4 > Systems requirements. However it overlaps with Hxxx and RTSP, that > -although unable to support all MPEG4 Systems options- are more > appealing for developers) In the initial intentions, it was > the box into > which the details of the various transports were to be defined. > Real-life however indicates that many people do not care about DAI or > architecture, which are believed to be sort of > "implementation issues", > and wanted to avoid mixing the details of a particular transport with > the DMIF specification. Therefore, the DMIF spec as such is not being > extended, and the "bits on the wire" are being defined in a separate > MPEG4 document (part 8): this document reflects the AVT work and > "imports" it in MPEG4 > > I hope I cleared your doubts. > > Best regards > > Guido Franceschini > > Telecom Italia Labs > TILAB - Multimedia Division > Via G.Reiss Romoli 274 > I-10148 Torino, Italy > tel + 39 011 228 6137 > fax + 39 011 228 6299 > > -----Original Message----- > From: steve.mcrobert@amd.com [mailto:steve.mcrobert@amd.com] > Sent: Thursday, September 13, 2023 9:21 PM > To: Guido.Franceschini@cselt.it > Cc: rkoenen@intertrust.com > Subject: implementation of SL/DMIF > > > Guido: > > I'm having trouble understanding how the Synchronization > Layer and the DMIF > are being implementated in practice. > > The work going on in the AVT group of IETF is focussed on RTP, & seems > largely to view the Synchronization Layer as overlapping with RTP & > therefore redundant. > > I can't find any work on the DMIF at all. > > Can you point me in the right direction? > > Thanks, Steve > > The reasonable man adapts himself to the world; the unreasonable one > persists to adapt the world to himself. Therefore all progress depends > on > the unreasonable man. -George Bernard Shaw, writer, Nobel laureate > (1856-1950) > > <> > From rkoenen intertrust.com Wed Sep 19 12:19:21 2001 From: rkoenen intertrust.com (Rob Koenen) Date: Wed Jul 30 14:06:51 2003 Subject: [M4IF Technotes] RE: implementation of SL/DMIF Message-ID: <720AE932C238D411B4D100C04F10DA6B03CB93E4@exchange.epr.com> > Part 8 is not yet at its final stage. You can only get it -in its > current form- by being part of your National Body within ISO No, it is publicly available. See http://www.cselt.it/mpeg/working_documents.htm and look in the MPEG4 Systems section for 14496-8 FCD Rob From lpearlst ati.com Fri Sep 21 15:23:43 2001 From: lpearlst ati.com (Larry Pearlstein) Date: Wed Jul 30 14:06:51 2003 Subject: [M4IF Technotes] Very basic question about video bitstream syntax and ES definitio ns Message-ID: <5337D585DDD3D111996B0008C728F07DFA9F6D@pa00fsr01.pa.atitech.com> Dear M4IF community members, I'm wondering about the syntax that I've found in MPEG-4 video bitstreams. I see the following: 0000 0101 video_object_start_code 0000 0120 video_object_layer_start_code 00c8 = "0000 0000 1100 1000" > random_acc = 0 video_object_type_indication = 0x01, simple object type is_object_layer_id = 1 verid = 0010, priority = 001 etc. My confusion comes from the fact that it seems that the syntax of the file begins in the middle of the VisualObject syntax. Perhaps I've missed some text that suggests that this is allowed, suggested, etc? In the conformance spec it says: "A bitstream is the coded representation of one layer of a single visual object." Based on this definition, I'd expect to find a visual_object_start_code at the beginning of the file. Also, I'm confused about the definition about an MPEG-4 "Elementary Stream". Figure 6-12 suggests that a Visual Object Layer is an elementary stream. I would imagine that a VideoObjectLayer is a type of Visual Object Layer, right? But the text suggests that a VideoObjectLayer contains configuration information that is not part of an elementary stream. Also, VideoObjectLayer is hierarchically above the 5 functions that are enumerated as "entry points" for elementary streams. So - is a VideoObjectLayer an Elementary Stream? Is an MPEG-4 video bitstream file an elementary stream? Is an MPEG-4 video bitstream file a VideoObjectLayer, etc? Thanks for any help. Also, please forgive me if this isn't the appropriate forum for this question, it's the first time I've posted. Thanks, Larry Pearlstein ATI -------------- next part -------------- An HTML attachment was scrubbed... URL: /pipermail/mp4-tech/attachments/20010921/be405be7/attachment.html From Prabhudev_Hosur objectvideo.com Fri Sep 21 16:32:21 2001 From: Prabhudev_Hosur objectvideo.com (Prabhudev Hosur) Date: Wed Jul 30 14:06:52 2003 Subject: [M4IF Technotes] Very basic question about video bitstream syntax and ES definitio ns In-Reply-To: <5337D585DDD3D111996B0008C728F07DFA9F6D@pa00fsr01.pa.atitech.com> Message-ID: <001101c142d4$228c13f0$1e10a8c0@atom.dbvision.net> Larry Pearlstein, 1) A visual bitstream should start with Visual_object_sequence_start_code 2) A visual elementary stream is defined differently for combined and separate configurations to address video only decoding and MPEG-4 systems level decoding. In the first case, an elementary stream is the entire visual bitstream for a visual object layer. In the second case, it is only all the data except the data after either video object layer (for video visual object) header or visual object header (for other visual objects) -Prabhu ObjectVideo -----Original Message----- From: technotes-admin@lists.m4if.org [mailto:technotes-admin@lists.m4if.org]On Behalf Of Larry Pearlstein Sent: Friday, September 21, 2023 2:24 PM To: 'technotes@lists.m4if.org' Subject: [M4IF Technotes] Very basic question about video bitstream syntax and ES definitio ns Dear M4IF community members, I'm wondering about the syntax that I've found in MPEG-4 video bitstreams. I see the following: 0000 0101 video_object_start_code 0000 0120 video_object_layer_start_code 00c8 = "0000 0000 1100 1000" > random_acc = 0 video_object_type_indication = 0x01, simple object type is_object_layer_id = 1 verid = 0010, priority = 001 etc. My confusion comes from the fact that it seems that the syntax of the file begins in the middle of the VisualObject syntax. Perhaps I've missed some text that suggests that this is allowed, suggested, etc? In the conformance spec it says: "A bitstream is the coded representation of one layer of a single visual object." Based on this definition, I'd expect to find a visual_object_start_code at the beginning of the file. Also, I'm confused about the definition about an MPEG-4 "Elementary Stream". Figure 6-12 suggests that a Visual Object Layer is an elementary stream. I would imagine that a VideoObjectLayer is a type of Visual Object Layer, right? But the text suggests that a VideoObjectLayer contains configuration information that is not part of an elementary stream. Also, VideoObjectLayer is hierarchically above the 5 functions that are enumerated as "entry points" for elementary streams. So - is a VideoObjectLayer an Elementary Stream? Is an MPEG-4 video bitstream file an elementary stream? Is an MPEG-4 video bitstream file a VideoObjectLayer, etc? Thanks for any help. Also, please forgive me if this isn't the appropriate forum for this question, it's the first time I've posted. Thanks, Larry Pearlstein ATI -------------- next part -------------- An HTML attachment was scrubbed... URL: /pipermail/mp4-tech/attachments/20010921/5ccddc98/attachment.html From Prabhudev_Hosur objectvideo.com Fri Sep 21 17:01:56 2001 From: Prabhudev_Hosur objectvideo.com (Prabhudev Hosur) Date: Wed Jul 30 14:06:52 2003 Subject: [M4IF Technotes] Very basic question about video bitstream syntax and ES definitio ns In-Reply-To: <001101c142d4$228c13f0$1e10a8c0@atom.dbvision.net> Message-ID: <001a01c142d8$44d28120$1e10a8c0@atom.dbvision.net> Please correct 2) as: A visual elementary stream is defined differently for combined and separate configurations to address video only decoding and MPEG-4 systems level decoding. In the first case, an elementary stream is the entire visual bitstream for a visual object layer. In the second case, it is all the data after either video object layer (for video visual object) header or visual object header (for other visual objects) Prabhu ObjectVideo -----Original Message----- From: technotes-admin@lists.m4if.org [mailto:technotes-admin@lists.m4if.org]On Behalf Of Prabhudev Hosur Sent: Friday, September 21, 2023 3:32 PM To: 'Larry Pearlstein'; technotes@lists.m4if.org Subject: RE: [M4IF Technotes] Very basic question about video bitstream syntax and ES definitio ns Larry Pearlstein, 1) A visual bitstream should start with Visual_object_sequence_start_code 2) A visual elementary stream is defined differently for combined and separate configurations to address video only decoding and MPEG-4 systems level decoding. In the first case, an elementary stream is the entire visual bitstream for a visual object layer. In the second case, it is only all the data except the data after either video object layer (for video visual object) header or visual object header (for other visual objects) -Prabhu ObjectVideo -----Original Message----- From: technotes-admin@lists.m4if.org [mailto:technotes-admin@lists.m4if.org]On Behalf Of Larry Pearlstein Sent: Friday, September 21, 2023 2:24 PM To: 'technotes@lists.m4if.org' Subject: [M4IF Technotes] Very basic question about video bitstream syntax and ES definitio ns Dear M4IF community members, I'm wondering about the syntax that I've found in MPEG-4 video bitstreams. I see the following: 0000 0101 video_object_start_code 0000 0120 video_object_layer_start_code 00c8 = "0000 0000 1100 1000" > random_acc = 0 video_object_type_indication = 0x01, simple object type is_object_layer_id = 1 verid = 0010, priority = 001 etc. My confusion comes from the fact that it seems that the syntax of the file begins in the middle of the VisualObject syntax. Perhaps I've missed some text that suggests that this is allowed, suggested, etc? In the conformance spec it says: "A bitstream is the coded representation of one layer of a single visual object." Based on this definition, I'd expect to find a visual_object_start_code at the beginning of the file. Also, I'm confused about the definition about an MPEG-4 "Elementary Stream". Figure 6-12 suggests that a Visual Object Layer is an elementary stream. I would imagine that a VideoObjectLayer is a type of Visual Object Layer, right? But the text suggests that a VideoObjectLayer contains configuration information that is not part of an elementary stream. Also, VideoObjectLayer is hierarchically above the 5 functions that are enumerated as "entry points" for elementary streams. So - is a VideoObjectLayer an Elementary Stream? Is an MPEG-4 video bitstream file an elementary stream? Is an MPEG-4 video bitstream file a VideoObjectLayer, etc? Thanks for any help. Also, please forgive me if this isn't the appropriate forum for this question, it's the first time I've posted. Thanks, Larry Pearlstein ATI -------------- next part -------------- An HTML attachment was scrubbed... URL: /pipermail/mp4-tech/attachments/20010921/3cea7542/attachment.html From garysull microsoft.com Fri Sep 21 15:40:11 2001 From: garysull microsoft.com (Gary Sullivan) Date: Wed Jul 30 14:06:52 2003 Subject: [M4IF Technotes] Very basic question about video bitstream syntax and ES definitions Message-ID: <0170DDAD0BADFA4CBEC3B55A0748DCCC040C1CD2@red-msg-02.redmond.corp.microsoft.com> Skipped content of type multipart/alternative From lpearlst ati.com Mon Sep 24 10:04:37 2001 From: lpearlst ati.com (Larry Pearlstein) Date: Wed Jul 30 14:06:53 2003 Subject: [M4IF Technotes] Very basic question about video bitstream sy ntax and ES definitions Message-ID: <5337D585DDD3D111996B0008C728F07DFA9F79@pa00fsr01.pa.atitech.com> Dear Gary, Thank you for your reply. I think my main confusion on the ES question came from the labels in the blocks in Fig. 6-12 like "Elementary Stream Visual Object 1 Layer 1". Also, perhaps the term "header" is used somewhat loosely? The syntax is expressed hierarchically, yet some of the syntax layers are described as headers. Thanks, Larry -----Original Message----- From: Gary Sullivan [mailto:garysull@microsoft.com] Sent: Friday, September 21, 2023 5:40 PM To: Larry Pearlstein; technotes@lists.m4if.org Subject: RE: [M4IF Technotes] Very basic question about video bitstream syntax and ES definitions This is addressed in 6.2.1 of MPEG-4 visual. There is a distinct division between "configuration information" and "elementary stream data". There is a clear definition of the "entry points for elementary streams, and entry into these functions defines the breakpoint between configuration information and elementary streams". The elementary stream does not contain the visual object header or the visual object layer header or the video object layer header. Those structures all fall above the defined entry points. Configuration information may be carried separately or may be combined with elementary stream data. Some configuration information is necessary for being able to decode a stream. This is why some files that contain only one elementary stream may contain headers that are not part of that elementary stream, and is why the issue is a tricky one. I believe the visual spec is reasonably clear on this issue. But you're talking about the contents of a file, and I believe file formats are outside the scope of the visual spec. You need to get your information about the format of your file from somewhere else. Best Regards, -Gary Sullivan -----Original Message----- From: Larry Pearlstein [mailto:lpearlst@ati.com] Sent: Friday, September 21, 2023 11:24 AM To: 'technotes@lists.m4if.org' Subject: [M4IF Technotes] Very basic question about video bitstream syntax and ES definitions Dear M4IF community members, I'm wondering about the syntax that I've found in MPEG-4 video bitstreams. I see the following: 0000 0101 video_object_start_code 0000 0120 video_object_layer_start_code 00c8 = "0000 0000 1100 1000" > random_acc = 0 video_object_type_indication = 0x01, simple object type is_object_layer_id = 1 verid = 0010, priority = 001 etc. My confusion comes from the fact that it seems that the syntax of the file begins in the middle of the VisualObject syntax. Perhaps I've missed some text that suggests that this is allowed, suggested, etc? In the conformance spec it says: "A bitstream is the coded representation of one layer of a single visual object." Based on this definition, I'd expect to find a visual_object_start_code at the beginning of the file. Also, I'm confused about the definition about an MPEG-4 "Elementary Stream". Figure 6-12 suggests that a Visual Object Layer is an elementary stream. I would imagine that a VideoObjectLayer is a type of Visual Object Layer, right? But the text suggests that a VideoObjectLayer contains configuration information that is not part of an elementary stream. Also, VideoObjectLayer is hierarchically above the 5 functions that are enumerated as "entry points" for elementary streams. So - is a VideoObjectLayer an Elementary Stream? Is an MPEG-4 video bitstream file an elementary stream? Is an MPEG-4 video bitstream file a VideoObjectLayer, etc? Thanks for any help. Also, please forgive me if this isn't the appropriate forum for this question, it's the first time I've posted. Thanks, Larry Pearlstein ATI -------------- next part -------------- An HTML attachment was scrubbed... URL: /pipermail/mp4-tech/attachments/20010924/ce86fc3d/attachment.html From biswas tataelxsi.co.in Tue Sep 25 11:22:38 2001 From: biswas tataelxsi.co.in (Biswajit Biswas) Date: Wed Jul 30 14:06:53 2003 Subject: [M4IF Technotes] H.26L video coding Message-ID: <005901c1457d$e7231870$0c14010a@tataelxsi.co.in> Hi all, I was just evaluating H.26L(ITU-T) video encoding quality. I found, it offers much superior quality at significantly low bit-rate. It uses Context-based adaptive binary arithmetic coding (CABAC) technique for entropy coding. Among many new things I am just mentioning a few, it uses more than 1 previous frame for motion estimation, scalable macro-block sizes (16X8, 4X8, 8X16 etc), five different prediction mode for B -frames encoding, use of deblocking filter for encoder etc. Is MPEG4 planning to adopt some of this techniques in the newer video profiles like Advanced Real Time Streaming (ARTS) , Advanced Coding Efficiency(ACE)? regards Bis ----------------------------------------------------- | Biswajit Biswas | Office ph#: 91-80-8410148 | | TATA ELXSI LIMITED | (extn: 254) | | Hoody, WhiteField Rd | Fax Number: 91-80-8410152 | / )| Mahadevapura Post | Res ph# : 91-80-5271518 |( \ / / | Bangalore 560 048 | | \ \ _( (_ | INDIA | _) )_ (((\ \>|__/->__________________________________________<-\__| Hi, I buy the international standard ISO/IEC 14496-(1,2,3,4,5,6) First Edition 2024-04-01 Corrected and republished 2024-03-01 The version of the video software is 901 (Microsoft MPEG-4 Visual CODEC FDIS 1.02 (990812)), and I would wish to know if an electronic addresse exists where I can register and be informed into the last news. and I went know, how can i run the encoder MPEG4 to different bit rate using the parameter file. and I have some questions .... In the parameter file version 901, I set the bit rate using RateControl.Type [0] = "TM5" RateControl.BitsPerVOP [0] = 64000 The resultat are very bad, the quality of the image is very bad. I do not understand. In the version 901 the parameter for indicate the bit rate is RateControl.BitsPerVOP [0] = 64000 ??? thank you for your all information excuseme for my English PhD. Al Merci beaucoup. _________________________________________________________________ T?l?chargez MSN Explorer gratuitement ? l'adresse http://explorer.msn.fr/intl.asp From aara10 hotmail.com Tue Sep 25 13:34:04 2001 From: aara10 hotmail.com (Alejandro RAMIREZ) Date: Wed Jul 30 14:06:53 2003 Subject: [M4IF Technotes] [M4IF Infolist] information and question Message-ID: Hi, I buy the international standard ISO/IEC 14496-(1,2,3,4,5,6) First Edition 2024-04-01 Corrected and republished 2024-03-01 The version of the video software is 901 (Microsoft MPEG-4 Visual CODEC FDIS 1.02 (990812)), and I would wish to know if an electronic addresse exists where I can register and be informed into the last news. and I went know, how can i run the encoder MPEG4 to different bit rate using the parameter file. and I have some questions .... In the parameter file version 901, I set the bit rate using RateControl.Type [0] = "TM5" RateControl.BitsPerVOP [0] = 64000 The resultat are very bad, the quality of the image is very bad. I do not understand. In the version 901 the parameter for indicate the bit rate is RateControl.BitsPerVOP [0] = 64000 ??? thank you for your all information excuseme for my English PhD. Al Merci beaucoup. _________________________________________________________________ T?l?chargez MSN Explorer gratuitement ? l'adresse http://explorer.msn.fr/intl.asp _______________________________________________ M4IF General Information list Infolist@lists.m4if.org http://lists.m4if.org/mailman/listinfo/infolist From khuber sorensontech.com Tue Sep 25 10:33:31 2001 From: khuber sorensontech.com (Kris Huber) Date: Wed Jul 30 14:06:53 2003 Subject: [M4IF Technotes] H.26L video coding Message-ID: <6E031E06378BD311AEF20090273CE1BA409326@el-postino.s-vision.com> Hello Bis, H.26L proponents responded to a recent call for proposals for advanced video coding efficiency technologies and it did well in the evaluation. I believe it, or some of its features, may become new MPEG-4 video coding tools, although this is by no means a certainty. There's a general philosophy in MPEG about having a single tool per functionality, and quite dramatic improvement in some significant dimension must be demonstrated to create an exception to that. The ARTS and ACE profiles you mention are already defined, and it is unprecedented for profiles to change their tool set after definition. We have one small exception so far, in the exclusion of the interlace tool in one of the profiles (FGS, I think), at a level where the nominal vop rate is only 15 fps. But this exception is very sensible and deliberately made for complexity reasons because interlace in the the source material is so easily avoidable at low frame rates. Normally any new tools only become part of new profiles rather than being added as new levels to existing profiles. Otherwise confusion is created about the tool set associated with a profile, and the definition of profile as "tool set" is violated. Regards, Kris -----Original Message----- From: Biswajit Biswas [mailto:biswas@tataelxsi.co.in] Sent: Monday, September 24, 2023 10:53 PM To: technotes@lists.m4if.org Subject: [M4IF Technotes] H.26L video coding Hi all, I was just evaluating H.26L(ITU-T) video encoding quality. I found, it offers much superior quality at significantly low bit-rate. It uses Context-based adaptive binary arithmetic coding (CABAC) technique for entropy coding. Among many new things I am just mentioning a few, it uses more than 1 previous frame for motion estimation, scalable macro-block sizes (16X8, 4X8, 8X16 etc), five different prediction mode for B -frames encoding, use of deblocking filter for encoder etc. Is MPEG4 planning to adopt some of this techniques in the newer video profiles like Advanced Real Time Streaming (ARTS) , Advanced Coding Efficiency(ACE)? regards Bis ----------------------------------------------------- | Biswajit Biswas | Office ph#: 91-80-8410148 | | TATA ELXSI LIMITED | (extn: 254) | | Hoody, WhiteField Rd | Fax Number: 91-80-8410152 | / )| Mahadevapura Post | Res ph# : 91-80-5271518 |( \ / / | Bangalore 560 048 | | \ \ _( (_ | INDIA | _) )_ (((\ \>|__/->__________________________________________<-\__| \ \_/ ////) \ / e-mail: biswas@tataelxsi.co.in \ / \ _/ \_ / / / \ \ -------------- next part -------------- An HTML attachment was scrubbed... URL: /pipermail/mp4-tech/attachments/20010925/78bdfc7d/attachment.html From rkoenen intertrust.com Tue Sep 25 10:31:00 2001 From: rkoenen intertrust.com (Rob Koenen) Date: Wed Jul 30 14:06:53 2003 Subject: [M4IF Technotes] H.26L video coding Message-ID: <720AE932C238D411B4D100C04F10DA6B03CB9526@exchange.epr.com> Bis, The existing profiles are what they are: existing profiles. One doesn't change them anymore, that would cause major interoperability problems. MPEG has taken a similar look, and plans to undertake a new standardization effort, jointly with ITU-T. From rkoenen intertrust.com Tue Sep 25 10:34:23 2001 From: rkoenen intertrust.com (Rob Koenen) Date: Wed Jul 30 14:06:53 2003 Subject: [M4IF Technotes] H.26L video coding Message-ID: <720AE932C238D411B4D100C04F10DA6B03CB9527@exchange.epr.com> Kris, > The ARTS and ACE profiles you mention are already defined, > and it is unprecedented for profiles to change their tool set > after definition. We have one small exception so far, in the > exclusion of the interlace tool in one of the profiles (FGS, > I think), at a level where the nominal vop rate is only 15 > fps. This is not true. The tool set of FGS Profile was *NOT* changed after its definition. It was dfined this way right from the start. The exception here is that interlace is excluded at a lower level, while usually tools are not deteremined by levels but only by profiles - as you accurately write below. > But this exception is very sensible and deliberately > made for complexity reasons because interlace in the the > source material is so easily avoidable at low frame rates. > Normally any new tools only become part of new profiles > rather than being added as new levels to existing profiles. > Otherwise confusion is created about the tool set associated > with a profile, and the definition of profile as "tool set" > is violated. > > Regards, > Kris Rob From khuber sorensontech.com Tue Sep 25 14:02:02 2001 From: khuber sorensontech.com (Kris Huber) Date: Wed Jul 30 14:06:53 2003 Subject: [M4IF Technotes] H.26L video coding Message-ID: <6E031E06378BD311AEF20090273CE1BA409328@el-postino.s-vision.com> Hello Rob, I didn't mean to imply that the tool set changed *after* FGS profile definition. By "exception" I meant exception only to the general rule that if you know the name of the profile a decoder implementation conforms to, then you know all of its tools. As you well know, the special case for a lower level of FGS profile was discussed during definition the FGS profile at the Noordwijkerhout, NL meeting, which I was also fortunate enough to attend. Best regards, Kris -----Original Message----- From: Rob Koenen [mailto:rkoenen@intertrust.com] Sent: Tuesday, September 25, 2023 10:34 AM To: 'Kris Huber'; 'Biswajit Biswas' Cc: technotes@lists.m4if.org Subject: RE: [M4IF Technotes] H.26L video coding Kris, > The ARTS and ACE profiles you mention are already defined, > and it is unprecedented for profiles to change their tool set > after definition. We have one small exception so far, in the > exclusion of the interlace tool in one of the profiles (FGS, > I think), at a level where the nominal vop rate is only 15 > fps. This is not true. The tool set of FGS Profile was *NOT* changed after its definition. It was dfined this way right from the start. The exception here is that interlace is excluded at a lower level, while usually tools are not deteremined by levels but only by profiles - as you accurately write below. > But this exception is very sensible and deliberately > made for complexity reasons because interlace in the the > source material is so easily avoidable at low frame rates. > Normally any new tools only become part of new profiles > rather than being added as new levels to existing profiles. > Otherwise confusion is created about the tool set associated > with a profile, and the definition of profile as "tool set" > is violated. > > Regards, > Kris Rob From ramakrishna_kakarala agilent.com Wed Sep 26 11:24:40 2001 From: ramakrishna_kakarala agilent.com (ramakrishna_kakarala@agilent.com) Date: Wed Jul 30 14:06:53 2003 Subject: [M4IF Technotes] dquant in macroblock header Message-ID: Hi all, Does the "dquant" parameter in a macroblock header affect the quantiser step only for that specific macroblock, or also for all remaining macroblocks in the VOP? Thanks Ram ------------------------------------------- Ramakrishna Kakarala |Fax:(650) 485-8029 Agilent Technologies |Ph: (650) 485-5782 3500 Deer Creek Rd | MS 26U2 Palo Alto CA 94304 -- www.labs.agilent.com/personal/Ram_Kakarala/ From rkoenen intertrust.com Wed Sep 26 12:26:15 2001 From: rkoenen intertrust.com (Rob Koenen) Date: Wed Jul 30 14:06:55 2003 Subject: [M4IF Technotes] FW: [M4IFmembers] Stream ID Assignment in MPEG-4 Start-codes and MPEG-2 System Draf t Amendments Message-ID: <720AE932C238D411B4D100C04F10DA6B03CB95A4@exchange.epr.com> Let's move to the Technotes list. Rob -----Original Message----- From: Munsi Haque [mailto: Sent: Wednesday, September 26, 2023 9:34 AM To: M4IF member list (E-mail) Subject: [M4IFmembers] Stream ID Assignment in MPEG-4 Start-codes and MPEG-2 System Draf t Amendments Dear Members : We have noticed the following issues in the ISO Working Group-11 documents: 1) In document w3908.doc, Table-21 specifies the start-codes with stream ID, as shown below . These start-codes are for MPEG-4 specific visual streams. The start-codes with streamID C0 to C5 are assigned for MPEG-4 specific streams. Also so far I could not locate the start code C6 through FF as System Start Code, in the corresponding System Spec, w3561.doc. BM__Ref461688497 Table 21: Start Code Values name start code value (hexadecimal) video_object_start_code 00 through 1F video_object_layer_start_code 20 through 2F reserved 30 through 3F fgs_bp_start_code 40 through 5F reserved 60 through AF visual_object_sequence_start_code B0 visual_object_sequence_end_code B1 user_data_start_code B2 group_of_vop_start_code B3 video_session_error_code B4 visual_object_start_code B5 vop_start_code B6 slice_start_code B7 extension_start_code B8 fgs_vop_start_code B9 fba_object_start_code BA fba_object_plane_start_code BB mesh_object_start_code BC mesh_object_plane_start_code BD still_texture_object_start_code BE texture_spatial_layer_start_code BF texture_snr_layer_start_code C0 texture_tile_start_code C1 texture_shape_layer_start_code C2 stuffing_start_code C3 reserved C4-C5 System start codes (see note) C6 through FF NOTE System start codes are defined in ISO/IEC 14496-1 2) In document w3845.doc (ISO/IEC 13818-1: 2000: Proposed Draft Amednment 1: Transport of Metadata), Table 2-18 shows the following: Table 2-18 -- Stream_id assignments Stream_id Note stream coding 1011 1100 1 program_stream_map 1011 1101 2 private_stream_1 1011 1110 padding_stream 1011 1111 3 private_stream_2 110x xxxx ISO/IEC 13818-3 or ISO/IEC 11172-3 or ISO/IEC 13818-7 or ISO/IEC 14496-3 audio stream number x xxxx 1110 xxxx ITU-T Rec. H.262 | ISO/IEC 13818-2 or ISO/IEC 11172-2 or ISO/IEC 14496-2 video stream number xxxx 1111 0000 3 ECM_stream 1111 0001 3 EMM_stream 1111 0010 5 ITU-T Rec. H.222.0 | ISO/IEC 13818-1 Annex A or ISO/IEC 13818-6_DSMCC_stream 1111 0011 2 ISO/IEC_13522_stream 1111 0100 6 ITU-T Rec. H.222.1 type A 1111 0101 6 ITU-T Rec. H.222.1 type B 1111 0110 6 ITU-T Rec. H.222.1 type C 1111 0111 6 ITU-T Rec. H.222.1 type D 1111 1000 6 ITU-T Rec. H.222.1 type E 1111 1001 7 ancillary_stream 1111 1010 ISO/IEC14496-1_SL-packetized_stream 1111 1011 ISO/IEC14496-1_FlexMux_stream 1111 1100 descriptive data stream 1111 1101 reserved data stream 1111 1110 reserved data stream 1111 1111 4 program_stream_directory As you see in the above table, if the MPEG-4 audio streams are carried in MPEG-2 System packets (PES), then the streamID 0xC0 to 0xDF are used for audio stream. 3) So there could be some mismatches, if those MPEG-4 streams of "texture_snr_layer_start_code C0" " texture_tile_start_code C1 " " texture_shape_layer _start_code C2 " " stuffing _start_code C3 " or "reserved C4 -C5" are carried by MPEG-2 system streams. [Munsi Haque] Is it a serious mismatch ? Also it may be noted that w3845.doc is a PROPOSED DRAFT AMENDEMNT, and so it is not final yet perhaps . Best regards , Munsi Haque TVIA, Inc. 4001 Burton Drive, Santa Clara, CA 95054, USA e-mail: mhaque@tvia.com -------------- next part -------------- An HTML attachment was scrubbed... URL: /pipermail/mp4-tech/attachments/20010926/c984f899/attachment.html From ramki emuzed.com Thu Sep 27 11:29:19 2001 From: ramki emuzed.com (Ramkishor Korada) Date: Wed Jul 30 14:06:55 2003 Subject: [M4IF Technotes] dquant in macroblock header References: Message-ID: <011801c14711$2db83e70$1b0aa8c0@blr.emuzed.com> Hi, Quantizer scale gets updated as and when dquant is found in the macroblock header and if there is no update then the existing quantizer scale is used. So, dquant affects the quantizer step for the remaining macroblocks in the VOP. -ramkishor Architect - Video Multimedia Technologies Division Emuzed India Bangalore www.emuzed.com ----- Original Message ----- From: To: Sent: Wednesday, September 26, 2023 10:54 PM Subject: [M4IF Technotes] dquant in macroblock header > Hi all, > > Does the "dquant" parameter in a macroblock header affect > the quantiser step only for that specific macroblock, or also > for all remaining macroblocks in the VOP? > > Thanks > Ram > ------------------------------------------- > Ramakrishna Kakarala |Fax:(650) 485-8029 > Agilent Technologies |Ph: (650) 485-5782 > 3500 Deer Creek Rd | > MS 26U2 > Palo Alto CA 94304 > -- > www.labs.agilent.com/personal/Ram_Kakarala/ > > _______________________________________________ > Technotes mailing list > Technotes@lists.m4if.org > http://lists.m4if.org/mailman/listinfo/technotes > > From claes.gustavsson popwire.com Thu Sep 27 10:25:42 2001 From: claes.gustavsson popwire.com (Claes Gustavsson) Date: Wed Jul 30 14:06:55 2003 Subject: [M4IF Technotes] *.mp4 Message-ID: Hi... I need information about the MPEG-4 fileformat, especially how the hinting works. (Standard number, www, books - anything...) brgds /Claes From kmr iis.fhg.de Thu Sep 27 11:05:44 2001 From: kmr iis.fhg.de (Vinod Kumar) Date: Wed Jul 30 14:06:55 2003 Subject: [M4IF Technotes] Quarterpel motion estimation Message-ID: <3BB2DDD8.AA0EDA58@iis.fhg.de> HI Has any one worked on quarterpel motion estimation. Is the interpolation for quarterpel done every macroblock or is the entire vop interpolated. Since half pel is bilinear interpolation, there wouldnt be a problem if the interpolation is done on one entire vop... but is that the case with quarterpel also? regards kmr From ramki emuzed.com Thu Sep 27 14:51:53 2001 From: ramki emuzed.com (Ramkishor Korada) Date: Wed Jul 30 14:06:55 2003 Subject: [M4IF Technotes] Quarterpel motion estimation References: <3BB2DDD8.AA0EDA58@iis.fhg.de> Message-ID: <037201c1472d$7abad6d0$1b0aa8c0@blr.emuzed.com> Hi, When quarter pel motion estimation is enabled, then halh pel samples are not bilinearly interpolated. They are estimated at a block level by using 8-tap symmetrical FIR filter. At the block edges/boundaries, mirror extension is done because of 8-tap filter. Quarter pel samples are interpolated from the half pel and integer pel values. More details can be found in Section 7.6.2.2. of the visual(14496-2) standard. Doing interpolation on entire VOP is not possible. regards, ramkishor Architect - Video Multimedia Technologies Division Emuzed India Bangalore www.emuzed.com ----- Original Message ----- From: "Vinod Kumar" To: Sent: Thursday, September 27, 2023 1:35 PM Subject: [M4IF Technotes] Quarterpel motion estimation > HI > Has any one worked on quarterpel motion estimation. Is the > interpolation for quarterpel done every macroblock or is the entire vop > interpolated. Since half pel is bilinear interpolation, there wouldnt be > a problem if the interpolation is done on one entire vop... but is that > the case with quarterpel also? > > regards > kmr > _______________________________________________ > Technotes mailing list > Technotes@lists.m4if.org > http://lists.m4if.org/mailman/listinfo/technotes > > From rkoenen intertrust.com Thu Sep 27 09:48:32 2001 From: rkoenen intertrust.com (Rob Koenen) Date: Wed Jul 30 14:06:55 2003 Subject: [M4IF Technotes] *.mp4 Message-ID: <720AE932C238D411B4D100C04F10DA6B03CB95FB@exchange.epr.com> > I need information about the MPEG-4 fileformat, especially how the > hinting works. > (Standard number, Best standard reference 14496-1:2001 (to be published on 1 Oct 2023) Also look at all the Quicktime documentation there is around. Also look at http://www.m4if.org/resources.html for pointers to resources Rob From anuradha smartyantra.com Fri Sep 28 18:32:23 2001 From: anuradha smartyantra.com (anuradha) Date: Wed Jul 30 14:06:55 2003 Subject: [M4IF Technotes] max size in simple profile Message-ID: Hi, Can someone help me with the maximum frame size supported by simple profile? The standard says, "typical session size" as CIF for level3. Does it mean I cant encode any frame larger than CIF( 352 x 288 x 30 ) using simple profile? Regards Anuradha From Prabhudev_Hosur objectvideo.com Fri Sep 28 10:24:20 2001 From: Prabhudev_Hosur objectvideo.com (Prabhudev Hosur) Date: Wed Jul 30 14:06:55 2003 Subject: [M4IF Technotes] max size in simple profile In-Reply-To: Message-ID: <000601c14820$e2697540$1e10a8c0@atom.dbvision.net> Hi If you are decoding a dingle VO in simple profile level-3, then you can decode any frame, which has total number of macroblocks <= 396 (e.g., a frame of size 640x144). Furthermore, Max. VMV buffer size of 792 and VCV decoder rate of 11880 have to be satisfied. Regards, Prabhu ObjectVideo -----Original Message----- From: technotes-admin@lists.m4if.org [mailto:technotes-admin@lists.m4if.org]On Behalf Of anuradha Sent: Friday, September 28, 2023 8:02 AM To: technotes@lists.m4if.org Subject: [M4IF Technotes] max size in simple profile Hi, Can someone help me with the maximum frame size supported by simple profile? The standard says, "typical session size" as CIF for level3. Does it mean I cant encode any frame larger than CIF( 352 x 288 x 30 ) using simple profile? Regards Anuradha _______________________________________________ Technotes mailing list Technotes@lists.m4if.org http://lists.m4if.org/mailman/listinfo/technotes From anuradha smartyantra.com Sat Sep 29 17:59:39 2001 From: anuradha smartyantra.com (anuradha) Date: Wed Jul 30 14:06:55 2003 Subject: [M4IF Technotes] max size in simple profile In-Reply-To: <000601c14820$e2697540$1e10a8c0@atom.dbvision.net> Message-ID: Hi, I am trying to encode a frame of arbitrary size, greater than CIF using Simple Profile. Short Video Header format doesn't allow me to use arbitary sizes( Table 6.25 in visual standard ). Can I achieve this by using 4 Vidoe Objects each of size less than or equal to CIF? In simple Profile L3, if I use 4 Video Objects, then what is the Maximun total area of 4 Video Object Planes? Is it 396x4 macroblocks or just 396 macroblocks ? Thanks Regards Anuradha Subject: RE: [M4IF Technotes] max size in simple profile Hi If you are decoding a dingle VO in simple profile level-3, then you can decode any frame, which has total number of macroblocks <= 396 (e.g., a frame of size 640x144). Furthermore, Max. VMV buffer size of 792 and VCV decoder rate of 11880 have to be satisfied. Regards, Prabhu ObjectVideo -----Original Message----- From: technotes-admin@lists.m4if.org [mailto:technotes-admin@lists.m4if.org]On Behalf Of anuradha Sent: Friday, September 28, 2023 8:02 AM To: technotes@lists.m4if.org Subject: [M4IF Technotes] max size in simple profile Hi, Can someone help me with the maximum frame size supported by simple profile? The standard says, "typical session size" as CIF for level3. Does it mean I cant encode any frame larger than CIF( 352 x 288 x 30 ) using simple profile? Regards Anuradha _______________________________________________ Technotes mailing list Technotes@lists.m4if.org http://lists.m4if.org/mailman/listinfo/technotes _______________________________________________ Technotes mailing list Technotes@lists.m4if.org http://lists.m4if.org/mailman/listinfo/technotes From ramki emuzed.com Sun Sep 30 17:52:10 2001 From: ramki emuzed.com (Ramkishor Korada) Date: Wed Jul 30 14:06:55 2003 Subject: [M4IF Technotes] max size in simple profile References: Message-ID: <00bc01c149a2$28730240$1b0aa8c0@blr.emuzed.com> Hi, ----- Original Message ----- From: "anuradha" To: Sent: Saturday, September 29, 2023 4:59 PM Subject: RE: [M4IF Technotes] max size in simple profile > Hi, > > I am trying to encode a frame of arbitrary size, greater than CIF using > Simple Profile. Short Video Header format > doesn't allow me to use arbitary sizes( Table 6.25 in visual standard ). Arbitrary sizes can be used, but not greater than CIF size. > Can I achieve this by using 4 Vidoe Objects each of size less than or > equal to CIF? Yes. it is possible. > In simple Profile L3, if I use 4 Video Objects, then what is the Maximun > total area of 4 Video Object Planes? Is it 396x4 > macroblocks or just 396 macroblocks ? The max. no. macroblocks for all the four video objects is 396. > > Thanks > > Regards > Anuradha > > Subject: RE: [M4IF Technotes] max size in simple profile > Hi > > If you are decoding a dingle VO in simple profile level-3, then you can > decode any frame, which has total number of macroblocks <= 396 (e.g., a > frame of size 640x144). > Furthermore, Max. VMV buffer size of 792 and VCV decoder rate of 11880 have > to be satisfied. > > Regards, > Prabhu > ObjectVideo > > -----Original Message----- > From: technotes-admin@lists.m4if.org > [mailto:technotes-admin@lists.m4if.org]On Behalf Of anuradha > Sent: Friday, September 28, 2023 8:02 AM > To: technotes@lists.m4if.org > Subject: [M4IF Technotes] max size in simple profile > > Hi, > Can someone help me with the maximum frame size supported by simple profile? > The standard says, "typical session size" as > CIF for level3. Does it mean I cant encode any frame larger than CIF( 352 x > 288 x 30 ) using simple profile? > > Regards > Anuradha > > > > _______________________________________________ > Technotes mailing list > Technotes@lists.m4if.org > http://lists.m4if.org/mailman/listinfo/technotes > > _______________________________________________ > Technotes mailing list > Technotes@lists.m4if.org > http://lists.m4if.org/mailman/listinfo/technotes > > _______________________________________________ > Technotes mailing list > Technotes@lists.m4if.org > http://lists.m4if.org/mailman/listinfo/technotes > > From dim psytel-research.co.yu Sun Sep 30 11:50:23 2001 From: dim psytel-research.co.yu (Ivan Dimkovic) Date: Wed Jul 30 14:06:55 2003 Subject: [M4IF Technotes] MPEG-4 V2 Audio Reference Software Message-ID: <000201c149a1$3ed36c10$0100a8c0@hal> Hi all, Does anybody know the status of the MPEG-4 V2 Audio Reference Software (incorporating AAC Low-Delay, and ER tools), known as 14496-5 AMD1 ? Is it (and when) planned for release? We need AAC LD decoder in order to test and debug optimized Low-Delay encoder. Kindest Regards, ************************************************* Ivan Dimkovic, MPEG-4 Solutions Developer PsyTEL Research Multimedia Coding Solutions Belgrade, Yugoslavia phone: +381 64 11 40 600 +381 63 264 334 fax: +381 11 32 25 275 email: dim@psytel-research.co.yu www: http://www.psytel-research.co.yu *************************************************