On Sun, Feb 17, 2013 at 4:45 PM, Harry van Haaren wrote:
>
> On Sun, Feb 17, 2013 at 9:20 PM, Paul Coccoli wrote:
>>
>> JACK ringbuffers are
>> ideally suited to passing simple types (like floats), and not vairable
>> sized things (like different derived Event classes). Your enum for
>> event ty
On Sun, Feb 17, 2013 at 4:41 PM, Harry van Haaren wrote:
>
>
> On Sun, Feb 17, 2013 at 9:20 PM, Paul Coccoli wrote:
>>
>> This scheme sounds error prone. In general, copying C++ objects via
>> memcpy (or writing them 1 byte at a time into the ringbuffer, which is
>> what I think you're proposing
On Sun, Feb 17, 2013 at 9:20 PM, Paul Coccoli wrote:
> JACK ringbuffers are
> ideally suited to passing simple types (like floats), and not vairable
> sized things (like different derived Event classes). Your enum for
> event types is a bit of a red flag, too. While its perfectly valid,
> "type
On Sun, Feb 17, 2013 at 9:20 PM, Paul Coccoli wrote:
> This scheme sounds error prone. In general, copying C++ objects via
> memcpy (or writing them 1 byte at a time into the ringbuffer, which is
> what I think you're proposing) is a bad idea.
Nope, write them one sizeof( event->size() ) at a
On Sun, Feb 17, 2013 at 10:35 AM, Harry van Haaren
wrote:
> On Sun, Feb 17, 2013 at 3:57 AM, M Donalies
> wrote:
>>
>> No locks or mutexes in a callback function. I need to think about that
>> one.
>
> This is indeed a "lovely" topic for debate. I'm bound to say that, I'm
> currently doing a fina
On Sun, Feb 17, 2013 at 3:57 AM, M Donalies wrote:
> No locks or mutexes in a callback function. I need to think about that one.
>
This is indeed a "lovely" topic for debate. I'm bound to say that, I'm
currently doing a final-year project for college on the topic.
I've came up with a solution, whi
Am 17.02.2013 00:06 schrieb "Ralf Mardorf" :
> If this is all, I didn't read everything, then what's the problem?
Except for the SysEx length there's no problem at all. I just wanted to
show you that MIDI has been in use beyond music for years.
> I already mentioned that I would like coders to ta
No locks or mutexes in a callback function. I need to think about that one.
That rules out the most obvious choice for preparing events for dispatch while
transport is rolling, which would be a producer-consumer model with some
thread as the producer and the callback as consumer.
--
7:8
__
On Saturday 16 February 2013 03:58:10 Frank Kober wrote:
> I've tried to do that move from an ALSA backend to a JACK MIDI one in
> QMidiArp, and used vectors as a queue for event timings. It doesn't
> support tempo changes on the fly and I even didn't think about how to
> implement this. The ALSA s
On Fri, Feb 15, 2013 at 01:46:03PM -0800, J. Liles wrote:
> On Fri, Feb 15, 2013 at 12:22 PM, Paul Davis
> wrote:
>
>
> >
> > nobody has ever stepped up to write a library based on JACK MIDI that
> > would do "MIDI sequencing" in the sense of your "deliver this event at time
> > T where T is arb
On Sat, Feb 16, 2013 at 02:13:33PM -0500, Paul Davis wrote:
> On Sat, Feb 16, 2013 at 12:21 PM, Pedro Lopez-Cabanillas <
> pedro.lopez.cabanil...@gmail.com> wrote:
> >
> > There are other use cases for MIDI that don't involve soft synths, or even
> > don't involve music at all. What I find laughab
On Sat, 16 Feb 2013 23:46:59 +0100, Felix Homann
wrote:
Am 16.02.2013 23:23 schrieb "Ralf Mardorf" :
"Musical Instrument Digital Interface"
MSC has been an industry standard for 20+ years now. So who cares what
MIDI
was meant to be in the eighties? When I am concerned with MIDI it's about
Am 16.02.2013 23:23 schrieb "Ralf Mardorf" :
>
> "Musical Instrument Digital Interface"
MSC has been an industry standard for 20+ years now. So who cares what MIDI
was meant to be in the eighties? When I am concerned with MIDI it's about
MSC.
___
Linux-a
On Sat, 16 Feb 2013 22:54:40 +0100, Felix Homann
wrote:
Am 16.02.2013 20:31 schrieb "Ralf Mardorf" :
If you like to use MIDI as a serial interface for something else, then I
won't call it MIDI,
Have you heard of MIDI Show Control?
No, I heard about MSC for the first time now. MIDI is limi
Am 16.02.2013 20:31 schrieb "Ralf Mardorf" :
>
> If you like to use MIDI as a serial interface for something else, then I
won't call it MIDI,
Have you heard of MIDI Show Control?
___
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
http:
On 02/15/2013 09:22 PM, Paul Davis wrote:
> the only effort i have seen in the open source world to implement a
> general purpose MIDI sequencing library that did "future" sequencing was
> something called (something like) TME3.
Don't forget MidiShare.
--
Dr. Albert Gr"af
Dept. of Music-Informat
On Sat, 16 Feb 2013 20:31:15 +0100, Ralf Mardorf
wrote:
On Sat, 16 Feb 2013 20:13:33 +0100, Paul Davis
wrote:
There are other use cases for MIDI that don't involve soft synths, or
even don't involve music at all. What I find laughable is the arrogance
of pretending that everybody fits a
On Sat, 16 Feb 2013 20:13:33 +0100, Paul Davis
wrote:
There are other use cases for MIDI that don't involve soft synths, or
even don't involve music at all. What I find laughable is the arrogance
of pretending that everybody fits a single use case.
I didn't follow this thread, I randomly r
On Sat, Feb 16, 2013 at 12:21 PM, Pedro Lopez-Cabanillas <
pedro.lopez.cabanil...@gmail.com> wrote:
> **
>
> There are other use cases for MIDI that don't involve soft synths, or even
> don't involve music at all. What I find laughable is the arrogance of
> pretending that everybody fits a single
On Saturday 16 February 2013 13:15:51 Pedro Lopez-Cabanillas wrote:
> On Friday 15 February 2013 15:19:03 M Donalies wrote:
> > If I want to support
> > both audio and midi, then I have to learn 2 completely different and
> > conflicting api's.
>
> Audio and MIDI are two totally different conce
On Saturday 16 February 2013 10:59:22 Paul Davis wrote:
> On Sat, Feb 16, 2013 at 10:49 AM, Bill Gribble wrote:
> > On Sat, 2013-02-16 at 09:18 -0500, Paul Davis wrote:
> > > Great Dictator and Malevolent Guru
> >
> > Polite Grind band name alert!
>
> actually, its a duo. the problem is, i know wh
On Sat, Feb 16, 2013 at 10:49 AM, Bill Gribble wrote:
> On Sat, 2013-02-16 at 09:18 -0500, Paul Davis wrote:
> > Great Dictator and Malevolent Guru
>
> Polite Grind band name alert!
>
actually, its a duo. the problem is, i know which one i am but who is going
to play the other one?
_
On Sat, 2013-02-16 at 09:18 -0500, Paul Davis wrote:
> Great Dictator and Malevolent Guru
Polite Grind band name alert!
Thanks,
Bill Gribble
___
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo
On Feb 15, 2013, at 18:41 11, M Donalies wrote:
> I suppose I've been spoiled by the Qt documentation.
You have been! I regard TrollTech's docs as the 'gold standard' for the entire
industry; even M$ docs, for all their bloat, are not near as easy to use.
Cheers!
|---
On Feb 15, 2013, at 15:19 03, M Donalies wrote:
> Why is it that I can find
> entire books on programming the linux kernel, but so little about either Alsa
> or Jack?
In a nutshell: because the communities to which the Linux kernel is relevant
are larger, by several orders of magnitude. They
On Sat, Feb 16, 2013 at 7:15 AM, Pedro Lopez-Cabanillas <
pedro.lopez.cabanil...@gmail.com> wrote:
> **
>
> I like to explain this issue with an analogy: it is similar to the image
> world, where you have vector graphics (MIDI) and bit-mapped or raster
> graphics (digital audio). There are Linux p
On Friday 15 February 2013 15:19:03 M Donalies wrote:
> If I want to support
> both audio and midi, then I have to learn 2 completely different and
> conflicting api's.
Audio and MIDI are two totally different concepts from the beginning. You can
mix both of them in your application, but to do
On Saturday 16 February 2013 10:31:42 Frank Kober wrote:
> If you don't like
> it noone obliges you to use jack or Qt or ALSA ;) and it's good that way
> no?
So long as unfair propaganda like this exists, I will continue with my
counter-propaganda:
http://wiki.linuxaudio.org/faq/start#qwhat_is_th
>
> De : Pedro Lopez-Cabanillas
>À : M Donalies
>Cc : linux-audio-dev@lists.linuxaudio.org
>Envoyé le : Samedi 16 février 2013 11h02
>Objet : Re: [LAD] making sense of Jack MIDI; or, is this an appropriate use
>for Jack?
>
>
>On
On Friday 15 February 2013 18:41:11 M Donalies wrote:
> I suppose I've been spoiled by the Qt documentation.
Good luck with that. You should know that your new and great benevolent
dictator and guru thinks that Qt is not written in C++, but in some other
dialect that needs to be preprocessed bef
On Friday 15 February 2013 15:19:03 M Donalies wrote:
> And, furthermore, you young whippersnappers... what does that mean
> anyway...
I suppose that it means that my work and I have been bullied in this mailing
list in the past by the great benevolent dictator and guru. After that, I have
beco
- Mail original -
> De : M Donalies
> À : linux-audio-dev@lists.linuxaudio.org
> Cc :
> Envoyé le : Vendredi 15 février 2013 17h23
> Objet : [LAD] making sense of Jack MIDI; or, is this an appropriate use for
> Jack?
> Using Alsa sequencer, I put events on a queue
On Fri, Feb 15, 2013 at 11:41 PM, M Donalies wrote:
> There's no "here's how you use these guys" sections.
Hi M!
As a relative new-comer to linux-audio, I struggled with the same issues
you're having.
I had intended to document my own learning of JACK MIDI, and have a repo
online here
concernin
On 15/02/13 M Donalies wrote:
>On Friday 15 February 2013 13:19:57 J. Liles wrote:
>> It means that you have to do that tricky 'sequencing' part, which
>> consists of scheduling (MIDI) events and only placing them onto the
>> JACK buffer at the appropriate instant. ALSA MIDI does this for you,
>>
On Fri, Feb 15, 2013 at 10:46 PM, J. Liles wrote:
>
> On Fri, Feb 15, 2013 at 12:22 PM, Paul Davis wrote:
...
>> what could make quite a bit of sense would be a utility JACK client that
>> played an SMF file via JACK MIDI. this would be *relatively* simple to do
>> (once you figure out what godawfu
On Friday 15 February 2013 16:46:03 J. Liles wrote:
> Yes it does. jack-smf-tools. I've seen a few others too the names of which
> escape me (in Python, I believe).
Thanks!
I haven't a clue what the Jack stuff is doing at this point. But I plan to
strip it to the bare essentials, start tinkering,
On Fri, Feb 15, 2013 at 6:41 PM, M Donalies wrote:
> On Friday 15 February 2013 15:22:20 Paul Davis wrote:
> > the JACK API is fully documented. tutorials on basic use of the audio API
> > exist. the big difference here is that there are several example blobs of
> > source, ranging from the explic
On Friday 15 February 2013 15:22:20 Paul Davis wrote:
> the JACK API is fully documented. tutorials on basic use of the audio API
> exist. the big difference here is that there are several example blobs of
> source, ranging from the explicitly "example" clients within the JACK
> source code package
On Fri, Feb 15, 2013 at 4:46 PM, J. Liles wrote:
>
> what could make quite a bit of sense would be a utility JACK client that
>> played an SMF file via JACK MIDI. this would be *relatively* simple to do
>> (once you figure out what godawful lump of code you plan to use to parse
>> SMF) and would
On Fri, Feb 15, 2013 at 12:22 PM, Paul Davis wrote:
>
> nobody has ever stepped up to write a library based on JACK MIDI that
> would do "MIDI sequencing" in the sense of your "deliver this event at time
> T where T is arbitrary". nothing is stopping anyone from doing that.
>
FWIW I have the emb
On Fri, Feb 15, 2013 at 3:19 PM, M Donalies wrote:
>
> [insert rant: If html email is for children, shouldn't serious
> documentation
> refrain from flash, javascript,
although flash is on its way out (thanks largely to apple, but also html5 +
), javascript is at the core of a lot serious websit
On Friday 15 February 2013 13:19:57 J. Liles wrote:
> It means that you have to do that tricky 'sequencing' part, which consists
> of scheduling (MIDI) events and only placing them onto the JACK buffer at
> the appropriate instant. ALSA MIDI does this for you, as well as providing
> a nice API for
On Friday 15 February 2013 12:53:37 Pedro Lopez-Cabanillas wrote:
> Maybe you already have read the propaganda, and came here honestly
> wondering about the truth behind it:
>
> http://wiki.linuxaudio.org/faq/start#qwhat_is_the_difference_between_jack-
> midi_and_alsa-midi
Yes, and I've been tryi
On Fri, Feb 15, 2013 at 2:15 PM, Pedro Lopez-Cabanillas <
pedro.lopez.cabanil...@gmail.com> wrote:
> **
>
>
>
> I'm not going to comment your whole message, only this little bit:
>
>
>
> On Friday 15 February 2013 13:33:48 M Donalies wrote:
>
> > 2) Jack let's me know what time it is through a cal
On Fri, Feb 15, 2013 at 12:53 PM, Pedro Lopez-Cabanillas <
pedro.lopez.cabanil...@gmail.com> wrote:
> **
>
> I'm hated among Jack MIDI zealots in these lists,
>
[ ... ]
>
>
> Jack MIDI looks like it had been conceived with the goal that Ardour
> become the one and only sequencer application,
>
I'm not going to comment your whole message, only this little bit:
On Friday 15 February 2013 13:33:48 M Donalies wrote:
> 2) Jack let's me know what time it is through a callback.
It does. As a frame position within the audio stream. It depends on the sample
rate of the audio stream, you know:
On Fri, Feb 15, 2013 at 10:33 AM, M Donalies wrote:
> On Friday 15 February 2013 11:12:04 Paul Davis wrote:
> > JACK does not provide sequencing facilities. It simply transports MIDI
> > between ports.
> >
> > > If I wanted to do the sequencing myself, what would be involved?
> >
> > a lot.
>
> Do
On Friday 15 February 2013 11:12:04 Paul Davis wrote:
> JACK does not provide sequencing facilities. It simply transports MIDI
> between ports.
>
> > If I wanted to do the sequencing myself, what would be involved?
>
> a lot.
Does that mean:
Don't even think about it unless you're a systems prog
On Friday 15 February 2013 11:23:02 M Donalies wrote:
> 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.
Maybe you already have read the propaganda, and came here honestly wondering
On Fri, Feb 15, 2013 at 11:23 AM, M Donalies wrote:
> 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.
>
that is a part of the goal, but a deeper one is to provide sample-accura
>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 prog
51 matches
Mail list logo
