Re: [dev] Request for name suggestions: suckless video editor

2017-01-12 Thread Mattias Andrée
On Fri, 13 Jan 2017 01:34:40 +0530
Mohammed Zohaib Ali Khan  wrote:

> > How about `Tasveer'. It actually means pictorial
> > representation of information and it can alternatively
> > be abbreviated to tsvr - Teletyped Simple Video
> > Revision[er] (or something else with R. I honestly feel
> > `Revision[er]' is cooler than `editor' ;) ).
> >
> > Regards,
> > Zohaib  
> 
> Adding to my previous comment `Tasveer' has a deep
> meaning. It comes from the root letters TSVR. Which when
> used in this sequence form words which are all used to
> express similar meanings. Some of which I know of are:
> 
> 1. Tasavvur - To imagine.
> 2. Tasveer - Pictorial representation.
> 
> There are many coming out of these root letters but
> unfortunately I do not know all, as I am no linguist in
> semetic languages.
> 
> 
> Regards,
> 
> Zohaib
> 

I like the suggestion, but I prefer ‘blind’.


pgpTLQWix3U2r.pgp
Description: OpenPGP digital signature


Re: [dev] Request for name suggestions: suckless video editor

2017-01-12 Thread Mohammed Zohaib Ali Khan
> How about `Tasveer'. It actually means pictorial representation of
> information and it can alternatively be abbreviated to tsvr -
> Teletyped Simple Video Revision[er] (or something else with R. I
> honestly feel `Revision[er]' is cooler than `editor' ;) ).
>
> Regards,
> Zohaib

Adding to my previous comment `Tasveer' has a deep meaning. It comes
from the root letters TSVR. Which when used in this sequence form
words which are all used to express similar meanings. Some of which I
know of are:

1. Tasavvur - To imagine.
2. Tasveer - Pictorial representation.

There are many coming out of these root letters but unfortunately I do
not know all, as I am no linguist in semetic languages.


Regards,

Zohaib



Re: [dev] Request for name suggestions: suckless video editor

2017-01-12 Thread Mohammed Zohaib Ali Khan
On Thu, Jan 12, 2017 at 8:05 PM, Calvin Morrison  wrote:
>
> On 11 January 2017 at 20:12, Mattias Andrée  wrote:
> > Greetings!
> >
> > I'm working a non-graphical video editor. However, I need a
> > proper name for the project, and I have no idea what to call
> > it, so I'm taking suggestions from you.
> >
> > A non-graphical video editor may sound a bit insane. There
> > will be a graphical tool for finding locating frames, but
> > that is as graphical as it gets, as far as I can foresee at
> > the moment. The reasons for a non-graphical video editor
> > are:
> >
> > •  It's source control friendly and it's easy for a user to
> >resolve merge conflicts and identify changes.
> >
> > •  Rendering can take a very long time. With this approach,
> >the user can use Make to only rerender parts that have
> >been changes.
> >
> > •  No room for buggy GUI:s, which currently is a problem on
> >the large video editors for Linux.
> >
> > •  Less chance that the user makes a change by mistake
> >without noticing it, such as moving a clip in the editor
> >by mistake instead of for example resizing.
> >
> > •  Even old crappy computers can be used for large projects.
> >
> > •  Very easy to utilise command line image editors for modify
> >frames, or to add your own tools for custom effects.
> >
> > Currently there is no support for audio, I'm not sure it's
> > actually needed, but I will investigate this later. If it's
> > added, I will only add tools for audio, it will not be for
> > audio effects, such tools already exists and are not needed.
> >
> > The video editor uses it's own format, it is a simply container
> > with the metadata: number of frames, width, heights, and
> > pixel format, followed by a magic value and the video in a
> > raw format. Currently the only support pixel format is
> > CIE XYZ with alpha expressed in `double`:s, but in the future
> > I may also add support for `float`:s for faster computations.
> > So the format is not portable between machines.
> >
> >
> > Mattias Andrée
>
> How about?
>
> sve?
>
> suckless video editor.
> simple video editor
> small video edtior
>
> or if you're hardcore
>
> fsve
>
> f***ing small video editor
> f***ing suckless video editor
> f**ing simple video editor
>

How about `Tasveer'. It actually means pictorial representation of
information and it can alternatively be abbreviated to tsvr -
Teletyped Simple Video Revision[er] (or something else with R. I
honestly feel `Revision[er]' is cooler than `editor' ;) ).

Regards,
Zohaib



Re: [dev] Request for name suggestions: suckless video editor

2017-01-12 Thread Calvin Morrison
On 11 January 2017 at 20:12, Mattias Andrée  wrote:
> Greetings!
>
> I'm working a non-graphical video editor. However, I need a
> proper name for the project, and I have no idea what to call
> it, so I'm taking suggestions from you.
>
> A non-graphical video editor may sound a bit insane. There
> will be a graphical tool for finding locating frames, but
> that is as graphical as it gets, as far as I can foresee at
> the moment. The reasons for a non-graphical video editor
> are:
>
> •  It's source control friendly and it's easy for a user to
>resolve merge conflicts and identify changes.
>
> •  Rendering can take a very long time. With this approach,
>the user can use Make to only rerender parts that have
>been changes.
>
> •  No room for buggy GUI:s, which currently is a problem on
>the large video editors for Linux.
>
> •  Less chance that the user makes a change by mistake
>without noticing it, such as moving a clip in the editor
>by mistake instead of for example resizing.
>
> •  Even old crappy computers can be used for large projects.
>
> •  Very easy to utilise command line image editors for modify
>frames, or to add your own tools for custom effects.
>
> Currently there is no support for audio, I'm not sure it's
> actually needed, but I will investigate this later. If it's
> added, I will only add tools for audio, it will not be for
> audio effects, such tools already exists and are not needed.
>
> The video editor uses it's own format, it is a simply container
> with the metadata: number of frames, width, heights, and
> pixel format, followed by a magic value and the video in a
> raw format. Currently the only support pixel format is
> CIE XYZ with alpha expressed in `double`:s, but in the future
> I may also add support for `float`:s for faster computations.
> So the format is not portable between machines.
>
>
> Mattias Andrée

How about?

sve?

suckless video editor.
simple video editor
small video edtior

or if you're hardcore

fsve

f***ing small video editor
f***ing suckless video editor
f**ing simple video editor



Re: [dev] Request for name suggestions: suckless video editor

2017-01-12 Thread Finn O'leary

On 2017-01-12 3:52 am, Amer wrote:

I want the tools to have a common prefix of 2 to 4 characters plus
a dash. Any other ideas of awesome arbitrary things, I cannot think
of anything else that is not already used?


Short names were exhausted, really?)
At least AUR is free of them.

eiv
eivy
evior
eviour
ouvie
muv
cvq
veq
yvi
vidj
vwet
koe
koan
fyu
hevu
...


'ved' seems to be free. It also follows suite of names for text editors 
:D




Re: [dev] Request for name suggestions: suckless video editor

2017-01-12 Thread Mattias Andrée
On Thu, 12 Jan 2017 13:55:36 +0100
Laslo Hunhold  wrote:

> On Thu, 12 Jan 2017 02:12:11 +0100
> Mattias Andrée  wrote:
> 
> Hey Mattias,
> 
> > I'm working a non-graphical video editor. However, I
> > need a proper name for the project, and I have no idea
> > what to call it, so I'm taking suggestions from you.  
> 
> just call it "blind", the name is not taken afaik.

That's a fun name. I'll use it unless someone comes
up with something even better.

> 
> > Currently there is no support for audio, I'm not sure
> > it's actually needed, but I will investigate this
> > later. If it's added, I will only add tools for audio,
> > it will not be for audio effects, such tools already
> > exists and are not needed.  
> 
> Well, audio should be in it in case you want to anything
> with it other than uploading webm's to 4chan which are
> silent by default.

I meant, that I don't think there is a need for the project
to support audio, ffmpeg and tools for effects are probably
enough.

> 
> > The video editor uses it's own format, it is a simply
> > container with the metadata: number of frames, width,
> > heights, and pixel format, followed by a magic value
> > and the video in a raw format. Currently the only
> > support pixel format is CIE XYZ with alpha expressed in
> > `double`:s, but in the future I may also add support
> > for `float`:s for faster computations. So the format is
> > not portable between machines.  
> 
> single- and double-precision floating-point numbers are
> standardized and thus portable, however, you have to deal
> with endianness one way or another. I would generally
> recommend using doubles despite the speed-tradeoff,
> because rounding errors are horrible enough, especially
> if we're talking about an editing-pipeline.

Yes, that's why I choose to use it, and it will be
the default even if single-precision is added.

> 
> Also, keep in mind that the data-format is the most
> crucial component of your software. If you get it right
> and make it "network-safe", you can do anything with it.
> If you mess it up, make it too complex or too simple, you
> might as well not start working on a video editor. If you
> store each frame in a raw format anyway, you might just
> think about using ffmpeg to extract all keyframes,
> convert them to farbfeld and align them in memory in some
> way (as a suggestion). As discussed at the last slcon, I
> am still in the process of finding the right approach
> with farbfeld, so stay tuned.
> 
> Keep us updated here, but keep in mind that video editing
> is a monumental task. I have been working on multiple
> concepts for a suckless image editor for two years now
> and just a few weeks ago I was able to hit a breakthrough
> I hope to be able to pursue in the next months. Image
> editing is a much simpler task than video editing,
> especially given the sucky containers that are used in
> the industry.
> 
> Cheers
> 
> Laslo
> 



pgpCz9ulVTUF_.pgp
Description: OpenPGP digital signature


Re: [dev] Request for name suggestions: suckless video editor

2017-01-12 Thread Laslo Hunhold
On Thu, 12 Jan 2017 02:12:11 +0100
Mattias Andrée  wrote:

Hey Mattias,

> I'm working a non-graphical video editor. However, I need a
> proper name for the project, and I have no idea what to call
> it, so I'm taking suggestions from you.

just call it "blind", the name is not taken afaik.

> Currently there is no support for audio, I'm not sure it's
> actually needed, but I will investigate this later. If it's
> added, I will only add tools for audio, it will not be for
> audio effects, such tools already exists and are not needed.

Well, audio should be in it in case you want to anything with it other
than uploading webm's to 4chan which are silent by default.

> The video editor uses it's own format, it is a simply container
> with the metadata: number of frames, width, heights, and
> pixel format, followed by a magic value and the video in a
> raw format. Currently the only support pixel format is
> CIE XYZ with alpha expressed in `double`:s, but in the future
> I may also add support for `float`:s for faster computations.
> So the format is not portable between machines.

single- and double-precision floating-point numbers are standardized
and thus portable, however, you have to deal with endianness one way or
another. I would generally recommend using doubles despite the
speed-tradeoff, because rounding errors are horrible enough, especially
if we're talking about an editing-pipeline.

Also, keep in mind that the data-format is the most crucial component of
your software. If you get it right and make it "network-safe", you can
do anything with it. If you mess it up, make it too complex or too
simple, you might as well not start working on a video editor.
If you store each frame in a raw format anyway, you might just think
about using ffmpeg to extract all keyframes, convert them to farbfeld
and align them in memory in some way (as a suggestion). As discussed at
the last slcon, I am still in the process of finding the right approach
with farbfeld, so stay tuned.

Keep us updated here, but keep in mind that video editing is a
monumental task. I have been working on multiple concepts for a
suckless image editor for two years now and just a few weeks ago I was
able to hit a breakthrough I hope to be able to pursue in the next
months. Image editing is a much simpler task than video editing,
especially given the sucky containers that are used in the industry.

Cheers

Laslo

-- 
Laslo Hunhold 



Re: [dev] Request for name suggestions: suckless video editor

2017-01-12 Thread Mattias Andrée
On Thu, 12 Jan 2017 12:42:02 +0100
Hadrien Lacour  wrote:

> So this is a bit like Vapoursynth?
> 

I'm not sure how Vapoursynth works, but it sounds like
the basic idea is the same, but that the approach is
different.


pgpSVEOvRAQfV.pgp
Description: OpenPGP digital signature


Re: [dev] Request for name suggestions: suckless video editor

2017-01-12 Thread Hadrien Lacour
So this is a bit like Vapoursynth?



Re: [dev] Request for name suggestions: suckless video editor

2017-01-12 Thread Mattias Andrée
It's a great idea, what do you think about ‘teletyped video’?

On Thu, 12 Jan 2017 16:47:36 +0800
Ivan Tham  wrote:

> I would suggest TV (Text-based Video editor).
> 
> On Wed, Jan 11, 2017 at 08:39:44PM -0800, Louis Santillan
> wrote:
> >(ht) Hot Tub
> >(httm) Hot Tub Time Machine
> >(ufeh) *nix Flying Erase-Head (an early video editing
> >machines) (ued) *nix EditDroid
> >(vzmx) Vision Mixer
> >
> >
> >Github suggests:
> >(pos) psychic-octo-spork
> >(sdd) super-duper-doodle
> >(syen) symmetrical-enigma
> >(vpara) vigilant-parakeet
> >(sspoon) super-spoon
> >
> >On Wed, Jan 11, 2017 at 7:56 PM, Mattias Andrée
> > wrote:  
> >> On Thu, 12 Jan 2017 05:52:27 +0200
> >> Amer  wrote:
> >>  
> >>> >I want the tools to have a common prefix of 2 to 4
> >>> >characters plus a dash. Any other ideas of awesome
> >>> >arbitrary things, I cannot think of anything else
> >>> >that is not already used?  
> >>>
> >>> Short names were exhausted, really?)
> >>> At least AUR is free of them.
> >>>
> >>> eiv
> >>> eivy
> >>> evior
> >>> eviour
> >>> ouvie
> >>> muv
> >>> cvq
> >>> veq
> >>> yvi
> >>> vidj
> >>> vwet
> >>> koe
> >>> koan
> >>> fyu
> >>> hevu
> >>> ...
> >>>  
> >>
> >> The name can be long, but it must have a short
> >> abbreviation that I can use as a prefix for the
> >> names of the commands.  
> >  
> 



