webinterface:webinterface
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
webinterface:webinterface [2024/01/28 17:08] – benjamin | webinterface:webinterface [2024/10/01 21:54] (current) – [User Form] emcodem | ||
---|---|---|---|
Line 70: | Line 70: | ||
=== Introduction to Manual Review === | === Introduction to Manual Review === | ||
- | {{: | + | |
Since Version 1.4 there is Manual review (Review Queue) Menu Item. | Since Version 1.4 there is Manual review (Review Queue) Menu Item. | ||
Line 83: | Line 83: | ||
- Feature 2: Additionally create a Form using webui Form variables and get very sophisticated information from the user e.g. a MAM Metadata Form | - Feature 2: Additionally create a Form using webui Form variables and get very sophisticated information from the user e.g. a MAM Metadata Form | ||
+ | |||
+ | \\ | ||
How it works: | How it works: | ||
Line 89: | Line 91: | ||
* Optionally you can present a nice Form using webui form variables, after the user selected one option and before he starts the follow-up | * Optionally you can present a nice Form using webui form variables, after the user selected one option and before he starts the follow-up | ||
- | + | {{webinterface:manual_review_1.png? | |
- | {{: | + | {{webinterface: |
+ | {{webinterface: | ||
==== User Form ==== | ==== User Form ==== | ||
Line 100: | Line 102: | ||
There is a GUI for creating and editing the look and feel of Form fields found on Webinterface in the " | There is a GUI for creating and editing the look and feel of Form fields found on Webinterface in the " | ||
- | {{:webinterface: | + | {{webinterface: |
The following types of userinput are supported: | The following types of userinput are supported: | ||
Line 142: | Line 144: | ||
</ | </ | ||
- | https:// | + | ==== Segment submission and processing ==== |
- | === Submit all selected files into one job for concat/stitch === | + | Currently since Webint 1.4.0.38, you need to use the player to set in/out points. |
+ | Of course your workflow must add support for this special type of source. | ||
- | In FFAStrans workflow editor - workflow properties, you can enter a workflow description. Add the keyword webui_stitch. If this word is found in the workflow description, | + | In case of segments, Webinterface will submit |
- | ---------------------------------------- | ||
- | ==== User Manager Menu==== | + | **Simple example: |
+ | In this case, we just showcase a minimal workflow, due to the nature of ffmpeg " | ||
- | {{gallery>: | + | {{ : |
- | This menu is only useful if " | ||
- | The purpose is to filter Webinterface access rights based on users. Here is the procedure : | ||
- | - Create first your groups (admin, users, monitoring, | ||
- | - Click on a group (admin for example) and assign rights (drag a grid row from left to right). | ||
- | - Create admin user(name and password), click on it and drag a group from left to right to link user to a group. | ||
- | - Repeat the procedure to link each user to his group. | ||
+ | **More complex, frame accurate example:** | ||
+ | This is a complex showcase where we use Avisynth to cut the segments frame accurately and after that, stitch all source files into one. | ||
- | You can use filters per group(filter rules), see inbuilt documentation for details. | + | {{ : |
- | ------------------------------------------- | ||
- | ==== Server Configuration Menu==== | ||
- | {{gallery>: | ||
+ | ==== Submit all selected files as array into one job for concat/ | ||
- | This menu allows to configure | + | In FFAStrans workflow editor - workflow properties, you can enter a workflow description. Add the keyword webui_stitch. If this word is found in the workflow description, all selected files are submitted as json array into s_source variable and you can use e.g. the "Foreach" |
- | See inbuilt documentation for settings details.\\ | + | |
- | (See [[webinterface# | + | * Note that webui_stitch keyword in the workflow description will cause %s_source% variable to be a JSON array of file paths or URLs. |
+ | |||
+ | ---------------------------------------- | ||
+ | |||
+ | ==== User Manager Menu==== | ||
+ | |||
+ | {{tutorials: | ||
+ | |||
+ | ------------------------------------------- | ||
- | ----------------------------------------------- | ||
==== Scheduler Menu==== | ==== Scheduler Menu==== | ||
Line 225: | Line 229: | ||
< | < | ||
- | == New documentation work in progress for webinterface | + | === Jobstarter workflow control using URL Parameters since Version 1.4 === |
[[webui_jobstarter]] | [[webui_jobstarter]] | ||
+ | === Override CSS globally === | ||
+ | |||
+ | [[webui_alternate_server]] | ||
+ | |||
+ | === Retrieve username of logged in user who submitted a job from Webui === | ||
+ | |||
+ | If a job was submitted on WebUI Job Submitter page, this variable should carry the username of the logged in user: | ||
+ | %s_job_submit_username% | ||
webinterface/webinterface.1706461694.txt.gz · Last modified: 2024/01/28 17:08 by benjamin