Ticket #219 (closed defect: fixed)

Opened 3 years ago

Last modified 2 years ago

[Stills] No still job on audio files

Reported by: Frans Owned by: robert
Priority: minor Milestone: MediaMosa 2.3
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

We see that still jobs are started regardless of the type of media. Still jobs should not be started with audio files

server	Einde STILL job: 512433 met status: FAILED
Go to asset 1S6QQ41jTsxF8B2ljBC5XXYv

Attachments

trac_219_jobs.png Download (14.9 KB) - added by Michiel.Schok 2 years ago.
trac_219_logging.png Download (60.3 KB) - added by Michiel.Schok 2 years ago.
trac_219_exception.png Download (9.4 KB) - added by Michiel.Schok 2 years ago.

Change History

Changed 3 years ago by Frans

  • milestone changed from MediaMosa X.X to MediaMosa 2.1

Changed 3 years ago by Frans

  • moscow set to Should Have

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 Must Have
  • milestone changed from MediaMosa 2.2 to MediaMosa 2.3

Changed 3 years ago by peter

  • estimated_hours set to 3

Changed 3 years ago by forgacs

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

Changed 3 years ago by forgacs

  • owner changed from forgacs to robert

@Robert: I have implemented a check on mime type in the create_still_job() function. If the current file is audio, then it doesn't start the still job.
It doesn't drop any exception in case of audio file, but we can consider this behavior.

Changed 3 years ago by forgacs

@Robert: I have implemented the new exception. It catch (and hide) the exception in case of upload.

Changed 3 years ago by robert

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

Changed 2 years ago by Michiel.Schok

  • tested set to yes

Uploaded audio mediafile.
Asset 'E1ggfsYtfUGQmSETQynw1mBY' / mediafile 'q1eHbkjXsOnGfTDBKHzpSeVO' .
Details available at  http://beheer.acceptatie.vpcore.snkn.nl//admin/mediamosa/browse/asset/E1ggfsYtfUGQmSETQynw1mBY

My observation:
1. 3 jobs are started: id 2189 (upload), 2190 (still), 2191 (transcode)
2. job 2190 and 2191 failed, and *both* show up in logging.
3. The only message that is missing in the logging is 'job 2190 failed'.

Me thinks (but Frans can override me of course) that this is a crappy workaround and a waste of time.

I would have liked to see that somewhere in the process of sending a job to the queue or picking it up and starting to run ffmpeg that there would be an analysis of the technical metadata of the mediafile. And if MediaMosa detects that it is an audio-file, then there should be a graceful exit. Not a FAILED code, but rather 'INFORMATION': still job not executed on an audio-only file.

On the other hand: at the moment, there is so much logging into the page  http://beheer.acceptatie.vpcore.snkn.nl/admin/mediamosa/browse/log that I don't use it anymore for troubleshooting or informational purposes to keep an eye on potential problems.

so, therefore: tested: yes, accepted: to decide by Frans.
Will add some screenshots.

Changed 2 years ago by Michiel.Schok

Changed 2 years ago by Michiel.Schok

Changed 2 years ago by Frans

  • status changed from closed to reopened
  • resolution fixed deleted

Not accepted.

"I have implemented a check on mime type in the create_still_job() function. If the current file is audio, then it doesn't start the still job."

Needs attention ans will reopen.

Changed 2 years ago by Michiel.Schok

I was triggered by the 'mime type' in the note of Frans.
Closer inspection reveals the mime-type to be 'application/octet-stream'...
Strange for a mp3 file, but that's another problem.

But I tried a couple of more files, and finally found a file with mimetype 'mpeg/audio'. And then, no still job is generated, and we observe another entry in the log file, which is attached as screenshot.

and then it seems that it has been implemented as I would have liked...
I stand corrected.

Changed 2 years ago by Michiel.Schok

Changed 2 years ago by Frans

So the real issue here is that mp3 should be tagged with an other Mime type than application/octet-stream.

One of:
audio/mpeg, audio/x-mpeg, audio/mp3, audio/x-mp3, audio/mpeg3, audio/x-mpeg3, audio/mpg, audio/x-mpg, audio/x-mpegaudio

Changed 2 years ago by forgacs

@Robert:
It should work well, if the mime type is one of the "audio/...".
I think the problem is the "application/octet-stream".

Changed 2 years ago by Michiel.Schok

Correct, I tried some .mp3 files, and the one that detected as 'audio/...' went well.
As we rely on the 'file' tool to produce correct mime-types, this ticket can be closed.

Changed 2 years ago by Frans

  • status changed from reopened to closed
  • accepted changed from no to yes
  • resolution set to fixed
Note: See TracTickets for help on using tickets.