Yep improved in the next version, coming soon.mutools wrote:At the moment the end point of the line is regarded as exclusive = not inclusive. I'll see if i can change that. I agree that would be more relevant from user pov.Reincke wrote:Similar prob occured (pre 6.4.21) also on curves (e.g. pitch bend). Trying to get a curve from e.g. 0.5 down to 0 often (but not always) results in different values, although 0 was displayed in value preview. Is this fixed too? I often work with pitch bends in the event graph editor.
MuLab 6.4.26 Test
-
- KVRAF
- Topic Starter
- 13865 posts since 24 Jun, 2008 from Europe
-
- KVRist
- 409 posts since 26 Jul, 2010 from Germany
-
- KVRAF
- Topic Starter
- 13865 posts since 24 Jun, 2008 from Europe
There is a new MuLab 6.4.23 test version in http://www.mutools.com/forsythia
Changes since M6.4.22:
OSX: Simply replace the MuLab.app by the new version.
Windows: Simply replace the MuLab.exe + MuLab.ID files by the new versions.
Changes since M6.4.22:
- Finetuned display position of the window title text, avoiding the text to go under the window buttons. Especially relevant on OSX where the title text is centered.
- Fixed an issue that sometimes caused jacks to have irrelevant names.
- MUX front panel: On adding a new module button, it now has an On/Off button by default. (previously the default was not to have such button)
- Composer: Lassoing parts could select parts on collapsed tracks. Fixed.
- Event Graph Editor: Line edits are now end point inclusive.
And ensured that when drawing pitchbend/controller/parameter event curves that the end value is exactly as intended.
OSX: Simply replace the MuLab.app by the new version.
Windows: Simply replace the MuLab.exe + MuLab.ID files by the new versions.
-
- Banned
- 1132 posts since 21 Feb, 2015
Superb! Yes, I hope you do keep it like that Jo. It is a nice elegant design, like tabs. I use those buttons alot! Nice and fast.mutools wrote:I'll keep it as is.Reincke wrote:Any comments regarding the composer button question?
-
- KVRAF
- Topic Starter
- 13865 posts since 24 Jun, 2008 from Europe
There is a new MuLab 6.4.24 test version in http://www.mutools.com/forsythia
Changes since M6.4.23:
OSX: Simply replace the MuLab.app by the new version.
Windows: Simply replace the MuLab.exe + MuLab.ID files by the new versions.
Changes since M6.4.23:
- Upon deleting multiple connections, the popup question had a little text error after the connection count. Fixed.
- Modular Editor: While holding [Shift] clicking the background does not clear the selection anymore. This makes it easier to multi-select cables.
- Changing the MIDI Setup now properly updates the MIDI input and output module names.
- Fixed a low level bug that could possibly cause a crash in certain specific cases, eg sometimes when closing a project or when quitting.
- Modular editor: Right-click module jack now only pops up context menu when relevant.
- MUX Modular: In and out jacks now have same name as the respective in and out modules in the modular editor of that MUX.
- MUX VST: Improved propagation of the audio input and output names towards the host.
- Note To Modulation Converter now has a Low and High Key which define the note key range.
Notes lower than low key will generate the minimum value, notes higher than high key will generate the maximum value.
If you don't want that notes outside the defined key range cause a modulation value update, insert a Note Filter before the Note To Modulation Converter.
OSX: Simply replace the MuLab.app by the new version.
Windows: Simply replace the MuLab.exe + MuLab.ID files by the new versions.
-
- KVRist
- 179 posts since 26 Feb, 2007
Spot on! Great job.mutools wrote: Note To Modulation Converter now has a Low and High Key which define the note key range.
Notes lower than low key will generate the minimum value, notes higher than high key will generate the maximum value.
tL.
Professional.
-
- KVRAF
- Topic Starter
- 13865 posts since 24 Jun, 2008 from Europe
There is a new MuLab 6.4.25 test version in http://www.mutools.com/forsythia
Changes since M6.4.24:
OSX: Simply replace the MuLab.app by the new version.
Windows: Simply replace the MuLab.exe + MuLab.ID files by the new versions.
Please note that M6.4.25 really is a test version. Asking for testers here. Due to a couple of bug reports i had to make some low level changes and though i think everything is ok, making these low level code changes may have consequences i didn't think of. If that would be the case that should become clear quite fast. So please do test M6.4.25 as much as possible, the sooner it proves to be ok, the sooner i can continue on the next wishes. Of course i'll continue testing too. In case M6.4.25 would not be ok you can return to M6.4.24, that's why i left that version in the forsythia folder for now. Cheers!
Changes since M6.4.24:
- Fixed a bug when creating new modular inputs and outputs via copy-paste or ctrl-drag.
- Added special (hidden) support to correct a wrong modular io setup as a consequence of the bug described above:
MUX or PolySynth module context menu -> Rename -> enter "__cl" (without quotes) -> enter "reset modular io" (without quotes). - Event Graph Editor and Envelope Editor: In case of bipolar curves/envelopes, there now is improved behavior wrt the middle zero line.
- Improved handling of pitchbend events resulting in several advantages:
* Pitchbend events now properly travel thru a rack, no blocking at the pre/post point anymore.
* You can use pitchbend as a controller to a parameter and meanwhile also use it to keep on controlling pitch bend, if you want.
OSX: Simply replace the MuLab.app by the new version.
Windows: Simply replace the MuLab.exe + MuLab.ID files by the new versions.
Please note that M6.4.25 really is a test version. Asking for testers here. Due to a couple of bug reports i had to make some low level changes and though i think everything is ok, making these low level code changes may have consequences i didn't think of. If that would be the case that should become clear quite fast. So please do test M6.4.25 as much as possible, the sooner it proves to be ok, the sooner i can continue on the next wishes. Of course i'll continue testing too. In case M6.4.25 would not be ok you can return to M6.4.24, that's why i left that version in the forsythia folder for now. Cheers!
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
For pitchbend, I wasn't sure on a test for the original problem so I tried this:
Rack 1, send from first slot to Rack 2
Rack 1, send from last slot to Rack 3
Rack 2 - Alpinski (responds to PB at note on but not during note)
Rack 3 - Basic Synth (responds to PB in real time)
Both synths behaved as expected (and actually sounded very interesting together...).
Not sure at all how I would have triggered the problem with the modular I/Os but nothing crashed when I used the "reset modular io" command.
(Meanwhile, ctrl-drag to copy Rack 1 left it unconnected -- but that's a different FR altogether).
Rack 1, send from first slot to Rack 2
Rack 1, send from last slot to Rack 3
Rack 2 - Alpinski (responds to PB at note on but not during note)
Rack 3 - Basic Synth (responds to PB in real time)
Both synths behaved as expected (and actually sounded very interesting together...).
Not sure at all how I would have triggered the problem with the modular I/Os but nothing crashed when I used the "reset modular io" command.
(Meanwhile, ctrl-drag to copy Rack 1 left it unconnected -- but that's a different FR altogether).
-
- KVRAF
- Topic Starter
- 13865 posts since 24 Jun, 2008 from Europe
Thanks for testing!pljones wrote:For pitchbend, I wasn't sure on a test for the original problem so I tried this:
Rack 1, send from first slot to Rack 2
Rack 1, send from last slot to Rack 3
Rack 2 - Alpinski (responds to PB at note on but not during note)
Rack 3 - Basic Synth (responds to PB in real time)
Both synths behaved as expected (and actually sounded very interesting together...).
The original bug and how to reproduce it was talked about here: http://www.kvraudio.com/forum/viewtopic ... 9&t=437469Not sure at all how I would have triggered the problem with the modular I/Os but nothing crashed when I used the "reset modular io" command.
Do you mean copying a send?Meanwhile, ctrl-drag to copy Rack 1 left it unconnected -- but that's a different FR altogether.
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Thanks - I'll take a look.mutools wrote:The original bug and how to reproduce it was talked about here: http://www.kvraudio.com/forum/viewtopic ... 9&t=437469Not sure at all how I would have triggered the problem with the modular I/Os but nothing crashed when I used the "reset modular io" command.
No - in the Session MuX, racks with sends to other racks (as described above), show with connections. If I ctrl-drag to copy such a rack (Rack 1 in the example), it ends up with the sends in the slots but the connections are lost. There's another thread about this, I believe.mutools wrote:Do you mean copying a send?Meanwhile, ctrl-drag to copy Rack 1 left it unconnected -- but that's a different FR altogether.
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
I had a go at reproducing the drag input to get ghosts but couldn't recreate it.
What I did notice (again, I think reported elsewhere) was some strange lasso+drag copy behaviour.
Set up:
1) Create more than one module in mux
2) Deselect all module (click the mux background)
3) Lasso all the modules
First go:
4.1) Press-hold control, click-drag one of the selected modules
Expected result is that all the modules are drag-copied.
Actual result is that only the clicked module is drag-copied.
Second go (after setting up again):
4.2) Click-drag one of the selected modules, press-hold control before releasing the drag
Expected and actual result is that all the modules are drag-copied.
I'm uncomfortable that the two work differently - it doesn't seem quite right.
What I did notice (again, I think reported elsewhere) was some strange lasso+drag copy behaviour.
Set up:
1) Create more than one module in mux
2) Deselect all module (click the mux background)
3) Lasso all the modules
First go:
4.1) Press-hold control, click-drag one of the selected modules
Expected result is that all the modules are drag-copied.
Actual result is that only the clicked module is drag-copied.
Second go (after setting up again):
4.2) Click-drag one of the selected modules, press-hold control before releasing the drag
Expected and actual result is that all the modules are drag-copied.
I'm uncomfortable that the two work differently - it doesn't seem quite right.
-
- KVRAF
- 3207 posts since 17 Apr, 2010 from Slovenia
Anyone having trouble with copying sequences/making unique sequence?!
When I now [ctrl]+drag copy a sequence it is empty.
If I copy and paste, it creates another instance of the same sequence, but if I make it unique it's empty again.
When I now [ctrl]+drag copy a sequence it is empty.
If I copy and paste, it creates another instance of the same sequence, but if I make it unique it's empty again.
-
- KVRAF
- Topic Starter
- 13865 posts since 24 Jun, 2008 from Europe
To avoid confusion: It was a bug in M6.4.24 but has been fixed in M6.4.25.pljones wrote:I had a go at reproducing the drag input to get ghosts but couldn't recreate it.
Confirmed, will fix asap.What I did notice (again, I think reported elsewhere) was some strange lasso+drag copy behaviour.
-
- KVRAF
- Topic Starter
- 13865 posts since 24 Jun, 2008 from Europe
Confirmed, it's a consequence of the low level changes i made, missed that consequence. No prob, will fix asap. Thanks for reporting!Taron wrote:Anyone having trouble with copying sequences/making unique sequence?!
When I now [ctrl]+drag copy a sequence it is empty. If I copy and paste, it creates another instance of the same sequence, but if I make it unique it's empty again.
-
- KVRAF
- 3207 posts since 17 Apr, 2010 from Slovenia
np