> make the point well of how limiting the battery life can be for
> a MIDI wireless controller right now.
$2.99 will get you a 15 foot (~5 meter) USB 2.0 cable
http://www.newegg.com/Product/ProductList.aspx?Submit=ENE&N=210001+1177512103+1177412128&name=11+-+15+ft.
theres also 16 foot cables,
On Mar 31, 2007, at 5:26 AM, Jens M Andreasen wrote:
What I wonder is; wouldn't it be possible to bypass this USB radio
transmitter/recaiver dongle-thingie and fast forward to the wireless
capabilities already built in to most of modern portable devices sold
today? Hey, even the OLPC aimed at
On Sun, 2006-11-12 at 17:28 +0100, Pieter Palmers wrote:
[regarding midi over firewire]
> Note that this is already implemented in FreeBob. There is nothing
> preventing us from setting up a (random number here)-channel MIDI link
> over Firewire between one or more devices.
>
> A major issue h
Some stuff to read for Ethernet Midi, here is a Real Time Transport
protocol for Midi over network:
http://tools.ietf.org/html/rfc4695
Cheers,
Malte
--
Malte Steiner
media art + development
-www.block4.com-
Don't forget DMIDI IEEE P1639. Distributed MIDI over ethernet. It is still
alive and well and I'm developing code for other Os's apart from Linux. Also
working on a MIDI BOX with 32 MIDI ins and 32 MIDI outs all separately
addressable and just plugs into a 10/100/1000 ethernet hub/switch.
regard
On Sat, 2006-11-11 at 21:41 -0500, Gene Heskett wrote:
> On Saturday 11 November 2006 21:00, Tony Nelson wrote:
> >At 4:21 PM -0500 11/11/06, Gene Heskett wrote:
> > ...
> >
> This thread might be of interest to the linux-audio-dev group, so I've
> added them to the Cc:
>
> >>Yup, and its been a
Dmitry Baikov wrote:
What is a really major issue, that all hw synths still have that slow
31.5kbps link.
Nonetheless, glad to hear FW-MIDI being that fast. And what about
jitter there?
According to RME guys, without special handling USB-MIDI can suffer
delays about 6ms.
true
And with FW,
What is a really major issue, that all hw synths still have that slow
31.5kbps link.
Nonetheless, glad to hear FW-MIDI being that fast. And what about jitter there?
According to RME guys, without special handling USB-MIDI can suffer
delays about 6ms.
And with FW, they state there are the same pro
Gene Heskett wrote:
On Sunday 12 November 2006 06:16, Jens M Andreasen wrote:
On Sat, 2006-11-11 at 21:41 -0500, Gene Heskett wrote:
But I like that idea, a lot. Maybe some enterprising LAD people could
get together and spec something like a midi interface running over
firewire, compl
On Sunday 12 November 2006 06:16, Jens M Andreasen wrote:
>On Sat, 2006-11-11 at 21:41 -0500, Gene Heskett wrote:
>> But I like that idea, a lot. Maybe some enterprising LAD people could
>> get together and spec something like a midi interface running over
>> firewire, complete with the repeaters
On Sat, 2006-11-11 at 21:41 -0500, Gene Heskett wrote:
> But I like that idea, a lot. Maybe some enterprising LAD people could get
> together and spec something like a midi interface running over firewire,
> complete with the repeaters so it can be daisy-chained just like midi can
> be, and ho
On Saturday 11 November 2006 21:00, Tony Nelson wrote:
>At 4:21 PM -0500 11/11/06, Gene Heskett wrote:
> ...
>
This thread might be of interest to the linux-audio-dev group, so I've
added them to the Cc:
>>Yup, and its been a constant src of amazement to this old fart that
>> when the midi spec w
bingo. I kicked off a very similar thread with Paul Davis earlier in April...
On 5/30/06, Steve <[EMAIL PROTECTED]> wrote:
It is a good idea, as long as your interface is relatively simple...
but what about when you want to do something that is sort of custom to
your interface, like for example
It is a good idea, as long as your interface is relatively simple...
but what about when you want to do something that is sort of custom to
your interface, like for example showing the waveform on the screen by
sending peak or spectrum data.
you'll end up having to create a mini "custom" protocol
I wrote a client-side OSC sequencer for supercollider. check my site
for "scsynth".
On 5/29/06, Loki Davison <[EMAIL PROTECTED]> wrote:
On 5/27/06, Patrick Stinson <[EMAIL PROTECTED]> wrote:
> Take a look at OSC. It assumes that all computers' clocks are synced
> via ntp, which is more than adeq
On Tue, 2006-05-30 at 09:04 +1000, Loki Davison wrote:
> On 5/27/06, Patrick Stinson <[EMAIL PROTECTED]> wrote:
> > Take a look at OSC. It assumes that all computers' clocks are synced
> > via ntp, which is more than adequate to ensure its 64-bit fixed point
> > timestamps are accurate. This makes
On 5/27/06, Patrick Stinson <[EMAIL PROTECTED]> wrote:
Take a look at OSC. It assumes that all computers' clocks are synced
via ntp, which is more than adequate to ensure its 64-bit fixed point
timestamps are accurate. This makes the programming easier and more
reliable, as you only have to progr
iain duncan wrote:
>>I think that 'groove quantise' does have quite a specific meaning :
>>> To take the timing from one midi part, and apply it to another.
>>> So, you get the midi timing from a real drummer grooving away and
>>apply
>>> it to your beat. Then it pulls your beats to the nearest be
I think that 'groove quantise' does have quite a specific meaning :
To take the timing from one midi part, and apply it to another.
So, you get the midi timing from a real drummer grooving away and apply
it to your beat. Then it pulls your beats to the nearest beat in the
groove, rather than to t
Dave Robillard wrote:
>Hi all,
>
>Does anyone know of a page somewhere that explains just what (on a
>developer level) MIDI "groove" is? I want to implement it in a
>sequencer, but all I can find is user documentation pages with useless
>information.
>
>Is it as simple as each note having a time o
20 matches
Mail list logo
