[CinCV TNG] 5.1 updated tarballs and packages available.
sitelve at gmail.com
Sat Dec 10 19:30:33 CET 2016
> * Phyllis Smith/GG*
> * When you invoke each of the code base versions, none** of them are
> currently called "cin" or "cinx" except for 5.1 branch*
I did not say it. I meant that the idea of using Cin as the name under
which the application will be known (as the personal name of your branch),
is not good idea becase Cin is the common reduction of Cinelerra and
already belong to all.
As Danny already said: it's the same thing as Cinelerra, just shorter.
That's like calling Facebook FB.
> *Furthermore, when you install CV cinelerra, the installed command name is
> "cinelerra", not*
> *cinelerra-cv or cvo....*
Yes, you are right. I do not know why I was yesterday sure that CVO's
binary file is called `cinelerracv`
Obviously it was my glitch.
> * When you operate the HV build and run its command line binary, it is
> called "cinelerra". So if anything CV is using HV's command*
> *name, and it is already a conflict. *
Probably it should be changed. At least it makes sense to change it as it
is made in CVE (cinelerracve) and CVA (cinelerracvabin)
> *"cin" and "cinx" do not conflict with any of these version or command
> names. I really would prefer that it be called that,*
> *because it is already called that in the repo. *
My main suggestion was a change of name in About->Preferences because
that's how the branch is known among users.
Renaming of binary file was optional.
> *Igor is obviously the expert on the 2 versions and all of the branchs....*
:-/)) This "expert" made a lot of compilations, but forgot the name of
the binary file.
I'm no expert. These two plugins are "on my radar", because I have been
puzzling with FO and with HCCH's two parameters (start/end band for
lowpass). It seems to me that there is a bug(?) in HCCH, but I am not sure.
> *Am 10.12.2016 0:48, schrieb Phyllis Smith: *
>> * I have made the corrections .. The only reason I submitted it was
>> because hardly anyone wants to do documentation ..*
I like this compare. It is laconic and capacious.
It can be complemented, but this can be done gradually, step by step. It is
a big work.
> *Would you be interested in having an open bugtracker on -cv.org
* Users would have a way to report bugs and participate in them. I
think that level of user interaction is really missing here,
nearly every opensource project out there has а bugtracker.*
Oh.. these users do not want to make reports in the ML ..
But probably this would be a convenient thing for a user who do not want to
register in the ML
Is it possible to make an e-mail automatic notification to alert CV-ML's
subscribers when new report/message appears in the bugtracker ?
> * But in the end, I didn't put it up because no one wanted to use it from
> the developers side and our old bugtracker died out quickly because of
> that. -Danny*
There is a duplication of functions here. CV-ML wins because it is both
"bugtracker" and platform for discussion.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Cinelerra