[Cin] 2 little issue
Rafa Mar Multimedia en Gnu\Linux
rafamar.mm.ig at gmail.com
Mon Feb 1 20:14:19 CET 2021
Walter, you being SysAdmin you should know how to do something as simple as
this button so that it works with the "Environment variable" as you call
it, of your preference. I couldn't do it because I recognize that I don't
know anything about programming.
Phyllis, although it works perfectly, I think it would be best not to
include these changes. If any new users want to use the batch render wizard
and don't know how it works, they have the extensive and magnificent
English manual to turn to.
Another option is to hope that a programmer has time to study the Cinelerra
code and do it as you wish.
My friend told me that he could help me with specific, basic and simple
things, because more advanced things require time that he does not have now.
El lun, 1 feb 2021 a las 19:47, Walter Casanova via Cin (<
cin at lists.cinelerra-gg.org>) escribió:
> El lunes, 1 de febrero de 2021 13:37:37 -03 Rafa Mar Multimedia en
> via Cin escribió:
> > I asked the person who made this button and he told me that this "error"
> > only indicates that we have opened firefox from the Cinelerra shell,
> > because the application is closed, and that when closing it, it warns us
> > that we will no longer receive messages of this application.
> > The good thing about using xdg-open is that this command frees the shell
> > without human interaction, in fact if you open firefox from this call
> > button and close Cinelerra, firefox will remain open.
> > He told me that if in a terminal we execute the command:
> > xdg-open http://www.cinelerra-gg.org
> > With the browser closed, this will open it, open the indicated page and
> > terminal will be free to execute other commands. The same will happen
> > Cinelerra. But the "system" option that is used to launch this option
> > this line warns that the process will no longer show messages, because it
> > has been launched from cinelerra and cinelerra will remain open and
> > has closed.
> > I also asked him why this did not happen in other calls that do use
> > $CIN_BROWSER and he replied that in order to answer this question I
> > study the Cinelerra code in depth and that now I did not have time for
> > task.
> > He also told me that his solution is generic in C and that it will work
> > without creating any problems for Cinelerra, but that if those
> > do not like it, it is best not to use it. In these cases, it is best to
> > find another person, with more time, to provide a more satisfactory
> > solution for those responsible.
> > El lun, 1 feb 2021 a las 16:10, Phyllis Smith via Cin (<
> > cin at lists.cinelerra-gg.org>) escribió:
> > > Andrea, I also started getting this error message after installing the
> > > patch to use xdg-open instead of $CIN_BROWSER in the Batch Render menu
> > > which was hanging after using the help button if the browser was not
> > > already up. I may have to back this out. If you already have started
> > > Firefox or your usual browser in the usual way, it seems to be good.
> > > Further study is probably needed.
> > >
> > > ###!!! [Parent][RunMessage] Error: Channel closing: too late to
> > >
> > >> messages will be lost
> > >
> > > Starting CinGG from the terminal I often see this string (not always):
> > >> ###!!! [Parent][RunMessage] Error: Channel closing: too late to
> > >> send/recv, messages will be lost
> > >
> > > --
> > > Cin mailing list
> > > Cin at lists.cinelerra-gg.org
> > > https://lists.cinelerra-gg.org/mailman/listinfo/cin
> IMHO I prefer to use environment variables as it was before $ CIN_BROWSER,
> since xdg-open, it opens the default browser, but and if I don't want it
> open the default browser, whatever the reason, it seems more configurable
> this now .
> - | Walter Casanova | -
> - | Gnu / Linux - SysAdmin | -
> Cin mailing list
> Cin at lists.cinelerra-gg.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Cin