pgpJllckMK23z.pgp
Description: OpenPGP digital signature


Re: [dev] Request for name suggestions: suckless video editor

2017-01-12 Thread Ivan Tham

I would suggest TV (Text-based Video editor).

On Wed, Jan 11, 2017 at 08:39:44PM -0800, Louis Santillan wrote:

(ht) Hot Tub
(httm) Hot Tub Time Machine
(ufeh) *nix Flying Erase-Head (an early video editing machines)
(ued) *nix EditDroid
(vzmx) Vision Mixer


Github suggests:
(pos) psychic-octo-spork
(sdd) super-duper-doodle
(syen) symmetrical-enigma
(vpara) vigilant-parakeet
(sspoon) super-spoon

On Wed, Jan 11, 2017 at 7:56 PM, Mattias Andrée  wrote:

On Thu, 12 Jan 2017 05:52:27 +0200
Amer  wrote:


>I want the tools to have a common prefix of 2 to 4
>characters plus a dash. Any other ideas of awesome
>arbitrary things, I cannot think of anything else that
>is not already used?

Short names were exhausted, really?)
At least AUR is free of them.

eiv
eivy
evior
eviour
ouvie
muv
cvq
veq
yvi
vidj
vwet
koe
koan
fyu
hevu
...



The name can be long, but it must have a short
abbreviation that I can use as a prefix for the
names of the commands.




