No sound
|
|
Joep L. Blom
|
I hadn't have time to work on Musescore until now but I stil have my
sound problem. First, Toby, your advice to use the line: "BUILD_UBUNTU=1 debian/rules update-to-svn ", didn't work. My system says: " debian/rules not found file or directory" but I don't know where to use it. However, after I obtained the latest(?) version (1739) and compiled it successfully. However, I still don't have sound. In preferences the Soundfonts are found in the correct directory, and Alsa is selected however the mixer panel has the sound list empty. Also, in the score no walking blue line is visible when playing (so that's correct as no sound is produced). On another system (also Ubuntu 8.04) the sound works OK and I have the instrument list in the mixer panel. Apparently something is missing but I cant see what. I hope somebody can come with a solution or a way to check it. I'm working on a new score (with a deadline of course!) so I'm still using a commercial product but I hope one day to use Musescore!. Joep ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Mscore-developer mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/mscore-developer |
||||||||||||||||
Toby Smithe-2
|
Hi,
2009/4/14 Joep L. Blom <[hidden email]>: > I hadn't have time to work on Musescore until now but I stil have my > sound problem. > First, Toby, your advice to use the line: > "BUILD_UBUNTU=1 debian/rules update-to-svn ", didn't work. My system > says: " debian/rules not found file or directory" but I don't know where > to use it. However, after I obtained the latest(?) version (1739) and > compiled it successfully. "debian/rules" is a relative path to a script: you need to be in the package sources directory, one level beneath the "debian" directory in order for your shell to find and execute it. > However, I still don't have sound. More often than not, the problem is caused by another application hogging the sound card. What is the output of "lsof /dev/snd/*" before you run mscore and encounter this problem? What is the output of the mscore command itself? I apologise if I have asked these questions previously; I do not have your answers at hand. Good luck, -- Toby Smithe :: http://fulltinreality.com ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Mscore-developer mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/mscore-developer |
|
Joep L. Blom
|
Toby Smithe wrote:
> Hi, > > > "debian/rules" is a relative path to a script: you need to be in the > package sources directory, one level beneath the "debian" directory in > order for your shell to find and execute it. > >> However, I still don't have sound. > > More often than not, the problem is caused by another application > hogging the sound card. What is the output of "lsof /dev/snd/*" before > you run mscore and encounter this problem? What is the output of the > mscore command itself? I apologise if I have asked these questions > previously; I do not have your answers at hand. > > Good luck, > Toby, Thanks for the quick reply. I start mscore always from the panel-icon so the following error output was invisible: --------------------------------------------- joep@laguna:~/open2300-1.10$ mscore Suspending PulseAudio Alsa_driver: can't set sample rate to 0. init ALSA audio driver failed init ALSA driver failed init audio driver failed sequencer init failed Failure to resume: Invalid argument -------------------------------------- and the output of sudo lsof : -------------------------------------------------------- joep@laguna:~/open2300-1.10$ sudo lsof /dev/snd/* lsof: WARNING: can't stat() usbfs file system /proc/bus/usb/.usbfs Output information may be incomplete. COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME pulseaudi 8373 joep mem CHR 116,16 13959 /dev/snd/pcmC0D0p pulseaudi 8373 joep 17u CHR 116,0 13998 /dev/snd/controlC0 pulseaudi 8373 joep 24u CHR 116,0 13998 /dev/snd/controlC0 pulseaudi 8373 joep 42u CHR 116,0 13998 /dev/snd/controlC0 pulseaudi 8373 joep 43u CHR 116,16 13959 /dev/snd/pcmC0D0p mixer_app 8660 joep 20u CHR 116,0 13998 /dev/snd/controlC0 ------------------------------------------------------------------- When I started without Alsa (tag removed) Then the output was: -------------------------------------------- joep@laguna:~/open2300-1.10$ mscore Suspending PulseAudio init audio driver failed sequencer init failed Failure to resume: Invalid argument ---------------------------------------- I'm not very familiar with the inards of soundprocessing (I only use it) maybe you can gie some hints for clarification. Thanks, Joep ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Mscore-developer mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/mscore-developer |
||||||||||||||||
|
Toby Smithe-2
|
2009/4/14 Joep L. Blom <[hidden email]>:
> Toby, > Thanks for the quick reply. I start mscore always from the panel-icon so the > following error output was invisible: > --------------------------------------------- > joep@laguna:~/open2300-1.10$ mscore > Suspending PulseAudio > Alsa_driver: can't set sample rate to 0. > init ALSA audio driver failed > init ALSA driver failed > init audio driver failed > sequencer init failed > Failure to resume: Invalid argument > -------------------------------------- > and the output of sudo lsof : > -------------------------------------------------------- > joep@laguna:~/open2300-1.10$ sudo lsof /dev/snd/* > lsof: WARNING: can't stat() usbfs file system /proc/bus/usb/.usbfs > Output information may be incomplete. > COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME > pulseaudi 8373 joep mem CHR 116,16 13959 /dev/snd/pcmC0D0p > pulseaudi 8373 joep 17u CHR 116,0 13998 /dev/snd/controlC0 > pulseaudi 8373 joep 24u CHR 116,0 13998 /dev/snd/controlC0 > pulseaudi 8373 joep 42u CHR 116,0 13998 /dev/snd/controlC0 > pulseaudi 8373 joep 43u CHR 116,16 13959 /dev/snd/pcmC0D0p > mixer_app 8660 joep 20u CHR 116,0 13998 /dev/snd/controlC0 > ------------------------------------------------------------------- What the "lsof" output shows is expected: the PulseAudio daemon is using the soundcard. At the moment, there are two issues that prevent MuseScore working with PulseAudio: 1) PulseAudio doesn't support what is called "mmap access" for transferring audio 2) PortAudio (a portable audio library that MuseScore can use) doesn't support PulseAudio output Problem (1) isn't going to change, so we cannot use the default device, and use ALSA's PulseAudio soundcard emulation. Consequently, we must either interface with the soundcard hardware directly (ie, tell MuseScore to use a "hw" device; ie, "hw:0"), or support PulseAudio output. If we want to use an ALSA hardware device, we must make sure it is free for usage. Most soundcards do not do stream mixing in hardware, and so without software mixing (one application of PulseAudio) can only support one stream at a time. As we can see from above, that stream is usually PulseAudio, and this does usually simplify the desktop case. To work around this issue, when you call the "mscore" command, the program binary is not directly run. Instead, I have written a script that suspends PulseAudio (or checks for a JACK server), to free up the soundcard, and then call the MuseScore binary (mscore.real) with appropriate options. Sometimes, this does not solve the entire problem. MuseScore still, by default, tries to use the default ALSA card, which has not changed from the PulseAudio emulation. It is still (and now for a different reason), unable to use this card. MuseScore gives up in this case: how is it to know what cards are usable or available without the user telling it? It isn't, so this is why I recommend that users make sure in the MuseScore preferences, the ALSA setting points to a hardware device; usually, "hw:0". Ideally, MuseScore would be able to connect to PulseAudio, and the likely most beneficial means to do this would be via the PortAudio library. I did start work on an implementation of PortAudio's back-end for PulseAudio support, but as my time is severely limited, this got far enough to connect and tentatively open and close streams, but not far enough to do any real audio transfer work. It would be great if I had time to finish this, or if anyone else could pick up where I left off. Indeed, I published the code I had in bzr: https://code.launchpad.net/~tsmithe/+junk/portaudio.pulse I hope this clears things up for you, and other Ubuntu users. If you need any further clarification, do not hesitate to e-mail. Regards, -- Toby Smithe :: http://fulltinreality.com ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Mscore-developer mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/mscore-developer |
||||||||||||||||
|
Joep L. Blom
|
Toby Smithe wrote:
> What the "lsof" output shows is expected: the PulseAudio daemon is > using the soundcard. At the moment, there are two issues that prevent > MuseScore working with PulseAudio: > > 1) PulseAudio doesn't support what is called "mmap access" for > transferring audio > 2) PortAudio (a portable audio library that MuseScore can use) doesn't > support PulseAudio output > > Problem (1) isn't going to change, so we cannot use the default > device, and use ALSA's PulseAudio soundcard emulation. Consequently, > we must either interface with the soundcard hardware directly (ie, > tell MuseScore to use a "hw" device; ie, "hw:0"), or support > PulseAudio output. > > If we want to use an ALSA hardware device, we must make sure it is > free for usage. Most soundcards do not do stream mixing in hardware, > and so without software mixing (one application of PulseAudio) can > only support one stream at a time. As we can see from above, that > stream is usually PulseAudio, and this does usually simplify the > desktop case. To work around this issue, when you call the "mscore" > command, the program binary is not directly run. Instead, I have > written a script that suspends PulseAudio (or checks for a JACK > server), to free up the soundcard, and then call the MuseScore binary > (mscore.real) with appropriate options. > > Sometimes, this does not solve the entire problem. MuseScore still, by > default, tries to use the default ALSA card, which has not changed > from the PulseAudio emulation. It is still (and now for a different > reason), unable to use this card. MuseScore gives up in this case: how > is it to know what cards are usable or available without the user > telling it? It isn't, so this is why I recommend that users make sure > in the MuseScore preferences, the ALSA setting points to a hardware > device; usually, "hw:0". > > Ideally, MuseScore would be able to connect to PulseAudio, and the > likely most beneficial means to do this would be via the PortAudio > library. I did start work on an implementation of PortAudio's back-end > for PulseAudio support, but as my time is severely limited, this got > far enough to connect and tentatively open and close streams, but not > far enough to do any real audio transfer work. It would be great if I > had time to finish this, or if anyone else could pick up where I left > off. Indeed, I published the code I had in bzr: > > https://code.launchpad.net/~tsmithe/+junk/portaudio.pulse > > I hope this clears things up for you, and other Ubuntu users. If you > need any further clarification, do not hesitate to e-mail. > > Regards, > I finally had the time to follow your suggestion and replace the default term in the ALsa tag in I/O with the direct hardware parameters and it works like a charm. So yesterday I had some time to try it. As I'm accustomed to Finale I have a learning curve to follow. One of the differences is that Musescore uses less the mouse and more the keyboard. So it took, for example, some before I discovered how to enter slurs, but it's progressing. Of course when you start using a program you discover wishes. One -cosmetic? - I have is that I would like to see a so-called "scroll mode" when entering a score. Musescore now only has a "Page-mode" where you see the score WYSWYG. However, I write arrangements for more instruments (2 piano's, quintet, sextet, big band) and I like to see all instruments together (e.g. 17 voices in a big band score) which I can scale to get an overview of e.g. 8-bars or 12-bars phrases. (I always print the conductor score in landscape with 12 bars per page ). Especially the possibility to switch between the 2 display modes is attractive. I have, however, no idea if it can be achieved without too much changing. I'm very happy to have found an opensource alternative for the closed source commercial score applications which are in my opinion much too bloated, force you to pay every year for a new version, whose output cannot be read by older versions and still are defect in certain areas. Joep ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ Mscore-developer mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/mscore-developer |
||||||||||||||||
| Free Embeddable Forum Powered by Nabble | Help |
