Ticket #70 (closed defect: fixed)

Opened 4 years ago

Last modified 3 years ago

0016797: 4 [Analyse] Windows Media screencam wordt niet herkend als Windows Media

Reported by: admin Owned by: MC-Arjen
Priority: major Milestone: MediaMosa 2.2
Component: Core Version:
Keywords: Cc:
MoSCoW: Must Have Estimated time after impact analysis:
Related to project: none Tested: yes
Accepted: yes Estimated Hours: 3

Description

0016797: 4 [Analyse] Windows Media screencam wordt niet herkend als Windows Media
 http://mantis.kennisnet.nl/view.php?id=16797

Als een screencam opname, gemaakt met Windows Media Encoder wordt geanalyseerd, wordt deze niet herkend als Windows Media. Hierdoor wordt het juiste container type niet gezet, waarna de file niet streambaar is.

Zie output log in 'additional information'

ffmpeg heeft echter wel voldoende aanwijzingen dat het hier een 'MSS2' gecodeerde video betreft, en dus afspeelbaar zou kunnen zijn via de Windows Media streamers.

 http://en.wikipedia.org/wiki/Windows_Media_Video [] voor meer informatie over de parameters. Ik vermoed dat 'MSS1', 'WMVP' en 'WVP2' ook niet zullen werken. Van alle formaten zijn diverse video's in SURFmedia aanwezig.

Ik weet dat 'transcoding' niet goed gaat, en heb daar vrede mee. Maar bij de analyse mag best de conclusie getrokken worden dat het Windows Media betreft (content-type zetten), zodat de streaming wel goed gaat.

Change History

Changed 4 years ago by admin

ANALYSE job returned output: /mnt/naspcd1/vpx-acc/data/H/H7C8JhRh56y29tTFbkdKTT5X: could not find codec parameters - Error: Could not find codec parameters. This is most likely a problem with the encoding of the original media.

FFmpeg version SVN-r15936, Copyright (c) 2000-2008 Fabrice Bellard, et al.
configuration: --enable-libx264 --enable-gpl --enable-pthreads --enable-libmp3lame --enable-libfaac --enable-libfaad --enable-libvorbis --enable-libtheora --enable-libgsm --enable-libxvid
libavutil 49.12. 0 / 49.12. 0
libavcodec 52. 3. 0 / 52. 3. 0
libavformat 52.23. 1 / 52.23. 1
libavdevice 52. 1. 0 / 52. 1. 0
built on Nov 26 2008 10:17:33, gcc: 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)
[asf @ 0x89fc240]Could not find codec parameters (Video: MSS2 / 0x3253534D, 1288x1008, 250 kb/s)
/mnt/naspcd1/vpx-acc/data/H/H7C8JhRh56y29tTFbkdKTT5X: could not find codec parameters

Changed 4 years ago by admin

(0027120)
klop01 (manager)
2009-06-24 13:10

Het probleem zit niet zozeer in de MSS2 codec maar in de "0x3253534D" codec. Deze wordt niet herkent door ffmpeg. Op zich is dit een algemeen probleem dat gevolg is van de principiele keuze om af te gaan op de analyse van ffmpeg. Om niet alleen voor dit uitzonderingsgeval een oplossing te vinden willen we het volgende voorstellen;

We blijven bij analyse van ffmpeg, omdat dit nu eenmaal de meeste informatie geeft over de video, echter bij falen van ffmpeg analyse gebruiken we een fallback op mime-type. We kunnen analyseren of een mapping van mime-type naar containertype kunnen maken en op basis hiervan het containerveld in de technische metadata vullen. => aanpassing in het analyse script.

(het zou overigens ook interessant zijn om te analyseren of op basis van het bestaande materiaal hoe de mimetype/containertype verdeling is)

Changed 4 years ago by Frans

  • component set to Core
  • related_to set to none
  • milestone changed from MediaMosa 1.6 to MediaMosa 1.7

wait for new FFMpeg

Changed 4 years ago by MC-arjen

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

At the moment of 1.7 the latest official version is still ffmpeg 0.5. If at 2.0 the version is still not updated, we could backport the mss2 codec detection in the ffmpeg code, and include that version in the 2.0 release?

Changed 3 years ago by Frans

  • owner changed from frans to MC-Arjen
  • milestone changed from MediaMosa 1.7 to MediaMosa 2.0

OK.

Changed 3 years ago by robert

  • moscow set to Must Have
  • milestone changed from MediaMosa 2.0 to MediaMosa 2.1

