Linux-audio-dev

linux-audio-dev@lists.linuxaudio.org

3 participants
7520 discussions

by Federico Lopez

Hi, I compiled Aliki in a new machine and I can not capture impulses because aliki crash when I try to load a sweep file in the capture dialog. I can create a sweep file, I tried to create diferent sweep files but any of these files can be loaded in the capture dialog. When Aliki crash there is some Backtrace in the console, I pasted here: http://hastebin.com/pobileyiru.avrasm Using: Ubuntu12.10 Quantal kernel: 3.5.0-23-generic x86_64 Thanks in advance, federico lopez PD: I used Aliki in another 32bits machine without problems.

12 years, 10 months

Re: [LAD] making sense of Jack MIDI; or, is this an appropriate use

by Jeff McClintock

Message: 7 Date: Sun, 17 Feb 2013 17:10:11 -0500 From: Paul Coccoli < <mailto:pcoccoli@gmail.com> pcoccoli(a)gmail.com> >You're effectively serializing your object and passing them over the ringbuffer. If you do it this way, you should at least consider explicitly embedding the type and length as the first member of EventBase (and have each derived class set their own type and length in their constructors), and reading those before touching the object you read. Very good, that's what I do. The event is serialised to the ringbuffer, one member at a time (so I don't rely on a particular memory layout, or padding. The Type of message and the length are the first two values. (this example sends some text to the GUI to display a message box).. my_output_stream& strm = MessageQueToGui(); strm << id_to_long("mbox"); strm << (int) ( sizeof(wchar_t) * msg.size() + sizeof(int) + sizeof(icontype)); // message length. strm << msg; strm << icontype; Jeff

12 years, 10 months

Re: [LAD] avw lv2 plugins with Ardour 3 on KX Studio

by Aurélien Leblond

Hi Kane, I believe this issue is due to the fact that Ardour doesn't support CV port (it is the same in Jalv). In these plugins, the CV Port are used to control when the Beat Repeater/Slicer would be repeating/slicing. @David: Can you confirm? Kind Regards, Aurélien On Mon, Feb 18, 2013 at 9:57 AM, <wolfbiter(a)gmail.com> wrote: > So after some time spent installing all the packages, I managed to get your plugins to install on my system (latest version of KXstudio). I can see your plugins via the plugin manager of ardour3 (beta 5, the most recent), but when I try to load any of them I get these mysterious errors (one per load attempt): > > "[ERROR]: LV2: "Beat Repeater - Stereo" port 2 has no known data type > [ERROR]: LV2: "Beat Repeater - Mono" port 1 has no known data type > [ERROR]: LV2: "Beat Slicer - Stereo" port 2 has no known data type" > > This is a shot in the dark, but I was wondering if it had to do with this line from http://ardour.org/node/5351#comments > > "Name insert and send ports as "return" and "send" rather than "in" and "out". It is possible that this might break some connections in some existing sessions. " > > I'm extremely excited to be a user of your Beat Repeater and Beat Slicer - let me know what I can do! > > Thanks, > Kane

12 years, 10 months

C++11 user defined literals: Musical duration

by Mario Lang

hi. The following just manifested itself while experimenting with code. I find it quite neat since it makes for quite natural looking constants: class duration_log { int8_t log; public: constexpr duration_log(int log) : log(log) {} constexpr operator int() const { return log; } template<char...> friend duration_log constexpr operator"" _th(); }; duration_log constexpr maxima = 3; duration_log constexpr longa = 2; duration_log constexpr breve = 1; duration_log constexpr whole = 0; duration_log constexpr half = -1; duration_log constexpr quarter = -2; template<> duration_log constexpr operator"" _th<'8' >() { return -3; } template<> duration_log constexpr operator"" _th<'1', '6' >() { return -4; } template<> duration_log constexpr operator"" _th<'3', '2' >() { return -5; } template<> duration_log constexpr operator"" _th<'6', '4' >() { return -6; } template<> duration_log constexpr operator"" _th<'1', '2', '8'>() { return -7; } template<> duration_log constexpr operator"" _th<'2', '5', '6'>() { return -8; } --- (there is actually no need for the wrapper class duration_log, but it makes it easier to play with overloaded functions. You could of course just replace duration_log with int, if you do not care for type safety.) Now I can write things like "16_th" or "64_th". It turns out that there is a quite neat formula for the typical music notation duration calculation. Given that the base rhythmic type is expressed as a log (as in LilyPond for instance), the rational number of the duration with a certain amount of dots and time modification (tuple) can be written like this: #include <boost/rational.hpp> template<typename Rational = boost::rational<int>> inline Rational augmented_rational( int log, unsigned dots , int numerator, int denominator ) { return log < 0 ? Rational { ((1 << (dots + 1)) - 1) * numerator , denominator << -log << dots } : Rational { (((1 << (dots + 1)) - 1) << log) * numerator , denominator << dots }; } --- This is quite efficient since there is no need to multiply or manipulate rational numbers in any way. You just get the final value straight out of the expression. Comments? -- CYa, ⡍⠁⠗⠊⠕

12 years, 10 months

Deciphering jack-smf-utils -- Jack MIDI stuff

by M Donalies

I haven't really looked at the recorder program, but the player is pretty cool. To make it easier for me to understand, I simplified the code somewhat (got rid of lash stuff, reduced output to a single port, etc) so my code excerpts below don't match up exactly with the original code. The first question is a rather stupid one: How long is a Jack frame? If we're running at 44.1 kHz, is a frame 1/44100 sec? Or is it some multiple? Or is it something else? And does the process callback get called at each frame while transport is rolling? process_callback() calls process_midi_output(), wherein we find: port_buffer = jack_port_get_buffer(output_port, nframes); Why the nframes parameter? Is there a separate buffer area for each frame? A little later in the same function we have: last_frame_time = jack_last_frame_time(jack_client); Is this the time of the end of the last process cycle? -- 7:8

12 years, 10 months

making sense of Jack MIDI; or, is this an appropriate use for Jack?

by M Donalies

From what I can tell, the Jack midi interface aspires to hide the underlying Alsa api so an app developer can just use Jack midi and not have to muck with Asla. If this is true, then how do I use Jack in the following senerio: I'm writing a toy gui SMF player that outputs midi events so a program like fluidsynth can play them. Using Alsa sequencer, I put events on a queue with a time and Alsa takes care of the rest. If I just use the Jack midi api, how much of this process can Jack do? I'm assuming "not much," since all the apps that I've looked at the source of use the Alsa sequencer. If I wanted to do the sequencing myself, what would be involved? Or am I completely missing the point of what Jack can do? -- 7:8

12 years, 10 months

Presonus 1818 VSL Was: Re: So what do you think sucks about Linux audio ?

by Felix Homann

Hi Paul, 2013/2/5 Paul Davis <paul(a)linuxaudiosystems.com> > > > so how does this look? > > http://ardour.org/files/aspecs.png > > this looks very comprehensible indeed. You're recommending the Presonus 1818VSL device which looks very interesting. How about the advertised effects like "reverb and delay effects and [...] compression, limiting, semi-parametric EQ, and high-pass filter". Are they done in hardware and accessable from Alsa or are these pure software effects not usable in Linux? Regards, Felix

12 years, 10 months

C/gtk3/cairo meter widget

by Patrick Shirkey

Hi, Before I spend any time to rewrite the gtkmeter.c/h widget for JAMin to gtk3/cairo does anyone have one already finished? Needs to be in C. -- Patrick Shirkey Boost Hardware Ltd

12 years, 10 months

Linux audio articles in LWN

by Dave Phillips

Greetings, Just a pointer to articles I've written to date for the Linux Weekly News. Their policy is to reserve initial viewing for subscribers only, but afterwards the articles are publicly accessible. So, for the interested among ye : A Brief Survey Of Linux Audio Session Managers (January 2013) http://lwn.net/Articles/533594/ The Synthesizers Of Sean Bolton (December 2012) http://lwn.net/Articles/527556/ 21st Century Csound (November 2012) http://lwn.net/Articles/523166/ A Tale Of Two Sequencers [harmonySeq and Softwerk] (October 2012) http://lwn.net/Articles/520348/ Keeping Up With Kdenlive (September 2012) http://lwn.net/Articles/516016/ The Linux Audio Workstation, parts 1 & 2 (August 2012) http://lwn.net/Articles/509958/ http://lwn.net/Articles/510046/ A Survey Of Linux Audio Plugins (June 2012) http://lwn.net/Articles/502183/ A Report From LAC2012 (May 2012) http://lwn.net/Articles/495612/ Interesting to note how quickly things evolve in the Linux world. Stuff I wrote only a few months ago is already outdated by development trends. Keep up the good work, devs ! Anyway, enjoy, and your comments are welcome. Best, dp

12 years, 10 months

So what do you think sucks about Linux audio ?

by Dave Phillips

Greetings, I've been reading a lot of negative (read: vitriolic) commentary about the world of Linux audio development and applications. I won't bother to say where, just "the usual places" will have to suffice. Of greater interest to me is the commentary itself - it seems to boil down to the following plaints and lamentations (in no particular order) : Too many distros. Too many audio-optimized distros. Not enough native plugins, esp. instruments. Inconsistent support for VST/VSTi plugins. Too many unstable/unfinished applications. Too many "standards" (esp. wrt plugins). Poor external/internal session management. Poor support for certain modes of composition (think Ableton Live). Lack of support for contemporary hardware. Confusion re: desktops, and GUI toolkits. Too difficult to set up audio system. JACK is a pain. Too much conflict/fragmentation within the development community. I'm not so interested in comments on the commentary, I have my own, but say what you will about the list. I figure that most denizens of these lists already have ready replies and responses to these and other criticisms, many of which have been voiced here previously. What I'm more interested in is what *you* think is missing most or just plain wrong about the situation. Please, try to speak your piece without flames or dissing other developers and/or their work. Frankly speaking, I've had enough of that crap, and I'm most thankful these days for such forum amenities as "mute user" and autodiscard, along with the standard filters found in mail clients. <aside> I'm reminded of John Cage's comments regarding the behavior of the NY Philharmonic when they destroyed his equipment during the premire of Atlas Eclipticalis, something to the effect that his concerns had ceased to be musical and had become social, i.e. that he had to figure a way to allow people to be free yet behave themselves with respect towards the common goal (e.g. Cage's music and property). I'm going to guess that he was still working on that up to his death. </aside> So, in your honest and bold opinion as user and/or developer, what do we lack most and what can we do without that we already have ? Please feel free to expand your remarks as you like. I'm planning an article on the topic and will likely use selected comments, subject to approval of course. Best, dp

12 years, 10 months

Jump to page:

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-dev