Yes I understand that, it's just I think these questions are more on a strategic level than just adding additional features - committing more to Mac is not on the same level as say adding a loop device or something.mutools wrote:They are relevant poll options because they take R&D time. And this poll will be one of the input factors for deciding the priorities for the M7 R&D.aMUSEd wrote:Then again thinking about this, these shouldn't be options in some vote.aMUSEd wrote:Mux modular and 64 bit for Mac definitely - also AU support.
Your biggest wish for M7
- KVRAF
- 37390 posts since 14 Sep, 2002 from In teh net
- KVRAF
- 9091 posts since 28 May, 2005 from Netherneverlands
What does the "Optimized CPU usage" option actually mean? Isn't MuLab/Mux not yet fully optimized at this point? Where could it gain most optimization and approx how much?
No band limits, aliasing is the noise of freedom!
-
- KVRist
- 82 posts since 16 Jun, 2005
hello, Jo,
win! 
the win-win solution, for me, because of being on both platforms, will mean double gain.
all the best...
win!mutools wrote:supporting the mac platform will also (indirectly) have benefits for the Windows version, for example because MuLab will be taken more serious which hopefully results in more resources for MuLab and MUX on all platforms
the win-win solution, for me, because of being on both platforms, will mean double gain.
all the best...
- KVRAF
- Topic Starter
- 13860 posts since 24 Jun, 2008 from Europe
There always is room for optimization.Nielzie wrote:What does the "Optimized CPU usage" option actually mean? Isn't MuLab/Mux not yet fully optimized at this point?
In more complex MUX structures with many many modules, eg the MuDrum, which consists of 487 modules.Where could it gain most optimization?
- KVRAF
- 9091 posts since 28 May, 2005 from Netherneverlands
But the basic sequencer part of MuLab, without loading any additional mux modules, is optimized right?mutools wrote:There always is room for optimization.Nielzie wrote:What does the "Optimized CPU usage" option actually mean? Isn't MuLab/Mux not yet fully optimized at this point?In more complex MUX structures with many many modules, eg the MuDrum, which consists of 487 modules.Where could it gain most optimization?
No band limits, aliasing is the noise of freedom!
- KVRAF
- Topic Starter
- 13860 posts since 24 Jun, 2008 from Europe
Sure. Even MUX processing is optimized. But i think there is room for more optimization. Like in most software.
-
- KVRian
- 877 posts since 28 Feb, 2015 from Interstella 5555
totally agree (I'm not a Mac user)mutools wrote:supporting the mac platform will also (indirectly) have benefits for the Windows version, for example because MuLab will be taken more serious which hopefully results in more resources for MuLab and MUX on all platforms
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
This is true. The more flexible and powerful the better (I'd like to sequence a repeating pattern of 3.5/8, 11/16, 7/4 on one track against a "simple" 5/4 on another, for example - maybe each of them switching to different time signatures at some point). Basically, I think a sequence should have a time signature, so when you're editing, you see it that way, and the time signatures themselves shouldn't be too limited (in the "traditional sizes only" sense). You should then be able to put sequences anywhere and have the composer understand what's happening.EvilDragon wrote:Here's another thing that's quite important that could improve in ML7: time signatures!
- KVRist
- 117 posts since 7 Oct, 2014 from Suisse
All who can improve live performance is my wish.
Lot of things can be done yet, like using virtual and hardware synths together.
But as player with hardware synths there are things im missing.
Most i want is midi improvement.
1) All midi devices are merged together now. Merge should only be a option. Better would be Chanel+Device as control. This way we can use diffrent hardware interfaces for different jobs.
Having only 16 midi channels as is to small whe combining Hardware and Soft (Vsti Vst) gears (mixer , Fx , Synths, Drumbox, hardware sequencer )
2) Syncronising is most important thing in live. And in both way midi-in and midi-out. First for recording external harware sequencer and drumbox . Second for syncro midi timebased FX.
It much easier to control real knob than play around with a mouse in live situation.
3) Midi programme change for storing setup of internal and external midi insrument patch number and effects. Mulab has no patch oriented storage for the instruments and fx.
To keep mulab philosophy and compatibily to midi adding a module for midi patch would be nice. An other solution could be a list like midi channel connecting to modules who alleady exist.
But same could be applied with midi program change to connect modules to several midi program change numbers.
This way we can assign 128 programm number to modules as in channel list.
4) Would be nice having an easier audio recorder option for live situation, who dont record audio and midi on new tracks but only into a new file.
Multiple sound source from whith projet as audio input selection .
Until now i have use an auxiliry rack where im wiring audio from different sources . But Mulab records midi data on other tracks, whitch i dont need in live situation.
An external recorder who is not included in mulab projet could be the solution. Some kind of record what you hear. Should be in Mulab because Asio dont allow multiple instances of audio with external programms.
5)Edit audio in external is useless with asio because same problem as above. Add all basics into editor maybe vst processing too for quicker workflow.
Lot of good thing have been until now .
Thanks to all developper.
Lot of things can be done yet, like using virtual and hardware synths together.
But as player with hardware synths there are things im missing.
Most i want is midi improvement.
1) All midi devices are merged together now. Merge should only be a option. Better would be Chanel+Device as control. This way we can use diffrent hardware interfaces for different jobs.
Having only 16 midi channels as is to small whe combining Hardware and Soft (Vsti Vst) gears (mixer , Fx , Synths, Drumbox, hardware sequencer )
2) Syncronising is most important thing in live. And in both way midi-in and midi-out. First for recording external harware sequencer and drumbox . Second for syncro midi timebased FX.
It much easier to control real knob than play around with a mouse in live situation.
3) Midi programme change for storing setup of internal and external midi insrument patch number and effects. Mulab has no patch oriented storage for the instruments and fx.
To keep mulab philosophy and compatibily to midi adding a module for midi patch would be nice. An other solution could be a list like midi channel connecting to modules who alleady exist.
But same could be applied with midi program change to connect modules to several midi program change numbers.
This way we can assign 128 programm number to modules as in channel list.
4) Would be nice having an easier audio recorder option for live situation, who dont record audio and midi on new tracks but only into a new file.
Multiple sound source from whith projet as audio input selection .
Until now i have use an auxiliry rack where im wiring audio from different sources . But Mulab records midi data on other tracks, whitch i dont need in live situation.
An external recorder who is not included in mulab projet could be the solution. Some kind of record what you hear. Should be in Mulab because Asio dont allow multiple instances of audio with external programms.
5)Edit audio in external is useless with asio because same problem as above. Add all basics into editor maybe vst processing too for quicker workflow.
Lot of good thing have been until now .
Thanks to all developper.
- KVRian
- 975 posts since 21 Feb, 2015
Grizzellda wrote:It would be nice to have sub-folders in the VST management area. So I could have a folder for Compressors, then within that, folders for different types, companies, etcetera.
I don't think you understood my point. Yes, I realize I can define one level of a "group", to categorize the plug-ins, but I meant "groups within those groups". Example: A Compressor "group" (folder). A mouse click on that & it opens to 2 more "groups" (folders): #1- Old fashioned tube type. #2- Clean modern type. Then the actual dll's would be in those folders. That is what I meant. Sonar & Podium have this kind of management. Folders within folders. Can it be done?
Jo, the piano roll in MuLab, in my view, is beautiful. It is a large part of why I even got into the program.
What I like about it: Colour customization! The ease of assigning colours to the notes, and especially the different contrasts between selected & unselected, well that is the DOPE! Also the vertical scroll, making the notes really, really big. I dunno, but I just love that! Okay, yeah I'm a lunkhead! And the overall elegance of it. These dudes, these critics, man... are just way of base.
Those who want Fruity, well maybe they should just use Fruity. And why not? Fruity is cool, it is well established...Fruity has been around the block Holmes...but what on God's Green Earth does that have to do with MuLab?
Seriously, it's like complaining "which side the master rack is on..." Is this valid?
Left click to insert a note, then Ctrl left click to delete that note. Is this difficult? As I said earlier, regarding audio recording, what about this notion of actually learning how to use an application.
MuLab really is pretty straight forward, but like any software you have to learn the idiosyncrasies, don't just complain on an internet forum.
Oh yeah, Jo...about the beer pic you posted...heh heh
-
- KVRist
- 388 posts since 28 Oct, 2002
I applaud your enthusiastic defence of a great programme Grizzellda and you are correct about learning a programmes idiosyncrasy's. But have you tried the piano roll in Fruity? Its exultant, (worth trying to see why its being mentioned), so is the piano roll in Orion, both rolls are quick and intuitive. Its not about turning Mulab into anything else, Mulab is great as it is in its own right, its about suggesting our perceived improvements for Jo to look at and make the final decision. FWIW I've owned Fl for over 13 or 14 years and not made a thing in it, beside the piano roll the work flow doesn't work for me. With the right or left master rack positioning, its a "preference" thing, having used DAW's with the master at the right, I look there without thinking and was disappointed when I could not drag it to the right side of the mix panel. I know its an old dog, new tricks thing, my problem.Grizzellda wrote: Jo, the piano roll in MuLab, in my view, is beautiful. It is a large part of why I even got into the program.
Those who want Fruity, well maybe they should just use Fruity. And why not? Fruity is cool, it is well established...Fruity has been around the block Holmes...but what on God's Green Earth does that have to do with MuLab?
I tried changing the default to the pencil but I found it not as intuitive, kept erasing things and dragging/duplicating became a "drag"
- KVRAF
- Topic Starter
- 13860 posts since 24 Jun, 2008 from Europe
Chance is high there will be intermediate test versions so you can already try new things as they are implemented. I'm thinking about symbolic "M6.7" test versions. Of course certain steps will take time though.runaudio wrote:all this talk of mulab 7 i cant wait it going too be a long few months
-
- KVRist
- 118 posts since 20 Feb, 2013
In the editor should all sequences be visible, which are marked. It would be great, if there was multi-editing, that means you can mark all the sequences in the composer (even from different tracks) , which shall be displayed in the editor. With different colours it should be no problem to know which track they belong to.
- KVRAF
- Topic Starter
- 13860 posts since 24 Jun, 2008 from Europe
Such feature request indeed already is on the wishlist, but not yet planned for M7.0
Anyway, just a draft question: What if notes are overlapping: Which note should be seen then? How to access the other?
Anyway, just a draft question: What if notes are overlapping: Which note should be seen then? How to access the other?
