Hello Pders,
This is my first post to the pd-list.
I recently bought a Faderfox midi controller and was planning to use it with Pd (Win XP) but I'm running into problems. When I move a knob on the midi controller there is a delay of at least one second until the controller data show up in the Pd window (I simply output controllers using the [ctlin] object). This delay makes it pretty much unusable. I tried different command line arguments to find something that could speed things up and I managed to get quick midi input through the [ctlin] object, if I used -noaudio. But I'd like to use the audio system, so that's not really an option for me. Is MIDI on Win XP Pd really this bad? There is a warning message showing up in the Pd window when using MIDI on windows.
A solution would be to convert the MIDI to OSC in some other program and send it to Pd, but of course I prefer to just use the [ctlin] object in Pd, if possible. I also run Pd on Linux but unfortunately my soundcard (M-Audio Firewire 410) has no driver for Linux.
Cheers, Anton
Hello,
Anton Hörnquist a écrit :
with Pd (Win XP) but I'm running into problems. When I move a knob on the midi controller there is a delay of at least one second until the controller data show up in the Pd window (I simply output controllers using the [ctlin] object). This delay makes it pretty much unusable. I
did you try MIDI controllers with another software?
tried different command line arguments to find something that could speed things up and I managed to get quick midi input through the [ctlin] object, if I used -noaudio. But I'd like to use the audio system, so that's not really an option for me. Is MIDI on Win XP Pd really this bad? There is a warning message showing up in the Pd window when using MIDI on windows.
What is this error message?
MIDI on XP is bad indeed, and I have to run my midi application under linux to get a latency lower than human sound perception, without artefacts, and with a cheap soundcard.
If you know a bit about development you might be interested about this:
http://msdn.microsoft.com/archive/default.asp?url=/archive/en-us/dnargame/ht...
Anyway, I suggest to have a deep look into your computer configuration, you might have a problem with the system.
A solution would be to convert the MIDI to OSC in some other program and send it to Pd, but of course I prefer to just use the [ctlin] object in Pd, if possible. I also run Pd on Linux but unfortunately my soundcard (M-Audio Firewire 410) has no driver for Linux.
Indeed I use OSCx for a lower latency, but almost all paywares doesn't use this communication protocol. They are almost all stupidly stucked on the old MIDI.
Cheers, Anton
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Jan 4, 2008 6:16 PM, Patrice Colet pat@mamalala.org wrote:
with Pd (Win XP) but I'm running into problems. When I move a knob on the midi controller there is a delay of at least one second until the controller data show up in the Pd window (I simply output controllers using the [ctlin] object). This delay makes it pretty much unusable. I
did you try MIDI controllers with another software?
Yes - the controller works perfectly with the other software I've tested it with (Ableton Live, Max/MSP, MIDI-OX)
tried different command line arguments to find something that could speed things up and I managed to get quick midi input through the [ctlin] object, if I used -noaudio. But I'd like to use the audio system, so that's not really an option for me. Is MIDI on Win XP Pd really this bad? There is a warning message showing up in the Pd window when using MIDI on windows.
What is this error message?
In the Pd window: Warning: midi input is dangerous in Microsoft Windows; see Pd manual)
MIDI on XP is bad indeed, and I have to run my midi application under linux to get a latency lower than human sound perception, without artefacts, and with a cheap soundcard.
If you know a bit about development you might be interested about this:
http://msdn.microsoft.com/archive/default.asp?url=/archive/en-us/dnargame/ht...
Anyway, I suggest to have a deep look into your computer configuration, you might have a problem with the system.
Thanks for the link, I'll look into it! But this is not a general Win XP problem for me, it's a Pd problem. As I wrote, other programs work fine, no latency at all. When I only use the midi system of Pd it works fine. But when I use both the audio and midi system in Pd, there is delay in incoming midi.
Cheers Anton
Anton Hörnquist a écrit :
On Jan 4, 2008 6:16 PM, Patrice Colet pat@mamalala.org wrote:
What is this error message?
In the Pd window: Warning: midi input is dangerous in Microsoft Windows; see Pd manual)
Ah, this is not related with ctlin, I'm using sometimes midiin and midiout for handling MTC and MIDI clock, i haven't see a pd related problem yet with these objects.
XP problem for me, it's a Pd problem. As I wrote, other programs work fine, no latency at all. When I only use the midi system of Pd it works fine. But when I use both the audio and midi system in Pd, there is delay in incoming midi.
Thanks for giving this precious precision, i didn't understand it in the first message, and forgot to ask what version of pd are you using?
I've never been into this kind of problem with all win32 pd versions I tried, and I'm actually on Pd version 0.41-0test05.
Even if i couldn't be on any help, maybe your answers will drive pd devels to find out a solution.
Pk
hi i think i remember a similar problem in my case i have 2 soundcard: via-integrated and m-audio-delta1010 similar (or same) latency problem ocured when i was using midi from "m-audio" and audio engine on my "via". so im using always my m-audio card for everything (anyway better;) i think that it may be the problem of cheap soundcard, or the drivers for it. maybe you can try some stuff like asio4all and try to run it with this driver, maybe try with a better quality soundcard... my only recommendation is to try all possibilities with your audio-midi connections :) hope this brings u somwhere greets nikola
Anton Hörnquist wrote:
On Jan 4, 2008 6:16 PM, Patrice Colet pat@mamalala.org wrote:
with Pd (Win XP) but I'm running into problems. When I move a knob on the midi controller there is a delay of at least one second until the controller data show up in the Pd window (I simply output controllers using the [ctlin] object). This delay makes it pretty much unusable. I
did you try MIDI controllers with another software?
Yes - the controller works perfectly with the other software I've tested it with (Ableton Live, Max/MSP, MIDI-OX)
tried different command line arguments to find something that could speed things up and I managed to get quick midi input through the [ctlin] object, if I used -noaudio. But I'd like to use the audio system, so that's not really an option for me. Is MIDI on Win XP Pd really this bad? There is a warning message showing up in the Pd window when using MIDI on windows.
What is this error message?
In the Pd window: Warning: midi input is dangerous in Microsoft Windows; see Pd manual)
MIDI on XP is bad indeed, and I have to run my midi application under linux to get a latency lower than human sound perception, without artefacts, and with a cheap soundcard.
If you know a bit about development you might be interested about this:
http://msdn.microsoft.com/archive/default.asp?url=/archive/en-us/dnargame/ht...
Anyway, I suggest to have a deep look into your computer configuration, you might have a problem with the system.
Thanks for the link, I'll look into it! But this is not a general Win XP problem for me, it's a Pd problem. As I wrote, other programs work fine, no latency at all. When I only use the midi system of Pd it works fine. But when I use both the audio and midi system in Pd, there is delay in incoming midi.
Cheers Anton
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Thanks for the help. Using ASIO4ALL with Firewire 410 (instead of the official ones) seemed to solve the midi problem. I've used ASIO4ALL with my internal laptop card some time but wasn't aware it would work for firewire devices aswell. The official Firewire 410 drivers work fine with all other audio software I use though, so there's something strange about Pd with these particular drivers.
Cheers, Anton
On Jan 4, 2008 10:09 PM, jeremaja niko jeremaja.niko@googlemail.com wrote:
hi i think i remember a similar problem in my case i have 2 soundcard: via-integrated and m-audio-delta1010 similar (or same) latency problem ocured when i was using midi from "m-audio" and audio engine on my "via". so im using always my m-audio card for everything (anyway better;) i think that it may be the problem of cheap soundcard, or the drivers for it. maybe you can try some stuff like asio4all and try to run it with this driver, maybe try with a better quality soundcard... my only recommendation is to try all possibilities with your audio-midi connections :) hope this brings u somwhere greets nikola
Anton Hörnquist wrote:
On Jan 4, 2008 6:16 PM, Patrice Colet pat@mamalala.org wrote:
with Pd (Win XP) but I'm running into problems. When I move a knob on the midi controller there is a delay of at least one second until the controller data show up in the Pd window (I simply output controllers using the [ctlin] object). This delay makes it pretty much unusable. I
did you try MIDI controllers with another software?
Yes - the controller works perfectly with the other software I've tested it with (Ableton Live, Max/MSP, MIDI-OX)
tried different command line arguments to find something that could speed things up and I managed to get quick midi input through the [ctlin] object, if I used -noaudio. But I'd like to use the audio system, so that's not really an option for me. Is MIDI on Win XP Pd really this bad? There is a warning message showing up in the Pd window when using MIDI on windows.
What is this error message?
In the Pd window: Warning: midi input is dangerous in Microsoft Windows; see Pd manual)
MIDI on XP is bad indeed, and I have to run my midi application under linux to get a latency lower than human sound perception, without artefacts, and with a cheap soundcard.
If you know a bit about development you might be interested about this:
http://msdn.microsoft.com/archive/default.asp?url=/archive/en-us/dnargame/ht...
Anyway, I suggest to have a deep look into your computer configuration, you might have a problem with the system.
Thanks for the link, I'll look into it! But this is not a general Win XP problem for me, it's a Pd problem. As I wrote, other programs work fine, no latency at all. When I only use the midi system of Pd it works fine. But when I use both the audio and midi system in Pd, there is delay in incoming midi.
Cheers Anton
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-
Anton Hörnquist -
jeremaja niko -
Patrice Colet