Webinterface
Re: Webinterface
New release, now with support for segments and "concat".
https://github.com/emcodem/ffastrans_we ... g/1.4.0.38
Player was changed from VLC to MPV and it delivers really really good performance and accuracy. We have now Frame step.
It is not 100% frame accurate but pretty close.
Example Workflows for segment processing:
https://ffastrans.com/wiki/doku.php?id= ... processing
Sorry that the docs are not yet completely updated, blame @knk for making pressure
https://github.com/emcodem/ffastrans_we ... g/1.4.0.38
Player was changed from VLC to MPV and it delivers really really good performance and accuracy. We have now Frame step.
It is not 100% frame accurate but pretty close.
Example Workflows for segment processing:
https://ffastrans.com/wiki/doku.php?id= ... processing
Sorry that the docs are not yet completely updated, blame @knk for making pressure
emcodem, wrapping since 2009 you got the rhyme?
Re: Webinterface
Looking good, segments and concat is a nice addition, will have to play around with that. UI overall seems quite a bit snappier too.
I did notice something in the Job Submitter, files are always sorted by creation date, descending. Clicking on a header sorts by that type, but changing the directory always resets sorting back to creation date. Is it possible to change that default behaviour in a setting somewhere? If it is, I seem to overlook it.
I did notice something in the Job Submitter, files are always sorted by creation date, descending. Clicking on a header sorts by that type, but changing the directory always resets sorting back to creation date. Is it possible to change that default behaviour in a setting somewhere? If it is, I seem to overlook it.
Re: Webinterface
Pressure is what makes life on earth possible!
Thanks a lot for this release! Great new features! Huge improvements!
Been testing it for a few hours now with my main workflows.
VU meter seems to be a bit faded in the player...maybe it can be fixed in the player config file, will check.
Now for the down part, it doesn't seem to be compatible with my previous "major" workflows.
The concat feature "stitch" tag has a big differences from the previous version. It still doesn't seem to show the "current name" that it is transcoding, nor does it seem to allow a custom "main job" name for people to be able to identify their job in the monitor window.
I've tested the example workflows and the "for each" branch of transcoding always provides the name of the 1st file in the submited list.
Also there seems to be a constrain in the global number of input files, since the command line seems to big holding UNC paths, etc.
These are just some first thoughts... Thanks a lot!
Re: Webinterface
Thanks a lot for giving it a shot Stef! What you say is true, unchangeable currently. I believe i did save the sort order in some older version but i reverted because it caused troubles and felt kind of weird for larger shares. However, of course you have a valid point here, i might want to re-enable saving the sort order but maybe only for the current session or for the current browse location? What you think?
Also, if you re-order, what do you usually use, "name"?
emcodem, wrapping since 2009 you got the rhyme?
Re: Webinterface
Up in front, thank you so much for investing serious thoughts and time into the stuff, really appreciated.
I started by trying to keep mpv parameters in the mpv.conf but it turned out quickly that we have to insert/change filters depending on source file, so the filter chain is now calculated on server side, source_code/node_components/player.js. For me and @momocampo, the AV sync was always about 5-6 frames off, so i decided add a rule like "if there is audio, then insert asetpts=PTS-0.24/TB"
For my xdcamhd sources and youtube stuff it seems to be about +- 1 frame now.
This should go into the future documenation:
When add the stitch functionality to your workflow (webui_stitch in wf_description), in the past, we just populated s_source with a JSON array of files. But this did lead to bad behaviour everywhere so we changed that:
The current behaviour is:
2) "for each" not changing the source name is something we discussed already internally, a topic for @admin for sure. Lots of stuff to do in that area (like re-parsing s_source)
3) exactly, instead of submitting a json array into s_source, i changed it now to submit the first source file name into s_source.
I hope you can give some example how to reproduce that, this has high priority. Is it like i just need to submit hundreds of files to one of my example workflows?
Very valid point and very well expressed. My big sister always says "the earth without art is just eh" but your point is much more valid than hers
Might i ask what is the offset for you?
I started by trying to keep mpv parameters in the mpv.conf but it turned out quickly that we have to insert/change filters depending on source file, so the filter chain is now calculated on server side, source_code/node_components/player.js. For me and @momocampo, the AV sync was always about 5-6 frames off, so i decided add a rule like "if there is audio, then insert asetpts=PTS-0.24/TB"
For my xdcamhd sources and youtube stuff it seems to be about +- 1 frame now.
Very sorry for not being fully backwards compatible here, but i needed to stop "misusing" s_source and fill it with some simple string instead of complex data structures.
This should go into the future documenation:
When add the stitch functionality to your workflow (webui_stitch in wf_description), in the past, we just populated s_source with a JSON array of files. But this did lead to bad behaviour everywhere so we changed that:
The current behaviour is:
- for backward compatibility you can set s_source at start of your job to %webui_a_source%. This contains a plain JSON array of files without any in/out points, just filenames (as it was before, so this should work for your workflows)
- a complex JSON object with in/out points and similar stuff is populated into %webui_o_source%, this is what the example workflows use
1) naming the "main job" is currently done with the first source file. I'll think about how we could connect a webui_variable with s_source to change this.knk wrote: ↑Thu Oct 03, 2024 2:22 pm It still doesn't seem to show the "current name" that it is transcoding, nor does it seem to allow a custom "main job" name for people to be able to identify their job in the monitor window.
I've tested the example workflows and the "for each" branch of transcoding always provides the name of the 1st file in the submited list.
2) "for each" not changing the source name is something we discussed already internally, a topic for @admin for sure. Lots of stuff to do in that area (like re-parsing s_source)
3) exactly, instead of submitting a json array into s_source, i changed it now to submit the first source file name into s_source.
That should not be the case, there should be no "builtin" point where we hand over the full list of files on a commandline. E.g. ffmpeg gets a ffconcat list from text file.
I hope you can give some example how to reproduce that, this has high priority. Is it like i just need to submit hundreds of files to one of my example workflows?
emcodem, wrapping since 2009 you got the rhyme?
Re: Webinterface
I think I can speak for almost everyone here and say the "We" are the ones that must thank you for this amazing piece of software!
For the retro-compatibility part the webui_a_source works like a charm. Thanks a lot!
If you find any "elegant" way to redefine the source file name please share.
When users add their files via web browser and fill a form to rename what's to be the output name it would be great if the "Source" column could display that same variable so they could "track" their jobs in the monitor window. It's just to a more "user friendly" approach.
Time to keep testing!
This was my bad...Forgot my own documentation
Have a QC PC running the new engine version and the processors file was overwritten. The changes made in the previous one probably make no sense in the new architecture, only when applied to the previous webui s_source structure...
I have a friend who's a mechanic and gets actual goosebumps and chills when he hears certain motors working. He calls it art. So despite how hugely broad and subjective as it is, your big sis is absolutely right!
All the best!
Re: Webinterface
@knk
thanks for the nice words and let me know any findings while testing.
oh craps, now i know what you mean with "faded" VU meter, i published this release with an old version of mpv.conf. Just for info, i don't have yet an automated way of creating a release, so i copy all "relevant" files manually into some folder. This way of course guarantees that i miss something or even have some stuff too much in the release. I really need some automated way for creating a new release.
I updated the release zip file (replaced it in same version), but the only change will be that the tools/mpv/mpv.conf file has exactly this content and nothing else:
thanks for the nice words and let me know any findings while testing.
oh craps, now i know what you mean with "faded" VU meter, i published this release with an old version of mpv.conf. Just for info, i don't have yet an automated way of creating a release, so i copy all "relevant" files manually into some folder. This way of course guarantees that i miss something or even have some stuff too much in the release. I really need some automated way for creating a new release.
I updated the release zip file (replaced it in same version), but the only change will be that the tools/mpv/mpv.conf file has exactly this content and nothing else:
Code: Select all
[ffasVidProfile]
load-scripts=no
of = mpegts
ofopts-add=flush_packets=1
#omit_video_pes_length helps jsmpeg find video packet length,client decode performance optimized
ofopts-add=omit_video_pes_length=false
ovc=mpeg1video
ovcopts-add=g=1
ovcopts-add=b=6M
oac=mp2
oacopts-add=b=128k
keep-open-pause=no
loop-playlist=inf
keep-open=always
cache=no
hr-seek-framedrop=yes
Unfortunately there is no way to do that, it's buried within the ffastrans source code, so maybe we have something for it in the next version if we keep nagging @admin.If you find any "elegant" way to redefine the source file name please share.
emcodem, wrapping since 2009 you got the rhyme?
Re: Webinterface
Hi there!
There is some problems with creating and editing web vars
I've made an issue at GitHub
https://github.com/emcodem/ffastrans_webui/issues/79
There is some problems with creating and editing web vars
I've made an issue at GitHub
https://github.com/emcodem/ffastrans_webui/issues/79
Re: Webinterface
@krskvch,
how embarressing that must be for @momocampo for not seeing this error when testing
No need to open the case twice, having it here in the forum will be more responsive than on github.
Should be solved, all download links updated. You just replace server.exe for update from the 4 days old version.
Hope i did not make any fatal mistake with the quick release...
how embarressing that must be for @momocampo for not seeing this error when testing
No need to open the case twice, having it here in the forum will be more responsive than on github.
Should be solved, all download links updated. You just replace server.exe for update from the 4 days old version.
Hope i did not make any fatal mistake with the quick release...
emcodem, wrapping since 2009 you got the rhyme?
Re: Webinterface
Hey @Emcodem, I don't see everything but you're right, weird that we both work on the same stuff with @knk
Sorry Bro, I should have looked on the forum first.
Sorry Bro, I should have looked on the forum first.