MuLab 10.1.25

[tiger001]

should we install this beta or keep going strong with ML 10 ?

(i ask because i don't use plugins)

[MuTools]

MuLab App M10.1.7 beta for Win64 and Mac is available on https://www.mutools.com/mulab/app/lates ... /beta.html

MuLab Plugin M10.1.7 beta for Win64 is available on https://www.mutools.com/mulab/plugin/la ... /beta.html

What's changed:

• Improved Plugin Manager: Couple of small bug fixes as reported yesterday by pljones. Thx pljones!
• Improved plugin scanning on Mac. Thx Michael for your reports!
• Important bug fix when scanning the system for files and there are files containing a '%' character.
  This could cause a crash on both Windows and MacOS. Nasty long term bug. Fixed.
• Added "Delete" to the context menu of plugins in the project browser.
• Other small improvements.

[MuTools]

should we install this beta or keep going strong with ML 10 ?
(i ask because i don't use plugins)

You're very welcome to start using this M10.1.7 beta.
The main changes compared to M10.0 are plugin related.
But it's still a beta. If you notice bad things, let me know.

[MuTools]

OK, so when I rerun a full scan over Program Files, a ton of DLLs are found and MuLab happily doesn't crash (having been told to skip jsoundds.dll). When I go into Plugin Manager, VST2, Effects, I see a whole bunch of stuff...

Using M10.1.7 do Plugin Manager -> Options -> Rescan All.
That should fix it ie. it should move 7zip etc to the Unrecognizeds group.

[pljones]

Does this clarify it?

No, you basically repeated what I'd posted. I don't think you understood. I'm after a way to delete the custom name I set previously. I don't want it any more. I can't set it to empty, as far as I could tell. So I'm asking "Where's the delete option?".

[pljones]

OK, so when I rerun a full scan over Program Files, a ton of DLLs are found and MuLab happily doesn't crash (having been told to skip jsoundds.dll). When I go into Plugin Manager, VST2, Effects, I see a whole bunch of stuff...

Using M10.1.7 do Plugin Manager -> Options -> Rescan All.
That should fix it ie. it should move 7zip etc to the Unrecognizeds group.

Yep, worked perfectly now! Thanks.

[pljones]

Does this clarify it?

No, you basically repeated what I'd posted. I don't think you understood. I'm after a way to delete the custom name I set previously. I don't want it any more. I can't set it to empty, as far as I could tell. So I'm asking "Where's the delete option?".

OK, maybe I misunderstood you -- yes, using edit and then setting the field to empty does delete it. I'm sure I tried that before...

[MuTools]

yes, using edit and then setting the field to empty does delete it. I'm sure I tried that before...

Yes that's the way indeed.

[sl23]

I am getting a weird error in playback of an audio sequence. Will try to explain, but might be best to send project if easier.
I recorded two samples of my Roland S-1 pattern. Both are the same pattern with different filter position.
I add the open filter sample and it plays ok.
Then i add the closed filter sample and it causes the first to start playback with first beat as open, then the rest as closed filter.
This happens even if I mute or remove the closed sample entirely.
I will email the project...
Never mind, I found the issue... It was the Audio settings needing to be 48000Hz!

[PelletProject]

I have been experiencing a particular bug that I couldn't place for about a month now, affecting some of my projects, but I haven't been able to replicate it reliably until now.

When going between projects, especially larger ones, there is a chance that one or more occupied slots within racks may stop functioning. Audio will stop passing through, affecting everything after in the chain. The corresponding Rack's modular area doesn't see any changes, so the particular module is broken until it gets replaced or deleted. This is true for stock modules and VSTs, and it happens regardless of if VSTs are used in a given project file at all. Thankfully, it does not permanently break the project file itself, and it can resolve by restarting the project.

An additional note on this bug: There seems to be a repeatable factor involved, as when testing between two project files I had, it would consistently break the same slots on one or both projects.

I will email you a test project file I made to highlight what I mean.

[sl23]

That's the exact issue I had. But mine only ever happened with W1 Limiter, so I thought that was the problem. It would block the audio, but bypassing the plugin would restore audio. To fix the issue, all I could do was replace the plugin with a new instance in the same slot.
If I didn't replace and just restarted the project, the issue remained as part of the project itself.

[MuTools]

That's the exact issue I had. But mine only ever happened with W1 Limiter, so I thought that was the problem. It would block the audio, but bypassing the plugin would restore audio. To fix the issue, all I could do was replace the plugin with a new instance in the same slot.
If I didn't replace and just restarted the project, the issue remained as part of the project itself.

Attention, it's not because results may be alike that cause is alike.
I mean: Possibly these are 2 different issues. I don't know.
I couldn't repeat Pellet Project's issue but i'll follow up via email.
Pellet Project's test project is without any plugin, while you're talking about a plugin.
Once plugins are involved we may have a different case.
Also: When Pellet Project relaunches MuLab and reopens the project, all is fine again.
That's essentially different from what you write.

So my question to you sl23 is: Do you have a step-by-step, starting with launching M10.1.7, which repeats the issue you encounter each and every time?

[MuTools]

PS: If you have such project, please minimize it as much as possible (1: delete plugin 2: save 3: retest. Goto step 1.) until the issue disappears. Then use the previous test version, ie. the last minimized project version that still repeats the issue, to doublecheck the issue and send it to me. Thx.

[MuTools]

Meanwhile i found the bug reported by Pellet Project.
That one will be fixed in the next M10.1.8.
It's certainly a bug that only caused 'temporary' trouble ie. audio not coming thru a module,
but upon (saving and) reloading the project it's ok again. It's not something that affects a project file.

@sl23: You wrote that the issue you encountered is something that is saved in the project.
So this must be a different issue.
Please provide details to narrow it down, preferably a minimized project that repeats the issue, as described in my prev post.

[sl23]

Thanks Jo, and yes, of course, I agree, it could well be an entirely different issue.
I have updated all my projects since having that problem, so have nothing to share at present. But if I get it again, then yes, I will send to you a simple repeatable project.
For now, just ignore my post as I haven't come across it in about 6-9 months. It may have even been resolved?
I just mentioned it as PelletProjects issue was virtually identical to mine. I did post about it before, but there was no resolution then.