Linux-audio-user September 2007

linux-audio-user@lists.linuxaudio.org

130 participants
158 discussions

Start a nNew thread

[LAU] could you remove me of the list

by enrico berg

18 years, 5 months

Re: [LAU] An atrocity committed with PD (MIDI Spec) + (XG)

by david

thomas fisher wrote: > On Friday 31 August 2007 01:09:07 david wrote: >> Steve McConville wrote: >>>> I am curious - has there been any move to modernize the MIDI >>>> connectivity standards to include USB or Ethernet? >>> There has been - there is a midi over usb standard. >>> >>> Midi is a poor starting point for modernisation not just beacause of >>> the pragmatic compromises mentioned above but also because it is >>> wholly unlayered (the spec covers everything from the physical up to >>> the presentational layer), >> That could be separated fairly easily, I'd think. >> >>> and has it's expansion room squeezed into >>> the SysEx ghetto. >> That's a big problem. >> >>> Midi over ethernet would be even less pleasant, and >>> less logical, than doing RS-232 over ethernet. >> Only reason I mentioned Ethernet is that there are analog musical >> instruments around already that can transmit their audio via Ethernet >> (instead of analog audio cables). >> >>> OSC has fixed these problems and should have been built into >>> everything since the mid-90s but so many people have invested time in >>> learning MIDI that they wouldn't countenance working with anything >>> else. It looks like RESTful web services may eventually replace both, >>> however. >> I suspect that MIDI won't be budged. It is a standard in the music >> world, and I doubt that many musicians care about it's limitations. They >> may not even be aware of them. MIDI certainly keeps time in a lot finer >> increments than I'm able to play - that's why sequencer programs have >> quantization functions! > > How does the " XG " extension play into this? How proprietary is it? I don't know - and each week I play a Yahama PSR-740 keyboard with Yamaha's XG. I've recorded some MIDIs using it, and they open just fine in Rosegarden and play in fluidsynth. Or maybe you're talking about something else? -- David gnome(a)hawaii.rr.com authenticity, honesty, community

18 years, 5 months

[LAU] qjackctl not starting...

by Preston C.

It used to start. I went into setting did some things and now it won't start. I think I changed everything back to default. This is the error message I get: 16:46:41.732 Patchbay deactivated. 16:46:41.773 Statistics reset. JACK tmpdir identified as [/dev/shm] 16:46:41.865 MIDI connection graph change. 16:46:42.061 MIDI connection change. 16:46:42.064 MIDI connection graph change. 16:46:49.479 Startup script... 16:46:49.479 artsshell -q terminate JACK tmpdir identified as [/dev/shm] 16:46:50.257 Startup script terminated with exit status=256. 16:46:50.258 JACK is starting... 16:46:50.260 jackd -R -dalsa -dhw:0 -r48000 -p1024 -n3 16:46:50.263 JACK was started with PID=3379 (0xd33). jackd 0.103.0 Copyright 2001-2005 Paul Davis and others. jackd comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK compiled with System V SHM support. loading driver .. SSE2 detected apparent rate = 48000 creating alsa driver ... hw:0|hw:0|1024|3|48000|0|0|nomon|swmeter|-|32bit control device hw:0 configuring for 48000Hz, period = 1024 frames, buffer = 3 periods ALSA: final selected sample format for capture: 16bit little-endian ALSA: got smaller periods 2 than 3 for capture ALSA: cannot configure capture channel cannot load driver module alsa no message buffer overruns 16:46:50.468 JACK was stopped successfully. 16:46:50.471 Post-shutdown script... 16:46:50.473 killall jackd jackd: no process killed 16:46:50.702 Post-shutdown script terminated with exit status=256. 16:46:52.289 Could not connect to JACK server as client. Please check the messages window for more info. JACK tmpdir identified as [/dev/shm]

18 years, 5 months

[LAU] qjackctl and Qsampler

by Preston Callison

I thought that I had it worked out, but I don't. I can start qjackctl and Qsampler, but I cannot get any sound to be produced. I am completely new to this and do not know what to connect in the connections setting in qjackctl. Also, I don't know if I have Qsampler setup right. In Qsampler, I go to edit and then add new channel. Then I select the GIG engine and open the 32 meg piano. My midi input is ALSA, port 0, channel 1. Device is midi ALSA device 0. Audio output type is Jack, device is Audio Jack device 2, in the sampler channel is audio 0 and audio 1, and in the device channel is audio Jack 0 and audio Jack 1. I then click ok and this is the message that Qsampler gives me: ----------------------------------------------------------------------------------------------- LSCPServer: Client connection established on socket:4. LSCPServer: Client connection established on socket:5. 21:11:53.641 New Channel setup... 21:12:03.000 Channel 0 added. 21:12:03.018 Channel 0 Audio driver: JACK. 21:12:03.041 Channel 0 MIDI driver: ALSA. 21:12:03.043 Channel 0 MIDI port: 0. 21:12:03.045 Channel 0 MIDI channel: 0. 21:12:03.287 Channel 0 Engine: GIG. 21:12:03.307 Channel 0 Instrument: "/home/Preston/Desktop/gig files/S1000 CDRom SteinwayD/PARTITION A/VOLUME 001/32 MEG PIANO.gig" (0). JACK tmpdir identified as [/dev/shm] SSE2 detected Starting disk thread...OK Loading gig file '/home/Preston/Desktop/gig files/S1000 CDRom SteinwayD/PARTITION A/VOLUME 001/32 MEG PIANO.gig'...OK Loading gig instrument...OK Caching initial samples... OK ------------------------------------------------------------------------------------------------- In qjackctl, I have these options in the connections panel. In the audio tab as readable clients alsa_pcm and LinuxSampler. In the audio tab as writable there are alsa_pcm (playback_1 and playback_2). In the midi tab as readable clients there are midi through and Audigy 2 Ex [1005]. In the midi tab as writable clients there are midi through, Audigy 2 Ex [1005], EMU 10K1 wavetable, and Linux Sampler. Any help is much appreciated. All I want to do as of now is get sound from Linux Sampler. Best Regards, Preston

