M8.6.28 beta
-
- KVRAF
- 5573 posts since 30 May, 2006 from Hollow Earth
My reasoning was based on speculations that, for example, Ableton could not implement MPE because they had to rewrite the very core on the applications while MIDI 2 seems to be on their plate.
So if they can do without rewriting the deep aspect of the application then it’s probably not that drastic in terms of restructuring the DAW.
So if they can do without rewriting the deep aspect of the application then it’s probably not that drastic in terms of restructuring the DAW.
ABEFLGMOPPRRST 
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
It definitely are interesting evolutions and i'll study it more in depth at the appropriate r&d time after M9 is rocking and rolling. Thx for highlighting this.
-
- KVRAF
- 5573 posts since 30 May, 2006 from Hollow Earth
MuLabmutools wrote: Sat Sep 26, 2020 7:45 pm It definitely are interesting evolutions and i'll study it more in depth at the appropriate r&d time after M9 is rocking and rolling. Thx for highlighting this.
ABEFLGMOPPRRST 
-
- KVRist
- 256 posts since 3 May, 2009
Glad that those issue were solved!
But, while using the multisampla module, i noticed that the preview from the "keyboard preview" is still routing to output instead the preview rack.
I don't know, maybe is as it.
But, i like to know that all the previews goes to the same route.
Is that possible?
Thanks thanks thanks
But, while using the multisampla module, i noticed that the preview from the "keyboard preview" is still routing to output instead the preview rack.
I don't know, maybe is as it.
But, i like to know that all the previews goes to the same route.
Is that possible?
Thanks thanks thanks
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
Thx for reporting this.FabBad wrote: Sun Sep 27, 2020 6:38 pm But, while using the multisampla module, i noticed that the preview from the "keyboard preview" is still routing to output instead the preview rack.
Will be fixed in the next update.
-
- KVRist
- 256 posts since 3 May, 2009
Jo, i have been using Mulab for much more time lately and is better and better everyday, so i was stumbled with a couple of bugs;
-set interpolation mode is missing in the shorcut list
-there's a delay response in contextual menus
-pressing "e" on a midi or audio secuence in the stream view it hit the same edit shortcut as that is assigned to module in mux area
-similar to abobe, some shorcuts don't correspond to assigned view (see gif)
-strange behavior when zooming in fullscreen (see gif 2)
-"drag parameter" doesn't works when it uses shortcuts (see gif 3)
and finally a aesthetic issue (LOW priority), the ruler level view is a bit unnecessary oversized
Thank you for your great work
Regards
FaB
-set interpolation mode is missing in the shorcut list
-there's a delay response in contextual menus
-pressing "e" on a midi or audio secuence in the stream view it hit the same edit shortcut as that is assigned to module in mux area
-similar to abobe, some shorcuts don't correspond to assigned view (see gif)
-strange behavior when zooming in fullscreen (see gif 2)
-"drag parameter" doesn't works when it uses shortcuts (see gif 3)
and finally a aesthetic issue (LOW priority), the ruler level view is a bit unnecessary oversized
Thank you for your great work
Regards
FaB
You do not have the required permissions to view the files attached to this post.
-
- KVRAF
- 2270 posts since 30 Aug, 2004 from Lancaster, UK
Wow, how much one can learn through reading this kind of thread!
Drag parameter was news to me. I'm thinking that since I can ctrl-drag an instrument or effect from one rack to another to duplicate it (a feature I use A LOT), ctrl-drag could perhaps also be used for, say, a volume fader., and perhaps in all sorts of places. So: same result as Drag parameter, but a tad quicker.
But maybe that conflicts with other stuff and it's not that important I guess, so no sweat!
Drag parameter was news to me. I'm thinking that since I can ctrl-drag an instrument or effect from one rack to another to duplicate it (a feature I use A LOT), ctrl-drag could perhaps also be used for, say, a volume fader., and perhaps in all sorts of places. So: same result as Drag parameter, but a tad quicker.
But maybe that conflicts with other stuff and it's not that important I guess, so no sweat!
Thu Oct 01, 2020 1:15 pm Passing Bye wrote:
"look at SparkySpark's post 4 posts up, let that sink in for a moment"
Go MuLab!
"look at SparkySpark's post 4 posts up, let that sink in for a moment"
Go MuLab!
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
That will be fixed in the next update.
Please elaborate, maybe with a video.-there's a delay response in contextual menus
If you use the same key for different shortcuts, but those shortcuts are both relevant in the context you're pressing that shortcut key, then indeed you can cause ambiguous situations.-pressing "e" on a midi or audio secuence in the stream view it hit the same edit shortcut as that is assigned to module in mux area
-similar to abobe, some shorcuts don't correspond to assigned view (see gif)
wrong shortcuts in wrong place.gif
For example in the example with the N = Edit in Audio Lab and N = Normalize, when you hit N on an audio part then both these functions are relevant, and but only one of them can be triggered.
In such case it's better to use different shortcut keys.
I'll reply on the other issues soon.
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
Please give me step by step how to repeat this.FabBad wrote: Wed Sep 30, 2020 4:26 am -strange behavior when zooming in fullscreen (see gif 2)strange behaviour in the redraw waveform on audio stream2.gif
Will be fixed in the next update.-"drag parameter" doesn't works when it uses shortcuts (see gif 3)drag parameter shortcut doesn't works.gif
It uses the same width as the piano keyboard in the midi sequence editor. This may be important when stacking editors vertically so that the time line is aligned.and finally a aesthetic issue (LOW priority), the ruler level view is a bit unnecessary oversized
2020-09-30_005258.png
Thanks for reporting those issue and for your constructive feedback
-
- KVRist
- 256 posts since 3 May, 2009
Please elaborate, maybe with a video.-there's a delay response in contextual menus
well, maybe i have to much assignations, would be nice a dupe detection, i don't know, highlighting the duplicates i guess..If you use the same key for different shortcuts, but those shortcuts are both relevant in the context you're pressing that shortcut key, then indeed you can cause ambiguous situations.
I Said strange because is most common in fullscreen and the file must be long enough.Please give me step by step how to repeat this.-strange behavior when zooming in fullscreen (see gif 2)strange behaviour in the redraw waveform on audio stream2.gif
_Load a audiofile with lenght greater than 10 seconds aprox directly to audiostream
_zoom in and out and see that there's a one zoom view that the waveform disapears.
Also, when a load an another audio file with diferent sample rate (96KHz), it seems to reproduce the same issue, but, the other one is functioning normaly.
ahh, nice! it makes sense now.It uses the same width as the piano keyboard in the midi sequence editor. This may be important when stacking editors vertically so that the time line is aligned.
Thanks Jo!
You do not have the required permissions to view the files attached to this post.
-
- KVRist
- 256 posts since 3 May, 2009
Well, now in another project, suddenly the synths stop working and when i close the program it pops up a notice "Logged 2 errors".
Viewing the log file... i can see the "Error PEG[217]" in it.
What is it means?
thanks again
Viewing the log file... i can see the "Error PEG[217]" in it.
What is it means?
thanks again
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
That's odd.FabBad wrote: Thu Oct 01, 2020 7:48 pmDelayed response 2020-10-01.7zPlease elaborate, maybe with a video.-there's a delay response in contextual menus
sometimes is worse 2020-10-01.7z
When does that happen?
Does it only happen in specific projects?
If it happens and you quit MuLab and reload the same project then is it still the same behavior?
If it happens in project X and when you then do New Project then is it still the same behavior?
Ok, i could repeat a similar issue. Will look into it.-strange behavior when zooming in fullscreen (see gif 2)strange behaviour in the redraw waveform on audio stream2.gif
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
Could it be that you're using Parameter Event Generators that are sending out an extreme amount of events?FabBad wrote: Fri Oct 02, 2020 1:42 am Well, now in another project, suddenly the synths stop working and when i close the program it pops up a notice "Logged 2 errors".
Viewing the log file... i can see the "Error PEG[217]" in it.
What is it means?
thanks again![]()
-
- KVRist
- 256 posts since 3 May, 2009
all the time.When does that happen?
any projectDoes it only happen in specific projects?
it persist from beginning and is there until i close the program.If it happens and you quit MuLab and reload the same project then is it still the same behavior?
Yes, the same behavior.If it happens in project X and when you then do New Project then is it still the same behavior?
Even happends in MUX as a plugin in other hosts.
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
I'm amazed that you say that it happens always as the first video you shared it seems to only happen in that second project window, not in the first. No?
Are you on windows or macos?
Are you using some special input device or a special setup?
Can you repeat the issue on another computer?
Is anyone else also encountering a delay when popping up context menus?
Are you on windows or macos?
Are you using some special input device or a special setup?
Can you repeat the issue on another computer?
Is anyone else also encountering a delay when popping up context menus?
