Re: [linux-audio-dev] Please test my MidiSport firmware loader
Fernando Pablo Lopez-Lezcano wrote: I've created a package which extracts the firmware for MidiSport devices from the Windows driver files and installs the hotplug script to download the firmware. I tested it with an Oxigen8 and a Midisport 2x2. Do you happen to know if the Midiman Quattro midi interface could use this method as well? The Quattro doesn't need a firmware download. The MIDI port should already work (since 0.9.0rc4). Regards, Clemens
Re: [linux-audio-dev] LADSPA output controller?
On Tue, 12 Nov 2002, Mario Lang wrote: So I'd need to connect a audio/controller output to a controller input of another LADSPA plugin. Do ladspa hosts like ecasound support this? Or am I taking a completely wrong route here and it should be done differently? A bit complicated, but possible: ecasound -b:128 -f:16,2,44100 \ -a:generator -i null -o null -el:analogueOsc,1,5,0.5,0.5 -eS:1 \ -a:target -i foo.wav -o alsa -el:pitchScale,1.0 -ksv:1,0.5,2,1,1 -c - analogueOsc generates audio data (5Hz sine wave, warmth=0.5, instability=0.5) to the otherwise silent 'generator' chain - -eS:1 stores the passing audio data to an audio stamp (ie. allows other parts of the network to access the audio data it sees) - chain 'target' reads from foo.wav, applies the pitchScale LADSPA plugin and writes the processed data to the default ALSA pcm output - -ksv converts the audio data from stamp 1 (-eS:1, ie. the analogueOsc output) into control data, scales the value to range [0.5,2.0], and uses the resulting value to control the pitchScale coefficient - the audio-control conversion is done by calculating RMS-volume for each 128 (-b:128) sample block which is then used to update the LADSPA plugin parameter value Of course, it's possible to use any audio input source (files, real-time inputs, LADSPA plugins, effect presets, etc) in the 'generator' chain. PS Ecasound has had this functionality since 1.9dev1 (Feb/2001), so for once (!) you don't have to get the latest CVS version to try this out. ;) -- http://www.eca.cx Audio software for Linux!
Re: [linux-audio-dev] Please test my MidiSport firmware loader
Good hack, Clemens! I've created a package which extracts the firmware for MidiSport devices from the Windows driver files and installs the hotplug script to download the firmware. You can get it at http://www.informatik.uni-halle.de/~ladischc/midisport_linux_firmware.html . There are some differences to Lars Doelle's GPL firmware: - it supports MidiSport 4x4/8x8/Keystation/Oxygen - no configuration file editing, just 'make install' - it requires ALSA because the Midiman firmware doesn't conform to the USB MIDI specification I don't have a MidiSport device, so this is completely untested. As Fernando said, it works. I have a Midisport2x2, but I don't need the Midiman's firmware, because my Midisport2x2 works very well with ezusbmidi firmware by Lars Doelle, but this can be useful for 4x4 and 8x8 owners... while there is not a better GPL solution. BTW, the latest midisport GPL firmwares and sources are available at linux-hotplug project CVS repository: http://sourceforge.net/cvs/?group_id=17679 (modulename firmware) Regards, Pedro -- ALSA Library Bindings for Pascal http://alsapas.alturl.com
Re: [linux-audio-dev] Please test my MidiSport firmware loader
I've created a package which extracts the firmware for MidiSport devices from the Windows driver files and installs the hotplug script to download the firmware. You can get it at http://www.informatik.uni-halle.de/~ladischc/midisport_linux_firmware.html. There are some differences to Lars Doelle's GPL firmware: - it supports MidiSport 4x4/8x8/Keystation/Oxygen - no configuration file editing, just 'make install' - it requires ALSA because the Midiman firmware doesn't conform to the USB MIDI specification I don't have a MidiSport device, so this is completely untested. GREAT!!! It works! Just tried it with current alsa cvs and the firmware loads and alsa likes it (well, almost, I still have problems with sequencer playback from muse, I have to try rebuilding muse from scratch). Well, I think it was just stale preferences in Muse that were causing the errors. I started activating all the tracing options in Muse, got lots of printouts and at some point I did a Save Preferences and after that it was working fine, both input and output. Hmmm, I thought that at some point I did erase all the .files related to Muse, maybe I missed one? Anyway, it is working now... -- Fernando
