Very nice
What about using MFOs there?!
Very nice

I'm not seeing this happen.Nielzie wrote:This is weird.. everytime I start MuLab 6.5.7 64-bit it adds a file called "t.png" to my system root c:\![]()
I still have this weird behaviour. The C:\t.png file is actually a picture of a little black "x" that is used to exit a window.pljones wrote:I'm not seeing this happen.Nielzie wrote:This is weird.. everytime I start MuLab 6.5.7 64-bit it adds a file called "t.png" to my system root c:\![]()
liquidsound wrote:Fantastic Editor. One thing... Is it possible to add a warning upon "Remove Component" '?
Ok will do.Taron wrote:[confirm requester] Yeah, that would be good habits!
Adding components is not done anymore by drag-dropping stuff on the front panel, as was in M6.4. It's done using the Add Component context menu function, pls see details in http://www.mutools.com/forsythia/M65%20 ... 20Info.txtrunaudio wrote:when i unlock the front panel then drag and drop a lfo over to it it wont let me add it
Sorry, that was for debugging purposes, it's removed from the next version. Thx for reporting.Nielzie wrote:This is weird.. everytime I start MuLab 6.5.7 64-bit it adds a file called "t.png" to my system root c:\![]()
OS: Windows 7 64-bit.
I had some things to do yesterday afternoon/evening. But then at the end of the day, yes i enjoyed a fresh cold beer, lovelyliquidsound wrote:He's watching this thread with a Large Cold Beer and having some very good time
Note that when editing front panels, the components are in a kind of frozen state, lets call it front panel edit mode. Renaming parameters is done in normal mode. To quickly switch between edit mode and normal mode assign a shortcut key to "Toggle Editing". I have [E] assigned to it.Taron wrote:I miss "rename" of parameters and the likes, which is something I use constantly on designing the front panel. I hope there's some reasonably easy way to bring this back?
Pls see http://www.mutools.com/info/docs/mux/us ... llers.htmlTaron wrote:Another thing I noticed earlier already in previous versions:
Midi Mapping strangeness
For example, I have a parameter directly from a module out of the polysynth mux like "Amplifier", dragged onto the front panel. On the front panel then, if I [Map MIDI Controller] it allows me to set what controller I want to use, all is well, no problems there. But if I go to the "Options > Edit MIDI Controller map", those mappings won't show up?
It's not surprising that those "hidden" mappings won't save with the preset and will be gone when loading the preset again.
I'm just curious if that is an oversight or whether there's method to the madness?
Just as a general note wrt FRs for more component types on the front panel: When i started on this new front panel system i also hoped for many more component types. But then i encountered certain complexities which i want to avoid at this point, until i find a solid solution for that. So at this point i keep things rather simple and safe. Maybe some more component types can be added in next versions, but i'll stay careful with it so the system stays clean, healthy and future proof. Besides that aspect i also want to release M6.5 soonish and also work on other important MU aspects. Then hopefully the MUX front panel system can be further extended step by step in next versions. Anyway, always feel free to make suggestions. As with other kinds of feature requests maybe i reply on it maybe not, but i do read & evaluate them all. Thx!runaudio wrote:any chance you could add the keyboard to the front panel next update because am looking to make my own sampler and would be very so grateful if i was able to add the keyboard to the front panel and also the drum note processor to the front as well for makeing your own drum machines thank you
Even nicer!
Thx!The implementation is quite workable atm. Very nice done!
You mean the grid size?A user-definable grid would be great though.
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement
© KVR Audio, Inc. 2000-2026