How's development going?

[theorize]

Just wondering what's going on with MuLab development in general, I've been away for a while I had to put it down for a while along with the rest of vst land. I got so tired of things not working right (still tired of that but i blame the VST standard for that one) and not being able to find a host that had a good workflow, was stable, easy to look at and well just meshed well with me. I've got a lot of software too, well not ALL of it but way more than I should to need to make music, although out of all of it MuLab is the one I'm the most hopefull for. It's really got a lot going for it, number one it's simplicity. Even though it appears simple it's really not, and that to me is the key because even though most things I do are rather simple there's always those patches and routings and what not that are rather complex and it's nice to have a host that has that kind of capability but doesn't have it in your way. A prime example of the opposite is Reaper. Wow that host has a SHIT TON of features but damn I refuse to sift through them (although I try) just to get to the ones I USE THE MOST. I don't know how to say exactly what I mean I guess, but it's something like personally for me JO you have the best vision I've seen in a host so far but it needs to be more effortless. What I'm talking about is things like workflow issues, it could really be a hell of a lot faster to do. Things like dragging files from the browser onto the keyboard map for the sampler, there's lots of potential for using the multisampler (the modular one) as a drum machine but getting the samples in and out of it (and your project) quickly is a must. The framework is there it just needs to be streamlined. And I think I've said this before but you shouldn't have to go to the i don't know what to call it it's been a while but the place in the project where all your samples are stored just to get that sample out. things should be localized, if I put a sample in the sampler then i should be able to take it out without having to go back to another section of the program to remove it and then figure out which sample whas it? Get this part right and you will make a huge step to having a great workflow. And the way the modular synth/sampler/fx idea is implemented is superb, the possibilities that could eventually be reached will make MuLab one of the most personalized hosts (if one is willing to do the work) ever though of. A few months ago I was just playing around brainstorming and could easily see how the ground was laid out to where it would be possible to not even need vst's if it was expanded, like the reaktor of hosts. That would be incredible and I would definitely be one of the people going in depth with it to have that "perfect environment" for making music.

I recieved a message a month or so ago about my skin for MuLab and yes I haven't worked on it for quite some time my life got all screwed up and have been using a monitor from i don't know probably the early 90's and I refuse to do graphics of any sort on it, it's just doesn't give a true enough picture. Here in a few days I'll have my monitor back and I promise I'll make it a number one priority to finish my skin I was very fond of it, while I'm staying away from VST land for now for composition I do like doing sound design with vst's and it would be nice to have MuLab to do it in. I just need to get all my plugins to work in one host and i'll be doing great but like i said the VST standard obviously has a shit ton of holes in it but I guess where stuck cussing for now.

My apologies in advance if this post doesn't make a whole lot of sense I'm working on probably my 7th beer. Anyway Jo I hope you keep going with MuLab for a long time and get it's issues sorted and make it the perfect host, people like me put an awful lot of hope that you will it really is unique.

[audiobot202]

Jo is still working on M3. We're all looking forward to it.
Agree with you about Reaper. Great features. Crap workflow.

Give me multi core support in M3 and I'm happy.

[MuTools]

...

Thanks a lot for sharing your thoughts!

MU.LAB 3 is very close to its test phase.

And though M3 may not be answering all of your whishes, i'm confident it is a very nice step forward, especially regarding usability!

If you're an experienced software user and not afraid of hunting and reporting bugs and bottlenecks, please let me know your email address so i can add you to the M3 test group.

My apologies in advance if this post doesn't make a whole lot of sense I'm working on probably my 7th beer. Anyway Jo I hope you keep going with MuLab for a long time and get it's issues sorted and make it the perfect host, people like me put an awful lot of hope that you will it really is unique.

Please let me know which issues you mean!

[bpblog]

theorize, i saw some previews of your skin and would love to see it finished!

jo, still interested in this one?


http://i50.tinypic.com/33m29s2.png

[theorize]

I'm interested in that one i think it looks awesome! The transport is dope. I wish more people would do interfaces like that I am a huge fan of pixels, I'd like to see a set of FX plugs done in pixels. maybe once i'm done with my skin I'll try to do one in all pixels damn that would be hard for me though i've never really done anything other than small icons.

Jo once I get a chance I'll sit down with MuLab and make some notes about how I think it could improve, it might be good to take the time to form it all into coherent thoughts I'm pretty good at things like that when I set my mind to it.

[bpblog]

we could colab.

[MuTools]

The skin structure has changed in M3. Not dramatically though, but the M2 skins needs some updating. At this point i'm concentrating on getting M3 into its test phase, upgrading alternative skins is planned lateron.