18 years, 5 months

[LAU] getting started with qjackctl and Linux Sampler...

by Preston Callison

I have used midi on Windows with Gigastudio and understand how to get it working. I would like to use my .gig files on Linux because I am afraid of another crash due to Gigastudio and I cannot afford to due another Windows install and then reinstall all of my software. The questions that I have is how to get qjackctl to get the midi signal from my TMK-88 midi controller and route them to Linux Sampler. A couple of questions are: -How can you tell if qjackctl is receiving a midi signal from your keyboard? -Is there anyway to tell if qjackctl is sending an output signal? -How do I setup qjackctl and run it out to Linux Sampler? I have a Sound Blaster Audigy 2 Ex Platinum sound card. I don't understand how to use qjackctl or Linux Sampler? Thanks.

18 years, 5 months

[LAU] Re: getting started with qjackctl and Linux Sampler...

by Preston Callison

On 8/31/07, Preston Callison <gprestonc(a)gmail.com> wrote: > I thought that I had it worked out, but I don't. I can start qjackctl > and Qsampler, but I cannot get any sound to be produced. I am > completely new to this and do not know what to connect in the > connections setting in qjackctl. Also, I don't know if I have Qsampler > setup right. > > In Qsampler, I go to edit and then add new channel. Then I select the > GIG engine and open the 32 meg piano. My midi input is ALSA, port 0, > channel 1. Device is midi ALSA device 0. Audio output type is Jack, > device is Audio Jack device 2, in the sampler channel is audio 0 and > audio 1, and in the device channel is audio Jack 0 and audio Jack 1. I > then click ok and this is the message that Qsampler gives me: > ----------------------------------------------------------------------------------------------- > LSCPServer: Client connection established on socket:4. > LSCPServer: Client connection established on socket:5. > 21:11:53.641 New Channel setup... > 21:12:03.000 Channel 0 added. > 21:12:03.018 Channel 0 Audio driver: JACK. > 21:12:03.041 Channel 0 MIDI driver: ALSA. > 21:12:03.043 Channel 0 MIDI port: 0. > 21:12:03.045 Channel 0 MIDI channel: 0. > 21:12:03.287 Channel 0 Engine: GIG. > 21:12:03.307 Channel 0 Instrument: "/home/Preston/Desktop/gig > files/S1000 CDRom SteinwayD/PARTITION A/VOLUME 001/32 MEG PIANO.gig" > (0). > JACK tmpdir identified as [/dev/shm] > SSE2 detected > Starting disk thread...OK > Loading gig file '/home/Preston/Desktop/gig files/S1000 CDRom > SteinwayD/PARTITION A/VOLUME 001/32 MEG PIANO.gig'...OK > Loading gig instrument...OK > Caching initial samples... > OK > ------------------------------------------------------------------------------------------------- > > In qjackctl, I have these options in the connections panel. In the audio tab as readable clients alsa_pcm and LinuxSampler. In the audio tab as writable there are alsa_pcm (playback_1 and playback_2). In the midi tab as readable clients there are midi through and Audigy 2 Ex [1005]. In the midi tab as writable clients there are midi through, Audigy 2 Ex [1005], EMU 10K1 wavetable, and Linux Sampler. > > Any help is much appreciated. All I want to do as of now is get sound > from Linux Sampler. > > Best Regards, > Preston > >

18 years, 5 months

[LAU] Thanks for pointing me to PD

by Ken Restivo

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I had avoided PD for a long time because I don't like clicky-draggy things, and prefer working with text. Bah, what was I thinking??! PD is tight! Fast, simple, and it works. I love it. Many thanks to whomever pointed me at PD. I had been banging my head against the wall, trying to figure out how to build MIDI-controlled instruments in SC/ChucK/Csound-- and it turned out to be trivially easy in PD. There was some sample code, I modified it, and here we are: http://www.restivo.org/blog/podpress_trac/web/184/0/phoneme-dance.ogg (description here: http://www.restivo.org/blog/archives/184) I also had avoided dealing with seq24 for a long time, but now after having used it for a few tunes, I like it a lot. (Hydrogen, PHASEX, AZR3, and fluidsynth were also used on this tune) - -ken -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG0UJMe8HF+6xeOIcRApzlAJ0UYFfdgjf9dYW4sTjHo4ZbTotI7wCgsVB5 fnnFsJbr9JB4RmDqXQTf7LI= =TNYn -----END PGP SIGNATURE-----

18 years, 5 months

[LAU] EMU 0404 driver?

by Hein Zelle

Hello list, This might be more suitable for an alsa mailinglist, but I'll try here anyway. I've searched the alsa sound card matrix for emu 0404 drivers, and found nothing there. Anyone here with experience on getting this thing to work in linux? It's a PCI card, in this case. I've found several posts on an ubuntu forum regarding a driver for two other emu cards (in development), but no conclusive things about a driver for the 0404. Kind regards, Hein Zelle >-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-< Hein Zelle hein(a)icce.rug.nl http://www.icce.rug.nl/~hein >-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-<

18 years, 5 months

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Linux-audio-user September 2007