Just to be clear, I meant MuX VST and I was testing in Reaper. Before updating MuLab, I could get the error in both. After, it worked... in both, which is weird.mutools wrote:It affects editing sequences. And as the Sequence Player uses sequences, yes this fix is also relevant to the Sequence Player.pljones wrote:By the way, does this affect the Sequence player in MuX? I think it does, if I'm testing it right.
-EDIT 2- Hm. Seems to work now. Weird.
about shortcuts
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
Elaborating myself: In M6.5.43 (=MuLab & Mux Vst) when a sequence contained mixed event types, the context functions were not right. There was not an error message but when eg. a sequence contained notes and pitchbend, the Transpose function wasn't available. That's fixed in MuLab 6.5.44. The respective MUX Vst update will follow soon. If you much need that MUX Vst update, let me know and i'll make sure it becomes available asap. Otherwise it will be soonish.
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
I mean:
I tested before the update in MuLab, using a sequence in the composer to reproduce the error and confirmed it.
I tested before the update in Reaper, using a sequence in MuX VST to reproduce the error and confirmed it.
I updated MuLab.
I tested after the update in MuLab, using a sequence in the composer to reproduce the error and it was gone.
I tested after the update in Reaper, using a sequence in MuX VST to reproduce the error and it was gone... which is weird.
I don't need MuX updated myself, I was more confused about my testing, as I'm now assuming I did it wrong...
I tested before the update in MuLab, using a sequence in the composer to reproduce the error and confirmed it.
I tested before the update in Reaper, using a sequence in MuX VST to reproduce the error and confirmed it.
I updated MuLab.
I tested after the update in MuLab, using a sequence in the composer to reproduce the error and it was gone.
I tested after the update in Reaper, using a sequence in MuX VST to reproduce the error and it was gone... which is weird.
I don't need MuX updated myself, I was more confused about my testing, as I'm now assuming I did it wrong...
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
