Please email me the "PreferredFilesAndFolders.Txt" file which is in MuLab/User/SettingsDHR53 wrote:Here's the browser window I get every time I load a sequence:
regardless whether I load a sequence or not?? Same window every time.
MuLab 4.4.2
-
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
-
- KVRist
- 186 posts since 21 Apr, 2008 from Perth
I think I have found a possible issue:
When playing the virtual midi keyboard and going to tweak a parameter on a synth; notes get stuck and I need to use the Help->Panic option to stop the sounds.
Also if I'm playing the virtual keyboard / hold down a note and try to tweak a parameter; the particular parameter knob goes crazy.
When playing the virtual midi keyboard and going to tweak a parameter on a synth; notes get stuck and I need to use the Help->Panic option to stop the sounds.
Also if I'm playing the virtual keyboard / hold down a note and try to tweak a parameter; the particular parameter knob goes crazy.
-
- KVRAF
- 3160 posts since 28 Mar, 2008 from a Galaxy S7 far far away
-
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
-
- KVRAF
- 2308 posts since 27 Jan, 2011
re8 wrote:I think your prices are a bit too low IMHO; I would expect about $200USD if not more for the flagship model
Shhh!
http://www.youtube.com/watch?v=3tDj_Van ... uNbgY-4qFK
Circumcision's just another way of saying 'bye to the 'hood
Circumcision's just another way of saying 'bye to the 'hood
-
- KVRist
- 83 posts since 19 May, 2012
It kind of depends how you look at it:lingyai wrote:re8 wrote:I think your prices are a bit too low IMHO; I would expect about $200USD if not more for the flagship model
Shhh!
At one hand the possibilities for the modular synth thing is vast. On the other hand there's a lack of basic functions that DAW's should have, like:
- muting of individual notes so you can experiment more easily with melodic changes (on the other hand you can also easily copy the sequence to a new lane and mute the other),
- basic Windows functions like being able to select the text with SHIFT+HOME after typing an Explicit Sequence Name that you want to change instead of having to type it all over,
- Multi-Core support (yes I know this will be implemented and that it's just a small team or a single programmer for Mulab), etc.
- Drag & Drop from Sequence Manager into Composer (currently I have no clue about how to get the Sequence from the Manager into the Composer...I'll post topic on it)
Also, compared to Reaper (60 dollars), the (audio) recording options are minimal in Mulab. But then again Reaper doesn't come packed with all the synth-stuff/possibilities that Mulab has so you need another solution for that if you need it...
Ultimately I think Mulab is great and I recently purchased the UL version, even though the XT version would have been sufficient for my needs, but I wanted to give my support to this project so that it will only become better
-
- KVRAF
- 2308 posts since 27 Jan, 2011
megalodonnl wrote:
- Multi-Core support (yes I know this will be implemented and that it's just a small team or a single programmer for Mulab), etc.
Hmmm... I have a multicore PC. Does this mean that both the DAW and the VSTis / VSTfx which I'd use within a MULAB project would all be working off one core?
If that's the case I think I'd need to wait until multi-core support is available.
Is there an ETA for this?
http://www.youtube.com/watch?v=3tDj_Van ... uNbgY-4qFK
Circumcision's just another way of saying 'bye to the 'hood
Circumcision's just another way of saying 'bye to the 'hood
-
- KVRAF
- 2308 posts since 27 Jan, 2011
Actually, perhaps I spoke too soon. Better to ask the question -- in which ways does lack of multicore suport affect performance? (Sorry for such a technically naive question)
http://www.youtube.com/watch?v=3tDj_Van ... uNbgY-4qFK
Circumcision's just another way of saying 'bye to the 'hood
Circumcision's just another way of saying 'bye to the 'hood
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
AIUI, the GUI and Audio are already on separate threads, which means if you have multi-threading support on your CPU, one does not hold up the other unnecessarily. VSTs are run on the audio thread for processing audio data. VST GUIs I would expect to be on the GUI thread.
Within each thread, however, there would be the opportunity to distribute processing over additional threads. If you have support for more than two threads (preferably more than two cores, hyperthreading isn't really going to cut it, I imagine), these could then process work in parallel (where appropriate). One of the issues with multi-threading is ensuring the threading model retains consistency (i.e. you're only doing in parallel things that do not depend on each other's outcome... and other stuff... I avoid it...). For example, if you have two tracks playing two instruments, those two instruments do not affect each other until their audio has been created and hits the master channel, so they could run in parallel. However, a reverb on a send from both would need to be run after each instrument had created its audio and also before the instrument audio got to the master channel (as it's audio would need to arrive at the same time), hence it would not be running in parallel.
Within each thread, however, there would be the opportunity to distribute processing over additional threads. If you have support for more than two threads (preferably more than two cores, hyperthreading isn't really going to cut it, I imagine), these could then process work in parallel (where appropriate). One of the issues with multi-threading is ensuring the threading model retains consistency (i.e. you're only doing in parallel things that do not depend on each other's outcome... and other stuff... I avoid it...). For example, if you have two tracks playing two instruments, those two instruments do not affect each other until their audio has been created and hits the master channel, so they could run in parallel. However, a reverb on a send from both would need to be run after each instrument had created its audio and also before the instrument audio got to the master channel (as it's audio would need to arrive at the same time), hence it would not be running in parallel.
-
- KVRAF
- 2308 posts since 27 Jan, 2011
Urgh... big words... head hurts... lips growing tired from reading ... sounds... not good.
I just like to have lots of stuff going on without thinking too much...
I just like to have lots of stuff going on without thinking too much...
http://www.youtube.com/watch?v=3tDj_Van ... uNbgY-4qFK
Circumcision's just another way of saying 'bye to the 'hood
Circumcision's just another way of saying 'bye to the 'hood
-
- KVRist
- 83 posts since 19 May, 2012
Are you part of the Mutools Team for coding, Pete?pljones wrote:AIUI, the GUI and Audio are already on separate threads, which means if you have multi-threading support on your CPU, one does not hold up the other unnecessarily. VSTs are run on the audio thread for processing audio data. VST GUIs I would expect to be on the GUI thread.
Within each thread, however, there would be the opportunity to distribute processing over additional threads. If you have support for more than two threads (preferably more than two cores, hyperthreading isn't really going to cut it, I imagine), these could then process work in parallel (where appropriate). One of the issues with multi-threading is ensuring the threading model retains consistency (i.e. you're only doing in parallel things that do not depend on each other's outcome... and other stuff... I avoid it...). For example, if you have two tracks playing two instruments, those two instruments do not affect each other until their audio has been created and hits the master channel, so they could run in parallel. However, a reverb on a send from both would need to be run after each instrument had created its audio and also before the instrument audio got to the master channel (as it's audio would need to arrive at the same time), hence it would not be running in parallel.
Anyway, my Athlon X2 260 copes well, even without multi-core support in Mulab and without HyperThreading in the cpu. But multi-core support is always welcome because it should make a difference (for instance: Reaper seems to have great MultiCore support and it shows when looking at cpu load).
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Nope, just a long-time (occasional) user/tester/questioner-of-Jo 
. I say "occasional" -- these days I don't seem to have time for anything much... (Post-MSc course shock, I think.) But I'm a general techy and so on... (Muzys was my first DAW - I still have Muzys 2.44 archived as of 20021231 - and I've basically stuck with Jo's way since then. My only "other" DAW is Reaper, and only for NINJAM...)
. I say "occasional" -- these days I don't seem to have time for anything much... (Post-MSc course shock, I think.) But I'm a general techy and so on... (Muzys was my first DAW - I still have Muzys 2.44 archived as of 20021231 - and I've basically stuck with Jo's way since then. My only "other" DAW is Reaper, and only for NINJAM...)-
- KVRAF
- 2308 posts since 27 Jan, 2011
Does MULab have envelope automation of things like audio volume and panning, as well as of VSTi / VST fx parameters?
http://www.youtube.com/watch?v=3tDj_Van ... uNbgY-4qFK
Circumcision's just another way of saying 'bye to the 'hood
Circumcision's just another way of saying 'bye to the 'hood
-
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
Yes, you can use automation parts for that. See http://www.mutools.com/info/docs/mulab/overview.html
-
- KVRAF
- 2973 posts since 10 Sep, 2003 from Karlskoga, Stockholm, Sweden
I went out of my Maschine shell to work in Mulab today ... and it was pretty easy actually! Since i "Mux" all my plugins, it was easy to duplicate a track. Drag'n'drop the midi and load the Mux - Done
However, i think i encountered a bug. At the bottom where the rack is, the scrolling would stop working and the handle you drag to go left and right would look like as if there was no more racks to scroll through. Hard to explain
Lets try it this way: If you have only three racks, then there's no need to scroll as all are visible at the same time. Once you add more racks, you wont be able to see them all and the "handle" at the bottom (a long horizontal line) indicates you can drag it right and left. When this 'bug' occurs, the handle, even though you can't see all racks as you have too many for the monitor resolution to see, looks like as if there's only a few (ie as if there was only three or four). Scrolling would stop working as well.
Through some magic process i would get the scrolling back after a while, and then gone again.
If this is something new, then ill try to hunt it down to see exactly what it is that i do, next time i work in mulab.
http://soundcloud.com/bj-rnlundberg/the-voices-within <- the result of today's work
However, i think i encountered a bug. At the bottom where the rack is, the scrolling would stop working and the handle you drag to go left and right would look like as if there was no more racks to scroll through. Hard to explain
Lets try it this way: If you have only three racks, then there's no need to scroll as all are visible at the same time. Once you add more racks, you wont be able to see them all and the "handle" at the bottom (a long horizontal line) indicates you can drag it right and left. When this 'bug' occurs, the handle, even though you can't see all racks as you have too many for the monitor resolution to see, looks like as if there's only a few (ie as if there was only three or four). Scrolling would stop working as well.
Through some magic process i would get the scrolling back after a while, and then gone again.
If this is something new, then ill try to hunt it down to see exactly what it is that i do, next time i work in mulab.
http://soundcloud.com/bj-rnlundberg/the-voices-within <- the result of today's work
