Trouble building current CVS

I'm having trouble building kino from the current CVS; I cleared out all
my previous files, refetched the whole thing from scratch with cvs co kino
then ran autogen to build the configurate file

but when I run configure, I get:

config.status: error: cannot find input file: src/Makefile.in

is this a generated file that didn't?

--

-- 
Gary Lawrence Murphy <garym at linux.ca>
"what I need is a job that doesn't interfere with my work"

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

possible endian bugs while playing movies with XVideo method

I just played the first time with kino 0.8 (as of openSuSE 10.2) and
1.1.0 with a Sony DCR-TRV16E DV-VCR on my PowerMac G5.

The default in preferences->display is XVideo instead of GDK. With
XVideo, the picture in capture mode is all light greeen and pink.

Is this an endian bug?

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

Re: possible endian bugs while playing movies with XVideo method

On Thursday 02 August 2007 1:48:58 pm Olaf Hering wrote:
> I just played the first time with kino 0.8 (as of openSuSE 10.2) and
> 1.1.0 with a Sony DCR-TRV16E DV-VCR on my PowerMac G5.
>
> The default in preferences->display is XVideo instead of GDK. With
> XVideo, the picture in capture mode is all light greeen and pink.
>
> Is this an endian bug?

I worked with a guy not too long ago on a number of endian issues, but this 
never came up. I have received reports similar to this over the years, and I 
thought some folks returned to say there was some ATI X server bug causing 
this. I don't have a big endian machine in order to debug this myself. Maybe 
someone else here will speak up.

Also, see these relevant links:

http://osdir.com/ml/video.kino.devel/2005-03/msg00022.html
http://kino.cvs.sourceforge.net/kino/kino/src/frame.cc?r1=1.43&r2=1.44

--

-- 
+-DRD-+

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

Re: possible endian bugs while playing movies with XVideo method

On Thu, Aug 02, Dan Dennedy wrote:

> On Thursday 02 August 2007 1:48:58 pm Olaf Hering wrote:
> > I just played the first time with kino 0.8 (as of openSuSE 10.2) and
> > 1.1.0 with a Sony DCR-TRV16E DV-VCR on my PowerMac G5.
> >
> > The default in preferences->display is XVideo instead of GDK. With
> > XVideo, the picture in capture mode is all light greeen and pink.
> >
> > Is this an endian bug?
> 
> I worked with a guy not too long ago on a number of endian issues, but this 
> never came up. I have received reports similar to this over the years, and I 
> thought some folks returned to say there was some ATI X server bug causing 
> this. I don't have a big endian machine in order to debug this myself. Maybe 
> someone else here will speak up.

The same happens with exporting to DVD.
Maybe I will find some missing or incorrect endian conversions.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

Re: One more report about Kino

On Monday 06 August 2007 5:22:31 am Thomas TS wrote:
> Dan Dennedy wrote:
> > Please confirm that Kino version is 1.0.0 in the About dialog.
>
> Now the PC is not with me... but it is the regular ArchLinux Kino .

Maybe a version installed from a CD iso is different than what is in the 
repository today.

> Will confirm this latter.
>
> >> Capturing from a camcorder that has composite video out.
> >> Passing through a Sony converter to Firewire.
> >>
> >> Did not click at any button on Kino, just run it...
> >>
> >> As soon as the can starts to play the tape, Kino drops out with
> >> 'segmentation fault'.
> >> Despite no action of capture was given to Kino !!
> >
> > It is hard for me to run a Arch system that is close to the same as the
> > package versions in this area because I am a developer. I do have the
> > Arch Kino 1.0.0 package I can test, but I can not reproduce the problem.
> > If you run from a terminal window, it might produce a backtrace that you
> > can send, but Arch packages are stripped often making it useless.
>
> OK. But you could have a regular Arch to test your releases...

and regular debian (stable, tesing, unstable), fedora cores, mandrivas, 
ubuntus, and opensuse's, etc. Sorry, but the community including you is my 

MiniDV camera

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

_______________________________________________
Kino-dev mailing list
Kino-dev <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kino-dev

