Closed smolnp closed 5 years ago
when you click the "stop render" button, the process appears for a couple of seconds just before closing the render window
Yes, this is because for technical reasons:
I don't think we have possibility for improvement here, the "Stop render" action will always take time, even more if you do it right at the start when it is still launching. Closing this as wontfix.
The problem is not to close the render, but the fact that the render process is not visible in the dialogue "Flowblade Timeline Render", but in the terminal is visible.
Do you mean that the progress bar and texts are never visible when doing rendering, or is the problem that they are only visible after few seconds?
If the problem is that progress bar and texts are never visible this does not reproduce here.
If the problem is that progress bar and texts are only visible after few seconds this essentially cannot be fixed.
The technical problem is that to get the render going we are launching a bunch or threads, re-initing MLT for another process, basically 25% of work needed to lauch Flowblade itself and this takes time.
There is something we can do though, we can change the text "0%" to text "Initialing Render..." to communicate that we are initilizing.
texts are never visible when doing rendering
There is a file in hidden directory in your home folder /home/your_home_folder_name/.flowblade/log_single_render
Post the contents of that file here.
Some other questions:
When did this first happen? Are you running the latest code from repository? Does this happen on all types of render or on just some types?
I'm leaving house for now will reply later.
video_codecs:
audio_codecs:
formats:
I received a question, I decided to double-check on this Linux distribution.
this happens on both 1.16 and the version from the master branch.
this happens on all types of rendering.
it seems too on openmandriva, magea and arh
Ok, we got this:
qt5ct: using qt5ct plugin /usr/lib64/python2.7/site-packages/mlt.py:938: Warning: g_main_context_push_thread_default: assertion 'acquired_context' failed this = _mlt.new_Producer(*args)
It is the Qt-messing-flowblade thing again maybe. I pushed a patch that might work, can you try if repo works now?
Everything works, thank you! You can close the question.
Thanks for the input, could have missed this for the release. I'll keep this open until after release for information.
In subsequent sequences, the text is also not displayed during rendering.
H i, could you be a bit more specific, do you mean render works first time, but not after that, or do you mean that "Batch Render Tool" does not work? "Batch Render Tool" has not been fixed yet but I know the problem and will patch it before release.
it's easier for me to show, but the problem with the encoding seems to be here again https://youtu.be/eJs4Ap3n5yY
Please, give all bug reports as step -by-step instructions to reproduce the problem. I was not able to understand the problem from the video. It just seemed random clicking around that made no sense to me at all.
Flowblade with the English interface: • Add clip to timeline • Render → Full Length (Marked Range) everything is working... • Add New Sequence • Add clip to timeline • Render → Full Length (Marked Range) everything is working… Flowblade with the with Russian interface: • Add clip to timeline • Render → Full Length (Marked Range) everything is working... • Add New Sequence • Add clip to timeline • Render → Full Length (Marked Range) no text showing work rendering.
Thank you, confirmed.
Unexplained videos are like riddles from developer point of view because one does not know what to look for.
understand, next time I will describe the sequence of actions taken
Fixed in repo, will be in 2.0.
rendering works, the graphic process is not displayed