I'd just like to add that the same happens to MIDI with DSP off on a rather strong machine (Opteron 148 @ 2200).
In which sense "the same happens"? Do you mean that sending a MIDI message takes more CPU time than it should?
On Wed, Apr 7, 2010 at 4:26 PM, Matteo Sisti Sette < matteosistisette@gmail.com> wrote:
I'd just like to add that the same happens to MIDI with DSP off on a rather strong machine (Opteron 148 @ 2200).
In which sense "the same happens"? Do you mean that sending a MIDI message takes more CPU time than it should?
Sorry i meant that giving too much job (in zero logical time....) to the GUI has an impact on MIDI timing.
Andras
2010/4/7 András Murányi muranyia@gmail.com:
Sorry i meant that giving too much job (in zero logical time....) to the GUI has an impact on MIDI timing.
Andras
Hi, What I noticed in a few project where I was using a heavy GUI and a midi controller was a big delay in the midi signal transmission. I always solved this problem splitting the GUI/engine patch and midi control patch in two different pd's instances . Does Anyone has experienced something similar?
husk
András Murányi escribió:
On Wed, Apr 7, 2010 at 4:26 PM, Matteo Sisti Sette <matteosistisette@gmail.com mailto:matteosistisette@gmail.com> wrote:
> I'd just like to add that the same happens to MIDI with DSP off on > a rather strong machine (Opteron 148 @ 2200). In which sense "the same happens"? Do you mean that sending a MIDI message takes more CPU time than it should?Sorry i meant that giving too much job (in zero logical time....) to the GUI has an impact on MIDI timing.
Oh yes of course, it has impact on everything :)
-
András Murányi -
Husk 00 -
Matteo Sisti Sette