Re: Kino screencasts

On Tue, Jul 31, 2007 at 11:02:31PM +0200, Stefan M. Fendt wrote:
> I tried istanbul and xvidcap as well. Both did produce *very*
> poor results. Istanbul had no option to use a higher qscale
> which made the recordings useless due to massive block- and
> ringing-artefacts and xvidcap was not capable to record at
> least 5fps without dropouts...

On my system, xvidcap does 10--20+ FPS without any problems
(not fullscreen but IIRC considerable portions of 1600x1200).
The CPU is Athlon64 3700+, RAM size is 1G, the system has
three HDDs including one mainly for [photo/DV] content.

If anyone's interested, I can try to come up with more concise
xvidcap results.

--

-- 
 ---- WBR, Michael Shigorin <mike <at> altlinux.ru>
  ------ Linux.Kiev http://www.linux.kiev.ua/

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

Re: MiniDV camera

On Monday 06 August 2007 12:34:46 am Arpad Kardos wrote:
> Hi!
>
> Sorry to bother's you, i just have a quick question please.
>
> I have a Sony DCR-HC21 MiniDV camera, it connect's with USB cable.(This is
> my webcam as well on xp).
>
> My question is: There's any Linux Driver for it? And if is there, please
> let me know where can i find it.

The linux driver is called linux-uvc or uvcvideo:
http://linux-uvc.berlios.de/

But, it only works with UVC compliant camera--just because your camera has USB 
does not mean it is UVC compliant. Also, there are multiple UVC video formats 
(payloads), one of which is DV. dvgrab in CVS (soon to be release 3.0) now 
supports the combination of linux-uvc and UVC-DV compliant camera.

--

-- 
+-DRD-+

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

Re: Kino screencasts

On Monday 06 August 2007 1:32:50 pm Michael Shigorin wrote:
> On Tue, Jul 31, 2007 at 11:02:31PM +0200, Stefan M. Fendt wrote:
> > I tried istanbul and xvidcap as well. Both did produce *very*
> > poor results. Istanbul had no option to use a higher qscale
> > which made the recordings useless due to massive block- and
> > ringing-artefacts and xvidcap was not capable to record at
> > least 5fps without dropouts...
>
> On my system, xvidcap does 10--20+ FPS without any problems

This framerate is quite adequate.

> (not fullscreen but IIRC considerable portions of 1600x1200).

Do you think you can do an area of 800x600  <at> 15fps where only about half of 
that space includes a video playing?

> The CPU is Athlon64 3700+, RAM size is 1G, the system has
> three HDDs including one mainly for [photo/DV] content.
>
> If anyone's interested, I can try to come up with more concise
> xvidcap results.

What kind of video compression are you using?

--

-- 
+-DRD-+

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

Kino on ArchLinux: it works ?

Dan Dennedy wrote:
> Maybe a version installed from a CD iso is different than what is in the 
> repository today.
>   
ArchLinux install by default repos the 1.0.0 Kino version.

I did build only ffmpeg2theora and oggfrw on this Arch box...
All the rest came from pacman from Arch.

> and regular debian (stable, tesing, unstable), fedora cores, mandrivas, 
> ubuntus, and opensuse's, etc. Sorry, but the community including you is my 
> quality assurance department. This is just a hobby, not a profession. Maybe 
> if you used the mailing list or forum others can confirm or deny your 
> experience.
>   
 !! I am using Arch after your recommendation to do so !!

And it is a very nice distro from all means, so far... Anyway, after two 
weeks with Fedora 7, any distro will seem nice  

> Then, more than likely, there is a problem with the linkage to ffmpeg. Since 
> the package version I tested (Arch 1.0.0) uses static linking with the copy 
> of ffmpeg provided in the kino release tarball, I find this very odd. I guess 
> it could be bad linkage to libdv as well.
>
> I can not resolve this without getting a version confirmation, meaningful 
> backtrace, and build configuration. I am sorry to disappoint you. You are not 
> the first. Oh well.
>   
$ ldd /usr/bin/kino

 >>  libdv.so.4 => /usr/lib/libdv.so.4 (0x00002b3cd6fc0000)
        libiec61883.so.0 => /usr/lib/libiec61883.so.0 (0x00002b3cd70eb000)
        libasound.so.2 => /usr/lib/libasound.so.2 (0x00002b3cd71f8000)
        libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 
