>>I think this is a bit unrealistic. It would be a very heavy burden on
the
>>cpu, disk, and the X server because images would have to be
constantly saved,
>>loaded, blt, etc. A quick calculation shows me that this is
~800MB/minute
>>uncompressed. PVRs can do this because they have specialised and
dedicated
>>hardware. We do not.
>>I think we're going to stay away from playing video streams. It
doesn't
>>make sense when there are so many players, including arts. The
closest we
>>should come is perhaps embedding an arts player object when it
becomes more
>>evolved. KWinTV is an application for viewing V4L and Xv streams -
streaming
>>video overlays from hardware devices.
>>Now what would be cool is to support mpeg hardware, another feature
of V4L
>>at least. That could be a playback source and a recording source.
I absolutely agree -> just a thought... ;-) We in South Africa have a
lot of commercials
anyway...
Cheers,
From kwintv@mail.kde.org Sat Mar 23 10:42:06 2002
From: kwintv@mail.kde.org (Stefan Hellwig)
Date: Sat, 23 Mar 2002 11:42:06 +0100
Subject: [Kwintv] KWinTV (CVS) does not work anymore on KDE3 RC4
Message-ID: <200203231142.06732.stefan@stefanhellwig.de>
Hi!
A strange thing happens here. I've recompiled KDE yesterday (it's RC4 now=
)
into a clean/empty directory. Then I took KWinTV's CVS code and did a cle=
an
compile/reinstall. However, the compiled binary does not work anymore, an=
d
when I want to start it from the console (to get debugging info) the only=
=20
thing =09I get is this:
ASSERT: debug output not ended with \n
ASSERT: debug output not ended with \n
ASSERT: debug output not ended with \n
ASSERT: debug output not ended with \n
ASSERT: debug output not ended with \n
When I run the binary that I made (using the same KWinTV CVS code) for KD=
E3=20
RC 3 it runs fine - even in RC4. Just the newly compiled binary that I=20
made using RC4 includes and libraries (and qt-copy) does not work. When I=
=20
try to give it some parameters (or just a "-?") it gives me a segmentatio=
n=20
fault. Can anyone reproduce this? Since the code did not change recently=20
my guess is that it has to do something with a change made to Qt or KDE=20
recently...
BTW, I really like all the ideas regarding the re-write of KWinTV, I just=
=20
didn't have the time to comment on it. Plus, it does not work for me on=20
KDE3 RC4 as well (using latest CVS).
Regards, Stefan.
--=20
The Jenna von Oy WebSite - http://www.jennavonoy.com/
Run by fans, for fans, in cooperation with Jenna von Oy!
From kwintv@mail.kde.org Mon Mar 25 02:43:07 2002
From: kwintv@mail.kde.org (=?iso-8859-1?B?U2ViYXN0aeFuIEdvbnrhbGV6?=)
Date: Sun, 24 Mar 2002 23:43:07 -0300
Subject: [Kwintv] PAL-NC
Message-ID: <002001c1d3a6$cc8fe9e0$ff0ffea9@SEBA>
This is a multi-part message in MIME format.
------=_NextPart_000_001C_01C1D38D.A6149220
Content-Type: multipart/alternative;
boundary="----=_NextPart_001_001D_01C1D38D.A6149220"
------=_NextPart_001_001D_01C1D38D.A6149220
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hello !
I want to use the kwintv app with the PAL-NC norm.
At the page http://www.mathematik.uni-kl.de/~wenk/kwintv/ver.html, one =
can read the following change log item:
0.7.4 --- 1. September 1999
* fixed code in dsp.cpp
* mute when gonig down
* added --enable-bnorms to configure script=20
to support extra bttv norms like PAL-NC -M -N NTSC-JP
(choosing PAL-N or NTSC-JP may crash your computer, so be careful!)
* added --disable-mixer to configure script=20
do disable mixer support by kwintv
* removed Import|xawtv from menu
* fixed bug in cut|copy|paste program
* removed vtx tree (will be back soon)
* fixed "wrong volume at startup" bug
* OSD only in full screen mode=20
but, I haven't the option --enable-bnorms in my kwintv which version is =
0.8.9
How can I view the PAL_NC norm ?
I attach 2 files:
* kwintv_version.txt (kwintv -v >kwintv_version.txt)
* kwintv_options.txt (kwintv --help-all > kwintv_options.txt)
Thank you in advance,
Sebasti=E1n Gonz=E1lez
------=_NextPart_001_001D_01C1D38D.A6149220
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hello !
I want to use the kwintv app with the =
PAL-NC=20
norm.
At the page http://www=
.mathematik.uni-kl.de/~wenk/kwintv/ver.html,=20
one can read the following change log item:
0.7.4 --- 1. =
September 1999
* fixed code in dsp.cpp
* mute when gonig down
* added --enable-bnorms to configure script=20
to support extra bttv norms like PAL-NC -M -N NTSC-JP
(choosing PAL-N or NTSC-JP may crash your computer, so be careful!)
* added --disable-mixer to configure script=20
do disable mixer support by kwintv
* removed Import|xawtv from menu
* fixed bug in cut|copy|paste program
* removed vtx tree (will be back soon)
* fixed "wrong volume at startup" bug
* OSD only in full screen mode
but, I haven't the option =
--enable-bnorms in my=20
kwintv which version is 0.8.9
How can I view the PAL_NC norm =
?
I attach 2 files:
* kwintv_version.txt (kwintv -v=20
>kwintv_version.txt)
* kwintv_options.txt (kwintv --help-all =
>=20
kwintv_options.txt)
Thank you in advance,
Sebasti=E1n =
Gonz=E1lez
------=_NextPart_001_001D_01C1D38D.A6149220--
------=_NextPart_000_001C_01C1D38D.A6149220
Content-Type: text/plain;
name="kwintv_options.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="kwintv_options.txt"
Usage: kwintv [Qt-options] [KDE-options] [options] =0A=
=0A=
KWinTV is a KDE application for TV cards=0A=
supported by a Video4Linux compatible driver.=0A=
=0A=
Generic options:=0A=
--help Show help about options=0A=
--help-qt Show Qt specific options=0A=
--help-kde Show KDE specific options=0A=
--help-all Show all options=0A=
--author Show author information=0A=
-v, --version Show version information=0A=
--license Show license information=0A=
-- End of options=0A=
=0A=
Qt options:=0A=
--display Use the X-server display 'displayname'.=0A=
--session Restore the application for the given =
'sessionId'.=0A=
--cmap Causes the application to install a private =
color=0A=
map on an 8-bit display.=0A=
--ncols Limits the number of colors allocated in the =
color=0A=
cube on an 8-bit display, if the application =
is=0A=
using the QApplication::ManyColor color=0A=
specification.=0A=
--nograb tells Qt to never grab the mouse or the =
keyboard.=0A=
--dograb running under a debugger can cause an =
implicit=0A=
-nograb, use -dograb to override.=0A=
--sync switches to synchronous mode for debugging.=0A=
--fn, --font defines the application font.=0A=
--bg, --background sets the default background color and an=0A=
application palette (light and dark shades =
are=0A=
calculated).=0A=
--fg, --foreground sets the default foreground color.=0A=
--btn, --button sets the default button color.=0A=
--name sets the application name.=0A=
--title sets the application title (caption).=0A=
--visual TrueColor forces the application to use a TrueColor =
visual on=0A=
an 8-bit display.=0A=
--inputstyle <inputstyle> sets XIM (X Input Method) input style. =
Possible=0A=
values are onthespot, overthespot, =
offthespot and=0A=
root.=0A=
--im <XIM server> set XIM server.=0A=
--noxim disable XIM.=0A=
=0A=
KDE options:=0A=
--caption <caption> Use 'caption' as name in the titlebar.=0A=
--icon <icon> Use 'icon' as the application icon.=0A=
--miniicon <icon> Use 'icon' as the icon in the titlebar.=0A=
--dcopserver <server> Use the DCOP Server specified by 'server'.=0A=
--nocrashhandler Disable crash handler, to get core dumps.=0A=
--waitforwm Waits for a WM_NET compatible windowmanager.=0A=
--style <style> sets the application GUI style.=0A=
--geometry <geometry> sets the client geometry of the main widget.=0A=
=0A=
Options:=0A=
--bpp <pits per pixel> color depth of the display is <pits per =
pixel>=0A=
-b, --palette <id> force used palette for display to <id>=0A=
-p, --shift <int> shift frame buffer (TV image) by <int> bytes=0A=
-s, --refresh <mode> set refresh mode to <mode>=0A=
-r, --device <dev> use device <dev> as video4linux device =
[/dev/video]=0A=
-d, --noxfree disable XFree extentions (VidMode, DGA, DV)=0A=
------=_NextPart_000_001C_01C1D38D.A6149220
Content-Type: text/plain;
name="kwintv_version.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="kwintv_version.txt"
Qt: 2.3.1=0A=
KDE: 2.2.1=0A=
KWinTV: 0.8.9=0A=
------=_NextPart_000_001C_01C1D38D.A6149220--
From kwintv@mail.kde.org Mon Mar 25 10:47:42 2002
From: kwintv@mail.kde.org (kwintv@mail.kde.org)
Date: Mon, 25 Mar 2002 11:47:42 +0100 (CET)
Subject: [Kwintv] PAL-NC
In-Reply-To: <002001c1d3a6$cc8fe9e0$ff0ffea9@SEBA>
Message-ID: <Pine.LNX.4.44.0203251146030.18274-100000@megarouter.rave.org>
On Sun, 24 Mar 2002, [iso-8859-1] Sebasti=E1n Gonz=E1lez wrote:
>
> Hello !
>
> I want to use the kwintv app with the PAL-NC norm.
>
> At the page http://www.mathematik.uni-kl.de/~wenk/kwintv/ver.html, one ca=
n read the following change log item:
> 0.7.4 --- 1. September 1999
> * fixed code in dsp.cpp
> * mute when gonig down
> * added --enable-bnorms to configure script
^^^^^^^^^^^^^^^^
I think you read over this :)
it is not a CLI option of kwintv but an option of the configure script.
so do:
=09./configure --enable-bnorms && make && make install
instead of
=09./configure && make && make install
> =09to support extra bttv norms like PAL-NC -M -N NTSC-JP
> (choosing PAL-N or NTSC-JP may crash your computer, so be careful!)
> * added --disable-mixer to configure script
> =09do disable mixer support by kwintv
> * removed Import|xawtv from menu
> * fixed bug in cut|copy|paste program
> * removed vtx tree (will be back soon)
> * fixed "wrong volume at startup" bug
> * OSD only in full screen mode
> but, I haven't the option --enable-bnorms in my kwintv which version is 0=
=2E8.9
>
> How can I view the PAL_NC norm ?
>
> I attach 2 files:
>
> * kwintv_version.txt (kwintv -v >kwintv_version.txt)
> * kwintv_options.txt (kwintv --help-all > kwintv_options.txt)
>
> Thank you in advance,
>
> Sebasti=E1n Gonz=E1lez
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~=
~~
Koen Bailleul Yet Another BO=
FH
4th year Computer Science (AT LAST!!!) Personal systems happily running Lin=
ux
E-mail: kbailleu@vub.ac.be Registered Linux User #531=
29
Homepage: www.microsoft.com :) Co-founder of Brussels Linux Users Gro=
up
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~=
~~
Message written on 100% recycled bytes, cleared without chlorine!!
=09=09 Q to Q: "DON'T PROVOKE THE BORG"
From kwintv@mail.kde.org Mon Mar 25 18:43:29 2002
From: kwintv@mail.kde.org (kwintv@mail.kde.org)
Date: 25 Mar 2002 18:43:29 -0000
Subject: [Kwintv] Bug#39775: Window titlebar is away on resize from fullscreen in normal windowmode
Message-ID: <20020325184329.15762.qmail@mail.kde.org>
Package: kwintv
Version: 0.8.9 (using KDE 2.2.1 )
Severity: normal
Installed from: SuSE
Compiler: gcc version 2.95.3 20010315 (SuSE)
OS: Linux (i686) release 2.4.10-4GB
OS/Compiler notes:
Window titlebar is away on resize from fullscreen in normal windowmode. I have set the full screen mode and later after a movie on a tv programm in normal window mode again, and then was the window titlebar away or out the screen (x:(0) y:(-20)). I cann't move the window without the titlebar..
(Submitted via bugs.kde.org)
(Called from KBugReport dialog)
From kwintv@mail.kde.org Tue Mar 26 01:27:50 2002
From: kwintv@mail.kde.org (George Staikos)
Date: Mon, 25 Mar 2002 20:27:50 -0500
Subject: [Kwintv] KWinTV (CVS) does not work anymore on KDE3 RC4
In-Reply-To: <200203231142.06732.stefan@stefanhellwig.de>
References: <200203231142.06732.stefan@stefanhellwig.de>
Message-ID: <200203252027.50283.staikos@kde.org>
The only thing that changed is the default video device. Try giving it
explicitly and see if it helps.
On Saturday 23 March 2002 05:42, Stefan Hellwig wrote:
> A strange thing happens here. I've recompiled KDE yesterday (it's RC4 now)
> into a clean/empty directory. Then I took KWinTV's CVS code and did a clean
> compile/reinstall. However, the compiled binary does not work anymore, and
> when I want to start it from the console (to get debugging info) the only
> thing I get is this:
>
> ASSERT: debug output not ended with \n
> ASSERT: debug output not ended with \n
> ASSERT: debug output not ended with \n
> ASSERT: debug output not ended with \n
> ASSERT: debug output not ended with \n
>
> When I run the binary that I made (using the same KWinTV CVS code) for KDE3
> RC 3 it runs fine - even in RC4. Just the newly compiled binary that I
> made using RC4 includes and libraries (and qt-copy) does not work. When I
> try to give it some parameters (or just a "-?") it gives me a segmentation
> fault. Can anyone reproduce this? Since the code did not change recently
> my guess is that it has to do something with a change made to Qt or KDE
> recently...
>
> BTW, I really like all the ideas regarding the re-write of KWinTV, I just
> didn't have the time to comment on it. Plus, it does not work for me on
> KDE3 RC4 as well (using latest CVS).
>
> Regards, Stefan.
--
George Staikos
From kwintv@mail.kde.org Tue Mar 26 03:50:16 2002
From: kwintv@mail.kde.org (=?iso-8859-1?B?U2ViYXN0aeFuIEdvbnrhbGV6?=)
Date: Tue, 26 Mar 2002 00:50:16 -0300
Subject: [Kwintv] trying to compile
Message-ID: <000901c1d479$57f52720$ff0ffea9@SEBA>
Hello!
I'm trying to compile the kwintv
I do ./configure --enable-bnorms
Then I do make, and when it tries to do
g++ -DHAVE_CONFIG_H -I. -I. -I.. -I/opt/kde/include -I/usr/lib/qt2//include
-I/usr/X11R6/include -O2 -c wintv.cpp
it displays an error message because it does not find the file kdickwidget.h
This file is located at /opt/kde2/include, but as you can see, it does not
pass the parameter -I/opt/kde2/include to the compiler
What should I do to compile it properly ?
My versions are:
Qt: 2.3.1
KDE: 2.2.1
KWinTV: 0.8.9
Thank you in advance,
Sebastián González
From kwintv@mail.kde.org Tue Mar 26 16:13:15 2002
From: kwintv@mail.kde.org (Stefan Hellwig)
Date: Tue, 26 Mar 2002 17:13:15 +0100
Subject: [Kwintv] KWinTV (CVS) does not work anymore on KDE3 RC4
In-Reply-To: <200203252027.50283.staikos@kde.org>
References: <200203231142.06732.stefan@stefanhellwig.de> <200203252027.50283.staikos@kde.org>
Message-ID: <200203261713.15173.stefan@stefanhellwig.de>
Hi!
On Tuesday 26 March 2002 02:27, George Staikos wrote:
> The only thing that changed is the default video device. Try giving it
> explicitly and see if it helps.
No, sadly it did not help. Well, at least KwinTV does not segfault when I=
=20
give it any command line options - but it still always reports the same=20
thing 5 times in a row:
ASSERT: debug output not ended with \n
When I start it without any command line options it gives me a segmentati=
on=20
fault. I somehow think it's not exactly KWinTV's "fault" but rather=20
related to a recent change to KDE itself. Probably a change to=20
KUniqueApplication or KCmdLineArgs?!
Regards, Stefan.
--=20
The Jenna von Oy WebSite - http://www.jennavonoy.com/
Run by fans, for fans, in cooperation with Jenna von Oy!
From kwintv@mail.kde.org Tue Mar 26 16:44:19 2002
From: kwintv@mail.kde.org (Stefan Hellwig)
Date: Tue, 26 Mar 2002 17:44:19 +0100
Subject: [Kwintv] KWinTV (CVS) does not work anymore on KDE3 RC4 (addition)
In-Reply-To: <200203261713.15173.stefan@stefanhellwig.de>
References: <200203231142.06732.stefan@stefanhellwig.de> <200203252027.50283.staikos@kde.org> <200203261713.15173.stefan@stefanhellwig.de>
Message-ID: <200203261744.19169.stefan@stefanhellwig.de>
Hi!
On Tuesday 26 March 2002 17:13, Stefan Hellwig wrote:
> [...] KUniqueApplication or KCmdLineArgs?!
Well, I've tried something by changing KWinTV back into a KApplication to=
=20
see what happens. After the change it didn't give me that "stupid" assert=
=20
anymore. Instead, this error came up:
KCrash: crashing.... crashRecursionCounter =3D 2
KCrash: Application Name =3D kwintv path =3D <unknown> pid =3D 9223
Unable to start dr. konqi
Still not very helpful...Then I put the KUniqueApplication back in and go=
t
the assert again so I searched for the assert and found it in kdecore's
kdebug.cpp:
kdbgstream::~kdbgstream() {
if (!output.isEmpty()) {
fprintf(stderr, "ASSERT: debug output not ended with \\n\n");
*this << "\n";
}
}
But since it still does not start, even when I change it into a normal=20
KApplication I guess the error is somewhere else. Well, as long as I can=20
use the KWinTV binary that I've compiled with KDE3RC2 I'm happy but
it is very strange nevertheless...
Regards, Stefan.
--=20
The Jenna von Oy WebSite - http://www.jennavonoy.com/
Run by fans, for fans, in cooperation with Jenna von Oy!
From kwintv@mail.kde.org Tue Mar 26 19:17:28 2002
From: kwintv@mail.kde.org (George Staikos)
Date: Tue, 26 Mar 2002 14:17:28 -0500
Subject: [Kwintv] KWinTV (CVS) does not work anymore on KDE3 RC4 (addition)
In-Reply-To: <200203261744.19169.stefan@stefanhellwig.de>
References: <200203231142.06732.stefan@stefanhellwig.de> <200203261713.15173.stefan@stefanhellwig.de> <200203261744.19169.stefan@stefanhellwig.de>
Message-ID: <200203261417.28516.staikos@kde.org>
Are you sure your build environment and shared lib paths are clean? What does
the backtrace say?
On Tuesday 26 March 2002 11:44, Stefan Hellwig wrote:
> Hi!
>
> On Tuesday 26 March 2002 17:13, Stefan Hellwig wrote:
> > [...] KUniqueApplication or KCmdLineArgs?!
>
> Well, I've tried something by changing KWinTV back into a KApplication to
> see what happens. After the change it didn't give me that "stupid" assert
> anymore. Instead, this error came up:
>
> KCrash: crashing.... crashRecursionCounter = 2
> KCrash: Application Name = kwintv path = <unknown> pid = 9223
> Unable to start dr. konqi
>
> Still not very helpful...Then I put the KUniqueApplication back in and got
> the assert again so I searched for the assert and found it in kdecore's
> kdebug.cpp:
>
> kdbgstream::~kdbgstream() {
> if (!output.isEmpty()) {
> fprintf(stderr, "ASSERT: debug output not ended with \\n\n");
> *this << "\n";
> }
> }
>
> But since it still does not start, even when I change it into a normal
> KApplication I guess the error is somewhere else. Well, as long as I can
> use the KWinTV binary that I've compiled with KDE3RC2 I'm happy but
> it is very strange nevertheless...
>
> Regards, Stefan.
--
George Staikos
From kwintv@mail.kde.org Tue Mar 26 20:30:30 2002
From: kwintv@mail.kde.org (Stefan Hellwig)
Date: Tue, 26 Mar 2002 21:30:30 +0100
Subject: [Kwintv] KWinTV (CVS) does not work anymore on KDE3 RC4 (addition)
In-Reply-To: <200203261417.28516.staikos@kde.org>
References: <200203231142.06732.stefan@stefanhellwig.de> <200203261744.19169.stefan@stefanhellwig.de> <200203261417.28516.staikos@kde.org>
Message-ID: <200203262130.30447.stefan@stefanhellwig.de>
--------------Boundary-00=_UYKLU2GQKTOP1XNUPPCH
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi!
On Tuesday 26 March 2002 20:17, George Staikos wrote:
> Are you sure your build environment and shared lib paths are clean?=20
I'm pretty sure. Last time I recompiled KDE3 I did it from scatch into an=
=20
empty directory. I also cleaned my $KDEHOME for KDE3. And since KDE3 (I'm=
=20
still using RC4 at the moment) works well I don't know what else could be=
=20
wrong. However, I plan to update to 3.0 (release) soon now and then I'll=20
try to recompile KWinTV once more.
> What does the backtrace say?
Sadly, there is no real backtrace available, at least I can't produce one=
=2E=20
KWinTV crashes way too early. Not even an strace gives me something reall=
y=20
useful (see attachment for the last few lines of the strace output)...
Never mind, I think I'll try again as soon as I have my system running th=
e=20
release version of KDE3 and then I'll see what happens. It's strange, to=20
say the least.
Regards, Stefan.
--=20
The Jenna von Oy WebSite - http://www.jennavonoy.com/
Run by fans, for fans, in cooperation with Jenna von Oy!
--------------Boundary-00=_UYKLU2GQKTOP1XNUPPCH
Content-Type: text/plain;
charset="iso-8859-1";
name="kwintv-strace.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="kwintv-strace.txt"
munmap(0x40017000, 115314) = 0
getpid() = 10893
rt_sigaction(SIGRT_0, {0x40d35740, [], 0x4000000}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {0x40d34d10, [], 0x4000000}, NULL, 8) = 0
rt_sigaction(SIGRT_2, {0x40d357d0, [], 0x4000000}, NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [RT_0], NULL, 8) = 0
_sysctl({{CTL_KERN, KERN_VERSION}, 2, 0xbffff3b4, 30, (nil), 0}) = 0
getpid() = 10893
brk(0) = 0x80dea68
brk(0x80dea98) = 0x80dea98
brk(0x80df000) = 0x80df000
getpid() = 10893
getpid() = 10893
modify_ldt(0x11, 0xbffff6e8, 0x10) = 0
old_mmap(NULL, 262144, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x41c01000
brk(0x80e1000) = 0x80e1000
getcwd("/install/kde3/TEST/kdenonbeta/kwintv/kwintv", 4095) = 44
pipe([3, 4]) = 0
fork() = 10894
ASSERT: debug output not ended with \n
ASSERT: debug output not ended with \n
ASSERT: debug output not ended with \n
ASSERT: debug output not ended with \n
close(4) = 0
read(3, 0xbffff61b, 1) = ? ERESTARTSYS (To be restarted)
--- SIGCHLD (Child exited) ---
read(3, "", 1) = 0
write(2, "ASSERT: debug output not ended w"..., 39ASSERT: debug output not ended with \n
) = 39
getpid() = 10893
getpid() = 10893
getpid() = 10893
_exit(255) = ?
--------------Boundary-00=_UYKLU2GQKTOP1XNUPPCH--
From kwintv@mail.kde.org Wed Mar 27 22:50:41 2002
From: kwintv@mail.kde.org (Gregor Riepl)
Date: Wed, 27 Mar 2002 23:50:41 +0100
Subject: [Kwintv] trying to compile
In-Reply-To: <000901c1d479$57f52720$ff0ffea9@SEBA>
References: <000901c1d479$57f52720$ff0ffea9@SEBA>
Message-ID: <3C98690D000B1C59@freesurfmta05.sunrise.ch> (added by postmaster@sunrise.ch)
On Tuesday, 26. March 2002 04:50, Sebastián González wrote:
> Hello!
>
> I'm trying to compile the kwintv
>
> I do ./configure --enable-bnorms
>
> Then I do make, and when it tries to do
>
> g++ -DHAVE_CONFIG_H -I. -I. -I.. -I/opt/kde/include -I/usr/lib/qt2//include
> -I/usr/X11R6/include -O2 -c wintv.cpp
>
> it displays an error message because it does not find the file
> kdickwidget.h
I assume that should be kdockwidget.h :)
>
> This file is located at /opt/kde2/include, but as you can see, it does not
> pass the parameter -I/opt/kde2/include to the compiler
It could be possible that you have an old kde version (<2.0.0) lying around
in /opt/kde/include which the configure script detects incorrectly as kde of
choice.
>
> What should I do to compile it properly ?
>
> My versions are:
> Qt: 2.3.1
> KDE: 2.2.1
> KWinTV: 0.8.9
>
> Thank you in advance,
>
> Sebastián González
>
> _______________________________________________
> kwintv mailing list
> kwintv@mail.kde.org
> http://mail.kde.org/mailman/listinfo/kwintv
--
In a world without walls and fences,
who needs Windows and Gates?
- Sun Microsystems
From kwintv@mail.kde.org Wed Mar 27 22:56:49 2002
From: kwintv@mail.kde.org (Gregor Riepl)
Date: Wed, 27 Mar 2002 23:56:49 +0100
Subject: [Kwintv] trying to compile
In-Reply-To: <000901c1d479$57f52720$ff0ffea9@SEBA>
References: <000901c1d479$57f52720$ff0ffea9@SEBA>
Message-ID: <3C985EE8000ADE61@freesurfmta01.sunrise.ch> (added by postmaster@sunrise.ch)
Woops sorry pressed the wrong key...
Here's the rest of the message:
>
> What should I do to compile it properly ?
The easiest way would be to move /opt/kde to /opt/kde1 or something and
/opt/kde2 to /opt/kde, but I assume you don't want to do this.
The most correct way would be adding better KDE version checks to
acinclude.m4 but this is stuff for the KDE guys.
So you should just try to add
--with-extra-includes=/opt/kde2/include --with-extra-libs=/opt/kde2/lib
to ./configure to get kwintv to compile. There's just the danger gcc might
mix up include files and/or libraries, so this could fail.
Just try it.
Greg
From kwintv@mail.kde.org Wed Mar 27 23:02:29 2002
From: kwintv@mail.kde.org (Gregor Riepl)
Date: Thu, 28 Mar 2002 00:02:29 +0100
Subject: [Kwintv] trying to compile
In-Reply-To: <000901c1d479$57f52720$ff0ffea9@SEBA>
References: <000901c1d479$57f52720$ff0ffea9@SEBA>
Message-ID: <3C98690D000B1F5F@freesurfmta05.sunrise.ch> (added by postmaster@sunrise.ch)
Once again :)
I just forgot one solution (correct and easy I suppose):
set KDEDIR to /opt/kde2 before running configure (don't forget to delete
config.cache!)
export KDEDIR=/opt/kde2
rm config.cache
./configure --whatever-option-you-may-need
Hope this helps!
Greg
From kwintv@mail.kde.org Wed Mar 27 01:33:26 2002
From: kwintv@mail.kde.org (Dennis Gies)
Date: Tue, 26 Mar 2002 20:33:26 -0500
Subject: [Kwintv] Picture Corruption
In-Reply-To: <3C98690D000B1F5F@freesurfmta05.sunrise.ch>
References: <000901c1d479$57f52720$ff0ffea9@SEBA> <3C98690D000B1F5F@freesurfmta05.sunrise.ch> (added by postmaster@sunrise.ch)
Message-ID: <200203270251.VAA15085@localhost.localdomain>
Hi all,
Lately I've been having trouble with TV picture corruption using KWinTV.
I've been having minor troubles with the cable and my television set also, so
I thought perhaps the signal level is a little bit low, but I don't know for
sure.
The corruption is intermittent and looks like horizontal streaking, as though
each line runs over a little bit to the next line. The sound comes through
OK. I have a screenshot if that would help, I figured I probably shouldn't
send it to the whole list.
Thanks!
Dennis
From kwintv@mail.kde.org Wed Mar 27 02:59:27 2002
From: kwintv@mail.kde.org (=?iso-8859-1?B?U2ViYXN0aeFuIEdvbnrhbGV6?=)
Date: Tue, 26 Mar 2002 23:59:27 -0300
Subject: [Kwintv] trying to compile
References: <000901c1d479$57f52720$ff0ffea9@SEBA> <3C98690D000B1F5F@freesurfmta05.sunrise.ch> (added by postmaster@sunrise.ch)
Message-ID: <000901c1d53b$9fc8ac80$ff0ffea9@SEBA>
Thank you!
This one worked. I can now watch color TV!
But now the program hangs up constantly.
Before I compiled this version, I used one version that came with the Suse
7.3
That one worked fine (it did not hang up), but the PAL-NC norm was not
supported
Any idea ?
----- Original Message -----
From: Gregor Riepl <seto-kun@freesurf.ch>
To: <kwintv@mail.kde.org>
Sent: Wednesday, March 27, 2002 8:02 PM
Subject: Re: [Kwintv] trying to compile
> Once again :)
>
> I just forgot one solution (correct and easy I suppose):
>
> set KDEDIR to /opt/kde2 before running configure (don't forget to delete
> config.cache!)
>
> export KDEDIR=/opt/kde2
> rm config.cache
> ./configure --whatever-option-you-may-need
>
> Hope this helps!
>
> Greg
> _______________________________________________
> kwintv mailing list
> kwintv@mail.kde.org
> http://mail.kde.org/mailman/listinfo/kwintv
From kwintv@mail.kde.org Thu Mar 28 16:43:58 2002
From: kwintv@mail.kde.org (Stefan Hellwig)
Date: Thu, 28 Mar 2002 17:43:58 +0100
Subject: [Kwintv] Is there something strange going on in CVS?!
Message-ID: <200203281743.58326.stefan@stefanhellwig.de>
Hi!
I've again tried to compile and run KWinTV (CVS) after compiling the late=
st=20
KDE code (CVS as of yesterday, using the KDE_3_0_BRANCH). And this is=20
where I noticed some inconsistencies:
I was always working with KWinTV in KDE_2_2_BRANCH, this is where I
committed all my changes, e.g. new icons, the new KConfig channel format,=
=20
etc. I checked out KWinTV with -r KDE_2_2_BRANCH and compiled it for KDE3=
=2E=20
And this binary still does not work and gives me these "crazy" asserts=20
(see my other e-mail on this) and exits/crashes.
Then I checked out KWinTV with -r HEAD and compiled it in the same=20
environment. And this works! However, that version does not have the new=20
channel file format (KConfig-based) that I introduced, nor any of the new=
=20
icons, etc. (Of course not, we've all been working on the KDE_2_2_BRANCH)=
=2E
So, my guess is that there's something strange going on in the CVS=20
repository or there's something wrong with the port of KwinTV to KDE3. Is=
=20
this possible? Can anyone try and verify this?
I've compiled KDE3 (-r KDE_3_0_BRANCH) into an empty directory yesterday,
I also deleted my $KDEHOME ($HOME/.kde3), and KDE3 (it actually reports t=
o=20
be 3.0.1 already :-) works very well - except for KWinTV (taken out of th=
e=20
KDE_2_2_BRANCH since there is no KWinTV in the KDE_3_0_BRANCH).
BTW, I also used the KDE_2_2_BRANCH "admin" directory for compiling KWinT=
V.
Regards, Stefan.
--=20
The Jenna von Oy WebSite - http://www.jennavonoy.com/
Run by fans, for fans, in cooperation with Jenna von Oy!
From kwintv@mail.kde.org Thu Mar 28 17:56:03 2002
From: kwintv@mail.kde.org (George Staikos)
Date: Thu, 28 Mar 2002 12:56:03 -0500
Subject: [Kwintv] Is there something strange going on in CVS?!
In-Reply-To: <200203281743.58326.stefan@stefanhellwig.de>
References: <200203281743.58326.stefan@stefanhellwig.de>
Message-ID: <200203281256.03902.staikos@kde.org>
Yes, the reason is that the 2_2_BRANCH is for KDE2. :) Even though the code
in the kwintv directory will work in KDE3, the autoconf, libtool etc were all
from KDE2. Please use HEAD for KDE3.
On Thursday 28 March 2002 11:43, Stefan Hellwig wrote:
> I've again tried to compile and run KWinTV (CVS) after compiling the latest
> KDE code (CVS as of yesterday, using the KDE_3_0_BRANCH). And this is
> where I noticed some inconsistencies:
>
> I was always working with KWinTV in KDE_2_2_BRANCH, this is where I
> committed all my changes, e.g. new icons, the new KConfig channel format,
> etc. I checked out KWinTV with -r KDE_2_2_BRANCH and compiled it for KDE3.
> And this binary still does not work and gives me these "crazy" asserts
> (see my other e-mail on this) and exits/crashes.
>
> Then I checked out KWinTV with -r HEAD and compiled it in the same
> environment. And this works! However, that version does not have the new
> channel file format (KConfig-based) that I introduced, nor any of the new
> icons, etc. (Of course not, we've all been working on the KDE_2_2_BRANCH).
>
> So, my guess is that there's something strange going on in the CVS
> repository or there's something wrong with the port of KwinTV to KDE3. Is
> this possible? Can anyone try and verify this?
>
> I've compiled KDE3 (-r KDE_3_0_BRANCH) into an empty directory yesterday,
> I also deleted my $KDEHOME ($HOME/.kde3), and KDE3 (it actually reports to
> be 3.0.1 already :-) works very well - except for KWinTV (taken out of the
> KDE_2_2_BRANCH since there is no KWinTV in the KDE_3_0_BRANCH).
> BTW, I also used the KDE_2_2_BRANCH "admin" directory for compiling KWinTV.
>
> Regards, Stefan.
--
George Staikos
From kwintv@mail.kde.org Thu Mar 28 18:14:12 2002
From: kwintv@mail.kde.org (Stefan Hellwig)
Date: Thu, 28 Mar 2002 19:14:12 +0100
Subject: [Kwintv] Is there something strange going on in CVS?!
In-Reply-To: <200203281256.03902.staikos@kde.org>
References: <200203281743.58326.stefan@stefanhellwig.de> <200203281256.03902.staikos@kde.org>
Message-ID: <200203281914.12323.stefan@stefanhellwig.de>
Hi!
On Thursday 28 March 2002 18:56, George Staikos wrote:
> Yes, the reason is that the 2_2_BRANCH is for KDE2. :) Even though the
> code in the kwintv directory will work in KDE3, the autoconf, libtool
> etc were all from KDE2. Please use HEAD for KDE3.
Well, somehow I feared something like that. The problem with using HEAD i=
s=20
that some changes, especially the new icons, introduced to KWinTV in=20
KDE_2_2_BRANCH are not available in HEAD :-(. Luckily, somehow at least=20
the new KConfig-based channel format seems to be there, in contrast to=20
what I said in my previous e-mail...
Besides, after reading the discussion about the port to KDE3 I thought th=
at=20
the port has been made to KDE_2_2_BRANCH instead.
So, basically, I believe we should move all the changes made to=20
KDE_2_2_BRANCH to HEAD. I'll have to investigate some more what changes=20
are missing. I'm sure that at least the icons are missing in HEAD, if not=
=20
more.
Regards, Stefan.
--=20
The Jenna von Oy WebSite - http://www.jennavonoy.com/
Run by fans, for fans, in cooperation with Jenna von Oy!
From kwintv@mail.kde.org Thu Mar 28 20:44:50 2002
From: kwintv@mail.kde.org (George Staikos)
Date: Thu, 28 Mar 2002 15:44:50 -0500
Subject: [Kwintv] Is there something strange going on in CVS?!
In-Reply-To: <200203281914.12323.stefan@stefanhellwig.de>
References: <200203281743.58326.stefan@stefanhellwig.de> <200203281256.03902.staikos@kde.org> <200203281914.12323.stefan@stefanhellwig.de>
Message-ID: <200203281544.50730.staikos@kde.org>
On Thursday 28 March 2002 13:14, Stefan Hellwig wrote:
> On Thursday 28 March 2002 18:56, George Staikos wrote:
> > Yes, the reason is that the 2_2_BRANCH is for KDE2. :) Even though the
> > code in the kwintv directory will work in KDE3, the autoconf, libtool
> > etc were all from KDE2. Please use HEAD for KDE3.
>
> Well, somehow I feared something like that. The problem with using HEAD is
> that some changes, especially the new icons, introduced to KWinTV in
> KDE_2_2_BRANCH are not available in HEAD :-(. Luckily, somehow at least
> the new KConfig-based channel format seems to be there, in contrast to
> what I said in my previous e-mail...
>
> Besides, after reading the discussion about the port to KDE3 I thought that
> the port has been made to KDE_2_2_BRANCH instead.
>
> So, basically, I believe we should move all the changes made to
> KDE_2_2_BRANCH to HEAD. I'll have to investigate some more what changes
> are missing. I'm sure that at least the icons are missing in HEAD, if not
> more.
Yes you should move these over to head too. This is why I don't want to
make any more 2.2 based kwintv releases. I don't intend to make any more 2.2
releases unless there are significant gains from it. I would like to make
one more 3.0-based release though.
The new code is going so quickly that I think we can manage to match the
0.8.x releases' basic functionality by May or June.
--
George Staikos
From kwintv@mail.kde.org Thu Mar 28 21:11:07 2002
From: kwintv@mail.kde.org (Michael Reiher)
Date: Thu, 28 Mar 2002 22:11:07 +0100
Subject: [Kwintv] Is there something strange going on in CVS?!
References: <200203281743.58326.stefan@stefanhellwig.de> <200203281256.03902.staikos@kde.org> <200203281914.12323.stefan@stefanhellwig.de>
Message-ID: <3CA386EB.3E2FEF01@gmx.de>
Stefan Hellwig wrote:
>
> Hi!
>
> On Thursday 28 March 2002 18:56, George Staikos wrote:
> > Yes, the reason is that the 2_2_BRANCH is for KDE2. :) Even though the
> > code in the kwintv directory will work in KDE3, the autoconf, libtool
> > etc were all from KDE2. Please use HEAD for KDE3.
Naa. You can as well use the 2_2 branch, I do it all the time. Don't know if
there is a problem with the admin dir, though. I simply symlinked the one from
my HEAD kde-common in there and that works fine.
>
> Well, somehow I feared something like that. The problem with using HEAD is
> that some changes, especially the new icons, introduced to KWinTV in
> KDE_2_2_BRANCH are not available in HEAD :-(. Luckily, somehow at least
> the new KConfig-based channel format seems to be there, in contrast to
> what I said in my previous e-mail...
>
> Besides, after reading the discussion about the port to KDE3 I thought that
> the port has been made to KDE_2_2_BRANCH instead.
Yes, that's right. But somebody later merged the KDE_2_2_BRANCH into HEAD. So
...
>
> So, basically, I believe we should move all the changes made to
> KDE_2_2_BRANCH to HEAD. I'll have to investigate some more what changes
> are missing. I'm sure that at least the icons are missing in HEAD, if not
> more.
... at least codewise HEAD contains everything that was in the 2_2 branch at
the time when the merge happend. (I diffed it against my local port and the
only thing missing was some autoconf/-make stuff David added to HEAD before the
merge). And IIRC there were no changes later to either branch...no, looking at
the CVS logs, that's not completly true. George did two fixes afterwards to
HEAD only. However according to the log it also seems as if the icons weren't
merged, but I havn't actually checked that. But that should have mostly
esthetical impact;)
Greets
Michael
From kwintv@mail.kde.org Thu Mar 28 23:22:14 2002
From: kwintv@mail.kde.org (Richard Moore)
Date: Thu, 28 Mar 2002 23:22:14 +0000
Subject: [Kwintv] Fwd: RE: KWinTV Feature Request: PVR Support
Message-ID: <200203282322.14117.rich@xmelegance.org>
---------- Forwarded Message ----------
Subject: RE: KWinTV Feature Request: PVR Support
Date: Wed, 27 Mar 2002 20:56:17 -0500
From: "Ron Van Dam" <rvandam@liwave.com>
To: "'Richard Moore'" <rich@xmelegance.org>
Sure, feel free to forward thisto the development mailing list.
Ron
-----Original Message-----
From: Richard Moore [mailto:rich@xmelegance.org]
Sent: Wednesday, March 27, 2002 11:58 AM
To: rvandam@liwave.com
Subject: Re: KWinTV Feature Request: PVR Support
----- Original Message -----
From: "Ron Van Dam" <rvandam@liwave.com>
To: "'Richard Moore'" <rich@kde.org>
Sent: Wednesday, March 27, 2002 1:49 PM
Subject: RE: KWinTV Feature Request: PVR Support
> Hi Rich,
>
> Thanks for the response back. I would like to point you to a windows
based
> program (iuVCR http://www.iulabs.com) that does PVR. Using a huge amoun=
t
of
> disk space to capture a stream is an acceptable solution. To capture fo=
r
an
> hour requires about 45-60 GB, but today's hard drives are now well over
100
> GB. By the end of this year there will be IDE drives in excess of 240 G=
B.
> Space will not be barrier.
Well, it will still be a problem for a lot of people but I agree with you=
r
point.
> You can also use the MJPEG codec to capture streams. Using MJPEG I can
> capture a hour at 640x480 using about 16-20 GB (including raw WAV audio=
).
> The MPJEG codec only utilizes about 50-60% of CPU on a 600 Mhz P2
(capturing
> a stream of 640x480 @ 29 fps, 24Bit RGB).
>
> Please don't think I am trying to pressure you into supporting PVR. I j=
ust
> wanted to provide you with my findings, so you would consider it a
feasible
> option. I fully understand the difficulties in implementing a PVR. I ju=
st
> didn't want you rule it out based upon your initial conclusions that it
> can't be done because of hardware constraints.
Thanks for the information, do you mind if i forward it to the developmen=
t
mailing list?
Cheers
Rich.
> Thanks again,
> Ron
>
> -----Original Message-----
> From: Richard Moore [mailto:rich@kde.org]
> Sent: Tuesday, March 26, 2002 8:20 PM
> To: rvandam@liwave.com
> Subject: Re: KWinTV Feature Request: PVR Support
>
>
> We've discussed this (see the kwintv mailing list archive) but the trou=
ble
> is
> doing it fast enough. With a fairly fast codec, the disk requirements (=
and
> therefore the required I/O bandwidth) are huge, and lowering the disk
usage
> makes the CPU load too high. I think this is one we'll have to forget f=
or
> now, though support for video capture of some sort is certainly part of
the
> plan.
>
> cheers
>
> Rich.
>
> On Sunday 24 March 2002 8:20 pm, you wrote:
> > Rich,
> >
> > Any thoughts about including a Personal Video Recorder support? What
>
> would
>
> > be cool is a recorder that can save a TV show (using MJPEG and WAV fo=
r
> > audio), and convert the captured stream into DIVX/MP3 format. Its
> > impossible to encode a stream in real time, so the only option would =
be
to
> > capture the stream using a light-weight video codec and then convert =
the
> > recorded stream, using a low-priority thread. This can basically be d=
one
> > using existing tools available, but it would be nice if these task we=
re
> > handled directly from KwinTV. This feature would certainly make KwinT=
V
one
> > of the cools apps for KDE.
> >
> > Take care,
> > Ron
-------------------------------------------------------
From kwintv@mail.kde.org Fri Mar 29 02:51:07 2002
From: kwintv@mail.kde.org (Rett D. Walters)
Date: Thu, 28 Mar 2002 20:51:07 -0600
Subject: [Kwintv] Bug In Kwintv
Message-ID: <HFEJKLPLNGIPOJGOOPMGIEJCCCAA.rettw@rtwnetwork.com>
Hello All:
I have downloaded and built Kwintv 0.8.11, and it crashes upon startup with
the following:
kwintv -r /dev/video0
KCrash: crashing.... crashRecursionCounter = 2
KCrash: Application Name = kwintv path = <unknown> pid - 5980
The a KDE window pops up with the following backtrace info:
0x40df9669 in __wait4 () from /lib/i686/libc.so.6
#0 0x40df9669 in __wait4 () from /lib/i686/libc.so.6
#1 0x40e75154 in __DTOR_END__ () from /lib/i686/libc.so.6
#2 0x405a9838 in KCrash::defaultCrashHandler () at eval.c:41
#3 <signal handler called>
#4 0x40e7373a in main_arena () from /lib/i686/libc.so.6
#5 0x4079cdad in QGList::append () from /usr/lib/qt-2.3.1/lib/libqt.so.2
#6 0x40807002 in QApplication::postEvent ()
from /usr/lib/qt-2.3.1/lib/libqt.so.2
#7 0x08071438 in TVApplication::x11EventFilter () at eval.c:41
#8 0x407c9fb3 in qt_x11EventFilter () from /usr/lib/qt-2.3.1/lib/libqt.so.2
#9 0x407d1c50 in QApplication::x11ProcessEvent ()
from /usr/lib/qt-2.3.1/lib/libqt.so.2
#10 0x407d121a in QApplication::processNextEvent ()
from /usr/lib/qt-2.3.1/lib/libqt.so.2
#11 0x4080874c in QApplication::enter_loop ()
from /usr/lib/qt-2.3.1/lib/libqt.so.2
#12 0x4080dbb4 in QDialog::show () from /usr/lib/qt-2.3.1/lib/libqt.so.2
#13 0x4080d52f in QDialog::exec () from /usr/lib/qt-2.3.1/lib/libqt.so.2
#14 0x403d1590 in createKMessageBox () at eval.c:41
#15 0x403d36d0 in KMessageBox::information () at eval.c:41
#16 0x0808cf4d in rcfile::load () at eval.c:41
#17 0x08070b1b in TVApplication::TVApplication () at eval.c:41
#18 0x08071b14 in main () at eval.c:41
#19 0x40d5b507 in __libc_start_main (main=0x80719a0 <main>, argc=3,
ubp_av=0xbffffa64, init=0x80559f8 <_init>, fini=0x80b7e00 <_fini>,
rtld_fini=0x4000dc14 <_dl_fini>, stack_end=0xbffffa5c)
at ../sysdeps/generic/libc-start.c:129
I am using Redhat 7.2 With Kernel 2.4.16 Stock Redhat except for kernel, and
a Voodoo 3 3500TV using the v3tv (v3tv.sourceforge.net) v4l driver. (I can
watch TV using Xawtv ok, but xawtv is, lets say a little to basic, I can't
even capture with it) Is kwintv not compatible with this setup or am I
doing something wrong?
Thanks,
Rett Walters
From kwintv@mail.kde.org Fri Mar 29 09:27:27 2002
From: kwintv@mail.kde.org (Did)
Date: 29 Mar 2002 10:27:27 +0100
Subject: [Kwintv] Ful screen ...
Message-ID: <1017394047.7470.10.camel@nunux>
Hello,
I have installed the MDK8.2 package and found the KWinTV soft.
It's a good soft...
A have a first question :
my screen ist 1024*768 and KWinTV ful screen ist 768*576 ...
Can i modifie this ?
Thank's
Did
From kwintv@mail.kde.org Fri Mar 29 13:11:37 2002
From: kwintv@mail.kde.org (Stefan Hellwig)
Date: Fri, 29 Mar 2002 14:11:37 +0100
Subject: [Kwintv] Is there something strange going on in CVS?!
In-Reply-To: <200203281544.50730.staikos@kde.org>
References: <200203281743.58326.stefan@stefanhellwig.de> <200203281914.12323.stefan@stefanhellwig.de> <200203281544.50730.staikos@kde.org>
Message-ID: <200203291411.37224.stefan@stefanhellwig.de>
Hi!
On Thursday 28 March 2002 21:44, George Staikos wrote:
> > [Icons not in HEAD]
> Yes you should move these over to head too.
Okay, I've moved the new icons from KDE_2_2_BRANCH to HEAD so that both=20
versions have a consistent set of icons.
> The new code is going so quickly that I think we can manage to match
> the 0.8.x releases' basic functionality by May or June.
Sounds great. I hope I will be able to contribute some code as well=20
although my schedule is pretty much messed up right now... BTW, if anyone=
=20
of you would like to see any updates/news/info on www.kwintv.org please=20
let me know. The page is still pretty much empty... Thanks!
Regards, Stefan.
--=20
The Jenna von Oy WebSite - http://www.jennavonoy.com/
Run by fans, for fans, in cooperation with Jenna von Oy!
From kwintv@mail.kde.org Fri Mar 29 13:19:35 2002
From: kwintv@mail.kde.org (Stefan Hellwig)
Date: Fri, 29 Mar 2002 14:19:35 +0100
Subject: [Kwintv] Is there something strange going on in CVS?!
In-Reply-To: <3CA386EB.3E2FEF01@gmx.de>
References: <200203281743.58326.stefan@stefanhellwig.de> <200203281914.12323.stefan@stefanhellwig.de> <3CA386EB.3E2FEF01@gmx.de>
Message-ID: <200203291419.35060.stefan@stefanhellwig.de>
Hi!
On Thursday 28 March 2002 22:11, Michael Reiher wrote:
> Naa. You can as well use the 2_2 branch, I do it all the time. Don't
> know if there is a problem with the admin dir, though. I simply
> symlinked the one from my HEAD kde-common in there and that works fine.
Well, no, I can't use the version that's in KDE_2_2_BRANCH because it=20
simply does not work for me still on KDE 3 (3.0.1 CVS), whereas the=20
version in HEAD does. So there is something wrong with the version in=20
KDE_2_2_BRANCH, I believe an important patch is missing from it since
the code is also different. Like George already said, the version in the=20
KDE_2_2_BRANCH is supposed to be for KDE2 and not KDE3.
> Yes, that's right. But somebody later merged the KDE_2_2_BRANCH into
> HEAD. So ...
Yes, and that someone (George, it seems :-) applied some very important=20
patches to the version in HEAD so that it actually works on KDE3 whereas=20
the one in KDE_2_2_BRANCH does not work on KDE3 - at least not here.
> George did two fixes afterwards to HEAD only.
Exactly, that's what I was saying. And that's why the version in HEAD wor=
ks=20
for me.
> However according to the log it also seems as if the icons weren't
> merged, but I havn't actually checked that. But that should have mostly
> esthetical impact;)
Yes, of course :-). I've copied the icons now from KDE_2_2_BRANCH to HEAD=
=20
to make both versions look the same. However, the code still remains=20
different.
Regards, Stefan.
--=20
The Jenna von Oy WebSite - http://www.jennavonoy.com/
Run by fans, for fans, in cooperation with Jenna von Oy!
From kwintv@mail.kde.org Sat Mar 30 18:35:24 2002
From: kwintv@mail.kde.org (Jason House)
Date: Sat, 30 Mar 2002 13:35:24 -0500
Subject: [Kwintv] Delayed system freeze
Message-ID: <3CA6056C.8040903@Verizon.net>
I've had only marginal success with viewing tv, can anyone help me keep
my computer from freezing?
When I run kwintv, two windows open, one is a configuration wizard and
the other shows the TV signal. I am able to interact with the wizard in
order to choose NTSC encoding and initiate a channel scan. The channel
scan goes for a while and then the computer freezes. I can't do
anything but manually hit the power button.
My hardware config
Motherboard: KR7A-RAID
Processor: AMD Athlon 1700+
Sound Card: Sound Blaster Live
Tuner Card: ATI TV Wonder
Video Card: ATI Rage 128
/etc/modules.conf is:alias parport_lowlevel parport_pc
alias scsi_hostadapter hpt37x2
alias eth0 8139too
alias sound-slot-0 emu10k1
post-install sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -L
>/dev/null 2>&1 || :
pre-remove sound-slot-0 /bin/aumix-minimal -f /etc/.aumixrc -S
>/dev/null 2>&1 || :
alias char-major-81 bttv
alias usb-controller usb-uhci
I am using the RAID feature, but I know that is not the cause because I
had trouble before I switched over to the raid array.
I also have tried xawtv without success. It freezes the computer after
a random period of time. 0-5 seconds... I have actually seen a real
channel for several seconds before everything dies. neither scantv nor
scanner crash my computer. It seems to me that it is somehow related to
the actual displaying of the channel. I've never heard any sound from
either program, but I don't care about that at the moment.
Any help would be greatly appreciated