From rkoenen intertrust.com Fri Jun 1 00:41:54 2001 From: rkoenen intertrust.com (Rob Koenen) Date: Wed Jul 30 14:06:33 2003 Subject: [M4IF Technotes] help about 14496-1 version 2 Message-ID: <720AE932C238D411B4D100C04F10DA6B032BC97F@exchange.epr.com> http://www.iso.ch/iso/en/CatalogueDetailPage.CatalogueDetail?ICS1=35&ICS2=40 &ICS3=0&CSNUMBER=24462 links to 14496-1:1999 - the 1999 version of MPEG-4 Systems Olivier, does that include Version 2? If not, when will the 2000 edition be available from ISO? Thanks, Rob -----Original Message----- From: Liang Cheng [mailto:lcheng61@hotmail.com] Sent: Wednesday, 30 May, 2001 15:54 To: technotes@lists.m4if.org Subject: [M4IF Technotes] help about 14496-1 version 2 Dear all, Now we met a trouble when we studied the interactivities between MPEG-4 node and human. We are unfortunately using 14496-1:1999(E) Date 1998-12-18, and the serial number of this document is N2501. Obviously, it is MPEG-4 system on version 1. We just heard the version 2 has already come up and it includes more advanced user interaction function. We look forward to obtaining it. Can someone of you tell me where we can buy the MPEG-4 standard serials in version 2? We will be appreciate it if you may help us. Liang _____ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com . _______________________________________________ Technotes mailing list Technotes@lists.m4if.org http://lists.m4if.org/mailman/listinfo/technotes -------------- next part -------------- An HTML attachment was scrubbed... URL: /pipermail/mp4-tech/attachments/20010531/74b90c57/attachment.html From olivier.avaro francetelecom.com Sun Jun 3 02:31:59 2001 From: olivier.avaro francetelecom.com (AVARO Olivier FTRD/DIH) Date: Wed Jul 30 14:06:33 2003 Subject: [M4IF Technotes] help about 14496-1 version 2 In-Reply-To: <720AE932C238D411B4D100C04F10DA6B032BC97F@exchange.epr.com> Message-ID: <000a01c0ebc0$e197bd00$0b436a20@rptw2kavaro> Hi all, Olivier, does that include Version 2? Yes. If not, when will the 2000 edition be available from ISO? First, it's not 2000 but 2001. The ISO secretariat is waiting for the proof of 14496-1:2001 from ITTF. So it should be here soon. cu, O. -------------- next part -------------- An HTML attachment was scrubbed... URL: /pipermail/mp4-tech/attachments/20010603/b9736f84/attachment.html From Jeyur.Patel Mysoremail.ltitl.com Mon Jun 4 13:30:08 2001 From: Jeyur.Patel Mysoremail.ltitl.com (Jeyur.Patel@Mysoremail.ltitl.com) Date: Wed Jul 30 14:06:34 2003 Subject: [M4IF Technotes] Doubt Message-ID: <65256A61.0026776F.00@Mysoremail.ltitl.com> Dear all, We have a basic doubt about MPEG-4 visual encoder and decoder Verification Model Software. We have got two Reference software for MPEG-4 visual natural CODECs, supplied with MPEG-4 standard ISO/IEC 14496-5, one is implementation of MPEG-4 visual natural encoder & decoder in 'ANSI C' and other is implementation of same in C++. We would like to know the Visual Profile and Level implementated in these Reference Software. Does it support Visual Simple Profile @ Level 3 ? Regards, Jeyur From rudinei icmc.sc.usp.br Mon Jun 4 15:24:05 2001 From: rudinei icmc.sc.usp.br (Rudinei Goularte) Date: Wed Jul 30 14:06:34 2003 Subject: [M4IF Technotes] mpeg-4 referece software Message-ID: <3B1BC435.C814985@icmc.sc.usp.br> Hi all! I've tried to compile the IM1Player (core) released by ISO as the MPEG-4 reference software at: http://isotc.iso.ch/livelink/livelink/fetch/2000/2489/Ittf_Home/PubliclyAvailableStandards.htm/ (look for 14496-5). I'm using Microsoft Visual C ++ v. 5.0 under Windows 98. The problem is that the compiler returns errors (see below). Fixing (I think) some parts of the code I found that some methods are not implemented. Is it true? I have to "fill in the blanks"? Or have ISO relesead a wrong version? Can someone help-me? Thanks in advance. Rudinei. " DMIFClientFilter.cpp ..\..\Include\ztl.h(233) : error C2678: binary '==' : no operator defined which takes a left-hand operand of type 'struct McteSlot' (or there is no acceptable conversion) FlexDmux.cpp ..\..\Include\ztl.h(233) : error C2678: binary '==' : no operator defined which takes a left-hand operand of type 'struct McteSlot' (or there is no acceptable conversion) MyChannel.cpp ..\..\Include\ztl.h(233) : error C2678: binary '==' : no operator defined which takes a left-hand operand of type 'struct McteSlot' (or there is no acceptable conversion) Error executing cl.exe. " From jean-claude.dufourd enst.fr Tue Jun 5 11:07:02 2001 From: jean-claude.dufourd enst.fr (Jean-Claude Dufourd) Date: Wed Jul 30 14:06:34 2003 Subject: [M4IF Technotes] mpeg-4 referece software References: <3B1BC435.C814985@icmc.sc.usp.br> Message-ID: <3B1C9326.A5F918A3@enst.fr> Rudinei Goularte wrote: > I'm using Microsoft Visual C ++ v. 5.0 under Windows 98. I have used only VC++ 6 for a long time. I believe you have to use v6 to compile the Systems reference software. Best regards JC -- Jean-Claude Dufourd @======================================@ ENST, Dept COMELEC The wing, over the big rock... 46, rue Barrault @======================================@ 75013 Paris Tel: +33145817807 Fax: +33145804036 From yossi neomagic.co.il Tue Jun 5 17:02:11 2001 From: yossi neomagic.co.il (Yossi) Date: Wed Jul 30 14:06:34 2003 Subject: [M4IF Technotes] Method 1 Quantisation Message-ID: <001601c0edc8$1e571700$64f95ac2@asp.co.il> Sirs, MPEG4 Video Verification Model (VM 16.0) presents two quantisation methods: H263 and MPEG4 (pp. 61-63). Section 3.4.4.2 describes Method 1 (H263), where Intra DC quantisation is level = dc_coeff // 8 Section 3.4.5.1.1 describes Method 2 (MPEG4), where Intra DC quantisation is level = dc_coeff//dc_scaler, where dc_scaler is a non-linear scaler based on Qp. However, Section 3.4.5.1.1 states, "Note: This section is valid for H.263 quantisation also." Is the Intra DC quantisation method presented in Sec. 3.4.4.2 incorrect? In particular, I am looking at the Simple Profile that allows only Method 1 for quantization (see Table 9-1 in Part 2 of the MPEG4 Standard, page 201). Should Intra DC quantisation for Simple Profile follow Section 3.4.4.2 or Section 3.4.5.1.1? Thank you, Yossi Shain NeoMagic Israel From peterh videospheres.com Tue Jun 5 10:27:44 2001 From: peterh videospheres.com (Peter Haighton) Date: Wed Jul 30 14:06:34 2003 Subject: [M4IF Technotes] Method 1 Quantisation In-Reply-To: <001601c0edc8$1e571700$64f95ac2@asp.co.il> Message-ID: Hi Yossi, The standard states that level = dc_coeff//dc_scaler but it also says that for H.263 (short header=1) dc_scaler is always 8 so that means that both sections are correct. Hope this helps Peter -----Original Message----- From: technotes-admin@lists.m4if.org [mailto:technotes-admin@lists.m4if.org]On Behalf Of Yossi Sent: Tuesday, June 05, 2023 10:02 AM To: technotes@lists.m4if.org Subject: [M4IF Technotes] Method 1 Quantisation Sirs, MPEG4 Video Verification Model (VM 16.0) presents two quantisation methods: H263 and MPEG4 (pp. 61-63). Section 3.4.4.2 describes Method 1 (H263), where Intra DC quantisation is level = dc_coeff // 8 Section 3.4.5.1.1 describes Method 2 (MPEG4), where Intra DC quantisation is level = dc_coeff//dc_scaler, where dc_scaler is a non-linear scaler based on Qp. However, Section 3.4.5.1.1 states, "Note: This section is valid for H.263 quantisation also." Is the Intra DC quantisation method presented in Sec. 3.4.4.2 incorrect? In particular, I am looking at the Simple Profile that allows only Method 1 for quantization (see Table 9-1 in Part 2 of the MPEG4 Standard, page 201). Should Intra DC quantisation for Simple Profile follow Section 3.4.4.2 or Section 3.4.5.1.1? Thank you, Yossi Shain NeoMagic Israel _______________________________________________ Technotes mailing list Technotes@lists.m4if.org http://lists.m4if.org/mailman/listinfo/technotes From peterh videospheres.com Tue Jun 5 12:33:47 2001 From: peterh videospheres.com (Peter Haighton) Date: Wed Jul 30 14:06:34 2003 Subject: [M4IF Technotes] mpeg-4 referece software Message-ID: Hello Rudinei, Olivier Avaro forwarded your question to the implementation group inside MPEG and here is the response that was received. Hope this helps. Thanks Olivier for your help. Peter -----Original Message----- From: owner-im1-sys@advent.ee.columbia.edu [mailto:owner-im1-sys@advent.ee.columbia.edu]On Behalf Of Wo Chang Sent: Tuesday, June 05, 2023 11:25 AM To: Franceschini Guido; olivier.avaro@francetelecom.com; Ref. Sys Im1 (E-mail) Subject: Re: [M4IF Technotes] mpeg-4 referece software Dear Rudinei, Guido is correct, you have to use VC6 in order to compile. It is specially true for DMIFClientFilter since its .dsp was generated by the earlier version of VCC (VC5). Before compiling IM1Player via VC6, you need to disable the DMIFClientFilter.dsp from READ-ONLY, so that VC6 can generate DMIFClientFilter.dsp for VC6. You also need to disable the READ-ONLY for the libs in IM1Core\Lib since a new set of libs will be written into this dir. I think this will get you going with the compilation. Have fun. --Wo ----- Original Message ----- From: "Franceschini Guido" To: ; "Ref. Sys Im1 (E-mail)" Sent: Tuesday, June 05, 2023 3:20 AM Subject: RE: [M4IF Technotes] mpeg-4 referece software > The code released always compiled (with VC6), but I remember someone having > troubles using VC5. > I suggest using VC6. > > Guido > > -----Original Message----- > From: AVARO Olivier FTRD/DIH [mailto:olivier.avaro@francetelecom.com] > Sent: Tuesday, June 05, 2023 7:26 AM > To: Ref. Sys Im1 (E-mail) > Subject: TR: [M4IF Technotes] mpeg-4 referece software > > > > Can someone help ? > cu, > O. > -----Message d'origine----- > De : technotes-admin@lists.m4if.org > [mailto:technotes-admin@lists.m4if.org]De la part de Rudinei Goularte > Envoye : lundi 4 juin 2001 19:24 > A : technotes@lists.m4if.org > Objet : [M4IF Technotes] mpeg-4 referece software > > > Hi all! > > I've tried to compile the IM1Player (core) released by ISO as the > MPEG-4 reference software at: > http://isotc.iso.ch/livelink/livelink/fetch/2000/2489/Ittf_Home/PubliclyAvai > lableStandards.htm/ > > (look for 14496-5). > > I'm using Microsoft Visual C ++ v. 5.0 under Windows 98. > > The problem is that the compiler returns errors (see below). Fixing (I > think) some parts of the code I found that some methods are not > implemented. Is it true? I have to "fill in the blanks"? Or have ISO > relesead a wrong version? > Can someone help-me? > > Thanks in advance. > > Rudinei. > > " > DMIFClientFilter.cpp > ..\..\Include\ztl.h(233) : error C2678: binary '==' : no operator > defined which takes a left-hand operand of type 'struct McteSlot' (or > there is no acceptable conversion) > FlexDmux.cpp > ..\..\Include\ztl.h(233) : error C2678: binary '==' : no operator > defined which takes a left-hand operand of type 'struct McteSlot' (or > there is no acceptable conversion) > MyChannel.cpp > ..\..\Include\ztl.h(233) : error C2678: binary '==' : no operator > defined which takes a left-hand operand of type 'struct McteSlot' (or > there is no acceptable conversion) > Error executing cl.exe. > " > > > _______________________________________________ > Technotes mailing list > Technotes@lists.m4if.org > http://lists.m4if.org/mailman/listinfo/technotes From pertti.lihavainen hulikakku.suomi.net Wed Jun 6 23:01:28 2001 From: pertti.lihavainen hulikakku.suomi.net (Pertti Lihavainen) Date: Wed Jul 30 14:06:34 2003 Subject: [M4IF Technotes] Subscribing to Technotes Message-ID: <007801c0eecb$dbd7d220$090b000a@suomi.net> Subscribing Pertti Lihavainen Koulukatu 32 D 56 90100 Oulu Finland pertti.lihavainen@hulikakku.suomi.net From rkoenen intertrust.com Thu Jun 7 17:27:03 2001 From: rkoenen intertrust.com (Rob Koenen) Date: Wed Jul 30 14:06:34 2003 Subject: [M4IF Technotes] re: doubt Message-ID: <720AE932C238D411B4D100C04F10DA6B032BD0F3@exchange.epr.com> -----Original Message----- From: Wollborn Michael (FV/SLM) * [mailto:Michael.Wollborn@de.bosch.com] Sent: Thursday, 07 June, 2001 5:41 To: Cc: 'Rob Koenen' Subject: Dear Jeyur, > We would like to know the Visual Profile and Level > implementated in these > Reference Software. > > Does it support Visual Simple Profile @ Level 3 ? the version 1 Reference Software should support all profiles defined in the version 1 of the Standard. Hence, regarding your question, it should also support the Visual Simple Profile. With respect to levels things get more complex, since the reference software was not designed to test conformance. And since it is a software solution, some parameters defined in the level may not apply. Therefore, I think the correct answer with this respect is that you can not really say it supports a certain level, since that also depends on the hardware used etc. Hope this helps. If you have any further related question don't hesitate to ask. Best Regards, Michael _______________________________________________________________________ Dipl.-Ing. Dipl.-Wirt.-Ing. Michael Wollborn Robert Bosch GmbH Phone: +49 5121 49 5017 FV/SLM, PO Box 777777 Fax: +49 5121 49 17 5017 31132 Hildesheim Email: Michael.Wollborn@de.bosch.com Germany http://www.tnt.uni-hannover.de/~wollborn _______________________________________________________________________ "It follows that the Scientist, like the Pilgrim, must wend a straight and narrow path between the Pitfalls of Oversimplification and the Morass of Overcomplication" - Richard Bellman _______________________________________________________________________ From rkoenen intertrust.com Fri Jun 8 00:45:21 2001 From: rkoenen intertrust.com (Rob Koenen) Date: Wed Jul 30 14:06:34 2003 Subject: FW: [M4IF Technotes] mpeg-4 referece software Message-ID: <720AE932C238D411B4D100C04F10DA6B032BD176@exchange.epr.com> -----Original Message----- From: owner-im1-sys@advent.ee.columbia.edu [mailto:owner-im1-sys@advent.ee.columbia.edu]On Behalf Of Wo Chang Sent: Tuesday, 05 June, 2001 8:25 To: Franceschini Guido; olivier.avaro@francetelecom.com; Ref. Sys Im1 (E-mail) Subject: Re: [M4IF Technotes] mpeg-4 referece software Dear Rudinei, Guido is correct, you have to use VC6 in order to compile. It is specially true for DMIFClientFilter since its .dsp was generated by the earlier version of VCC (VC5). Before compiling IM1Player via VC6, you need to disable the DMIFClientFilter.dsp from READ-ONLY, so that VC6 can generate DMIFClientFilter.dsp for VC6. You also need to disable the READ-ONLY for the libs in IM1Core\Lib since a new set of libs will be written into this dir. I think this will get you going with the compilation. Have fun. --Wo ----- Original Message ----- From: "Franceschini Guido" To: ; "Ref. Sys Im1 (E-mail)" Sent: Tuesday, June 05, 2023 3:20 AM Subject: RE: [M4IF Technotes] mpeg-4 referece software > The code released always compiled (with VC6), but I remember someone having > troubles using VC5. > I suggest using VC6. > > Guido > > -----Original Message----- > From: AVARO Olivier FTRD/DIH [mailto:olivier.avaro@francetelecom.com] > Sent: Tuesday, June 05, 2023 7:26 AM > To: Ref. Sys Im1 (E-mail) > Subject: TR: [M4IF Technotes] mpeg-4 referece software > > > > Can someone help ? > cu, > O. > -----Message d'origine----- > De : technotes-admin@lists.m4if.org > [mailto:technotes-admin@lists.m4if.org]De la part de Rudinei Goularte > Envoye : lundi 4 juin 2001 19:24 > A : technotes@lists.m4if.org > Objet : [M4IF Technotes] mpeg-4 referece software > > > Hi all! > > I've tried to compile the IM1Player (core) released by ISO as the > MPEG-4 reference software at: > http://isotc.iso.ch/livelink/livelink/fetch/2000/2489/Ittf_Home/PubliclyAvai > lableStandards.htm/ > > (look for 14496-5). > > I'm using Microsoft Visual C ++ v. 5.0 under Windows 98. > > The problem is that the compiler returns errors (see below). Fixing (I > think) some parts of the code I found that some methods are not > implemented. Is it true? I have to "fill in the blanks"? Or have ISO > relesead a wrong version? > Can someone help-me? > > Thanks in advance. > > Rudinei. > > " > DMIFClientFilter.cpp > ..\..\Include\ztl.h(233) : error C2678: binary '==' : no operator > defined which takes a left-hand operand of type 'struct McteSlot' (or > there is no acceptable conversion) > FlexDmux.cpp > ..\..\Include\ztl.h(233) : error C2678: binary '==' : no operator > defined which takes a left-hand operand of type 'struct McteSlot' (or > there is no acceptable conversion) > MyChannel.cpp > ..\..\Include\ztl.h(233) : error C2678: binary '==' : no operator > defined which takes a left-hand operand of type 'struct McteSlot' (or > there is no acceptable conversion) > Error executing cl.exe. > " > > > _______________________________________________ > Technotes mailing list > Technotes@lists.m4if.org > http://lists.m4if.org/mailman/listinfo/technotes From Jani.Huoponen hantro.com Mon Jun 11 08:18:21 2001 From: Jani.Huoponen hantro.com (Jani Huoponen) Date: Wed Jul 30 14:06:34 2003 Subject: [M4IF Technotes] Ac prediction Message-ID: Hi all, There seems to be one vague point in the Visual standard regarding the AC prediction, I would like to have your opinion on the interpretation of the standard. So the question is: What values are supposed to use in ac prediction if type of the prediction block (block 'A' or block 'C') is not intra? Standard does not seem to impose any restrictions on usage of inter blocks as ac predictor blocks but video verification model seems to specify that they should be handled the same way as blocks outside the VOP or video packet (i.e. use zero values as predictors instead of actual inter block ac coefficient values). BR, Jani ------------------------------------------------------------ Jani Huoponen Engineering Manager, System Design Hantro Products Oy Nahkatehtaankatu 2, 90100 Oulu, Finland +358-40-5272676 ------------------------------------------------------------ From ramki emuzed.com Mon Jun 11 18:51:03 2001 From: ramki emuzed.com (Ramkishor Korada) Date: Wed Jul 30 14:06:34 2003 Subject: [M4IF Technotes] Ac prediction References: Message-ID: <035b01c0f270$fd67c870$0d0aa8c0@blr.emuzed.com> Hi, When the block is not Intra (Inter), then they should be handled the same way as blocks outside VOP or packet i.e., use zero values as predictors. warm regards, ramkishor Architect - Video Digital Media Technology Division Emuzed Bangalore Division IndiraNagar,Bangalore www.emuzed.com ----- Original Message ----- From: "Jani Huoponen" To: Sent: Monday, June 11, 2023 9:48 AM Subject: [M4IF Technotes] Ac prediction > Hi all, > > There seems to be one vague point in the Visual standard regarding the AC > prediction, I would like to have your opinion on the interpretation of the > standard. > > So the question is: > > What values are supposed to use in ac prediction if type of the prediction > block (block 'A' or block 'C') is not intra? Standard does not seem to > impose any restrictions on usage of inter blocks as ac predictor blocks but > video verification model seems to specify that they should be handled the > same way as blocks outside the VOP or video packet (i.e. use zero values as > predictors instead of actual inter block ac coefficient values). > > 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 HerpelC thmulti.com Mon Jun 11 17:01:17 2001 From: HerpelC thmulti.com (Herpel Carsten) Date: Wed Jul 30 14:06:34 2003 Subject: [M4IF Technotes] Ac prediction Message-ID: <2CEEE9E85750D2119F4000805F317288DD8316@hanexch1.hanover.thmulti.com> The issue is: If this cannot be read unambiguously from the spec, a Corrigendum should be made to remove this ambiguity. Is it ambiguous from the written spec? Regards, Carsten +-----------------------------------------------------------+ | THOMSON multimedia -------------------------- CR Hannover | +-----------------------------------------------------------+ | Carsten Herpel | | Deutsche Thomson-Brandt GmbH | | Karl-Wiechert-Allee 74 Tel.: +49 511 418 2510 | | 30625 Hannover Fax.: +49 511 418 2483 | | Germany mailto:herpelc@thmulti.com | +-----------------------------------------------------------+ -----Original Message----- From: Ramkishor Korada [mailto:ramki@emuzed.com] Sent: 11 June, 2001 14:21 To: Jani Huoponen; technotes@lists.m4if.org Subject: Re: [M4IF Technotes] Ac prediction Hi, When the block is not Intra (Inter), then they should be handled the same way as blocks outside VOP or packet i.e., use zero values as predictors. warm regards, ramkishor Architect - Video Digital Media Technology Division Emuzed Bangalore Division IndiraNagar,Bangalore www.emuzed.com ----- Original Message ----- From: "Jani Huoponen" To: Sent: Monday, June 11, 2023 9:48 AM Subject: [M4IF Technotes] Ac prediction > Hi all, > > There seems to be one vague point in the Visual standard regarding the AC > prediction, I would like to have your opinion on the interpretation of the > standard. > > So the question is: > > What values are supposed to use in ac prediction if type of the prediction > block (block 'A' or block 'C') is not intra? Standard does not seem to > impose any restrictions on usage of inter blocks as ac predictor blocks but > video verification model seems to specify that they should be handled the > same way as blocks outside the VOP or video packet (i.e. use zero values as > predictors instead of actual inter block ac coefficient values). > > 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 pertti.lihavainen hulikakku.suomi.net Wed Jun 20 15:36:47 2001 From: pertti.lihavainen hulikakku.suomi.net (Pertti Lihavainen) Date: Wed Jul 30 14:06:34 2003 Subject: [M4IF Technotes] subscribed Message-ID: <002f01c0f98e$18ac2120$090b000a@suomi.net> Subscribed pertti.lihavainen@hulikakku.suomi.net -------------- next part -------------- An HTML attachment was scrubbed... URL: /pipermail/mp4-tech/attachments/20010620/894aed49/attachment.html From bj sasken.com Fri Jun 22 19:59:57 2001 From: bj sasken.com (B Jagadeesh) Date: Wed Jul 30 14:06:35 2003 Subject: [M4IF Technotes] GOV header for enhancement layer In-Reply-To: <035b01c0f270$fd67c870$0d0aa8c0@blr.emuzed.com> Message-ID: Dear All, Group of VOP (GOV) header is optional as per the MPEG-4 visual standard. In the case of temporal scalability, if an encoder decides to have a GOV header in the base layer, should the GOV header be present in the corresponding enhancement layer bit stream also? Can GOV header be present in the enhancement layer bit stream? Is it allowed as per MPEG-4 Visual standard? If base layer has GOV header and enhancement layer does not, then calculation of the Composition Time Stamp (CTS) for an enhancement layer VOP will depend on CTS of the Base layer VOPs. I request experts to comment on this. regards, B. Jagadeesh, Ph.D., Sasken Communication technologies Limited, Bangalore, Inida. From Jani.Huoponen hantro.com Tue Jun 26 09:22:20 2001 From: Jani.Huoponen hantro.com (Jani Huoponen) Date: Wed Jul 30 14:06:35 2003 Subject: [M4IF Technotes] Ac prediction Message-ID: Hi, Actually, this issue is not ambigous in the Visual standard, it does not say that you should treat inter blocks any differently from intra blocks. However, the video verification model document describes it other way, i.e., inter blocks should be treated as blocks outside of VOP or video packet (as Ramkishor says below). This interpretation seems to be quite common and if this is the way to do it then there should be a Corrigendum for it. Otherwise the Video Verification Model doc should be corrected to match the actual Visual standard. Which way to go? br, Jani > -----Original Message----- > From: Herpel Carsten [mailto:HerpelC@thmulti.com] > Sent: 11. kes?kuuta 2001 17:01 > To: technotes@lists.m4if.org > Subject: RE: [M4IF Technotes] Ac prediction > > > The issue is: If this cannot be read unambiguously from the spec, a > Corrigendum should be made to remove this ambiguity. > > Is it ambiguous from the written spec? > > Regards, > Carsten > +-----------------------------------------------------------+ > | THOMSON multimedia -------------------------- CR Hannover | > +-----------------------------------------------------------+ > | Carsten Herpel | > | Deutsche Thomson-Brandt GmbH | > | Karl-Wiechert-Allee 74 Tel.: +49 511 418 2510 | > | 30625 Hannover Fax.: +49 511 418 2483 | > | Germany mailto:herpelc@thmulti.com | > +-----------------------------------------------------------+ > > > > -----Original Message----- > From: Ramkishor Korada [mailto:ramki@emuzed.com] > Sent: 11 June, 2001 14:21 > To: Jani Huoponen; technotes@lists.m4if.org > Subject: Re: [M4IF Technotes] Ac prediction > > > Hi, > When the block is not Intra (Inter), then they should be > handled the same > way as blocks outside VOP or packet i.e., use zero values as > predictors. > > warm regards, > ramkishor > > Architect - Video > Digital Media Technology Division > Emuzed Bangalore Division > IndiraNagar,Bangalore > www.emuzed.com > > ----- Original Message ----- > From: "Jani Huoponen" > To: > Sent: Monday, June 11, 2023 9:48 AM > Subject: [M4IF Technotes] Ac prediction > > > > Hi all, > > > > There seems to be one vague point in the Visual standard > regarding the AC > > prediction, I would like to have your opinion on the > interpretation of the > > standard. > > > > So the question is: > > > > What values are supposed to use in ac prediction if type of > the prediction > > block (block 'A' or block 'C') is not intra? Standard does > not seem to > > impose any restrictions on usage of inter blocks as ac > predictor blocks > but > > video verification model seems to specify that they should > be handled the > > same way as blocks outside the VOP or video packet (i.e. > use zero values > as > > predictors instead of actual inter block ac coefficient values). > > > > 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 >