Hello,
Is there a simple (i.e. simpler than getting the pollfd and using them)
to force snd_seq_event_input() in blocking mode to return, so the the
calling thread can close the handle and cleanup ?
Neither snd_seq_close() nor snd_seq_nonblock() seem to have any effect.
--
FA
Hi all,
Om is a modular synthesizer that runs under Jack and uses LADSPA and/or
DSSI plugins for processing. The engine is an independant process
entirely controlled via OSC, is polyphonic, and supports subpatches.
More information, screenshots, and downloads available at
http://www.nongnu.org/om-synth/.
Please report bugs, feedback, feature requests, etc. on the Savannah
bugs page; or feel free to email me privately.
Enjoy,
-DR-
Hi, I'm extremely new to audio programming. I have a million questions, but the one burning my brain now is how do I
get a program written with the qt widget library to display an audio waveform. Also, any links to good documentation for
audio programming would be good.
Thanks
Mike Fisher
Hi,
Gungirl Sequencer Version 0.3.0 is ready,
and it comes with an impressive set of new
features:
- Automations, Fade-in, Fade-Out
- Unlimited Undo
- Sample Stretching and Trimming
- Unlimited Number of Tracks
- Zip-Packages of Songs
- Looping
About ggseq:
It's a simple Audio-Sequencer designed for arranging
small Sound-Loops, as available on CD from various
Producers. It's not a general Purpose Sound Editor, it
has no support for large audiofiles. It doesn't do
MIDI.
It's a fun toy, for people new to electronic
music-making.
It's available from the Gungirl Sequencer Homepage at:
http://ggseq.sourceforge.net/
There is a source tarball that requires the following
dependencies:
- wxGTK 2.4.x or later
- libsndfile 1.0.0 or later
- libsamplerate 0.0.15 or later
There is a statically linked binary release that should
run on most recent Version of the GNU/Linux OS,
provided GTK+ is installed.
And there is a win32 Installer.
Have fun
-Richard Spindler <richard.spindler AT gmail.com>
In case this is news, I'm reporting a total failure of the snd-hdsp
driver under the latest Fedora released kernel, 2.6.11-1.14_FC3spksmp,
both with the x86_64 and i686 kernels.
As a result, I've reverted to 2.6.10-1.770_FC3spksmp.i686.
I'm using 1.0.9RC2 of alsa driver, lib, utils, and tools. Firmware is
1.0.8 -- all most current releases.
It seems as if no symbol in the driver is recognized. Here's the output
from attempting to start alsa, and the relevant lines in dmesg:
service alsasound start
Starting sound driver: snd-hdsp FATAL: Error inserting snd_pcm
(/lib/modules/2.6.11-1.14_FC3spksmp/kernel/sound/core/snd-pcm.ko): Unknown
symbol in module, or unknown parameter (see dmesg)
WARNING: Error running install command for snd_pcm
FATAL: Error inserting snd_hdsp
(/lib/modules/2.6.11-1.14_FC3spksmp/kernel/sound/pci/rme9652/snd-hdsp.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
done
snd_pcm: disagrees about version of symbol snd_info_register
snd_pcm: Unknown symbol snd_info_register
snd_pcm: disagrees about version of symbol snd_info_create_module_entry
snd_pcm: Unknown symbol snd_info_create_module_entry
snd_pcm: disagrees about version of symbol snd_timer_notify
snd_pcm: Unknown symbol snd_timer_notify
snd_pcm: disagrees about version of symbol snd_timer_interrupt
snd_pcm: Unknown symbol snd_timer_interrupt
snd_pcm: disagrees about version of symbol snd_info_free_entry
snd_pcm: Unknown symbol snd_info_free_entry
snd_pcm: disagrees about version of symbol snd_ctl_register_ioctl
snd_pcm: Unknown symbol snd_ctl_register_ioctl
snd_pcm: disagrees about version of symbol snd_card_file_add
snd_pcm: Unknown symbol snd_card_file_add
snd_pcm: disagrees about version of symbol snd_unregister_device
snd_pcm: Unknown symbol snd_unregister_device
snd_pcm: disagrees about version of symbol snd_timer_new
snd_pcm: Unknown symbol snd_timer_new
snd_pcm: disagrees about version of symbol snd_device_new
snd_pcm: Unknown symbol snd_device_new
snd_pcm: disagrees about version of symbol snd_ctl_unregister_ioctl
snd_pcm: Unknown symbol snd_ctl_unregister_ioctl
snd_pcm: disagrees about version of symbol snd_info_create_card_entry
snd_pcm: Unknown symbol snd_info_create_card_entry
snd_pcm: disagrees about version of symbol snd_power_wait
snd_pcm: Unknown symbol snd_power_wait
snd_pcm: disagrees about version of symbol snd_device_free
snd_pcm: Unknown symbol snd_device_free
snd_pcm: disagrees about version of symbol snd_card_file_remove
snd_pcm: Unknown symbol snd_card_file_remove
snd_pcm: disagrees about version of symbol snd_info_unregister
snd_pcm: Unknown symbol snd_info_unregister
snd_pcm: disagrees about version of symbol snd_device_register
snd_pcm: Unknown symbol snd_device_register
snd_pcm: disagrees about version of symbol snd_register_device
snd_pcm: Unknown symbol snd_register_device
snd_hdsp: Unknown symbol snd_pcm_new
snd_hdsp: Unknown symbol snd_interval_refine
snd_hdsp: Unknown symbol snd_pcm_set_sync
snd_hdsp: Unknown symbol snd_pcm_hw_rule_add
snd_hdsp: Unknown symbol snd_interval_list
snd_hdsp: Unknown symbol snd_pcm_lib_ioctl
snd_hdsp: Unknown symbol snd_pcm_set_ops
snd_hdsp: Unknown symbol snd_pcm_hw_constraint_list
snd_hdsp: Unknown symbol _snd_pcm_hw_param_setempty
snd_hdsp: Unknown symbol snd_pcm_hw_constraint_msbits
snd_hdsp: Unknown symbol snd_pcm_period_elapsed
[3 unrelated httpd lines]
snd_pcm: disagrees about version of symbol snd_info_register
snd_pcm: Unknown symbol snd_info_register
snd_pcm: disagrees about version of symbol snd_info_create_module_entry
snd_pcm: Unknown symbol snd_info_create_module_entry
snd_pcm: disagrees about version of symbol snd_timer_notify
snd_pcm: Unknown symbol snd_timer_notify
snd_pcm: disagrees about version of symbol snd_timer_interrupt
snd_pcm: Unknown symbol snd_timer_interrupt
snd_pcm: disagrees about version of symbol snd_info_free_entry
snd_pcm: Unknown symbol snd_info_free_entry
snd_pcm: disagrees about version of symbol snd_ctl_register_ioctl
snd_pcm: Unknown symbol snd_ctl_register_ioctl
snd_pcm: disagrees about version of symbol snd_card_file_add
snd_pcm: Unknown symbol snd_card_file_add
snd_pcm: disagrees about version of symbol snd_unregister_device
snd_pcm: Unknown symbol snd_unregister_device
snd_pcm: disagrees about version of symbol snd_timer_new
snd_pcm: Unknown symbol snd_timer_new
snd_pcm: disagrees about version of symbol snd_device_new
snd_pcm: Unknown symbol snd_device_new
snd_pcm: disagrees about version of symbol snd_ctl_unregister_ioctl
snd_pcm: Unknown symbol snd_ctl_unregister_ioctl
snd_pcm: disagrees about version of symbol snd_info_create_card_entry
snd_pcm: Unknown symbol snd_info_create_card_entry
snd_pcm: disagrees about version of symbol snd_power_wait
snd_pcm: Unknown symbol snd_power_wait
snd_pcm: disagrees about version of symbol snd_device_free
snd_pcm: Unknown symbol snd_device_free
snd_pcm: disagrees about version of symbol snd_card_file_remove
snd_pcm: Unknown symbol snd_card_file_remove
snd_pcm: disagrees about version of symbol snd_info_unregister
snd_pcm: Unknown symbol snd_info_unregister
snd_pcm: disagrees about version of symbol snd_device_register
snd_pcm: Unknown symbol snd_device_register
snd_pcm: disagrees about version of symbol snd_register_device
snd_pcm: Unknown symbol snd_register_device
snd_hdsp: Unknown symbol snd_pcm_new
snd_hdsp: Unknown symbol snd_interval_refine
snd_hdsp: Unknown symbol snd_pcm_set_sync
snd_hdsp: Unknown symbol snd_pcm_hw_rule_add
snd_hdsp: Unknown symbol snd_interval_list
snd_hdsp: Unknown symbol snd_pcm_lib_ioctl
snd_hdsp: Unknown symbol snd_pcm_set_ops
snd_hdsp: Unknown symbol snd_pcm_hw_constraint_list
snd_hdsp: Unknown symbol _snd_pcm_hw_param_setempty
snd_hdsp: Unknown symbol snd_pcm_hw_constraint_msbits
snd_hdsp: Unknown symbol snd_pcm_period_elapsed
snd_pcm: disagrees about version of symbol snd_info_register
snd_pcm: Unknown symbol snd_info_register
snd_pcm: disagrees about version of symbol snd_info_create_module_entry
snd_pcm: Unknown symbol snd_info_create_module_entry
snd_pcm: disagrees about version of symbol snd_timer_notify
snd_pcm: Unknown symbol snd_timer_notify
snd_pcm: disagrees about version of symbol snd_timer_interrupt
snd_pcm: Unknown symbol snd_timer_interrupt
snd_pcm: disagrees about version of symbol snd_info_free_entry
snd_pcm: Unknown symbol snd_info_free_entry
snd_pcm: disagrees about version of symbol snd_ctl_register_ioctl
snd_pcm: Unknown symbol snd_ctl_register_ioctl
snd_pcm: disagrees about version of symbol snd_card_file_add
snd_pcm: Unknown symbol snd_card_file_add
snd_pcm: disagrees about version of symbol snd_unregister_device
snd_pcm: Unknown symbol snd_unregister_device
snd_pcm: disagrees about version of symbol snd_timer_new
snd_pcm: Unknown symbol snd_timer_new
snd_pcm: disagrees about version of symbol snd_device_new
snd_pcm: Unknown symbol snd_device_new
snd_pcm: disagrees about version of symbol snd_ctl_unregister_ioctl
snd_pcm: Unknown symbol snd_ctl_unregister_ioctl
snd_pcm: disagrees about version of symbol snd_info_create_card_entry
snd_pcm: Unknown symbol snd_info_create_card_entry
snd_pcm: disagrees about version of symbol snd_power_wait
snd_pcm: Unknown symbol snd_power_wait
snd_pcm: disagrees about version of symbol snd_device_free
snd_pcm: Unknown symbol snd_device_free
snd_pcm: disagrees about version of symbol snd_card_file_remove
snd_pcm: Unknown symbol snd_card_file_remove
snd_pcm: disagrees about version of symbol snd_info_unregister
snd_pcm: Unknown symbol snd_info_unregister
snd_pcm: disagrees about version of symbol snd_device_register
snd_pcm: Unknown symbol snd_device_register
snd_pcm: disagrees about version of symbol snd_register_device
snd_pcm: Unknown symbol snd_register_device
snd_hdsp: Unknown symbol snd_pcm_new
snd_hdsp: Unknown symbol snd_interval_refine
snd_hdsp: Unknown symbol snd_pcm_set_sync
snd_hdsp: Unknown symbol snd_pcm_hw_rule_add
snd_hdsp: Unknown symbol snd_interval_list
snd_hdsp: Unknown symbol snd_pcm_lib_ioctl
snd_hdsp: Unknown symbol snd_pcm_set_ops
snd_hdsp: Unknown symbol snd_pcm_hw_constraint_list
snd_hdsp: Unknown symbol _snd_pcm_hw_param_setempty
snd_hdsp: Unknown symbol snd_pcm_hw_constraint_msbits
snd_hdsp: Unknown symbol snd_pcm_period_elapsed
snd_pcm: disagrees about version of symbol snd_info_register
snd_pcm: Unknown symbol snd_info_register
snd_pcm: disagrees about version of symbol snd_info_create_module_entry
snd_pcm: Unknown symbol snd_info_create_module_entry
snd_pcm: disagrees about version of symbol snd_timer_notify
snd_pcm: Unknown symbol snd_timer_notify
snd_pcm: disagrees about version of symbol snd_timer_interrupt
snd_pcm: Unknown symbol snd_timer_interrupt
snd_pcm: disagrees about version of symbol snd_info_free_entry
snd_pcm: Unknown symbol snd_info_free_entry
snd_pcm: disagrees about version of symbol snd_ctl_register_ioctl
snd_pcm: Unknown symbol snd_ctl_register_ioctl
snd_pcm: disagrees about version of symbol snd_card_file_add
snd_pcm: Unknown symbol snd_card_file_add
snd_pcm: disagrees about version of symbol snd_unregister_device
snd_pcm: Unknown symbol snd_unregister_device
snd_pcm: disagrees about version of symbol snd_timer_new
snd_pcm: Unknown symbol snd_timer_new
snd_pcm: disagrees about version of symbol snd_device_new
snd_pcm: Unknown symbol snd_device_new
snd_pcm: disagrees about version of symbol snd_ctl_unregister_ioctl
snd_pcm: Unknown symbol snd_ctl_unregister_ioctl
snd_pcm: disagrees about version of symbol snd_info_create_card_entry
snd_pcm: Unknown symbol snd_info_create_card_entry
snd_pcm: disagrees about version of symbol snd_power_wait
snd_pcm: Unknown symbol snd_power_wait
snd_pcm: disagrees about version of symbol snd_device_free
snd_pcm: Unknown symbol snd_device_free
snd_pcm: disagrees about version of symbol snd_card_file_remove
snd_pcm: Unknown symbol snd_card_file_remove
snd_pcm: disagrees about version of symbol snd_info_unregister
snd_pcm: Unknown symbol snd_info_unregister
snd_pcm: disagrees about version of symbol snd_device_register
snd_pcm: Unknown symbol snd_device_register
snd_pcm: disagrees about version of symbol snd_register_device
snd_pcm: Unknown symbol snd_register_device
snd_hdsp: Unknown symbol snd_pcm_new
snd_hdsp: Unknown symbol snd_interval_refine
snd_hdsp: Unknown symbol snd_pcm_set_sync
snd_hdsp: Unknown symbol snd_pcm_hw_rule_add
snd_hdsp: Unknown symbol snd_interval_list
snd_hdsp: Unknown symbol snd_pcm_lib_ioctl
snd_hdsp: Unknown symbol snd_pcm_set_ops
snd_hdsp: Unknown symbol snd_pcm_hw_constraint_list
snd_hdsp: Unknown symbol _snd_pcm_hw_param_setempty
snd_hdsp: Unknown symbol snd_pcm_hw_constraint_msbits
snd_hdsp: Unknown symbol snd_pcm_period_elapsed
--
Janina Sajka Phone: +1.202.494.7040
Partner, Capital Accessibility LLC http://www.CapitalAccessibility.Com
Chair, Accessibility Workgroup Free Standards Group (FSG)
janina(a)freestandards.org http://a11y.org
If Linux can't solve your computing problem, you need a different problem.
Hello.
I started working on a Nord Modular to PD converter.
ftp://ftp.funet.fi/pub/sci/audio/devel/nordmodular/
NM users have patched thousands of free instruments
(http://nordsynth.zevv.nl). It would be nice to be able to
use the user-made instruments elsewhere.
I choosed PD but we should make the converter general enough
so that converters to other modular systems can be written.
I can work on them as well.
Check for "http://nmedit.sourceforge.net" for a NM instrument
file parser. The NM file format is close to PD's own. Anyone
could rewrite the parser standalone in C, Python, etc?
[[ I see no problem in writing the converter. Buying a Nord
Modular does not mean that its users should restrict
their intellectual property to Nord Modular. ]]
Juhana
--
http://music.columbia.edu/mailman/listinfo/linux-graphics-dev
for developers of open source graphics software
Hi Toby and All,
>But from my (limited) experience I see that not only does writing a
>CSound instrument require knowledge of the CSound language and of its
>architecture (that's obvious), but that *incorporating* an existing
>CSound instrument into a new composition requires almost the same
>skills. And those are computer programmer-level skills, not average
>music writer-level ones.
I would say that most computer music people who use sequencers do not write their own instruments either, rather opting for instruments built by someone else and using presets and modification of parameters via GUI. The same is possible in Csound to reuse someone else's instruments and only explore the instrument's qualities via configuration with text. With blue, you can create a GUI for instruments using it's builtin UI Builder (http://csounds.com/stevenyi/blue/blueDocs/html/blueSynthBuilder.html). Also, you can trade instruments--UI, instrument code, and presets--via the builtin BlueShare community interface. (i.e. explore the instruments on the server, download directly to your instrument library and start working). So, with the BlueSynthBuilder instruments and the PianoRoll, you can really get to working with Csound with a minimal amount of Csound knowledge.
>Let's make a comparison, although a simple, maybe unworthy one: Reasonâ„¢.
>Novice users don't *need* to know how the Malström* works to be able to
>1. load a patch 2. give it MIDI input and 3. start playing. They only
>need that kind of skill if they want to make their own patches or modify
>existing ones. (*: a small piece of soft-synth found in Reasonâ„¢)
>
>Granted, the power of any synth lies in customization, but IMHO part of
>its *usability* lies in being able to play it *without* knowing how to
>program it. That's what presets are for anyways!
>
>I'm under the impression that CSound fails right there.
I wouldn't quite agree. As mentioned above, one can reuse others' instruments with Csound and do the same thing as you mention, not concerning themselves with programming the instrument but exploring the parameters of the instrumet. With Csound alone it would be text as the interface versus Maelstrom's GUI interface, with blue there would be not much difference except blue's UI is not realtime.
>An ORC file you say? Most of the instruments I've seen need both and
>ORC and a SCO file to be of any use (problem #1.) Moreover, since you
>need to come up with a single ORC and a single SCO to make CSound render
>your composition, you have to merge the various ORC/SCO file-pairs of
>the instruments you want to use, along with the additional SCO file
>containing the actual notes (problem #2) and AFAIK you need vast
>knowledge of the ORC and SCO syntax to be able to do it (problem #3.)
blue has many features for orchestra management as well as SCO handling and generation via it's SoundObjects that generally alleviates issues as mentioned above with orc/sco file management.
>I could go on, but I think you see my point. (Unless I'm seriously
>misunderstanding how CSound works nowadays, in which case I'll apologize
>to everybody and go read some CSound mailing list archives!)
Well, I wouldn't say you've misunderstood Csound entirely, but just wanted to offer another view of Csound via my program blue in this message that may make Csound appear a bit differently than as you imagine.
steven