Hello, you all!
I'm having some trouble trying to use MIDI with my external keyboard
(Yamaha PSR 620, well, not a big kb, but it's what I have for now...)
The system sudenly freezes when I try to start or stop a song in a
sequencer software. That happend with Muse and with Rosegarden, so I
think that is not a software problem. I have an Asus motherboard,
especifically an A7N8X-X, with the nForce2 chipset and embedded AC97
for audio. I am using the intel8x0 module and MIDI is working, at
least for some time. The motherboard didn't come with the (in)famous
joystick port, so I bought a homemade connector to put in the back of
my box. It is working relatively well and I don't know if this is the
guilt or not...
I searched the net for this behaviour but didn't have much luck. Has
anyone experienced this kind of problem? I mean, is there anyone who
uses MIDI with the nForce2 successfully? It is freezing constantly in
my system and the only way to go on is to reset the computer. I think
that the the one to blame is the chipset but would like to hear some
advices and experiences from others owners of this hardware.
Thanks in advance and best my reagards.
--
-------------------------------------------
Denis A. Altoe Falqueto
-------------------------------------------
Hi All:
As I read it, the low latency kernel patch(es) only apply to kernel 2.4,
and with kernel 2.6 the only option for
improving latency is kernel pre-emption.
Have I got this much right?
If so, is it better to use a patched 2.4 kernel than a 2.6 kernel with
pre-emption?
TIA, Mick
--
Hello linux-audio-users
I'm not using (unfortunately) any Linuz now but
I'm planning to install Fedora. But we are close to the scheduled
release of F5. As I am total novice in those, here are my questions:
Is it nescessary to blow up everything when upgrading Fedora versions?
Do I need to install configure everything again?
-----
Best regards,
Mehmet Okonsar
mailto:okonsar@gmail.com
This card has NO ALSA support because Yamaha keeps it a closed affair and
Yamaha is barely supporting Windows. The card is old so why go any further?
I use the predecessor, a sw60xg. This is simply a MIDI sound generator and has
great advantage in using no IRQ, no DMA, nada--a port address: set the DIPs,
configure the driver and make music. Before Yamaha had W2K drivers for this
card, they suggested running it through the ubiquitous mpu401 driver. Voile,
and this works in Linux!
Has anyone tried running the MIDI of the sw1000xg this way? Playback?
Recording? (There are commands that can be sent to initialize the card but
getting to its audio is another matter.) If I can make full use of the MIDI
under Linux as well as Windows, I might take up someones' offer I cannot
refuse :-)
Hi!
I want to write DVD sutable for playing back with general DVD-player. Resulted DVD must
has Audio tracks at 44.1/16 PCM stereo format (without any compression), and must/may not
have any video info at all (almost all disk space must be used for audio streams). Tracks
must be separated to navigate to them with remote control.
Has anybody hints how to do this job? And, more common, is it possible?
Andrew
Or a journey into bad microphone business and inprecise
timing :)
http://ccmixter.org/media/files/thorwil/3768http://ccmixter.org/people/thorwil/thorwil_-_Troete_(a_mic_bottle_and_me).o…
A cheap dynamic mic, a water bottle. Whistling. Processing
it with the versatile Om. All recorded and arranged with the
capable MusE. Samples cut and in cases mistreated with the
exiting Sweep. End result piped through the marvelous Jamin.
No drugs or animals used.
I'm currently uploading a zip containing the single loops
(ogg) and the MusE, Om, Jamin files.
BTW, could someone make it possible to flac encode
32bit float wavs? I have no clue on that. Just thinking
it would be better for exchange (not via ccmixter, though,
given their filesize limit :)
I would love to see additions or alterations to this.
All comments welcomed.
Best,
Thorsten Wilms
Hi all,
I'd like to take a straw poll on how many Linux Audio users make use of
external MIDI devices. As a straight hands-up would be unlikely to yield
useful results, perhaps people could suggest what percentage of
external-MIDI-users exist within the LAU group. (As of Jan 06, say)
Additional comments re: problems encountered whilst configuring MIDI are
welcomed, but please start a new thread if you want to make bugreports.
Thankyou, It would be useful for me to be able to formulate some kind of
definitive answer on this subject.
tim hall
http://glastonburymusic.org.uk/tim
Hello all,
Sorry for the recent barrage of comments and questions from me. I
appreciate all of the answers I have received thus far.
One more question - regarding the relatively new CME UF7 USB/MIDI
controllers, are they compatible with ALSA? By compatible I mean
that, via USB, they are properly recognized and can be used
immediately, much like the M-Audio stuff. I've done Google searches
for CME + ALSA, and can't seem to find any information.
Thank you,
Josh
--
Josh Lawrence
http://www.hardbop200.com
Greetings Mark and all,
> From: Mark Knecht <markknecht(a)gmail.com>
>
> BTW - I tried Chuck for the first time this morning, just using a few
> examples to see how it worked. It built cleanly for Linux-Jack and
> came up working right away with no xruns. Since I'm not a programmer
> I'll probably never make effective use of it, unless someone builds
> some synths, but it seems like a very interesting way to try to build
> real synths such as those in Reaktor. I'm excited, but also worried
> I'll never make it useful. Anyway, for those programming types out
> there, if I can make sounds in 10 minutes I think you could make music
> in 30!
This semester we taught the PLOrk (Princeton Laptop Orchestra),
using ChucK and Max/MSP, to 14 freshman undergraduates, most
of whom had no prior programming experience:
http://plork.cs.princeton.edu/
By the 2nd week, they were creating programs synthesizing
generative drum machines and performing them on-the-fly:
http://plork.cs.princeton.edu/listen/machines/
Long before the end of the semester, the plorkists were all very
comfortable writing code, controlling physical models, using various
controllers (keyboards, triggerfingers, wacom tablets, light/pressure
sensors), building instruments out of processed vocal and acoustic
instrumental sounds, and networking and synchronizing multiple
machines together.
It is our hope that ChucK can be useful to researchers,
composers, and performers alike, providing different
paradigms for seasoned programmers and yet (hopefully)
clear and well-defined syntax/semantic to make it fun and
interesting for inexperienced coders. It seems so far that
as long as one is really interested in sound synthesis and
creating music, learning and using ChucK well is pretty
straightforward, the command line-friendly way of working
seems to present steeper learning curves than the language
itself. However, if one is already using Linux, the command
line obviously isn't an obstacle.
In the case of PLOrk, ChucK pretty quickly became a
second nature to the users. Programming should be as
simple and clear as possible, the only complexity should be
that which lies in the creativity and invention of the
programmer. It's unlikely that this goal is being totally
achieved in ChucK, but it is certainly something we are
striving towards.
Best,
Ge!