RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1713373 - ISO Media, MP4 Base Media v1 [IS0 14496-12:2003] not playing
Summary: ISO Media, MP4 Base Media v1 [IS0 14496-12:2003] not playing
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: gstreamer1
Version: 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Wim Taymans
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-23 13:43 UTC by Oliver Ilian
Modified: 2021-02-01 07:41 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-01 07:41:00 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Oliver Ilian 2019-05-23 13:43:47 UTC
Description of problem:
RHEL 8 cannot play mp4 files in "ISO Media, MP4 Base Media v1 [IS0 14496-12:2003]", but can play "ISO Media, MP4 v2 [ISO 14496-14]".

The file info for the not working file (it gives a full-screen green image)

Dimension: 1429 × 912
Codec: H.264 (High 4:4:4 Profile)
Framerate: 30 frames per second
Bitrate: 144 kbps

Version-Release number of selected component (if applicable):
rpm -qa | grep gstream | sort
gstreamer1-1.14.0-3.el8.x86_64
gstreamer1-plugins-bad-free-1.14.0-5.el8.x86_64
gstreamer1-plugins-base-1.14.0-4.el8.x86_64
gstreamer1-plugins-good-1.14.0-4.el8.x86_64
gstreamer1-plugins-good-gtk-1.14.0-4.el8.x86_64
gstreamer1-plugins-ugly-free-1.14.0-2.el8.x86_64
libnice-gstreamer1-0.1.14-7.20180504git34d6044.el8.x86_64
oneplay-gstreamer-codecs-pack-22-2.x86_64
PackageKit-gstreamer-plugin-1.1.12-2.el8.x86_64


How reproducible:
always

Steps to Reproduce:
1. download a movie in the format thats mentioned in the subject
2. play the video in totem


Actual results:
green screen, but sound is working

Expected results:
sound and video is working

Additional info:
The file can also not be played from Google drive in Firefox, but can be played in Google Chrome from Google drive

Comment 1 Oliver Ilian 2019-06-19 10:19:21 UTC
Do we have any update on this topic?

Thanks
Oliver

Comment 2 Wim Taymans 2019-08-13 13:15:36 UTC
where can I get oneplay-gstreamer-codecs-pack for testing?

Comment 5 Wim Taymans 2019-09-12 14:07:33 UTC
It looks like a bug/limitation of the oneplay codecs, I would suggest to let Fluendo take a look at it.

Comment 8 RHEL Program Management 2021-02-01 07:41:00 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


Note You need to log in before you can comment on or make changes to this bug.