Ticket #228 (new defect)

Opened 3 years ago

Last modified 19 months ago

Analyse of dual stream videos

Reported by: Michiel.Schok Owned by:
Priority: trivial Milestone: MediaMosa 3.1/3.5
Component: Core Version:
Keywords: Cc:
MoSCoW: Should Have Estimated time after impact analysis:
Related to project: none Tested:
Accepted: no Estimated Hours:

Description

We recently began uploading .avi containers which contain dual videostreams. the analysis script reports

server 	Analyse string: /opt/www/upload/htdocs/lua/vpx-analyse
> /mnt/naspcd1/vpx-acc/data ZXgldMozqtDD0vLLw36Yu1dS --always_hint_mp4
> --always_insert_metadata 	notice 	12/04/2009 - 14:47
> server 	Analyse returned output: [C]: ? - ffmpeg -i
> "/mnt/naspcd1/vpx-acc/data/Z/ZXgldMozqtDD0vLLw36Yu1dS" 2>&1
> /usr/bin/lua: /opt/www/upload/htdocs/lua/vpx-analyse:259: attempt to
> compare two nil values
> stack traceback:
> /opt/www/upload/htdocs/lua/vpx-analyse:259: in function 'find_best_streams'
> /opt/www/upload/htdocs/lua/vpx-analyse:308: in function 'analyse'
> /opt/www/upload/htdocs/lua/vpx-analyse:499: in main chunk
> [C]: ? 	notice 	12/04/2009 - 14:47
> server 	Analyse returned output: [C]: ? - ffmpeg -i
> "/mnt/naspcd1/vpx-acc/data/B/BPK15W3uWOyGsKHpDcG2RLK9" 2>&1
> /usr/bin/lua: /opt/www/upload/htdocs/lua/vpx-analyse:259: attempt to
> compare two nil values
> stack traceback:
> /opt/www/upload/htdocs/lua/vpx-analyse:259: in function 'find_best_streams'
> /opt/www/upload/htdocs/lua/vpx-analyse:308: in function 'analyse'
> /opt/www/upload/htdocs/lua/vpx-analyse:499: in main chunk
> [C]: ?

Analyse script shows on line 254 a guard

if video_max_bitrate_stream == nil

and then the offending line 259

elseif tonumber(bitrate) > video_max_bitrate

Maybe video_max_bitrate and video_max_bitrate_stream should be the same?

Change History

Changed 3 years ago by Frans

  • moscow set to Should Have
  • milestone changed from MediaMosa X.X to MediaMosa 2.1

Changed 3 years ago by Frans

  • milestone changed from MediaMosa 2.1 to MediaMosa 2.2

Changed 3 years ago by Frans

  • moscow changed from Should Have to Could Have

Changed 3 years ago by Frans

  • milestone changed from MediaMosa 2.2 to MediaMosa 2.3

Should test to see if still a valid issue

Changed 2 years ago by Frans

  • moscow changed from Could Have to Must Have
  • milestone changed from MediaMosa 2.3 to MediaMosa 3.0

Changed 2 years ago by peter

  • moscow changed from Must Have to Should Have

Didn't make it to definitive set of must have issues for MM 3.0.

Changed 19 months ago by Frans

  • milestone changed from MediaMosa 3.0 to MediaMosa 3.5
Note: See TracTickets for help on using tickets.