Ticket #394 (assigned defect)

Opened 3 years ago

Last modified 21 months ago

WebM bitrate is not set correcty

Reported by: Frans Owned by: Frans
Priority: minor Milestone: MediaMosa X.X
Component: Core Version:
Keywords: Cc:
MoSCoW: Must Have Estimated time after impact analysis:
Related to project: none Tested: yes
Accepted: yes Estimated Hours: 0

Description

In followup to ticket #295
http://mediamosa.org/trac/ticket/295

Original WebM file uploaded to VP-Core. Mime type is set correctly (video/webm), technical analysis is done correctly except for one thing: the bitrate. Transcode from WebM to flv (SURFmedia default preview) is going well. WebM file can be played in Chrome.

Another file in VP-core (original wmv) with a virtually empty transcoding profile (102) to webm. Transcode is going well, analysis is good, again a wrong bitrate is reported. Play succeeds again in chrome.

Change History

Changed 2 years ago by Frans

  • milestone changed from MediaMosa X.X to MediaMosa 2.4

Changed 2 years ago by Frans

  • moscow changed from Should Have to Must Have

Changed 2 years ago by forgacs

  • owner set to forgacs
  • status changed from new to assigned

Changed 2 years ago by forgacs

  • status changed from assigned to closed
  • resolution set to fixed

I have checked this issue with these Webm files:
 http://www.surfmedia.nl/medialibrary/item.html?id=i1cne64OVZG9UPGnjZdY9XkS
 http://www.surfmedia.nl/medialibrary/item.html?id=v1hPTf4wDNJNCEINmeERhoa6

These video files doesn't have bitrate according to ffmpeg. And it triggered this issue in vpx-analyse script.

Now I fixed it in that script.

Changed 2 years ago by robert

  • status changed from closed to reopened
  • resolution fixed deleted

Changed 2 years ago by robert

  • owner changed from forgacs to robert
  • status changed from reopened to assigned

Changed 2 years ago by robert

  • status changed from assigned to closed
  • resolution set to fixed

Changed 21 months ago by forgacs

Test: Upload a Webm mediafile.

Changed 21 months ago by Frans

  • status changed from closed to reopened
  • tested changed from no to yes
  • resolution fixed deleted

I did so with an upload of a WEBM video:

<app_id>33</app_id>
<asset_id>q1eUHtaF4YloCLh4hQW6dQZY</asset_id>
<mediafile_id>L2DYdrSQITjEsaiM9DE9WxvM</mediafile_id>

There still is empty bitrate info in the xml:

(<bitrate/>)

          <metadata>
            <video_codec>vp8</video_codec>
            <colorspace>yuv420p</colorspace>
            <width>1920</width>
            <height>912</height>
            <fps>23.98</fps>
            <audio_codec>vorbis</audio_codec>
            <sample_rate>48000</sample_rate>
            <channels>stereo</channels>
            <file_duration>00:02:00.38</file_duration>
            <container_type>matroska;webm</container_type>
            <bitrate/>
            <bpp/>
            <filesize>30810920</filesize>
            <mime_type>video/webm</mime_type>
            <is_hinted>FALSE</is_hinted>
            <is_inserted_md>FALSE</is_inserted_md>
          </metadata>

Also, the WLE doesn't know this video format:
Unknown format (matroska;webm)
But that is WLE related I guess.

Changed 21 months ago by forgacs

  • owner changed from robert to Frans
  • status changed from reopened to assigned

These video files doesn't have bitrate according to ffmpeg. It is the reason, that there isn't bitrate in the technical metadata.
In the previous version of MediaMosa we saw bitrate = 0. That was wrong. And it is fixed now.
I suggest to move this ticket to MediaMosa X.X till ffmpeg will provide bitrate information from these files.

Changed 21 months ago by Frans

  • accepted changed from no to yes
  • milestone changed from MediaMosa 3.0 to MediaMosa X.X

Ok. Fixed for now and moved to X.X for future modifications.

Note: See TracTickets for help on using tickets.