--
Do what you like, like what you do.  -- Pickfire



Re: [dev] Request for name suggestions: suckless video editor

2017-01-11 Thread Louis Santillan
(ht) Hot Tub
(httm) Hot Tub Time Machine
(ufeh) *nix Flying Erase-Head (an early video editing machines)
(ued) *nix EditDroid
(vzmx) Vision Mixer


Github suggests:
(pos) psychic-octo-spork
(sdd) super-duper-doodle
(syen) symmetrical-enigma
(vpara) vigilant-parakeet
(sspoon) super-spoon



On Wed, Jan 11, 2017 at 7:56 PM, Mattias Andrée  wrote:
> On Thu, 12 Jan 2017 05:52:27 +0200
> Amer  wrote:
>
>> >I want the tools to have a common prefix of 2 to 4
>> >characters plus a dash. Any other ideas of awesome
>> >arbitrary things, I cannot think of anything else that
>> >is not already used?
>>
>> Short names were exhausted, really?)
>> At least AUR is free of them.
>>
>> eiv
>> eivy
>> evior
>> eviour
>> ouvie
>> muv
>> cvq
>> veq
>> yvi
>> vidj
>> vwet
>> koe
>> koan
>> fyu
>> hevu
>> ...
>>
>
> The name can be long, but it must have a short
> abbreviation that I can use as a prefix for the
> names of the commands.



