SOLVED: massive basic functionality playback problem with MuLab and Kirnu arpeggiator
-
- KVRist
- 332 posts since 26 Jul, 2012
playback dropouts with MuLab, Kirnu Cream pre release 8 and Kirnu 1.2.1
1. playback with Kirnu arpeg starts out of time
2. playback with Kirnu arpeg is wrong
this problem only occours with Kirnu arpeggiators - any other freeware arpeggiators did'nt have this playback problems!
see also my post on:
http://www.kvraudio.com/forum/viewtopic.php?t=379602
1. playback with Kirnu arpeg starts out of time
2. playback with Kirnu arpeg is wrong
this problem only occours with Kirnu arpeggiators - any other freeware arpeggiators did'nt have this playback problems!
see also my post on:
http://www.kvraudio.com/forum/viewtopic.php?t=379602
Last edited by Hermu on Fri Apr 26, 2013 9:11 pm, edited 1 time in total.
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
There is an updated MuLab version 5.1.4 in http://www.mutools.com/mulab/everest
The easiest way to update is http://www.mutools.com/mulab/app-patch/Read%20Me.txt
So just like before simply replace the MuLab.exe and MuLab.ID by the new versions. (MuLab.ID is on Windows only)
This new version should fix the issues you had when using Kirnu Cream in MuLab.
Can you please confirm all is working fine now?
The easiest way to update is http://www.mutools.com/mulab/app-patch/Read%20Me.txt
So just like before simply replace the MuLab.exe and MuLab.ID by the new versions. (MuLab.ID is on Windows only)
This new version should fix the issues you had when using Kirnu Cream in MuLab.
Can you please confirm all is working fine now?
-
- KVRist
- Topic Starter
- 332 posts since 26 Jul, 2012
MuLab 5.1.4 Kirnu Cream playback is now much better, but not perfect.mutools wrote:There is an updated MuLab version 5.1.4 in http://www.mutools.com/mulab/everest
The easiest way to update is http://www.mutools.com/mulab/app-patch/Read%20Me.txt
So just like before simply replace the MuLab.exe and MuLab.ID by the new versions. (MuLab.ID is on Windows only)
This new version should fix the issues you had when using Kirnu Cream in MuLab.
Can you please confirm all is working fine now?
sometimes a additional note or Endless Note/Note Off problem with MUX VSTi/MuLab Instruments and Kirnu Cream appears.
i have verifyed this problem also with some other VSTi but this problems only appears with MUX VSTi/MuLab instruments.
tested with:
Windows 8 64bit
MuLab 5.1.4 (32 bit)
Track1: Kirnu Cream and Instrument: Leads -> A Space Journey
Track2: Kirnu Cream and VSTi Black Mamba - LED 5th of 12
Kirnu Cream 1.0 (32 bit) - PRESET: Init, Range C2 < B7
referenced VSTi:
Black Mamba with Demo Soundbank
http://www.zampler.de
MuLab&CreamNoteOff.MuSession was sent as email attachement to mutools
MuLab&CreamNoteOff.MuSession contains a 3 time looped midi sequence
- Note Off playback problem appears already within playback of first repeated part
Last edited by Hermu on Mon May 27, 2013 12:38 pm, edited 2 times in total.
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
Researched this issue and my conclusion is that it is on Kirnu's side. Problem with the order of the outputted note ons/offs. Please send that musession + info to Kirnu. I'm open for further communication with Kirnu if necessary.
- KVRist
- 248 posts since 12 Jan, 2013
That was Cream fault alright and will be fixed in the next version 1.0.1mutools wrote:Researched this issue and my conclusion is that it is on Kirnu's side. Problem with the order of the outputted note ons/offs. Please send that musession + info to Kirnu. I'm open for further communication with Kirnu if necessary.
Which I'll release probably tomorrow.
-
- KVRer
- 10 posts since 8 Feb, 2013
reminds me of my own problem with the akaiMPK61 arpeggiator, still unsolved...at mulab5.2.16
the noteOFF might not pass cause there are stucknotes when playing, at a point it is not possible to work. especially when I seem to be fit tight to rythm.
The midi in and output ports seem wrong. the clock doesn't pass if I don't set the in AND the out to akaiMPK61. so there is a loop. and all the notes are delayed. That's obvious.
the other akai ports seem useless(midiin2(akaiMPK61) and midiout2(akaiMPK61)): they have no effects in any configuration combining port1 and/or port2 of Mulab itself. No! I didn't forget to set the midiClockOutputModule «properly» at every single test, and the keyboard (wich is brand new) was always set to external since we know for long that mulab does not support external clock. And in fact woul'd change nothing for me, ...if it worked.
Now, any trial versions of the other softwares I tried didn't do it. It could be for some other reasons and I'm not saying anything wrong about mulab, it's simply amazing. But it doesn't seem to handle realtime playing properly, wich would be a major problem in my further development. I got used to its wonderfull MUX system and the way to create sounds and effects. For a composer-writer, it's just perfect. But now I wanna play with the ALSO amazing akaiMPK61's arpeggiator, and not delayed from the metronome.
I'm using music softwares since 1991. playing music since 1977. Went to university in music. I spent almost all my life in music. I woul'd like to know if you are gonna make research about it. According to your answer, I may delay any impulsive changes.
thanx.
the noteOFF might not pass cause there are stucknotes when playing, at a point it is not possible to work. especially when I seem to be fit tight to rythm.
The midi in and output ports seem wrong. the clock doesn't pass if I don't set the in AND the out to akaiMPK61. so there is a loop. and all the notes are delayed. That's obvious.
the other akai ports seem useless(midiin2(akaiMPK61) and midiout2(akaiMPK61)): they have no effects in any configuration combining port1 and/or port2 of Mulab itself. No! I didn't forget to set the midiClockOutputModule «properly» at every single test, and the keyboard (wich is brand new) was always set to external since we know for long that mulab does not support external clock. And in fact woul'd change nothing for me, ...if it worked.
Now, any trial versions of the other softwares I tried didn't do it. It could be for some other reasons and I'm not saying anything wrong about mulab, it's simply amazing. But it doesn't seem to handle realtime playing properly, wich would be a major problem in my further development. I got used to its wonderfull MUX system and the way to create sounds and effects. For a composer-writer, it's just perfect. But now I wanna play with the ALSO amazing akaiMPK61's arpeggiator, and not delayed from the metronome.
I'm using music softwares since 1991. playing music since 1977. Went to university in music. I spent almost all my life in music. I woul'd like to know if you are gonna make research about it. According to your answer, I may delay any impulsive changes.
thanx.
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
I think these are different cases. This topic was about a Vst plugin, and you're talking about syncing the arp on an external keyboard.aodes wrote:reminds me of my own problem with the akaiMPK61 arpeggiator, still unsolved...at mulab5.2.16
Assuming you meant me with "you", i'm sorry to say that i have no plans to research any MIDI sync problem in MuLab as i don't think there is a MIDI sync prob in MuLab. I already did an extra check on MuLab's MIDI clock out last week and all looked fine.I woul'd like to know if you are gonna make research about it. According to your answer, I may delay any impulsive changes.
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
