Mautoalign crashes
-
- KVRer
- 4 posts since 12 Feb, 2016
Having an issue with some Melda plugins. Mostly on MAutoAlign and MAutoVolume, MAutoDynamicEQ where selecting the morph presets button immediately crashes the host. Happens only 1 in 4 times or so but completely crashes host. Mac OS x el capitan on audacity, mulab, and studio one 3. Anyone else or any fixes? In audacity sometimes triggers Wxwidgets debug and selecting any option, yes, no or cancel just crashes.
-
- KVRian
- 915 posts since 2 May, 2015
...could you put your system "particulars" including current versions in you sig...I fooled around some with what you provided on my rig...all "seems" ok...those three plugs are all over my projects currently and "no worries" here...
.../s~
.../s~mba m2 15" | 16gig.ram | 1tb ssd | macOS 26.1 Tahoe
logic 11.2.2 | reaper 7.75 | cubase 14.0.4
focusrite.2i2 | A&H CQ18t
logic 11.2.2 | reaper 7.75 | cubase 14.0.4
focusrite.2i2 | A&H CQ18t
-
- KVRer
- Topic Starter
- 4 posts since 12 Feb, 2016
Update: Problems continuing on all my DAW's with MAutoAlign (almost 100% of time in the "A" preset.
Have looked around, sent emails to Melda and the problem is still persisting. Am adding links to two youtube videos I made showing the issue. Ignore what I'm doing with the preset morphing. With lack of any documentation on how that is supposed to be used I've just been tinkering with it to see how it can be used. The problem occurs without doing any of the preset morphing.
In essence this is what is happening:
The problem is happening when the plug in is opened, by default I think is chooses the A channel preset? If that is correct then what I am seeing is that whatever channel is the default channel/preset setting when the plug in is first launched, is the channel that is having the issue. What I seem to be noticing is that the default channel with the default settings, will show the error seen in the video when running MAutoAlign the first time it's opened.
Example:
Plugin launched, settings kept at default.
Selected all channels from the DAW/Audio Editor (all channels have audio, no blank tracks).
No other plugin running, just MAutoAlign.
Audio is played, either from the Play button in the plugin (in Audacity the plugin opens with a play, rew and ff button on bottom left corner of plugin screen) or from the play button in the DAW/Audio Editor.
From within the plugin and while the audio is playing am selecting "Analyze".
Plug in usually comes back with the error message. (nearly 100% of time on "A" preset).
I usually then re-do the above, and with audio playing again, will select "INV" in the plug-in.
Often then the plugin will show the activity in the plug-in screen. Usually the first time on default settings I don't see anything in the plug-in monitor screen.
So I can see the audio playing from the plug-in monitor, and then select "analyze".
What is confusing here is that sometimes the plugin runs with no error and sometimes the error comes up, even when I can see (and hear) audio showing in the plug-in monitor screen.
Until 9.18 I could always get the plugin to run by changing the preset from "A" to "G" (for example). The error almost always happens on the "A" preset. (Again, all tracks have audio). Usually then the plugin would run with no error, regardless if "INV" or "main track" was selected.
For some reason starting at ver 9.18 the error started coming up again when I changed the default preset from "A" to "G" so that now the error comes up (randomly it seems) on any channel preset. Running it a couple of times may or may not show the error again. For example can run the plugin and get the error, then make no changes and immediately run it again and it may or may not show the error a 2nd time.
That is the part I'm confused about. If the error happens on one setting, then nothing changed and the plugin run again, why does it run fine the second time (or 3rd or 5th) but not the first (or 4th, etc)? That is why the error just appears random to me.
above is referring to Mac OS X El Capitan and also Windows 8.1. occurs in Pro tools, Studio One, Logic Pro and Audacity.
here are the youtube links to videos:
this is in ProTools on Windows 8.1
next on in Audacity (please no comments slamming Audacity) on Mac OS X El Cap:
Have looked around, sent emails to Melda and the problem is still persisting. Am adding links to two youtube videos I made showing the issue. Ignore what I'm doing with the preset morphing. With lack of any documentation on how that is supposed to be used I've just been tinkering with it to see how it can be used. The problem occurs without doing any of the preset morphing.
In essence this is what is happening:
The problem is happening when the plug in is opened, by default I think is chooses the A channel preset? If that is correct then what I am seeing is that whatever channel is the default channel/preset setting when the plug in is first launched, is the channel that is having the issue. What I seem to be noticing is that the default channel with the default settings, will show the error seen in the video when running MAutoAlign the first time it's opened.
Example:
Plugin launched, settings kept at default.
Selected all channels from the DAW/Audio Editor (all channels have audio, no blank tracks).
No other plugin running, just MAutoAlign.
Audio is played, either from the Play button in the plugin (in Audacity the plugin opens with a play, rew and ff button on bottom left corner of plugin screen) or from the play button in the DAW/Audio Editor.
From within the plugin and while the audio is playing am selecting "Analyze".
Plug in usually comes back with the error message. (nearly 100% of time on "A" preset).
I usually then re-do the above, and with audio playing again, will select "INV" in the plug-in.
Often then the plugin will show the activity in the plug-in screen. Usually the first time on default settings I don't see anything in the plug-in monitor screen.
So I can see the audio playing from the plug-in monitor, and then select "analyze".
What is confusing here is that sometimes the plugin runs with no error and sometimes the error comes up, even when I can see (and hear) audio showing in the plug-in monitor screen.
Until 9.18 I could always get the plugin to run by changing the preset from "A" to "G" (for example). The error almost always happens on the "A" preset. (Again, all tracks have audio). Usually then the plugin would run with no error, regardless if "INV" or "main track" was selected.
For some reason starting at ver 9.18 the error started coming up again when I changed the default preset from "A" to "G" so that now the error comes up (randomly it seems) on any channel preset. Running it a couple of times may or may not show the error again. For example can run the plugin and get the error, then make no changes and immediately run it again and it may or may not show the error a 2nd time.
That is the part I'm confused about. If the error happens on one setting, then nothing changed and the plugin run again, why does it run fine the second time (or 3rd or 5th) but not the first (or 4th, etc)? That is why the error just appears random to me.
above is referring to Mac OS X El Capitan and also Windows 8.1. occurs in Pro tools, Studio One, Logic Pro and Audacity.
here are the youtube links to videos:
this is in ProTools on Windows 8.1
next on in Audacity (please no comments slamming Audacity) on Mac OS X El Cap:
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122 - KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
We were talking over email, so my last reply still stands:
Anyways I think you are sort of causing it with all that preset "madness".
Here's the thing, pretty much everything you did in that video didn't make sense. Using ABCD morphing doesn't make sense and it will certainly not improve the results. This feature is mostly for the creative effects. You'd first need to edit A settings somehow, samething for B, C, D. Then you'd use the morphing to morph between all these settings. But you didn't really do anything with A,B,C,D, not mentioning there's nothing creative to do. I even think we should remove the morphing from MAutoAlign, it just doesn't make sense. You also moved the grid in such a way that it made all of it even more useless. Changing INV prior to analysis is also useless.
So, from now, please do NOT use presets, do NOT use morphing, do NOT use A,B,C... snapshots. None of it is usefull for the plugin. You simply put it on all tracks, select Group for each if needed (it does NOT change the settings anyhow! it's just for you), potentially change the maximum delay and analyze. That's all. Just keep it simple
.
Anyways I think you are sort of causing it with all that preset "madness".
Here's the thing, pretty much everything you did in that video didn't make sense. Using ABCD morphing doesn't make sense and it will certainly not improve the results. This feature is mostly for the creative effects. You'd first need to edit A settings somehow, samething for B, C, D. Then you'd use the morphing to morph between all these settings. But you didn't really do anything with A,B,C,D, not mentioning there's nothing creative to do. I even think we should remove the morphing from MAutoAlign, it just doesn't make sense. You also moved the grid in such a way that it made all of it even more useless. Changing INV prior to analysis is also useless.
So, from now, please do NOT use presets, do NOT use morphing, do NOT use A,B,C... snapshots. None of it is usefull for the plugin. You simply put it on all tracks, select Group for each if needed (it does NOT change the settings anyhow! it's just for you), potentially change the maximum delay and analyze. That's all. Just keep it simple
.