Re: [dev] Request for name suggestions: suckless video editor

2017-01-11 Thread Mattias Andrée
On Thu, 12 Jan 2017 05:52:27 +0200
Amer  wrote:

> >I want the tools to have a common prefix of 2 to 4
> >characters plus a dash. Any other ideas of awesome
> >arbitrary things, I cannot think of anything else that
> >is not already used?  
> 
> Short names were exhausted, really?)
> At least AUR is free of them.
> 
> eiv
> eivy
> evior
> eviour
> ouvie
> muv
> cvq
> veq
> yvi
> vidj
> vwet
> koe
> koan
> fyu
> hevu
> ...
> 

The name can be long, but it must have a short
abbreviation that I can use as a prefix for the
names of the commands.


pgpvTaVmWOA1R.pgp
Description: OpenPGP digital signature


Re: [dev] Request for name suggestions: suckless video editor

2017-01-11 Thread Amer

I want the tools to have a common prefix of 2 to 4 characters plus
a dash. Any other ideas of awesome arbitrary things, I cannot think
of anything else that is not already used?


Short names were exhausted, really?)
At least AUR is free of them.

eiv
eivy
evior
eviour
ouvie
muv
cvq
veq
yvi
vidj
vwet
koe
koan
fyu
hevu
...



Re: [dev] Request for name suggestions: suckless video editor

