Re: [opensuse] Amarok and projectM visualization Solved!??
Hi!
Am 21.03.2010 um 02:54 schrieb Marc Chamberlin:
home:theMarix:KDE:Community is the identifier of someone's personal OBS project, which produces at least one repository (for different openSUSE versions, etc). If you search for projectM at software.opensuse.org/search you will get search hits from every repository that includes a *projectM* package.
I guess you want this repo: http://download.opensuse.org/repositories/home:/theMarix:/KDE:/Community/ope...
[...]
Thanks Will, Tejas for your help, but I am still not out of the woods yet. I found and installed the projectM-pulseaudio package. I can now bring up the projectM visualization but it is clearly not responding to any sound output from Amarok yet. It seems to generate patterns ok but not in sync to either volume or freq as I would expect. So something is still missing...
That package is from my repository in which I experiment with new packages that IMO would make sense in Contrib. While the build is proper I never got projectM working correctly in terms of properly responding to pulseaudio, which is pretty much the reason why this package is still stuck in my personal repo and not pushed to Contrib itself. (This problem is not packaging-related, I also experimented with non-packaged builds from the tarballs)
If anybody has any Idea on how to get this application running properly I'd be happy. :)
Regards, Matthias Thanks Matthias for your reply, but I don't think you replied to the mail list as your probably intended.. (I will reply to both you and it) I cannot say for certain what has fixed projectM for me, I had set this
-------- Original Message -------- Subject: Re: [opensuse] Amarok and projectM visualization Solved!?? Date: Wed, 31 Mar 2010 09:01:04 -0700 From: Marc Chamberlin <marc@marcchamberlin.com> Reply-To: marc@marcchamberlin.com To: Matthias Bach <marix@marix.org>, opensuse <opensuse@opensuse.org> On 3/31/2010 7:20 AM, Matthias Bach wrote: aside for now and wandered off to solve other problems (like getting mythTV, lirc and other media components up and running) During the course of doing all this I did note that when I installed one of the lirc packages, it forced a new update of the kernel for me, so perhaps that had something to do with the fix.. Anywise, as an inspiration, I just now decided to launch projectM-pulseaudio from a command line instead of using the KDE/SuSE menu, just to see if there would be any clues in the output. And I will be darned if the thing simply started working! So like I said, I have tried a lot of paths to get this and other components working and cannot say for certain what fixed it. If you want to compare your system to mine, I will be glad to help. Just send me commands that you want me to execute and I will post the results... Really is nice to have my old friend back!!! Love the visualizations! Thanks whoever fixed it! Marc.. -- Marc Chamberlin www.marcchamberlin.com A man said unto the universe - "Sir I Exist!" "However" replied the universe "I do not see where that creates in me a sense of an obligation" S Crane.
On 3/31/2010 10:38 AM, Marc Chamberlin wrote:
-------- Original Message -------- Subject: Re: [opensuse] Amarok and projectM visualization Solved!?? Date: Wed, 31 Mar 2010 09:01:04 -0700 From: Marc Chamberlin <marc@marcchamberlin.com> Reply-To: marc@marcchamberlin.com To: Matthias Bach <marix@marix.org>, opensuse <opensuse@opensuse.org>
Hi!
Am 21.03.2010 um 02:54 schrieb Marc Chamberlin:
home:theMarix:KDE:Community is the identifier of someone's personal OBS project, which produces at least one repository (for different openSUSE versions, etc). If you search for projectM at software.opensuse.org/search you will get search hits from every repository that includes a *projectM* package.
I guess you want this repo: http://download.opensuse.org/repositories/home:/theMarix:/KDE:/Community/ope...
[...]
Thanks Will, Tejas for your help, but I am still not out of the woods yet. I found and installed the projectM-pulseaudio package. I can now bring up the projectM visualization but it is clearly not responding to any sound output from Amarok yet. It seems to generate patterns ok but not in sync to either volume or freq as I would expect. So something is still missing... That package is from my repository in which I experiment with new packages that IMO would make sense in Contrib. While the build is proper I never got projectM working correctly in terms of properly responding to pulseaudio, which is pretty much the reason why this package is still stuck in my personal repo and not pushed to Contrib itself. (This problem is not packaging-related, I also experimented with non-packaged builds from the tarballs)
If anybody has any Idea on how to get this application running properly I'd be happy. :)
Regards, Matthias Thanks Matthias for your reply, but I don't think you replied to the mail list as your probably intended.. (I will reply to both you and it) I cannot say for certain what has fixed projectM for me, I had set this aside for now and wandered off to solve other problems (like getting mythTV, lirc and other media components up and running) During
On 3/31/2010 7:20 AM, Matthias Bach wrote: the course of doing all this I did note that when I installed one of the lirc packages, it forced a new update of the kernel for me, so perhaps that had something to do with the fix.. Anywise, as an inspiration, I just now decided to launch projectM-pulseaudio from a command line instead of using the KDE/SuSE menu, just to see if there would be any clues in the output. And I will be darned if the thing simply started working!
So like I said, I have tried a lot of paths to get this and other components working and cannot say for certain what fixed it. If you want to compare your system to mine, I will be glad to help. Just send me commands that you want me to execute and I will post the results...
Really is nice to have my old friend back!!! Love the visualizations! Thanks whoever fixed it!
Marc..
Well this looks like a bug, smells like a bug... but how should I report it? On my system I have a Creative Labs Audigy 4 Pro sound card AND I have connected to my computer, via a USB cable an ION turntable (which I primarily use under Windoz) YaST sound configuration was detecting this as a second sound device BUT I have been telling YaST to disable it. Which it happily reports that it is doing so. Well I just rebooted my system, restarted Amarok playing and then projectM-pulseaudio and darned if it stopped working on me again... So I decided to try starting projectM from a command line and lo and behold I see it is trying to connect to the second DISABLED sound device from what I see is being reported in the connectHelper: line. My guess is that projectM has been connecting at random to either of these two sound devices regardless of whether one has been disabled in YaST or not... I unplugged the USB cable to my ION turntable and now YaST and the rest of the system has no choice but to see/use the Audigy 4 card for sound. AND IT WORKS! So BIG red herring that I have been chasing!!! So which one of these tools is actually buggy? YaST? PulseAudio? projectM-pulseaudio? I cannot find adequate tools to help me isolate each of these components and track down any further what is at fault, but certainly one or more is! Marc..
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2010-04-01 at 17:01 -0700, Marc Chamberlin wrote:
Well this looks like a bug, smells like a bug... but how should I report it?
On my system I have a Creative Labs Audigy 4 Pro sound card AND I have connected to my computer, via a USB cable an ION turntable (which I primarily use under Windoz) YaST sound configuration was detecting this as a second sound device BUT I have been telling YaST to disable it. Which it happily reports that it is doing so.
Well I just rebooted my system, restarted Amarok playing and then projectM-pulseaudio and darned if it stopped working on me again... So I decided to try starting projectM from a command line and lo and behold I see it is trying to connect to the second DISABLED sound device from what I see is being reported in the connectHelper: line. My guess is that projectM has been connecting at random to either of these two sound devices regardless of whether one has been disabled in YaST or not... I unplugged the USB cable to my ION turntable and now YaST and the rest of the system has no choice but to see/use the Audigy 4 card for sound. AND IT WORKS! So BIG red herring that I have been chasing!!!
So which one of these tools is actually buggy? YaST? PulseAudio? projectM-pulseaudio? I cannot find adequate tools to help me isolate each of these components and track down any further what is at fault, but certainly one or more is!
I have a similar problem. I have a computer with a sound card that is detected but does not work, support is buggy. So I bought another sound card and plugged it. YaST detects both. I dissable the first one, it reports as dissabled... but it does not. I had to include it in /etc/modprobe.d/50-blacklist.conf: #Cer - https://bugzilla.novell.com/show_bug.cgi?id=564324 blacklist snd-hda-intel - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAku1N2oACgkQtTMYHG2NR9XvYgCggbRglywwtfd6VZB+Pi4BmNyd NmcAn2B6024hvEkcKMSHflVkXZqdYND6 =gELs -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (2)
-
Carlos E. R. -
Marc Chamberlin