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 Does anyone have any idea what this means? Another problem is that recently, when I compile CinGG from git, the autogen.sh step produces a lot of warnings and asks me to use "autoupdate". After using autoupdate everything works fine and I can go on with autogen.sh, configure, etc. I always use the same commands to compile (I do a copy/paste) and only lately it gives me this problem. Andrew had said it was a directory level issue, but I'm not knowledgeable to understand what that means or how to fix it. Do you know how to fix it? I bring back the exact instructions I use: " git clone --depth 1 "git://git.cinelerra-gg.org/goodguy/cinelerra.git" cinelerra5 cd /home/paz/cinelerra5/cinelerra-5.1 ./autogen.sh ./configure --with-single-user --with-booby make 2>&1 | tee /tmp/cin5.log && make install "
В сообщении от Monday 01 February 2021 11:54:27 Andrea paz via Cin написал(а):
Error: Channel closing: too late to send/recv, messages will be lost
Sounds like firefox/mozilla message, from quick googling around ? About second issue ..may be some system components (like automake?) were updated on your end, so now autoupdate is required? If it works for you you probably can just add this command into ./autogen.sh script ...
Thanks Andrew; I'm so stupid that I didn't think to put "autoupdate" inside "autogen.sh". Now everything is OK. PS: Recently Arch Linux updated "automake"; it may depend on this...
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 send/recv,
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
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 the terminal will be free to execute other commands. The same will happen with Cinelerra. But the "system" option that is used to launch this option with this line warns that the process will no longer show messages, because it has been launched from cinelerra and cinelerra will remain open and firefox 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 should study the Cinelerra code in depth and that now I did not have time for this 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 responsible 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 (< [email protected]>) 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 send/recv,
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 [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
El lunes, 1 de febrero de 2021 13:37:37 -03 Rafa Mar Multimedia en Gnu\Linux 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 the terminal will be free to execute other commands. The same will happen with Cinelerra. But the "system" option that is used to launch this option with this line warns that the process will no longer show messages, because it has been launched from cinelerra and cinelerra will remain open and firefox 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 should study the Cinelerra code in depth and that now I did not have time for this 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 responsible 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 (<
[email protected]>) 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 send/recv,
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 [email protected] 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 to open the default browser, whatever the reason, it seems more configurable like this now . -- - | Walter Casanova | - - | Gnu / Linux - SysAdmin | -
Walter, 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 to open the default browser, whatever the reason, it seems more configurable like this now .
Hopefully we can find a solution that works for everyone. Using $CIN_BROWSER caused a hang and that is why the switch to xdg-open. As a reminder, the hang occurred only when no browser was up already and the ? help key in the Batch Render menu was clicked on -- then you could do no more Cinelerra processing. RafaMar, Thanks for the feedback and I know that your programmer acquaintance is too busy for in depth work. And it is still very much appreciated! I will see if I can find another solution because I really like the ? key. CinelerraGG programming really is much harder than anyone realizes and takes a long, long time to understand all of the intricacies and still problems creep in.
My friend is having a lot of patience with me, today he gave me some good advice, but let's focus on Cinelerra GG I have forwarded this chain of emails to you. Here is his response. $CIN_BROWSER is a variable that just calls firefox. What happens if a person does not have firefox installed on their system? All the links that use $CIN_BROWSER will not work, they will do nothing. Do the test, go to the folder "/usr/bin" with administrator permissions and change the name to firefox, with a period behind it is enough. Now open Cinelerra from a terminal and try to open the commands you mentioned that work with $CIN_BROWSER, the result will be something like this: /bin/bash: firefox: command not found Now open the wizard that I made the button for and click, it is true that if you do not have another browser on your system, it will ask you with which application you want to open this file, or open it in an html editor, or in a text editor. In this specific case, when calling a local html file, if someone has assigned the opening of this type of file to another application, it will be this application that will open it. When this happens it is because the person is a programmer or works in web development environments, do not worry that he will know how to find the pdfs. I am not the right person to waste time making a button that satisfies the quirks of a user who does not want the help file to open in their default browser and has to be opened in Firefox no matter what. (I already told you what happens if firefox is not installed in the system) If anyone doubts what his revered $CIN_BROWSER variable really does, check the file.inc file at lines 45-46-47 and see what application it calls. I already anticipate that it is not enough to change this here, it is not that simple, but it is something that I would do, because if you do not have firefox Cinelerra it will fail in its calls to links with $CIN_BROWSER Don't worry about the [Parent] [RunMessage] error, any competent programmer or SysAdmin of Gnu/Linux knows that it is not of the slightest importance, and that more than an error it is a simple warning that does not affect to the stability or performance of Cinelerra. ----------------------------- After your answer two things have become very clear to me, $CIN_BROWSER is no better than xdg-open, it is simply an variable that should be modernized. $CIN_BROWSER only works with firefox, xdg-open does not force you to have firefox in order to get the Cinelerra links to work. ----------------------------- His advice is I not to waste any more time on a project so full of veteran users who believe they are proprietaries of the application and will do everything possible to sink any idea that does not come from them, and much more if it comes from a newcomer. Sadly, it is something very typical in the opensource environment. I'm going to heed his advice and take a break from Cinelerra. Phyllis, you can still count on me for spanish translations, if you want, otherwise, nothing happens, I will understand. Here in Spain we say that there are two types of people, those who put oil in the wheels so that they roll well and those who put sticks, to stop the good work. I am one of those who try to put oil, I cannot be comfortable in a team where there are people who dedicate themselves to putting sticks. Greetings to everyone, especially Phyllis and Andrew, with whom I have really enjoyed collaborating. El lun, 1 feb 2021 a las 20:14, Phyllis Smith via Cin (< [email protected]>) escribió:
Walter,
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 to open the default browser, whatever the reason, it seems more configurable like this now .
Hopefully we can find a solution that works for everyone. Using $CIN_BROWSER caused a hang and that is why the switch to xdg-open. As a reminder, the hang occurred only when no browser was up already and the ? help key in the Batch Render menu was clicked on -- then you could do no more Cinelerra processing.
RafaMar,
Thanks for the feedback and I know that your programmer acquaintance is too busy for in depth work. And it is still very much appreciated! I will see if I can find another solution because I really like the ? key. CinelerraGG programming really is much harder than anyone realizes and takes a long, long time to understand all of the intricacies and still problems creep in. -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
El lunes, 1 de febrero de 2021 19:52:34 -03 Rafa Mar Multimedia en Gnu\Linux via Cin escribió:
My friend is having a lot of patience with me, today he gave me some good advice, but let's focus on Cinelerra GG
I have forwarded this chain of emails to you. Here is his response.
$CIN_BROWSER is a variable that just calls firefox.
What happens if a person does not have firefox installed on their system? All the links that use $CIN_BROWSER will not work, they will do nothing.
Do the test, go to the folder "/usr/bin" with administrator permissions and change the name to firefox, with a period behind it is enough.
Now open Cinelerra from a terminal and try to open the commands you mentioned that work with $CIN_BROWSER, the result will be something like this: /bin/bash: firefox: command not found
Now open the wizard that I made the button for and click, it is true that if you do not have another browser on your system, it will ask you with which application you want to open this file, or open it in an html editor, or in a text editor.
In this specific case, when calling a local html file, if someone has assigned the opening of this type of file to another application, it will be this application that will open it. When this happens it is because the person is a programmer or works in web development environments, do not worry that he will know how to find the pdfs.
I am not the right person to waste time making a button that satisfies the quirks of a user who does not want the help file to open in their default browser and has to be opened in Firefox no matter what. (I already told you what happens if firefox is not installed in the system)
If anyone doubts what his revered $CIN_BROWSER variable really does, check the file.inc file at lines 45-46-47 and see what application it calls. I already anticipate that it is not enough to change this here, it is not that simple, but it is something that I would do, because if you do not have firefox Cinelerra it will fail in its calls to links with $CIN_BROWSER
Don't worry about the [Parent] [RunMessage] error, any competent programmer or SysAdmin of Gnu/Linux knows that it is not of the slightest importance, and that more than an error it is a simple warning that does not affect to the stability or performance of Cinelerra. ----------------------------- After your answer two things have become very clear to me, $CIN_BROWSER is no better than xdg-open, it is simply an variable that should be modernized.
$CIN_BROWSER only works with firefox, xdg-open does not force you to have firefox in order to get the Cinelerra links to work. ----------------------------- His advice is I not to waste any more time on a project so full of veteran users who believe they are proprietaries of the application and will do everything possible to sink any idea that does not come from them, and much more if it comes from a newcomer. Sadly, it is something very typical in the opensource environment.
I'm going to heed his advice and take a break from Cinelerra. Phyllis, you can still count on me for spanish translations, if you want, otherwise, nothing happens, I will understand.
Here in Spain we say that there are two types of people, those who put oil in the wheels so that they roll well and those who put sticks, to stop the good work. I am one of those who try to put oil, I cannot be comfortable in a team where there are people who dedicate themselves to putting sticks.
Greetings to everyone, especially Phyllis and Andrew, with whom I have really enjoyed collaborating.
El lun, 1 feb 2021 a las 20:14, Phyllis Smith via Cin (<
[email protected]>) escribió:
Walter,
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 to open the default browser, whatever the reason, it seems more configurable like this now .
Hopefully we can find a solution that works for everyone. Using $CIN_BROWSER caused a hang and that is why the switch to xdg-open. As a reminder, the hang occurred only when no browser was up already and the ? help key in the Batch Render menu was clicked on -- then you could do no more Cinelerra processing.
RafaMar,
Thanks for the feedback and I know that your programmer acquaintance is too busy for in depth work. And it is still very much appreciated! I will see if I can find another solution because I really like the ? key. CinelerraGG programming really is much harder than anyone realizes and takes a long, long time to understand all of the intricacies and still problems creep in. -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
I really don't understand what happened here but, I apologize, it could be that I was misunderstood. and more because my English is not very good. At no point have I wanted to impose my ideas, I only gave a humble opinion and I do not intend to change anything, only for a particular position. when I talk about environment variables. It's because GNU / linux users are generally used to doing and playing this, or at least most of it, and I don't think it's difficult to switch to .bashrc or zshrc.
*Walter,*
It was just a comment, but I support what's best for everyone on the programming level.
yes for the developer. using is xdg-open is better and avoids later problems great.
you do not need any approval from me friends.
I repeat again. I apologize if my comment caused any inconvenience
Do not worry. This is just the way programming works. Many times, I had to cover up the dog's ears around here because of the commentary. *RafaMar,* I understand your point of view and all of your help, feedback, and advice has been appreciated and has been used to make CinelerraGG better. Just a few comments. $CIN_BROWSER is a variable that just calls firefox.
Not true, Firefox is the default but the user can set it to anything. What happens if a person does not have firefox installed on their system?
Cinelerra does not hang and the user does not lose any work and that is what is most important. It is simply an variable that should be modernized
It is an environment variable that anyone can modernize on their own. We have a lot of old distros out there that we want to continue to work. so full of veteran users who believe they are proprietaries of the
application and will do everything possible to sink any idea that does not come from them, and much more if it comes from a newcomer.
Not at all true. We have taken and incorporated all ideas that came from anywhere.
On Mon, 1 Feb 2021, Phyllis Smith via Cin wrote:
yes for the developer. using is xdg-open is better and avoids later problems great.
$CIN_BROWSER is a variable that just calls firefox.
Hi all, may I make peace a bit? export CIN_BROWSER=xdg-open Set your $CIN_BROWSER to xdg-open and it should do the job. Should somebody prefer direct call of some definite browser, he still has the possibility to configure it explicitly. Why so much disputes for nothing... _______________________________________________________________________________ Georgy Salnikov NMR Group Novosibirsk Institute of Organic Chemistry Lavrentjeva, 9, 630090 Novosibirsk, Russia Phone +7-383-3307864 Email [email protected] _______________________________________________________________________________
В сообщении от Tuesday 02 February 2021 01:52:34 Rafa Mar Multimedia en Gnu\Linux via Cin написал(а):
My friend is having a lot of patience with me, today he gave me some good advice, but let's focus on Cinelerra GG
I have forwarded this chain of emails to you. Here is his response.
$CIN_BROWSER is a variable that just calls firefox.
? as lomg as override in Cinelerra_rc works I'm happy ..... On users, developers, and time .... well, different users have different workflows and tastes. Some prefer relative stability. Some can live with some changes. It hardly static - people who had more time in the past for adapting to "chages!!" may not have it anymore or at least for now. Sometimes new ideas universally better (for example I like virtual desktops and "hide window into titlebar" feature), sometimes ...not so. (KDE3 vs KDE4/5, Gnome2 vs Gnome3/4 vs Unity vs xfce vs IceWm ...) I for example can't read javascript, yet Shotcut's edl export written in this language now because main developer understand this lang well ... [0] so, yeah, preferences of developers and users matters ... Again, some ideas quite universal (source code is much simpler to alter than binary, yet not trivially simple. I can fix minor problem in Python script by guide [1] yet this doesn't make Blender itself any faster [tried animated titles from OLD Openshot 1.x, just because ... fixing Py script was much faster than bringing up modern qt5. Again, philosophy of usage .. if you prefer to install binary files - distro's provided pkg or flatpack is fine. If you want or need rareconfig or modification of source .. you better to have actually compileable on your resources project] I also not big fan of removing something because yeah, removing is always simpler than reintegrating something back. Sometimes this is not thing you can avoid, in bigger projects .... like kernel or Mesa. Also, popular in many medialibraries reworking symbol/function visibility sort of assume all ext. project have enough manpower for all this follow-us refactoring..... this doesn't feel so good at receiving end :/ yet I understand sometimes there is no other way to fit some concept in ... like both 8 and 10/12 bit h264 encoding (as it was done sometime in the past). Developers don't code at inf. speed, and sometimes good idea may not age well ... Life is full of such paradoxes, computing not expection! Sorry if you hoped for cleaner sub-world .... [0] - https://forum.shotcut.org/t/mlt2edl-script-error-fix/55 [1] - https://github.com/OpenShot/openshot-qt/issues/473
What happens if a person does not have firefox installed on their system? All the links that use $CIN_BROWSER will not work, they will do nothing.
Do the test, go to the folder "/usr/bin" with administrator permissions and change the name to firefox, with a period behind it is enough.
Now open Cinelerra from a terminal and try to open the commands you mentioned that work with $CIN_BROWSER, the result will be something like this: /bin/bash: firefox: command not found
Now open the wizard that I made the button for and click, it is true that if you do not have another browser on your system, it will ask you with which application you want to open this file, or open it in an html editor, or in a text editor.
In this specific case, when calling a local html file, if someone has assigned the opening of this type of file to another application, it will be this application that will open it. When this happens it is because the person is a programmer or works in web development environments, do not worry that he will know how to find the pdfs.
I am not the right person to waste time making a button that satisfies the quirks of a user who does not want the help file to open in their default browser and has to be opened in Firefox no matter what. (I already told you what happens if firefox is not installed in the system)
If anyone doubts what his revered $CIN_BROWSER variable really does, check the file.inc file at lines 45-46-47 and see what application it calls. I already anticipate that it is not enough to change this here, it is not that simple, but it is something that I would do, because if you do not have firefox Cinelerra it will fail in its calls to links with $CIN_BROWSER
Don't worry about the [Parent] [RunMessage] error, any competent programmer or SysAdmin of Gnu/Linux knows that it is not of the slightest importance, and that more than an error it is a simple warning that does not affect to the stability or performance of Cinelerra. ----------------------------- After your answer two things have become very clear to me, $CIN_BROWSER is no better than xdg-open, it is simply an variable that should be modernized.
$CIN_BROWSER only works with firefox, xdg-open does not force you to have firefox in order to get the Cinelerra links to work. ----------------------------- His advice is I not to waste any more time on a project so full of veteran users who believe they are proprietaries of the application and will do everything possible to sink any idea that does not come from them, and much more if it comes from a newcomer. Sadly, it is something very typical in the opensource environment.
I'm going to heed his advice and take a break from Cinelerra. Phyllis, you can still count on me for spanish translations, if you want, otherwise, nothing happens, I will understand.
Here in Spain we say that there are two types of people, those who put oil in the wheels so that they roll well and those who put sticks, to stop the good work. I am one of those who try to put oil, I cannot be comfortable in a team where there are people who dedicate themselves to putting sticks.
Greetings to everyone, especially Phyllis and Andrew, with whom I have really enjoyed collaborating.
El lun, 1 feb 2021 a las 20:14, Phyllis Smith via Cin (< [email protected]>) escribió:
Walter,
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 to open the default browser, whatever the reason, it seems more configurable like this now .
Hopefully we can find a solution that works for everyone. Using $CIN_BROWSER caused a hang and that is why the switch to xdg-open. As a reminder, the hang occurred only when no browser was up already and the ? help key in the Batch Render menu was clicked on -- then you could do no more Cinelerra processing.
RafaMar,
Thanks for the feedback and I know that your programmer acquaintance is too busy for in depth work. And it is still very much appreciated! I will see if I can find another solution because I really like the ? key. CinelerraGG programming really is much harder than anyone realizes and takes a long, long time to understand all of the intricacies and still problems creep in. -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
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 (< [email protected]>) escribió:
El lunes, 1 de febrero de 2021 13:37:37 -03 Rafa Mar Multimedia en Gnu\Linux 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 the terminal will be free to execute other commands. The same will happen with Cinelerra. But the "system" option that is used to launch this option with this line warns that the process will no longer show messages, because it has been launched from cinelerra and cinelerra will remain open and firefox 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 should study the Cinelerra code in depth and that now I did not have time for this 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 responsible 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 (<
[email protected]>) 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 send/recv,
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 [email protected] 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 to open the default browser, whatever the reason, it seems more configurable like this now .
-- - | Walter Casanova | - - | Gnu / Linux - SysAdmin | -
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
participants (6)
-
Andrea paz -
Andrew Randrianasulu -
Georgy Salnikov -
Phyllis Smith -
Rafa Mar Multimedia en Gnu\Linux -
Walter Casanova