Differences

This shows you the differences between two versions of the page.

--- webinterface:webinterface [2024/05/21 15:17] – [Tipps and Tricks] emcodem
+++ webinterface:webinterface [2026/05/12 23:17] (current) – [Submit all selected files as array into one job for concat/stitch] emcodem
@@ Line 17: / Line 17: @@
 Installing the Webinterface as a service is optional, you can also just execute "server.exe" for testing. \\ \\
-Before installing the webinterface, make sure the **FFAStrans API is running** as described here: [[gui:installation|Installation]].
 __**Note:**__ It is recommended to extract the installation package in the same folder than FFAStrans folder. \\
@@ Line 50: / Line 48: @@
 ====Main Menu====
-The Webinterface works only if :
-  * **FFAStrans API is running**
 If your webserver(webinterface) runs on the same server as your main ffastrans server, open your web browser and type : **http://localhost:3002**
@@ Line 144: / Line 139: @@
 </code>
-=== Submit all selected files as array into one job for concat/stitch ===
+==== Segment submission and processing ====
+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 case of segments, Webinterface will submit a special predefined variable called "o_source", this is a complex JSON object containing all the needed information.
+**Simple example:**
+In this case, we just showcase a minimal workflow, due to the nature of ffmpeg "concat" functionality it will only work correctly with I-Frame only source files.
+{{ :webinterface:emcodem_concat_1.4.3_ffmpeg_cuts_no_transcode.json |}}
+**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.
+{{ :webinterface:emcodem_concat_1.4.3_avisynth_cuts.json |}}
+==== Submit all selected files as array into one job for concat/stitch ====
 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" Processor to process all Files separately.
-  * Note that webui_stitch keyword in the workflow description will cause %s_source% variable to be a JSON array of file paths or URLs.
+In this case, webinterface submits 2 special variables to the job
+  * %webui_a_source% (note missing preceeding s_), a JSON array containing all submitted file paths
+  * %webui_o_source% a JSON objects, one per submitted file - this can contain in/out point if set in the player
 ----------------------------------------