Re: Can't compile on Slackware 13

On Sunday 25 April 2010, Dan Dennedy wrote:
>On Sun, Apr 25, 2010 at 3:54 PM, Shlomo Katz <[email protected]> wrote:
>>> That strikes me as re-inventing the wheel.  Kino already Just Works(TM).
>
>Only if the wheel is in the shape of DV and the size is SD or less.

What do you call SD?  My camera (Sony trv-460) does 720x480 to digital hi8 
tapes, which isn't HDTV, but it sure beats the daylights out of Never Twice 
Same Color.  The two weddings I've shot with it, and processed into DVD's 
were far sharper on my monitor, playing from the DVD's I gave them, than 
would have ever reproduced on the NTSC tv's everybody who played them had at 
the time.  I apologized for the poor repo on their tv's and explained that 
the video was much better than what they were seeing on their tv with a built 
in dvd player.

>> I agree! Kino is great. Period. I have tried many other editors and they
>> cannot compare, either because they don't include necessary features
>> (such as capture, timedate stamps), or they crash all the time on my low
>> end system (kdenlive, lives). I do, however, have high hopes for
>> OpenShot, and am eagerly anticipating the next release.
>>
>> As everyone knows, the software reflects the abilities of the programmer
>> (like good literature is a reflection of the author's literary worth),
>> and we have obviously been spoiled by Dan. It's a sad statement of free
>> software that it's prone to sudden disappearances. But then, no ones
>> paying Dan to
>
>It if is any consolation, I now work on MLT, which is the engine of
>OpenShot and Kdenlive and addresses the foundation that Kino lacks to
>deal with various wheel sizes. I overlapped development of Kino and
>MLT for several years and did not abandon Kino until I felt it was
>complete enough to hold people over until the new tools became ready.
>I think we are very close to the inflection point I had anticipated,
>possibly even passed it.

It will not be 'feature complete' until it can import from the camera over 
firewire, and control that camera over the firewire back channel like kino 
does seamlessly.

As fort lives, I had a job to clean up a tour dvd, and used lives to copy it 
to hard drive.  Audio and video looked great, but it was late, and the job 
needed the materials returned the next day since that was the only copy.

So I shut lives down, figuring I could start right back up where I'd left 
off.  Unforch, I was never able to find the magic twanger that gave me sound 
again, so that was 2 days work lost.  You tried to help at the time but 
nothing suggested rang the bell.  I messed with it off & one for another 
month and nuked it.  I tried kdenlive too, but it didn't want to open the 
files lives had written.

>> sit up all night and develop Kino, and he has expenses like everyone
>> else. Still, I disagree that Kino shouldn't be continued. It doesn't make
>> sense to leave such a gem to rot in the wasteland of frozen packages.
>> Could you see Apple one day saying, "Sorry, we have decided not to
>> continue with Final Cut"? I know one can't compare the two, but really: I
>> use Kino to edit movies under tight deadlines, and in place of FC.
>>
>> I don't know what to say, because this is really an issue. Perhaps a
>> rethinking of free software, and something to compensate the developers
>> for their work?
>
>I get a little pay to work on MLT, not nearly enough to go full time,
>but far more than I ever got for Kino.
>
>> SK
>
>Thanks for the compliments, guys.

IMO they are deserved.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If you try to leave the proper driving distance between you and the car in 
front of you, someone will always move in
		-- Murphy's Driving Laws n�1


------------------------------------------------------------------------------
_______________________________________________
Kino-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/kino-dev