[Mp4-tech] Is SP@LL supported for MPEG-2 video?

[Hughes Gary-DJWV76]

There is normative text in clause 8 of 13818-2 to the effect that a
decoder that supports SP ML MUST also be capable of decoding MP LL, so
by inference all legal MPEG-2 decoders are capable of decoding B
pictures.
The only level apparently defined for SP is ML. I don't think that
precludes you specifying SP LL in the bitstream, but it has no meaning
as an interoperability point. The profile and levels specify maxima;
there is nothing to preclude you encoding QCIF with I and P only in MP.
In practical terms, MP LL with low_delay set may be a better way of
expressing your requirements. 
gary
Gary Hughes
Video Architect, Advanced Engineering
Motorola On Demand Solutions, MA34
80 Central St.
Boxborough, MA  01719
Email: ghughes motorola.com
Office: 978 266 7269
Mobile: 978 339 3615
> -----Original Message-----
> From: mp4-tech-bounces lists.mpegif.org 
> [mailto:mp4-tech-bounces lists.mpegif.org] On Behalf Of Narendra Joshi
> Sent: Thursday, July 19, 2023 6:39 AM
> To: Gary Sullivan; mp4-tech lists.mpegif.org
> Subject: RE: [Mp4-tech] Is SP LL supported for MPEG-2 video?
> 
> 
> Annex E says that this clause it informative. 
> Also, table E.21, they have specified upper limit on the 
> sample density (image size and fps), bit-rate, VBV buffer 
> size. Does that mean any thing below the allowed limits (i.e. 
> MPEG-2 encoding for QCIF at 10 fps using I & P frames only) 
> is not an 'illegal' combination - so to say..?
> 
> Awaiting for reply,
> 
> thanks & regards,
> Narendra 
> 
> 
> -----Original Message-----
> From: Gary Sullivan [mailto:garysull windows.microsoft.com]
> Sent: Thursday, July 19, 2023 12:51 PM
> To: Narendra Joshi; mp4-tech lists.mpegif.org
> Subject: RE: [Mp4-tech] Is SP LL supported for MPEG-2 video?
> 
> 
> In a quick glance at the spec (not the latest version, but I don't
> recall a change to that aspect and don't have the battery 
> power to check
> further), I only found Main level for the Simple profile of 
> MPEG-2 video
> (Annex E Table E.21).
> 
> Best Regards,
> 
> Gary Sullivan 
> 
> +> -----Original Message-----
> +> From: mp4-tech-bounces lists.mpegif.org 
> +> [mailto:mp4-tech-bounces lists.mpegif.org] On Behalf Of Narendra 
> +> Joshi
> +> Sent: Wednesday, July 18, 2023 4:45 AM
> +> To: mp4-tech lists.mpegif.org
> +> Subject: [Mp4-tech] Is SP LL supported for MPEG-2 video?
> +> 
> +> 
> +> Hello,
> +> 
> +> Would like to know if SP LL (Simple Profile at low-level) 
> supported 
> +> in
> +> MPEG-2 video standard or not...
> +> 
> +> When I searched on internet, there are docs that say only Main 
> +> profile supports low-level, not simple profile.
> +> Also there are docs indicating - SP LL is valid combination for 
> +> MPEG-2 video.
> +> 
> +> My interest is, to get/create MPEG-2 compressed video streams for 
> +> QCIF size data, compressed at 10-12-15 fps, with bit rates in the 
> +> range 100 kbps to 400 kbps, with only I & P type frames (i.e. no B 
> +> frames). Am not sure whether this is an allowed legal 
> combination in 
> +> MPEG-2 though....
> +> And thus such streams would be prevalent in the market...
> +> 
> +> Would be helpful if someone replies with some concrete info..
> +> 
> +> thanks & regards,
> +> Narendra
> +> SASKEN BUSINESS DISCLAIMER
> +> -------------------------
> +> This message may contain confidential, proprietary or legally 
> +> privileged information. In case you are not the original intended 
> +> Recipient of the message, you must not, directly or 
> indirectly, use, 
> +> Disclose, distribute, print, or copy any part of this 
> message and you
> 
> +> are requested to delete it and inform the sender. Any 
> views expressed
> 
> +> in this message are those of the individual sender unless 
> otherwise 
> +> stated.
> +> Nothing contained in this message
> +> shall be construed as an offer or acceptance of any offer 
> by Sasken 
> +> Communication Technologies Limited ("Sasken") unless sent 
> with that 
> +> express intent and with due authority of Sasken. Sasken has taken 
> +> enough precautions to prevent the spread of viruses. However the 
> +> company accepts no liability for any damage caused by any virus 
> +> transmitted by this email
> +> 
> +> _______________________________________________
> +> NOTE: Please use clear subject lines for your posts. 
> Include [audio, 
> +> [video], [systems], [general] or another apppropriate 
> identifier to 
> +> indicate the type of question you have.
> +> 
> +> Note: Conduct on the mailing list is subject to the Antitrust 
> +> guidelines found at 
> +> http://www.mpegif.org/public/documents/vault/mp-out-30042-Ant
> +> itrust.php
> +> 
> SASKEN BUSINESS DISCLAIMER
> -------------------------
> This message may contain confidential, proprietary or legally 
> privileged information. In 
> case you are not the original intended Recipient of the 
> message, you must not, directly or 
> indirectly, use, Disclose, distribute, print, or copy any 
> part of this message and you are 
> requested to delete it and inform the sender. Any views 
> expressed in this message are 
> those of the individual sender unless otherwise stated. 
> Nothing contained in this message 
> shall be construed as an offer or acceptance of any offer by 
> Sasken Communication 
> Technologies Limited ("Sasken") unless sent with that express 
> intent and with due 
> authority of Sasken. Sasken has taken enough precautions to 
> prevent the spread of 
> viruses. However the company accepts no liability for any 
> damage caused by any virus 
> transmitted by this email
> 
> _______________________________________________
> NOTE: Please use clear subject lines for your posts. Include 
> [audio, [video], [systems], [general] or another apppropriate 
> identifier to indicate the type of question you have.
> 
> Note: Conduct on the mailing list is subject to the Antitrust 
> guidelines found at 
> http://www.mpegif.org/public/documents/vault/mp-out-30042-Anti
> trust.php
>