2017-01-11 Thread Mattias Andrée
On Wed, 11 Jan 2017 21:34:08 -0500
Greg Reagle  wrote:

> Why don't you name it after something totally arbitrary
> but totally awesome.  For example, there is a tree that
> is so toxic that standing under it during the rain will
> burn your skin, and it has a great name in Spanish, arbol
> de la muerte. [1]  There's all sorts of really cool stuff
> in nature.
> 
> [1]
> http://www.sciencealert.com/here-s-why-you-shouldn-t-stand-under-world-s-most-dangerous-tree
> 

Very interesting tree. I guess Manchineel works, but then
the question is, how should I name the tools? I want the
tools to have a common prefix of 2 to 4 characters plus a
dash. Perhaps ‘hm-’, as in ‘hippomane mancinella’, but
that could be confusing.

Any other ideas of awesome arbitrary things, I cannot
think of anything else that is not already used?


pgpkKGQbLEkw2.pgp
Description: OpenPGP digital signature


Re: [dev] Request for name suggestions: suckless video editor

2017-01-11 Thread Greg Reagle
Why don't you name it after something totally arbitrary but totally
awesome.  For example, there is a tree that is so toxic that standing
under it during the rain will burn your skin, and it has a great name in
Spanish, arbol de la muerte. [1]  There's all sorts of really cool stuff
in nature.

[1]
http://www.sciencealert.com/here-s-why-you-shouldn-t-stand-under-world-s-most-dangerous-tree