Moved to 2.1.

Changed 3 years ago by Frans

  • owner changed from MC-Arjen to michiel

Michiel, do we still have the original Windows Media screencam video?
The testasset on VP-Core acceptatie is deleted.

Changed 3 years ago by Michiel.Schok

I've uploaded a new asset on VP-Core production.
It's asset_id BVpiK1gfLAS5gzawETvcGXBy / mediafile_id

Output from the log:

	Analyse returned output: /mnt/naspcd1/vp-prod/01/vpx-prod/data/M/MldkfgM3dQCHh8RBz8gUiQVr: could not find codec parameters - ffmpeg -i "/mnt/naspcd1/vp-prod/01/vpx-prod/data/M/MldkfgM3dQCHh8RBz8gUiQVr" 2>&1
ffmpeg -i "/mnt/naspcd1/vp-prod/01/vpx-prod/data/M/MldkfgM3dQCHh8RBz8gUiQVr" 2>&1
Error: Could not find codec parameters. This is most likely a problem with the encoding of the original media.
Error: Could not find codec parameters. This is most likely a problem with the encoding of the original media.

FFmpeg version 0.5, Copyright (c) 2000-2009 Fabrice Bellard, et al.
configuration: --enable-nonfree --enable-libx264 --enable-gpl --enable-pthreads --enable-libmp3lame --enable-libfaac --enable-libfaad --enable-libvorbis --enable-libtheora --enable-libgsm --enable-libxvid --enable-libamr-nb --enable-libamr-wb
libavutil 49.15. 0 / 49.15. 0
libavcodec 52.20. 0 / 52.20. 0
libavformat 52.31. 0 / 52.31. 0
libavdevice 52. 1. 0 / 52. 1. 0
built on Dec 11 2009 21:09:13, gcc: 4.2.4 (Ubuntu 4.2.4-1ubuntu4)
[asf @ 0xa168290]Could not find codec parameters (Video: MSS2 / 0x3253534D, 954x928, 291 kb/s)
/mnt/naspcd1/vp-prod/01/vpx-prod/data/M/MldkfgM3dQCHh8RBz8gUiQVr: could not find codec parameters
FFmpeg version 0.5, Copyright (c) 2000-2009 Fabrice Bellard, et al.
configuration: --enable-nonfree --enable-libx264 --enable-gpl --enable-pthreads --enable-libmp3lame --enable-libfaac --enable-libfaad --enable-libvorbis --enable-libtheora --enable-libgsm --enable-libxvid --enable-libamr-nb --enable-libamr-wb
libavutil 49.15. 0 / 49.15. 0
libavcodec 52.20. 0 / 52.20. 0
libavformat 52.31. 0 / 52.31. 0
libavdevice 52. 1. 0 / 52. 1. 0
built on Dec 11 2009 21:09:13, gcc: 4.2.4 (Ubuntu 4.2.4-1ubuntu4)
[asf @ 0x9e96290]Could not find codec parameters (Video: MSS2 / 0x3253534D, 954x928, 291 kb/s)
/mnt/naspcd1/vp-prod/01/vpx-prod/data/M/MldkfgM3dQCHh8RBz8gUiQVr: could not find codec parameters

Changed 3 years ago by Michiel.Schok

  • owner changed from michiel to MC-Arjen

Changed 3 years ago by MC-arjen

  • milestone changed from MediaMosa 2.1 to MediaMosa 2.2

tested versus "FFmpeg version SVN-r22897" (17-04-2010): The windows media screencam codec is still not recognized:

[asf @ 0x8c8a420]Could not find codec parameters (Video: MSS2 / 0x3253534D, 954x928, 291 kb/s)

consider a patch to ffmpeg in version 2.2.

Changed 3 years ago by Michiel.Schok

Maybe you can consider the change you suggested 10 months ago: if ffmpeg analysis fails, and the mime-type suggests a windows media file: fill the container type with 'asf'.

The file is perfectly playable / streaming out of the Windows Media streaming servers, it's only VP-Core/ffmpeg that is not correctly detecting the container type.

Changed 3 years ago by robert

  • estimated_hours set to 3

Changed 3 years ago by MC-arjen

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

added a analyse exception: if ffmpeg cannot parse a containertype and mime gives "video/x-ms-asf", make container type "asf"

Changed 3 years ago by Michiel.Schok

  • tested set to yes
  • accepted changed from no to yes

The screencam is now identified as 'containertype=asf'.

Note: See TracTickets for help on using tickets.