|
Christopher Duncan wrote: Could I write this myself? Absolutely. Not.
"What Turing gave us for the first time (and without Turing you just couldn't do any of this) is he gave us a way of thinking about and taking seriously and thinking in a disciplined way about phenomena that have, as I like to say, trillions of moving parts.
Until the late 20th century, nobody knew how to take seriously a machine with a trillion moving parts. It's just mind-boggling." Daniel C. Dennett
|
|
|
|
|
Christopher Duncan wrote: Why aren't you writing pro video editing software?
'Cos all the pr0n I watch is already nicely edited.
Move along there, nothing to see here.
(Friday afternoon syndrome)
|
|
|
|
|
There are some alternatives...
LightWorks is a major player with pro editors. A few motion pictures have been done on it and it continues to pick up penetration each year. It isn't poised to knock off any of the ones you mentioned but then again Google didn't start out with 100% market share either.
The regular version (which is fairly capable and will teach you the basics) is free while there is a pro version that will set you back a massive $60 USD/yr.
LightWorks uses a different paradigm than the standard timeline-based editors and it definitely takes some getting used to. However, I think it is a good setup and once I learned it I think it has some advantages in the way the workflow is setup. I suggest giving it a look if you are tired of getting screwed by the big 3.
As for my rant...
As a developer, I think we sometimes walk around feeling like we are holding the hammer and every problem is a nail. In our limited exposure to any market, we think that there is a glaring gap that hasn't yet been filled or a major business opportunity that we can quickly write a script for and head for the sand. But any serious business venture starts out with lots and lots of research to understand the need, the opportunity, and to validate our ideas and assumptions before we even start a line of code. I'm not suggesting what you propose can't be done... quite the opposite. But I'm not sure that an enthusiastic posting on a coding site is the best start to a massive software project. (Unless you are looking for people to shoot you down... )
Many, many great software projects start with someone that sees a need and writes something that fills a void. I certainly think what you propose is possible and I hope you really can get something going, get some momentum, and release something useful and timely. But having been involved with some of this startup kind of stuff for a few years, I suggest making sure you know everything there is to know about the NLE segment... who the players are, what the advantages and disadvantages are of each, and get an idea of what your solution will do and what it will offer.
I also suggest starting SMALL and getting something out the door quick and into people's hands. Yes... they may blast it as useless for their needs but they will provide useful feedback. Your best ideas will come from your users who approach the problem without preconceived notions about what your software should or shouldn't do. Maybe write something that will let you import clips, set trim points, and render an output. Ensure you get over that minimum level of functionality before you take on the big boys.
Good luck!
|
|
|
|
|
Jason Gleim wrote: But any serious business venture starts out with lots and lots of research to understand the need, the opportunity, and to validate our ideas and assumptions before we even start a line of code.
But many non-serious ones don't do that. And some succeed.
|
|
|
|
|
Yes... that's true. But the post isn't about a hobby project. The OP is proposing a commercial product to go up against a number of established players. So while I appreciate the input, your comment really has no bearing on the discussion at hand.
|
|
|
|
|
Jason Gleim wrote: The OP is proposing a commercial product to go up against a number of established players.
And my comment applies to that.
Jason Gleim wrote: your comment really has no bearing on the discussion at hand.
In your opinion.
|
|
|
|
|
If it's just editing and not effects, I've found Sony's product to be reasonable.
The reason nobody breaks in is that everybody wants to use a standard format. Film makers develop their preference and stick to it for their career.
|
|
|
|
|
You can't make me, you can't make me.
|
|
|
|
|
Has anyone seen this this?
c+=, feminist programing language,created to smash the toxic Patriarchy that is inherent in and that permeates all current computer programming languages.
|
|
|
|
|
Quote: No constants or persistence. Rigidity is masculine; the feminine is fluid. I.e., fluid mechanics is hard for men 'because it deals with "feminine" fluids in contrast to "masculine" rigid mechanics'.
Pretty sure that's not the definition of "fluid mechanics"...
Yet another joke language, funny though
|
|
|
|
|
Well, it's still better than COBOL...
|
|
|
|
|
Certainly C is a much more fluid language than COBOL. Besides, it's not the developers who are rigid, it's the computers.
I must with all due respect to Grace Hopper et al that COBOL is the only feminine language. Now I have to be chauvinistic and say: "Just look at how verbose it is!"
Come to think of it, I think wives are less fluid than husbands -- husbands tend to want to leave dirty laundry wherever it lands, but wives insist on putting it in the hamper.
|
|
|
|
|
PIEBALDconsult wrote: husbands tend to want to leave dirty laundry wherever it lands, but wives insist on putting it in the hamper
Other way round here: but guess who gets to do the washing?
|
|
|
|
|
+5
no, never!
it´s oh so amusing cool
i haven´t yet looked into the code right now, but i´ll give the inherpreter a try definitely!
apart from that, the devil in me (or the angel ) thinks it may be sort of counterproductive to think, a language is feministic/patriarchic...
why is there always the Need for stereotyped thinking when it comes to men´s and women´s (programming) Habits...
i´m so bored with that...
there are good guys and bad Girls and vice versa...
|
|
|
|
|
Now that's funny!!
"Go forth into the source" - Neal Morse
|
|
|
|
|
even if nobody would believe it but i chuckled by reading this
(Anti)FeministSoftwareFoundation wrote:
plz::raise_awareness of_the_following "I don't feel like it, try again later\n";
post_on_tumblr trigger("RAPE\n");
|
|
|
|
|
similar to:
Quote: •Instead of Booleans we now have Boolean+, or bool+ for short, which has three states: true, false, and maybe. The number of states may go up as intersectionality of the moment calls for such a need.
"Go forth into the source" - Neal Morse
|
|
|
|
|
|
I would be curious to see how it will meet the numeric challenge of the following requirement.
"After birth, a program rolls for a 40% chance of executing literally as the code is written, 40% of being "psychoanalytically incompatible", and 40% of executing by a metaphorical epistemology the order of the functions found in main()."
|
|
|
|
|
"Access to this repository has been disabled by GitHub staff. Contact support to restore access to this repository."
Is unfortunately the message I got when trying to join in the fun. I guess that isn't so surprising given the other reports. Still, it would have been nice to see the whole gag, rather than just the punch-line.
|
|
|
|
|
|
Ahhaha :breathes: hahahahaha :breathes: ha!
I thought the punch-line at GitHub was funny. I'd never imagined the whole joke could be that funny and apply so many subtle and overt digs at the fairer sex. I'll share it with the missus in the morning since she''s got a fairly robust sense of humour. Zero coding knowledge, but that seems like a minor concern.
Thank-you so much!
|
|
|
|
|
I've just been writing a little tool at work and I wanted a busy indicator so I decided to steal the one out our main application. I had assumed it would have been an animated GIF or something, but no, it was this:
How to write a loading circle animation in .NET?[^]
Not seen that article before, but good work Martin.
You see, you write a little article and before you know it the code is in source control systems the world over!
Regards,
Rob Philpott.
|
|
|
|
|
If your saw a post of mine yesterday about getting a VB program landed on me 'to make it work' that is all, (it's not a complete rewrite in C# which is what it needs) I have done what I was dreading and it hasn't gone wrong yet testing abounds. I now move to the second part of the thing the flat file prep utility. Basically and ini file creator (which is then read in as a string dropping all /r /n picked out using substring)...which I have to add some serial port configuration to. It is a work of art, three different naming styles On Error Resume Next, GoTo used interestingly also this is using VS2013 which I have never used before...on the joy
Roll on 17:30 and the weekend!!
|
|
|
|
|
sounds like the coders were professionals!
I love this style, had to do the same Thing and i was so impressed by that style:
variablenames -> var1,var2 ...
if something goes wrong -> On Error Resume Next
no comments !
and no structure at all
was the best time of my life and i Keep up to follow that guide lines
thanks to the Person who wrote that code
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|