Re: [dev] Request for name suggestions: suckless video editor

2017-01-11 Thread Mattias Andrée
On Wed, 11 Jan 2017 17:37:20 -0800
Noah Birnel  wrote:

> On Wed, Jan 11, 2017 at 5:12 PM, Mattias Andrée
>  wrote:
> > Greetings!
> >
> > I'm working a non-graphical video editor. However, I
> > need a proper name for the project, and I have no idea
> > what to call it, so I'm taking suggestions from you.
> >
> > A non-graphical video editor may sound a bit insane.
> > There will be a graphical tool for finding locating
> > frames, but that is as graphical as it gets, as far as
> > I can foresee at the moment. The reasons for a
> > non-graphical video editor are:
> >  
> My goodness, you don't need to excuse it. This is a

I just wanted to explain it in case someone though it
was a waste of time, because it does sound impractical
to use.

> beautiful idea. It reminds me of sox (SOund eXchange), so
> it should of course be vix (VIdeo eXchange) or vex.

Good suggestion, however, there are already projects with
those names, so I cannot use either name.

> 
> Any code worth sharing yet?

Yes, there is the code as it looks right now:
https://github.com/maandree/vutil
However, I started out using RGBA and have not
tested to code since I change it to CIE XYZ.
Here is the last tested revision:
https://github.com/maandree/vutil/tree/51411b26324ce4a142c817428d4f34c0f94a6d94

> 
> Cheers,
> 
> Noah
> 



pgp_hGyc2gruy.pgp
Description: OpenPGP digital signature


Re: [dev] Request for name suggestions: suckless video editor

2017-01-11 Thread Noah Birnel
On Wed, Jan 11, 2017 at 5:12 PM, Mattias Andrée  wrote:
> Greetings!
>
> I'm working a non-graphical video editor. However, I need a
> proper name for the project, and I have no idea what to call
> it, so I'm taking suggestions from you.
>
> A non-graphical video editor may sound a bit insane. There
> will be a graphical tool for finding locating frames, but
> that is as graphical as it gets, as far as I can foresee at
> the moment. The reasons for a non-graphical video editor
> are:
>
My goodness, you don't need to excuse it. This is a beautiful idea. It
reminds me of sox (SOund eXchange), so it should of course be vix
(VIdeo eXchange) or vex.

Any code worth sharing yet?

Cheers,

Noah



[dev] Request for name suggestions: suckless video editor

2017-01-11 Thread Mattias Andrée
Greetings!

I'm working a non-graphical video editor. However, I need a
proper name for the project, and I have no idea what to call
it, so I'm taking suggestions from you.

A non-graphical video editor may sound a bit insane. There
will be a graphical tool for finding locating frames, but
that is as graphical as it gets, as far as I can foresee at
the moment. The reasons for a non-graphical video editor
are:

•  It's source control friendly and it's easy for a user to
   resolve merge conflicts and identify changes.

•  Rendering can take a very long time. With this approach,
   the user can use Make to only rerender parts that have
   been changes.

•  No room for buggy GUI:s, which currently is a problem on
   the large video editors for Linux.

•  Less chance that the user makes a change by mistake
   without noticing it, such as moving a clip in the editor
   by mistake instead of for example resizing.

•  Even old crappy computers can be used for large projects.

•  Very easy to utilise command line image editors for modify
   frames, or to add your own tools for custom effects.

Currently there is no support for audio, I'm not sure it's
actually needed, but I will investigate this later. If it's
added, I will only add tools for audio, it will not be for
audio effects, such tools already exists and are not needed.

The video editor uses it's own format, it is a simply container
with the metadata: number of frames, width, heights, and
pixel format, followed by a magic value and the video in a
raw format. Currently the only support pixel format is
CIE XYZ with alpha expressed in `double`:s, but in the future
I may also add support for `float`:s for faster computations.
So the format is not portable between machines.


Mattias Andrée


pgpdrwHaAau__.pgp
Description: OpenPGP digital signature