Re: [SLE] xawtv and frequencies
On Sun, 2 Dec 2001 15:45:23 +0700
Constant Brouerius van Nidek
Dear Geoff, As I did not download the sources I am a little bit lost. There above I have never build from sources so as a matter of fact, I need somebody to lean at ;-). Could you be of help?
Sure ... Here are the steps : (1) Go to http://bytesex.org/xawtv/index.html (2) Where you see "Latest version is 3.65, released 26 Nov 2001" you right-click on the 3.65 to download xawtv_3.65.tar.gz into some convenient directory. I have a /home/myusrename/Downloads directory for this purpose. I suggest that you create one. (3) When the download is complete you change to the directory in which you have downloaded xawtv_3.65.tar.gz and your enter: tar -xvzf xawtv_3.65.tar.gz (4) The result should be the creation of a sub-directory /xawtv-3.65 - which has various sub-directories of its own. (5) Change into that directory and enter: configure. A lot of stuff will fly past, and the last lines will be : creating Makefile creating src/Makefile creating tools/Makefile creating radio/Makefile creating man/Makefile creating i2c/Makefile creating font/Makefile creating webcam/Makefile creating http/Makefile creating libvbi/Makefile creating libng/Makefile creating cc/Makefile creating xawtv.spec creating config.h (6) If all that happens then we know that xawtv will compile on your system. It will not work if you do not have installed the development libraries that xawtv need to compile. You will have to refer back to me if that happens and include the error messages in your post. If it does work, then normally we would just go ahead and compile as the next step, but that is no good for you, because you are going to alter the source code. So next you enter: rm config.h and then : make distclean. A lot of messages will fly past and the result will be that you have a clean set of source files to work on. (7) Change directories to the /xawtv-3.65/src sub-directory. One of the file you will see there is frequencies.h. You need to load that into a *text editor* - such as kedit or pico or joe - *not* a wordprocessor. The opening lines are the one's you have seen me post here : /* * Worldwide channel/frequency list * * Nathan Laredo (laredo@broked.net) * * Frequencies are given in kHz */ #define NTSC_AUDIO_CARRIER 4500 #define PAL_AUDIO_CARRIER_I 6000 #define PAL_AUDIO_CARRIER_BGHN 5500 #define PAL_AUDIO_CARRIER_MN 4500 #define PAL_AUDIO_CARRIER_D 6500 #define SEACAM_AUDIO_DKK1L 6500 #define SEACAM_AUDIO_BG 5500 (8) You can now edit the #defines to any value you want in accordance with Doug's advice. When you have finished, save the file. (9) Change back into the /xawtv-3.65 sub-directory. Repeat step (5) - ie enter: configure. (10) If you do not see any errors, and the last line of the output is "creating config.h" you can next enter : make (11) The program will now compile. You will see some error messages fly by. They are probably irrelevant. The final lines you see will be : make[2]: Leaving directory `/home/your_usrename/Downloads/xawtv-3.65/cc' (cd man; make build) make[2]: Entering directory `/home/your_usrename/Downloads/xawtv-3.65/man' make[2]: Nothing to be done for `build'. make[2]: Leaving directory `/home/your_usrename/Downloads/xawtv-3.65/man' make[1]: Leaving directory `/home/your_usrename/Downloads/xawtv-3.65' (12) The next stage is *usually* to change to root and enter: make install. That will install the program into /usr/local/bin. Before doing so you should remove the existing xawtv rpm that you have installed. However I do not recommend that you do that yet, because it is likely that you will need to experiment with different values for the #defines. So you can just enter: /home/your_username/Downloads/xawtv-3.65/src/xawtv - This should run the new copy of xawtv you just compiled, without disturbing the old one that is in /usr/local/bin. (13) If you are not happy with the results, go back and repeat steps (6) to (12) until you are happy. Then you can remove the existin rpm and finally make install the copy you are happy with. Regards, Geoff _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
On Sunday 02 December 2001 19:06, you wrote:
On Sun, 2 Dec 2001 15:45:23 +0700
Constant Brouerius van Nidek
wrote: Dear Geoff, As I did not download the sources I am a little bit lost.
Sure ...
Here are the steps :
Dear Geoff, I had already a Download directory, so that was easy. Configure worked without problems, so it seems that I had all devels.
(6) If all that happens then we know that xawtv will compile on your system. If it does work, then normally we would just go ahead and compile as the next step, but that is no good for you, because you are going to alter the source code. So next you enter: rm config.h and then : make distclean. A lot of messages will fly past and the result will be that you have a clean set of source files to work on.
(7) Change directories to the /xawtv-3.65/src sub-directory. One of the file you will see there is frequencies.h. You need to load that into a *text editor* - such as kedit or pico or joe - *not* a wordprocessor. The opening lines are the one's you have seen me post here :
/* * Worldwide channel/frequency list * * Nathan Laredo (laredo@broked.net) * * Frequencies are given in kHz */ #define NTSC_AUDIO_CARRIER 4500 #define PAL_AUDIO_CARRIER_I 6000 #define PAL_AUDIO_CARRIER_BGHN 5500 #define PAL_AUDIO_CARRIER_MN 4500 #define PAL_AUDIO_CARRIER_D 6500 #define SEACAM_AUDIO_DKK1L 6500 #define SEACAM_AUDIO_BG 5500
(8) You can now edit the #defines to any value you want in accordance with Doug's advice. When you have finished, save the file.
What I do not yet understand, a # was for me always a remming out, a comment line. Is that here different? I thought it was a good idea to remove the # in front of the BGHN carrier but tha gave an error 2 and the compilation stopped. So I just changed the kHz figuresand I could not find any difference. The sound is still at the same place as before, even as I changed them to extremes.
(9) Change back into the /xawtv-3.65 sub-directory. Repeat step (5) - ie enter: configure.
(10) If you do not see any errors, and the last line of the output is "creating config.h" you can next enter : make
(11) The program will now compile. You will see some error messages fly by. They are probably irrelevant. The final lines you see will be :
make[2]: Leaving directory `/home/your_usrename/Downloads/xawtv-3.65/cc' (cd man; make build) make[2]: Entering directory `/home/your_usrename/Downloads/xawtv-3.65/man' make[2]: Nothing to be done for `build'. make[2]: Leaving directory `/home/your_usrename/Downloads/xawtv-3.65/man' make[1]: Leaving directory `/home/your_usrename/Downloads/xawtv-3.65'
(12) The next stage is *usually* to change to root and enter: make install. That will install the program into /usr/local/bin. Before doing so you should remove the existing xawtv rpm that you have installed. However I do not recommend that you do that yet, because it is likely that you will need to experiment with different values for the #defines. So you can just enter: /home/your_username/Downloads/xawtv-3.65/src/xawtv - This should run the new copy of xawtv you just compiled, without disturbing the old one that is in /usr/local/bin.
(13) If you are not happy with the results, go back and repeat steps (6) to (12) until you are happy. Then you can remove the existin rpm and finally make install the copy you are happy with.
Is it perhaps necesarry to remove the former compiled results or are they every time overwritten. I saw that the second and following "make" was very fast ready. Or is that normal. A further question, shoulld I have inserted anything in the following part of the file frequencies? Somewhere in the final result several choices can be made. Fourteen if I remeber right. Could I get Indonesia as one of the choices? Thanks for your help. A first is always scarry ;-) Regards Constant
On Sun, 2 Dec 2001 22:41:02 +0700
Constant Brouerius van Nidek
On Sunday 02 December 2001 19:06, you wrote:
On Sun, 2 Dec 2001 15:45:23 +0700
Constant Brouerius van Nidek
wrote: Dear Geoff, As I did not download the sources I am a little bit lost.
Sure ...
Here are the steps :
Dear Geoff, I had already a Download directory, so that was easy. Configure worked without problems, so it seems that I had all devels.
(6) If all that happens then we know that xawtv will compile on your system. If it does work, then normally we would just go ahead and compile as the next step, but that is no good for you, because you are going to alter the source code. So next you enter: rm config.h and then : make distclean. A lot of messages will fly past and the result will be that you have a clean set of source files to work on.
(7) Change directories to the /xawtv-3.65/src sub-directory. One of the file you will see there is frequencies.h. You need to load that into a *text editor* - such as kedit or pico or joe - *not* a wordprocessor. The opening lines are the one's you have seen me post here :
/* * Worldwide channel/frequency list * * Nathan Laredo (laredo@broked.net) * * Frequencies are given in kHz */ #define NTSC_AUDIO_CARRIER 4500 #define PAL_AUDIO_CARRIER_I 6000 #define PAL_AUDIO_CARRIER_BGHN 5500 #define PAL_AUDIO_CARRIER_MN 4500 #define PAL_AUDIO_CARRIER_D 6500 #define SEACAM_AUDIO_DKK1L 6500 #define SEACAM_AUDIO_BG 5500
(8) You can now edit the #defines to any value you want in accordance with Doug's advice. When you have finished, save the file.
What I do not yet understand, a # was for me always a remming out, a comment line. Is that here different? I thought it was a good idea to remove the # in front of the BGHN carrier but tha gave an error 2 and the compilation stopped. So I just changed the kHz figuresand I could not find any difference. The sound is still at the same place as before, even as I changed them to extremes.
In C source code a comment is text within /* ... */. You can see, therefore, that most of the text in frequencies.h is, in fact, just comments. The #define, however, is part of the C syntax that tells the compiler to create a certain kind of symbolic constant. Therefore you must replace every #.
(9) Change back into the /xawtv-3.65 sub-directory. Repeat step (5) - ie enter: configure.
(10) If you do not see any errors, and the last line of the output is "creating config.h" you can next enter : make
(11) The program will now compile. You will see some error messages fly by. They are probably irrelevant. The final lines you see will be :
make[2]: Leaving directory `/home/your_usrename/Downloads/xawtv-3.65/cc' (cd man; make build) make[2]: Entering directory `/home/your_usrename/Downloads/xawtv-3.65/man' make[2]: Nothing to be done for `build'. make[2]: Leaving directory `/home/your_usrename/Downloads/xawtv-3.65/man' make[1]: Leaving directory `/home/your_usrename/Downloads/xawtv-3.65'
(12) The next stage is *usually* to change to root and enter: make install. That will install the program into /usr/local/bin. Before doing so you should remove the existing xawtv rpm that you have installed. However I do not recommend that you do that yet, because it is likely that you will need to experiment with different values for the #defines. So you can just enter: /home/your_username/Downloads/xawtv-3.65/src/xawtv - This should run the new copy of xawtv you just compiled, without disturbing the old one that is in /usr/local/bin.
(13) If you are not happy with the results, go back and repeat steps (6) to (12) until you are happy. Then you can remove the existin rpm and finally make install the copy you are happy with.
Is it perhaps necesarry to remove the former compiled results or are they every time overwritten. I saw that the second and following "make" was very fast ready. Or is that normal.
It is safest to remove the former results with "make distclean" (see step(6)). It is *possible* that you do not need to do that, but I do not know how the results of compiling frequencies.h affect other parts of the code, and so errors may occur. In fact the less vigorous cleaning process that results from using "make clean" rather than "make distclean" would probably be sufficient, - but I am a pessimist.
A further question, shoulld I have inserted anything in the following part of the file frequencies? Somewhere in the final result several choices can be made. Fourteen if I remeber right. Could I get Indonesia as one of the choices?
It might be possible to do something like this, but I do not think that it is essential, and I doubt that we could do it in the context of frequencies.h - remember that most of the file is just comments and the references in ther to Indonesia are not actually affecting the code. If things go according to plan, and you can run the program by entering : /home/your_username/Downloads/xawtv-3.65/src/xawtv - then it should pick up your existing preferences in .xawtv and the only difference will be the separation between the picture and sound carrier frequencies.
Thanks for your help. A first is always scarry ;-)
You are welcome. This is interesting :-) Geoff _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
On Sunday 02 December 2001 19:06, you wrote:
On Sun, 2 Dec 2001 15:45:23 +0700
Constant Brouerius van Nidek
wrote: Dear Geoff, As I did not download the sources I am a little bit lost.
Here are the steps :
(1) Go to http://bytesex.org/xawtv/index.html
(2) Where you see "Latest version is 3.65, released 26 Nov 2001" you
(13) If you are not happy with the results, go back and repeat steps (6) to (12) until you are happy. Then you can remove the existin rpm and finally make install the copy you are happy with.
Dear Geoff, Whatever I tried, no change whatever at the behaviour of the sound channel, It is still found 16 to 20 clicks right of the picture. I assumed that there woud be some reaction from the new install after changing frequencies but a big NO go. The building of my "own " program from source went smooth. It gives me at least the courage to try it on other sources ;-).
On Mon, 3 Dec 2001 22:17:52 +0700
Constant Brouerius van Nidek
Dear Geoff, Whatever I tried, no change whatever at the behaviour of the sound channel, It is still found 16 to 20 clicks right of the picture. I assumed that there woud be some reaction from the new install after changing frequencies but a big NO go.
The fact that you saw no change at all was so surprising that I grepped the entire source code for references to those #define'd constants. I came up with nothing. That appears to mean that, although they are #defined and frequencies.h is incorporated into a number of source files, they are not actually used. Maybe they were used in the past but are no longer needed - then again maybe I just don't understand the source code. I have one last suggestion. You might be surprised how receptive most authors are to interesting feedback. I have written to several authors in situations where I have taken care to be sure that some strange behaviour I have seen is not just a result of my own stupidity. I have always had good responses, and once or twice my comments have resulted in changes in the code. If I were you I could not resist writing to Gerd Knorr about this.
The building of my "own " program from source went smooth. It gives me at least the courage to try it on other sources ;-).
Once you begin to compile your own programs (which is usually very easy), you will not want to go back to rpms. You have more control and more interest that way. After 18 months with this 7.0 installation I have about 130 programs in my Download directory that I have subsequently compiled, and most of the SuSE rpms for software I use often have been removed. Regards, Geoff _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
On Monday 03 December 2001 23:11, you wrote:
On Mon, 3 Dec 2001 22:17:52 +0700
Constant Brouerius van Nidek
wrote: Dear Geoff, Whatever I tried, no change whatever at the behaviour of the sound
The fact that you saw no change at all was so surprising that I grepped the
I have one last suggestion. You might be surprised how receptive most authors are to interesting feedback. I have written to several authors in situations where I have taken care to be sure that some strange behaviour I have seen is not just a result of my own stupidity. I have always had good responses, and once or twice my comments have resulted in changes in the code. If I were you I could not resist writing to Gerd Knorr about this.
Think that is a great idea and I will contact him tomorrow.
participants (2)
-
Constant Brouerius van Nidek
-
Geoff