MuTools

fluffy_little_something · Sat Jul 28, 2012 5:34 pm

mutools wrote:
fluffy_little_something wrote:Mine has crashed twice upon quitting, don't know if it is the same issue, though. Did it say something about a serious error and that it would try to save as much as possible?
Are you on OSX?

Besides that question, please do the same Vst test described above.

No, Windows 64. I only use one external VST, but I was not sure if it was because of that. I use it all the time and usually there are no crashes at all. Maybe it is a memory or OS issue as some other programs also tend to crash more readily (not just on my computer) as the workload grows, for instance some graphics programs.

DHR53 · Post by **DHR53** » Sat Jul 28, 2012 5:38 pm

The VSTs I'm currently using in most of my compositions are:

Vanguard, FM8, Albino 3, Musynth, MuDrum, Zebra 2 and Blue. This composition has a lot of Vanguards though, which I use a lot because it's very cpu efficient and I have a lot of sounds for it. I use a very small set of VIs in general, which I have a lot of sounds for, but most are in my arsenal because of those 2 reasons...

MuTools · Post by **MuTools** » Sat Jul 28, 2012 5:42 pm

I can't comment whether or not these are ok vst plugins. I cannot test each and every version of each and every vst plugin. If you want to get rid of the crashes, please do a critical elimination test as described before. If there is a bug in MuLab, i'll be there to help and fix. At this point i have no reason to suspect MuLab.

DHR53 · Post by **DHR53** » Sat Jul 28, 2012 7:18 pm

Well I just tried to load Zebra 2 in the song I've been working on and MuLab crashes every time. Then I loaded my template, and loaded Zebra 2 - same thing. Can't use the program if I can't use the (very few) plugins I use regularly... not sure how many plugs the Mac version has been tested with but these are not "unusual" plugins but the oldest and most widely used. I'm not going to go on and on about "my situation" as I guess other people are not having issues (PC version?) But I'm a little disappointed at this point... Did not want to go back to Logic.

Bummer!

MuTools · Post by **MuTools** » Sat Jul 28, 2012 7:33 pm

I'll test zebra 2 in MuLab 4.3.10 on OSX and report back.

DHR53 · Post by **DHR53** » Sat Jul 28, 2012 10:02 pm

O.K. I deleted Zebra and reloaded it and it's working now... Not sure what that means but it seems that the many versions I've loaded and reloaded are starting to break stuff?

zendorf · Post by **zendorf** » Sun Jul 29, 2012 10:57 am

I certainly have had no problems using Zebra in Win7. It is my main synth and I have tons of instances of it in Mulab and Mux Vst with no issues to speak of.

DHR53 · Post by **DHR53** » Sun Jul 29, 2012 12:01 pm

For the record... This is the Mac version of MuLab. I have a Macbook C2 duo 2.2ghz w/4gig of ram. OSX 10.6.8. Zebra has always been one of my main synths as I could get up to 20 instances running in Logic. Most of the synths I mentioned are super efficient on the Mac... That's why I use em'

And they sound good too

MuTools · Post by **MuTools** » Sun Jul 29, 2012 12:19 pm

mutools wrote:I'll test zebra 2 in MuLab 4.3.10 on OSX and report back.

Unfortunately i can't even plug-in Zebra 2 in MuLab 4.3.10 OSX, i got an "Invalid Vst plugin" alert on my system. I checked things out and reason is my mac is on OSX 10.4 and Zebra needs at least 10.5. OSX seems to break compatibilities often. Almost with every new animal they come up with, they break some compatibilities with previous versions. I know i'm not the only one suffering from that. I suspect this is no coincidence but rather an Apple strategy, forcing users and developers to upgrade their software and hardware all the time

DHR53 · Post by **DHR53** » Sun Jul 29, 2012 2:17 pm

Ughh... That's probably why Logic is the only DAW that works most of the time in OSX. And that's not saying much...

fluffy_little_something · Sun Jul 29, 2012 4:09 pm

I am really no Apple fan, quite to the contrary (never spent a single cent on anything Apple

), but 10.4 has already been around for 7 years, 10.5 for 5 years, there seems to be a new version every two years, currently 10.8

As a developer it might be better to always use the latest version. I mean, you can't develop your software for Windows XP anymore, either

pljones · Post by **pljones** » Mon Jul 30, 2012 7:11 am

fluffy_little_something wrote:I mean, you can't develop your software for Windows XP anymore, either

The point is, you can quite effectively write software that runs on Win2000 onwards without change (32-bit) and WinXP64 onward with minimal changes (64bit) and that are backward compatible (as far as XPSP3) if you stick within certain restrictions (that rarely get in the way). Certainly I've not heard many people here saying they've been forced to upgrade from WinXP to Win7 because a VST plugin doesn't work. They might have to upgrade their host to support a later VST version, as newer versions of that standard have emerged, but that's a different issue. It's rare to need to upgrade the underlying OS.

MuTools · Post by **MuTools** » Wed Aug 08, 2012 8:50 am

DHR53 wrote:Very strange. I don't have a clue where this default location is coming from when I load a sequence. It seems to have a mind of it's own. I just loaded a sequence with the favorites folder than closed the window... went back in and it's going back to the same location? Somewhere that has nothing to do with the program. I would say it was the system, but this is a brand new install of Snow Leopard on a reformatted drive.

I'm still amazed that you have this issue. I checked it again on OSX and all is working as intended: When i save or load an individual sequence the file browser open at the last used location.

Maybe we're talking about different things?
Can you please make a screencast of that problem so i can see what's happening.

MuTools

KVR Audio

Mus...ings