Ticket #265 (closed enhancement: fixed)

Opened 23 months ago

Last modified 16 months ago

more toolset definition

Reported by: MC-arjen Owned by: robert
Priority: major Milestone: MediaMosa 2.3
Component: Transcoding Version:
Keywords: Cc:
MoSCoW: Must Have Estimated time after impact analysis:
Related to project: none Tested: no
Accepted: no Estimated Hours: 16

Description

Currently the predefined tools are: 'ffmpeg' and 'windows'. In the settings in Mediamosa these toolsets are defined with a executable path.

In order to add more toolsets this needs to be configurable, the path should be stored in the database.

This is the first step in a more easy addition of more toolsets.

Change History

Changed 22 months ago by Frans

  • milestone changed from MediaMosa X.X to MediaMosa 2.2

Changed 21 months ago by Frans

  • moscow changed from Should Have to Must Have

Changed 20 months ago by robert

After more thinking we decided that this is not the start to make this setting work better than current situation.

Better is for per tool drupal module based. Where each Drupal module tool has hooks for listing, creating the execute path, and own tool settings stored into database.

Using this technology we can introduce new modules where new tools can be enabled, for example pdf2txt, transcription and image manipulation.

Changed 20 months ago by Frans

  • moscow changed from Must Have to Should Have

Changed 17 months ago by Frans

  • moscow changed from Should Have to Must Have
  • milestone changed from MediaMosa 2.2 to MediaMosa 2.3

Changed 17 months ago by peter

  • estimated_hours set to 16

Changed 16 months ago by forgacs

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

Changed 16 months ago by forgacs

  • owner changed from forgacs to robert

We have done with phase 1:
- The mediamosa_tool_params class was introduced with MySQL table {mediamosa_tool_params}. It is the new basic class for the tools.
- Two tool module was developed: mediamosa_tool_ffmpeg and mediamosa_tool_windows with two hooks: hook_mediamosa_tool_iteration() and hook_mediamosa_tool_mapping(). First hook gives back the tool name, and the second gives back the mapping parameters.
- The allowed_values field was redesigned. The separator was ";", and it is a serialized array now.

Changed 16 months ago by robert

  • status changed from assigned to closed
  • resolution set to fixed
Note: See TracTickets for help on using tickets.