(0x00002b3cd73d5000)
        librt.so.1 => /lib/librt.so.1 (0x00002b3cd74da000)
        libglade-2.0.so.0 => /usr/lib/libglade-2.0.so.0 (0x00002b3cd75e3000)
        libxml2.so.2 => /usr/lib/libxml2.so.2 (0x00002b3cd76fd000)
        libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 
(0x00002b3cd793b000)
        libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 
(0x00002b3cd7dba000)
        libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0x00002b3cd7f4e000)
        libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 
(0x00002b3cd806f000)
        libpng12.so.0 => /usr/lib/libpng12.so.0 (0x00002b3cd8187000)
        libpangocairo-1.0.so.0 => /usr/lib/libpangocairo-1.0.so.0 
(0x00002b3cd82aa000)
        libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0x00002b3cd83b4000)
        libcairo.so.2 => /usr/lib/libcairo.so.2 (0x00002b3cd84f8000)
        libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 
(0x00002b3cd8674000)
        libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 
(0x00002b3cd87b6000)
        libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x00002b3cd88b9000)
        libsamplerate.so.0 => /usr/lib/libsamplerate.so.0 
(0x00002b3cd8a57000)
        libXv.so.1 => /usr/lib/libXv.so.1 (0x00002b3cd8b74000)
        libXext.so.6 => /usr/lib/libXext.so.6 (0x00002b3cd8c79000)
        libdl.so.2 => /lib/libdl.so.2 (0x00002b3cd8d8a000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x00002b3cd8e8f000)
        librom1394.so.0 => /usr/lib/librom1394.so.0 (0x00002b3cd8fa9000)
        libavc1394.so.0 => /usr/lib/libavc1394.so.0 (0x00002b3cd90ad000)
        libraw1394.so.8 => /usr/lib/libraw1394.so.8 (0x00002b3cd91b2000)
        libSM.so.6 => /usr/lib/libSM.so.6 (0x00002b3cd92b8000)
        libICE.so.6 => /usr/lib/libICE.so.6 (0x00002b3cd93c0000)
        libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00002b3cd94dc000)
        libm.so.6 => /lib/libm.so.6 (0x00002b3cd96de000)
        libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00002b3cd985c000)
        libc.so.6 => /lib/libc.so.6 (0x00002b3cd996a000)
        libX11.so.6 => /usr/lib/libX11.so.6 (0x00002b3cd9bab000)
        /lib/ld-linux-x86-64.so.2 (0x00002b3cd6ea4000)
        libz.so.1 => /lib/libz.so.1 (0x00002b3cd9db4000)
        libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0x00002b3cd9ec8000)
        libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 
(0x00002b3cd9fcd000)
        libXrender.so.1 => /usr/lib/libXrender.so.1 (0x00002b3cda102000)
        libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0x00002b3cda20b000)
        libXi.so.6 => /usr/lib/libXi.so.6 (0x00002b3cda30d000)
        libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0x00002b3cda417000)
        libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0x00002b3cda51e000)
        libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 
(0x00002b3cda629000)
        libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x00002b3cda758000)
        libXau.so.6 => /usr/lib/libXau.so.6 (0x00002b3cda8e4000)
        libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x00002b3cda9e6000)
        libexpat.so.1 => /usr/lib/libexpat.so.1 (0x00002b3cdaaec000)

One can not see any link with ffmpeg here... or i miss something ?

$ pacman -Q | grep ffm
ffmpeg 20070505-4

$ pacman -Q | grep libdv
libdv 1.0.0-1

Why Kino can not read a regular DV file created with dvgrab seems to be 
odd...

I do not want to be  seem  ungrateful, it is just a matter about it 
works or not : Kino  + ArchLinux.
It is very simple to change distro anyway...

Thanks.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/