From: Kevin C. <ke...@co...> - 2008-04-04 06:39:43
|
On 3 April 2008 at 7:13, Pete Stieber <pst...@ve...> wrote: > I've separated the build instructions into wxWidgets and Jazz++ pages... > > http://jazzplusplus.sourceforge.net/buildingwx/ > > http://jazzplusplus.sourceforge.net/buildingjazz/ > > Let me know if anything isn't clear or you find typos or errors. It seems to be working. I'm building wxWidgets on my Mandriva 2008.0 laptop. It took a while to load all the development stuff on it. I normally just use it as a remote terminal to SSH into one of the other machines at the house, or I'll use it as a portable video player to watch streaming video, but no development until now. I'll let you know how the jazz build goes, which I'm certain won't start tonight. Thanks! -- Kevin |
From: Kevin C. <ke...@co...> - 2008-04-04 15:05:49
|
On 4 April 2008 at 7:40, Pete Stieber <pst...@ve...> wrote: > Thanks Kevin. I'm trying to understand the Jazz++ zombie process that > lives on when I exit Jazz++. It looks like it has to do with the ALSA > connection. When I reboot, the ALSA close message even fails. This > doesn't happen on the Fedora 8 box I test on. Rather than rebooting, is there an alsa service in /etc/init.d/... which could be restarted with the 'service' command? Alternatively, could 'alsactl' be used to shutdown alsa, rather than needing to reboot? > Keep us posted, and thanks for all of the testing, Will do, and you're welcome! -- Kevin |
From: Pete S. <pst...@ve...> - 2008-04-04 21:02:45
|
PS = Pete Stieber PS>> Thanks Kevin. I'm trying to understand the Jazz++ PS>> zombie process that lives on when I exit Jazz++. PS>> It looks like it has to do with the ALSA connection. PS>> When I reboot, the ALSA close message even fails. PS>> This doesn't happen on the Fedora 8 box I test on. KC = Kevin Cosgrove KC> Rather than rebooting, is there an alsa service in KC> /etc/init.d/... which could be restarted with the KC> 'service' command? Thanks for suggesting this Kevin. I'm a long time Red Hat/Fedora user and though the "service" command was specific to Red Hat. I'm starting to think there is a problem that is independent of Jazz++. I tried restarting ALSA from a cold boot and it also has problems... # service alsa restart Doing alsactrl to store mixer settings... [ OK ] Shutting down ALSA sound driver (version 1.0.14): no. (sound is being used by pid 6272)) [FAILED] ALSA driver (version 1.0.14) is already running. Process 6272 is the sound mixer applet (/usr/lib/mixer_applet2). Is this normal. I thought roo should be able to restart this service. When I check to see what ALSA version I have installed... $ rpm -qa | grep alsa libalsa2-1.0.15-0.rc1.4mdv2008.0 libalsa-data-1.0.15-0.rc1.4mdv2008.0 libalsa2-devel-1.0.15-0.rc1.4mdv2008.0 libalsa-oss0-1.0.14-2mdv2008.0 alsa-utils-1.0.15-0.rc1.1mdv2008.0 alsa-plugins-1.0.14-7mdv2008.0 Should 1.0.14 be mixed with 1.0.15? I don't want to get too caught up in Mandriva specific problems. Maybe I botched the install? Any ideas Kevin? Pete |
From: Pete S. <pst...@ve...> - 2008-04-05 04:00:14
|
PS = Pete Stieber PS>>> Thanks Kevin. I'm trying to understand the Jazz++ PS>>> zombie process that lives on when I exit Jazz++. PS>>> It looks like it has to do with the ALSA connection. PS>>> When I reboot, the ALSA close message even fails. PS>>> This doesn't happen on the Fedora 8 box I test on. KC = Kevin Cosgrove KC>> Rather than rebooting, is there an alsa service in KC>> /etc/init.d/... which could be restarted with the KC>> 'service' command? PS> Thanks for suggesting this Kevin. I'm a long time PS> Red Hat/Fedora user and though the "service" PS> command was specific to Red Hat. PS> PS> I'm starting to think there is a problem that is PS> independent of Jazz++. I tried restarting PS> ALSA from a cold boot and it also has problems... PS> PS> # service alsa restart PS> Doing alsactrl to store mixer settings... [ OK ] PS> Shutting down ALSA sound driver (version 1.0.14): no. (sound is being PS> used by pid 6272)) [FAILED] PS> ALSA driver (version 1.0.14) is already running. PS> PS> Process 6272 is the sound mixer applet PS> (/usr/lib/mixer_applet2). PS> PS> Is this normal. I thought root should be able to PS> restart this service. PS> PS> When I check to see what ALSA version I PS> have installed... PS> $ rpm -qa | grep alsa PS> libalsa2-1.0.15-0.rc1.4mdv2008.0 PS> libalsa-data-1.0.15-0.rc1.4mdv2008.0 PS> libalsa2-devel-1.0.15-0.rc1.4mdv2008.0 PS> libalsa-oss0-1.0.14-2mdv2008.0 PS> alsa-utils-1.0.15-0.rc1.1mdv2008.0 PS> alsa-plugins-1.0.14-7mdv2008.0 PS> PS> Should 1.0.14 be mixed with 1.0.15? PS> PS> I don't want to get too caught up in Mandriva PS> specific problems. Maybe I botched the install? PS> PS> Any ideas Kevin? I can't even stop the process with # service alsa force-stop This command tries to stop all processes attached to alsa, but gets stuck trying to kill the Jazz++ process with a SIGKILL. I'm not sure what to do next. Pete |
From: Pete S. <pst...@ve...> - 2008-04-05 05:31:30
|
PS = Pete Stieber PS> I'm trying to understand the Jazz++ PS> zombie process that lives on when I exit Jazz++... After putting in cout statements and rebooting several time, I think I commented out the offending code. Kevin, Make sure you update and rebuild Jazz++ before attempting to run it. Robert, If you are out there, you may want to update, rebuild and see how it goes. Thanks for all of the help, Pete |
From: Kevin C. <ke...@co...> - 2008-04-05 08:42:01
|
On 4 April 2008 at 22:32, Pete Stieber <pst...@ve...> wrote: > PS = Pete Stieber > PS> I'm trying to understand the Jazz++ > PS> zombie process that lives on when I exit Jazz++... > > After putting in cout statements and rebooting several time, I think I > commented out the offending code. > > Kevin, > Make sure you update and rebuild Jazz++ before attempting to run it. OK, will do. I've got wxWidgets to compile fine on the laptop. I didn't do anything with Jazz++ yet. So, your timing is great. Thanks... -- Kevin |
From: Pete S. <pst...@ve...> - 2008-04-07 17:50:43
|
PS = Pete Stieber PS>>> I'm trying to understand the Jazz++ PS>>> zombie process that lives on when I exit Jazz++... PS>> After putting in cout statements and rebooting PS>> several time, I think I commented out the PS>> offending code. PS>> PS>> Kevin, PS>> Make sure you update and rebuild Jazz++ before PS>> attempting to run it. KC = Kevin Cosgrove KC> OK, will do. I've got wxWidgets to compile fine KC> on the laptop. I didn't do anything with Jazz++ KC> yet. So, your timing is great. Kevin and anyone else who may be listening ;-) I've done some preliminary work on the harmony browser. Use "Tools... | Harmony Browser..." to give it a whirl. Let me know if it is acting properly. IIRC you were interested in this. Pete |
From: Kevin C. <ke...@co...> - 2008-04-07 18:09:27
|
On 7 April 2008 at 10:51, Pete Stieber <pst...@ve...> wrote: > I've done some preliminary work on the harmony browser. Use "Tools... | > Harmony Browser..." to give it a whirl. > > Let me know if it is acting properly. IIRC you were interested in this. I was/am quite interested in the harmony browser. It'll be the first feature I test out, other than basic operation. Thanks..... -- Kevin |
From: Kevin C. <ke...@co...> - 2008-04-09 17:02:54
|
On 4 April 2008 at 14:03, Pete Stieber <pst...@ve...> wrote: > Thanks for suggesting this Kevin. I'm a long time Red Hat/Fedora user > and though the "service" command was specific to Red Hat. > > I'm starting to think there is a problem that is independent of Jazz++. > I tried restarting ALSA from a cold boot and it also has problems... > > # service alsa restart > Doing alsactrl to store mixer settings... [ OK ] > Shutting down ALSA sound driver (version 1.0.14): no. (sound is being > used by pid 6272)) [FAILED] > ALSA driver (version 1.0.14) is already running. > > Process 6272 is the sound mixer applet (/usr/lib/mixer_applet2). > > Is this normal. I thought roo should be able to restart this service. That doesn't look normal. Here's what I get: [root@laptop2-INCOMING #31] service alsa restart Doing alsactl to store mixer settings... [ OK ] Shutting down ALSA sound driver (version 1.0.14): [ OK ] Starting ALSA version 1.0.14: snd_ali5451. [ OK ] [root@laptop2-INCOMING #32] > When I check to see what ALSA version I have installed... > > $ rpm -qa | grep alsa > libalsa2-1.0.15-0.rc1.4mdv2008.0 > libalsa-data-1.0.15-0.rc1.4mdv2008.0 > libalsa2-devel-1.0.15-0.rc1.4mdv2008.0 > libalsa-oss0-1.0.14-2mdv2008.0 > alsa-utils-1.0.15-0.rc1.1mdv2008.0 > alsa-plugins-1.0.14-7mdv2008.0 Here's what I have that grep finds: alsamixergui-0.9.0-0.12rc1_3mdv2008.0 alsaplayer-0.99.80-0.rc2.1mdv2008.0 alsaplayer-plugin-input-sndfile-0.99.80-0.rc2.1mdv2008.0 alsaplayer-plugin-input-vorbis-0.99.80-0.rc2.1mdv2008.0 alsaplayer-plugin-output-jack-0.99.80-0.rc2.1mdv2008.0 alsaplayer-plugin-ui-gtk-0.99.80-0.rc2.1mdv2008.0 alsa-plugins-1.0.14-7mdv2008.0 alsa-utils-1.0.15-0.rc1.1mdv2008.0 java-1.6.0-sun-alsa-1.6.0.05-1mdv2008.0 libalsa2-1.0.15-0.rc1.4mdv2008.0 libalsa2-devel-1.0.15-0.rc1.4mdv2008.0 libalsa-data-1.0.15-0.rc1.4mdv2008.0 libalsa-oss0-1.0.14-2mdv2008.0 > Should 1.0.14 be mixed with 1.0.15? Mine apparently is too. > I don't want to get too caught up in Mandriva specific problems. I don't blame you for wanting to stay out of distribution specific traps, whatever the distribution or trap. > Maybe I botched the install? Did it seem to go smoothly? > Any ideas Kevin? See if anything else can access ALSA? Does TiMidity play things? How about [x]playmidi? Good luck.... -- Kevin |
From: Pete S. <pst...@ve...> - 2008-04-09 22:51:24
|
PS = Pete Stieber wrote on 4 April 2008 at 14:03 PS>> I'm starting to think there is a problem that is PS>> independent of Jazz++. I tried restarting ALSA PS>> from a cold boot and it also has problems... PS>> PS>> # service alsa restart PS>> Doing alsactrl to store mixer settings... [ OK ] PS>> Shutting down ALSA sound driver (version 1.0.14): no. PS>> sound is being used by pid 6272)) [FAILED] PS>> ALSA driver (version 1.0.14) is already running. PS>> PS>> Process 6272 is the sound mixer applet PS>> (/usr/lib/mixer_applet2). PS>> PS>> Is this normal. I thought root should be able PS>> to restart this service. KC = Kevin Cosgrove KC> That doesn't look normal. Here's what I get: KC> KC> [root@laptop2-INCOMING #31] service alsa restart KC> Doing alsactl to store mixer settings... [ OK ] KC> Shutting down ALSA sound driver (version 1.0.14): [ OK ] KC> Starting ALSA version 1.0.14: snd_ali5451. [ OK ] KC> [root@laptop2-INCOMING #32] PS>> When I check to see what ALSA version I have installed... PS>> PS>> $ rpm -qa | grep alsa PS>> libalsa2-1.0.15-0.rc1.4mdv2008.0 PS>> libalsa-data-1.0.15-0.rc1.4mdv2008.0 PS>> libalsa2-devel-1.0.15-0.rc1.4mdv2008.0 PS>> libalsa-oss0-1.0.14-2mdv2008.0 PS>> alsa-utils-1.0.15-0.rc1.1mdv2008.0 PS>> alsa-plugins-1.0.14-7mdv2008.0 KC> Here's what I have that grep finds: KC> KC> alsamixergui-0.9.0-0.12rc1_3mdv2008.0 KC> alsaplayer-0.99.80-0.rc2.1mdv2008.0 KC> alsaplayer-plugin-input-sndfile-0.99.80-0.rc2.1mdv2008.0 KC> alsaplayer-plugin-input-vorbis-0.99.80-0.rc2.1mdv2008.0 KC> alsaplayer-plugin-output-jack-0.99.80-0.rc2.1mdv2008.0 KC> alsaplayer-plugin-ui-gtk-0.99.80-0.rc2.1mdv2008.0 KC> alsa-plugins-1.0.14-7mdv2008.0 KC> alsa-utils-1.0.15-0.rc1.1mdv2008.0 KC> java-1.6.0-sun-alsa-1.6.0.05-1mdv2008.0 KC> libalsa2-1.0.15-0.rc1.4mdv2008.0 KC> libalsa2-devel-1.0.15-0.rc1.4mdv2008.0 KC> libalsa-data-1.0.15-0.rc1.4mdv2008.0 KC> libalsa-oss0-1.0.14-2mdv2008.0 PS>> Should 1.0.14 be mixed with 1.0.15? KC> Mine apparently is too. PS>> I don't want to get too caught up in Mandriva PS>> specific problems. KC> I don't blame you for wanting to stay out of KC> distribution specific traps, whatever the KC> distribution or trap. PS>> Maybe I botched the install? KC> Did it seem to go smoothly? Yes. I didn't have any problems. PS>> Any ideas Kevin? KC> See if anything else can access ALSA? Does KC> TiMidity play things? How about [x]playmidi? I'll give it a try when I get home. I hear sound when I login and logout so I assumed sound was properly configured. Thanks for the help, Pete |
From: Pete S. <pst...@ve...> - 2008-04-10 03:28:28
|
PS = Pete Stieber wrote on 4 April 2008 at 14:03 PS>>> I'm starting to think there is a problem that is PS>>> independent of Jazz++. I tried restarting ALSA PS>>> from a cold boot and it also has problems... PS>>> PS>>> # service alsa restart PS>>> Doing alsactrl to store mixer settings... [ OK ] PS>>> Shutting down ALSA sound driver (version 1.0.14): no. PS>>> sound is being used by pid 6272)) [FAILED] PS>>> ALSA driver (version 1.0.14) is already running. PS>>> PS>>> Process 6272 is the sound mixer applet PS>>> (/usr/lib/mixer_applet2). PS>>> PS>>> Is this normal. I thought root should be able PS>>> to restart this service. KC = Kevin Cosgrove KC>> That doesn't look normal. Here's what I get: KC>> KC>> [root@laptop2-INCOMING #31] service alsa restart KC>> Doing alsactl to store mixer settings... [ OK ] KC>> Shutting down ALSA sound driver (version 1.0.14): [ OK ] KC>> Starting ALSA version 1.0.14: snd_ali5451. [ OK ] KC>> [root@laptop2-INCOMING #32] PS>> When I check to see what ALSA version I have installed... PS>> PS>> $ rpm -qa | grep alsa PS>> libalsa2-1.0.15-0.rc1.4mdv2008.0 PS>> libalsa-data-1.0.15-0.rc1.4mdv2008.0 PS>> libalsa2-devel-1.0.15-0.rc1.4mdv2008.0 PS>> libalsa-oss0-1.0.14-2mdv2008.0 PS>> alsa-utils-1.0.15-0.rc1.1mdv2008.0 PS>> alsa-plugins-1.0.14-7mdv2008.0 KC> Here's what I have that grep finds: KC> KC> alsamixergui-0.9.0-0.12rc1_3mdv2008.0 KC> alsaplayer-0.99.80-0.rc2.1mdv2008.0 KC> alsaplayer-plugin-input-sndfile-0.99.80-0.rc2.1mdv2008.0 KC> alsaplayer-plugin-input-vorbis-0.99.80-0.rc2.1mdv2008.0 KC> alsaplayer-plugin-output-jack-0.99.80-0.rc2.1mdv2008.0 KC> alsaplayer-plugin-ui-gtk-0.99.80-0.rc2.1mdv2008.0 KC> alsa-plugins-1.0.14-7mdv2008.0 KC> alsa-utils-1.0.15-0.rc1.1mdv2008.0 KC> java-1.6.0-sun-alsa-1.6.0.05-1mdv2008.0 KC> libalsa2-1.0.15-0.rc1.4mdv2008.0 KC> libalsa2-devel-1.0.15-0.rc1.4mdv2008.0 KC> libalsa-data-1.0.15-0.rc1.4mdv2008.0 KC> libalsa-oss0-1.0.14-2mdv2008.0 PS>> Should 1.0.14 be mixed with 1.0.15? KC> Mine apparently is too. PS>>> I don't want to get too caught up in Mandriva PS>>> specific problems. KC>> I don't blame you for wanting to stay out of KC>> distribution specific traps, whatever the KC>> distribution or trap. PS>>> Maybe I botched the install? KC>> Did it seem to go smoothly? PS> Yes. I didn't have any problems. PS>>> Any ideas Kevin? KC>> See if anything else can access ALSA? Does KC>> TiMidity play things? How about [x]playmidi? PS> I'll give it a try when I get home. I hear PS> sound when I login and logout so I assumed PS> sound was properly configured. Well Kevin, the last time I tried to use the machine with Mandriva, I couldn't even get it to recognize my USB keyboard. I tried multiple reboots... Tonight, everything worked. Even the ALSA restart. I even hooked up the M-AUDIO Uno cable I recommended in the other thread to my Roland TD-20 drum kit module, and Jazz++ worked using that setup. I did install TIMidity++ and it played the file too. Thanks for the help, Pete |
From: Kevin C. <ke...@co...> - 2008-04-10 03:58:24
|
On 9 April 2008 at 20:29, Pete Stieber <pst...@ve...> wrote: > Well Kevin, the last time I tried to use the machine with Mandriva, I > couldn't even get it to recognize my USB keyboard. I tried multiple > reboots... > > Tonight, everything worked. Even the ALSA restart. I even hooked up > the M-AUDIO Uno cable I recommended in the other thread to my Roland > TD-20 drum kit module, and Jazz++ worked using that setup. > > I did install TIMidity++ and it played the file too. Glad it's working for ya. > Thanks for the help, Not that I actually DID anything, but you're welcome... -- Kevin |
From: Pete S. <pst...@ve...> - 2008-04-04 14:40:18
|
PS = Pete Stieber PS>> I've separated the build instructions into wxWidgets PS>> and Jazz++ pages... PS>> PS>> http://jazzplusplus.sourceforge.net/buildingwx/ PS>> PS>> http://jazzplusplus.sourceforge.net/buildingjazz/ PS>> PS>> Let me know if anything isn't clear or you find PS>> typos or errors. KC = Kevin Cosgrove KC> It seems to be working. I'm building wxWidgets on KC> my Mandriva 2008.0 laptop. It took a while to load KC> all the development stuff on it. Sorry about that. KC> I normally just use it as a remote terminal to SSH KC> into one of the other machines at the house, or KC> I'll use it as a portable video player to watch KC> watch streaming video, but no development until now. KC> I'll let you know how the jazz build goes, which I'm KC> certain won't start tonight. Thanks Kevin. I'm trying to understand the Jazz++ zombie process that lives on when I exit Jazz++. It looks like it has to do with the ALSA connection. When I reboot, the ALSA close message even fails. This doesn't happen on the Fedora 8 box I test on. I'll have more time to look at it this weekend. Keep us posted, and thanks for all of the testing, Pete |