So I start jackd and it runs fine for a while. Then ALSA crashes and
triggers an xrun. Jackd continues to do its merry thing - minus the part
about spitting info out to my soundcard...
I've tried multiple usb intefaces. All work fine with other computers. I've
tried multiple version of Ubuntu with various versions of ALSA. Only this
machine is affected. I have 3 other machines that run these interfaces just
fine... So it seems to be a hardware compatibility issue not a software
glitch in one version.
I've tried many boot flags but to no avail. Am at a loss on how to
troubleshoot.
The machine is M4N75TD motherboard with a Phenom II 1055T and the latest
bios flash.
...Rods ;-)
Hey guys,
I'm looking for the "lowest-common-denominator" of audio file formats that
handle BPM info.
Do programs like Ardour / Audacity / Mixxx write BPM info when exporting /
analysing a file?
Cheers, -Harry
Hi All,
I am trying to read data from a usb microphone and using the pretty standard
method of using ioctl's to setup the sampling rate, channels, bits and block
size . This all works so the device is correctly setup. I then use "read" to
read samples from the device which shows up as /dev/dsp1. I get a lot more
samples from this read command in one second of recording than the set
sample rate. E.g. if i set 10Khz on one run i got 269312 samples. Looking at
the raw data it looks like there is a lot of duplication of data? is this
common for the audio input device? if so what kind of encoding is it (e.g
with some specific redundancy built in)?
thanks
farhan
Hi all,
I am working on a system which includes a connexant AD1989A HDA codec
connected to a ATOM processor.
I have four microphones connected to the B and C ports of this codec.
If I change one of the 3 capture gains present in the alsamixer (Capture,
Capture 1 or Capture 3), I can't have any more signal on the B and C ports
It seems to be due to the fact that ALSA breaks (for example for the Capture
gain) the link between the ADC selector 0 and ADC_0 widgets of the codec,
what can be easily seen with codecgraph.
Have you ever had this kind of problem?
Do you know how can I resolve it ?
Many thanks for your asnwers and best regards
Vincent
Could the community please review the attribution so we may continue
with our journey? This attribution appears on the website, github,
README and anywhere else you guys need to see it.
OOM2 is developed from the base code of MusE (Muse Sequencer) written by
the mighty Werner Schweer, and maintained and modified to the present
day, by the current Muse2 maintainer Robert Jonsson and his team.
We not only willingly credit Werner for his code, but add our deepest
respect and admiration as well.
Thanks for all your kind words and support.
P.S. Chris Cannam, the offer stands if you would like me to sign over
all my copyrighted oom code to you. As you explained open source
developers have very little but attribution. Well except those that make
big bucks off it.
--
Christopher Cherrett
ccherrett(a)openoctave.org
http://www.openoctave.org
Deep in the basement of the OpenOctaveProject, the team have been
working hard, to bring OpenOctaveMidi into the modern age. From the
new interface, to the workflow features, OOM2 is the result of a great
deal of hard work, and thought. In our Project journey towards a great
Linux Audio pipeline, OOM2 represents the next important step.
With the help of our platinum sponsor TSI, we were afforded two full
time developers to help with the task of getting to where we are
today. We would like to thank TSI for their continued longterm support
and encouragement.
OOM2 linear Midi and Audio sequencer.
We announce the beta release of the 2nd version of the OpenOctaveMidi
sequencer, known as OOM2. After a change of codebase, a complete
rebuild of the user interface, and the addition of new features and
functions, we're proud to present this version as our initial beta
release.
OOM2 is a linear Midi and Audio sequencer for the Linux operating
system in both 32 and 64bit.
OOM2 uses the following:
* JACK-audio - http://jackaudio.org
* JACK-midi - for midi support
* DSSI - synth plugins
* VST(i) - synth plugins (through DSSI, for the moment. We're
more interested in native linuxplugins, so the DSSI-VST implementation
may be removed.)
* ALSA-midi - for midi support
* QT4.6.0 or later (earlier versions may work, but are not tested)
You can download OOM2 from our github repository at:
git://github.com/ccherrett/oom.git
Use the command:
git clone git://github.com/ccherrett/oom.git
to install the source in an empty directory of your choosing, and
follow the build instructions in the Readme file.
Please note we're adding new commits each day, and more features are
coming very soon, hence the Beta release notice.
We hope you enjoy using OOM2, and should you have anything you'd like
to report, please send an email to:
development(a)openoctave.org
We can also be found on irc at #openoctave (freenode)
Visit www.openoctave.org to find out more!
Alex.
-------- Original Message --------
Subject: Re: [LAU] [LAD] OpenOctaveMidi2 (OOM2) beta release
From: Orcan Ogetbil <oget.fedora(a)gmail.com>
To: Paul Davis <paul(a)linuxaudiosystems.com>
Cc: LAU Mail List <linux-audio-user(a)lists.linuxaudio.org>, Linux Audio
Developers <Linux-audio-dev(a)lists.linuxaudio.org>
Date: 01/27/2011 11:26 AM
> On Thu, Jan 27, 2011 at 11:08 AM, Paul Davis wrote:
>> On Thu, Jan 27, 2011 at 9:39 AM, alex stone wrote:
>>> Deep in the basement of the OpenOctaveProject, the team have been
>>> working hard, to bring OpenOctaveMidi into the modern age. From the
>>> new interface, to the workflow features, OOM2 is the result of a great
>>> deal of hard work, and thought. In our Project journey towards a great
>>> Linux Audio pipeline, OOM2 represents the next important step.
>> I think it would be a little more respectful if you notified this
>> crowd precisely which *existing* codebase you "put a blowtorch to". i
>> already know the answer, but i think it would better to hear it from
>> you guys. altering the indentation and global search-and-replace of
>> the project name does not constitute much of a blowtorch.
>>
> Hi Paul,
>
> Let me shed some light from the opposite side.
>
> I was one of the developers of the "existing codebase" [1]. Actually,
> I joined the project formally about 3 months ago and I believe I made
> a significant contribution in porting it to Qt4. The way I joined to
> the project was traditional: sent a couple useful patches so that
> people can get to know me, and after a couple rounds I got commit
> rights. From my experience with open source projects, this is the way
> things evolve. (I sent patches to ardour too in the past, you folks
> have been friendly all the time. I am pretty sure same thing would
> have happened if I contributed more frequently.)
>
> OOM folks took a different approach. Originally, we granted them an
> SVN branch and we were working under the same umbrella. They put
> really hard work in their branch, and I admired most of what they did.
> The plan was to merge their new features into the trunk. So we asked
> for patches for individual features. This never came from them.
> Instead they wanted us to grab everything (or a subset) as is. Our
> team did not have the resources to take the diff of each individual
> file to filter out each separate feature, and we simply didn't want to
> accept *everything* as is. Thus, we proposed them to fork. This is
> purely due to differences in the workflow and creativity.
Thanks for the clarification.
> That said, I believe the original codebase deserved a little more
> credit than what is there in the bottom corner of the AUTHORS file.
> Moreover, when they forked off, they _kindly_ asked us to not backport
> some of the changes they made (mostly appearance related). While I do
> not have any intention of using their look, I found this a little odd.
> You are borrowing tens of thousands of lines of code from a project,
> don't give them credit in your project webpage, and tell them not to
> use your little contribution in their original codebase. There is
> something morally wrong here.
As for not using our look, you are free to the style sheet I created for
you but change the colors was all I was asking. You should communicate
these things directly to me instead of out here in the lions den :)
As for more attribution, what would you like. I have no issues with
giving you props where you need it. So what do you need?
You know there seems to be this idea that we are coming out there to
destroy someones project. You said it yourself that we code fast and
hard. The reason for this is that we simply need the software. When we
were dealing with Rosegarden Micheal McIntyre could not stop swearing at
us so we forked. He felt we were invading and told us he refused to let
us take over. Oh well :)
You know I never wanted to develop audio software, I have much bigger
fish to fry. It is just my wife's pipeline is so big that the current
software was caving in. I tried to get help from the coders, but there
is never much of that to go around. So I took matters into my own hands.
We are not like Ardour asking for money all the time. We are doing this
to write music. If people (Chris Cannam) and others feel they need more
attribution, then that part is really easy to fix.
I suspect there is much more to this puzzle than attribution. I suspect
we rocked the boat just a bit too much and too fast.
Well..... it is only going to get worse if that is the case. I need much
more to finish my project with my wife. We have very big plans. This
software is such a little part of our lives, but we do need it.
Anyhow. I have been up for days coding and need some sleep.
I hope you all enjoy our features. After all they are much better than
anything in Linux for orchestral scoring. We really outdid ourselves! :)
Enjoy!
> Anyhow, I wish them good luck with their project.
>
> Best,
> Orcan
>
> [1] http://lists.linuxaudio.org/pipermail/linux-audio-user/2010-December/075007…
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user(a)lists.linuxaudio.org
> http://lists.linuxaudio.org/listinfo/linux-audio-user
--
Christopher Cherrett
ccherrett(a)openoctave.org
http://www.openoctave.org
On Sat, 2011-01-29 at 15:11 -0500, Raymond Martin wrote:
> > To remember: If copyrights were not explicitly and in writing signed
> > over to you then they were not.
> >
> > /j
>
> The copyright in the license is the credit!
These are dire straits. I am afraid your ship is heading towards the
cliffs. Read your charts again, carefully, before proceeding.
SCO also had some imaginative ideas about copyright. They were wrecked!
/j
Hi everybody, I'm new to the list. Wassup :)
I have a question regarding liblv2-gui. On the site
(http://ll-plugins.nongnu.org/liblv2-gui.html) there are warnings all over the
place about how the lib is not compatible with rev 3+ of LV2. I searched the
archives of this list and Google, but to no avail, so I'm asking: is there a new
version of this toolset in the works? One that is fully compatible with the
latest version of LV2? I'm enjoying the work that Mr. Luthman has put into this
toolset and would like to continue using it for my current project.
Thanks,
Michael Bechard
