It can be used in a MUX.Taifunk wrote:what exactly is the synth module modulation output and where it works?
MuLab 7.0.47
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
-
- KVRian
- 620 posts since 27 Jul, 2001 from france
Is it that Mulab have a song default lenght set to 100 bars ?pljones wrote:It seems to shrink things so the scrollbars have nowhere to scroll, regardless of how much of the scrollable area is in use.
PQ
free software at : http://pquenin.free.fr/pqnaudio
free music at : http://www.soundclick.com/thepqueninproject
free software at : http://pquenin.free.fr/pqnaudio
free music at : http://www.soundclick.com/thepqueninproject
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
Sorry for the delayed response. That 'circle' is the O of Overview. It takes all parts and markeers into account. For the composer it also defaults to showing minimum 2.5 minutes at the current tempo. Is that ok? If not feel free to make a suggestion about how to define how much must be shown upon clicking that overview button.pquenin wrote:Is it that Mulab have a song default lenght set to 100 bars ?pljones wrote:It seems to shrink things so the scrollbars have nowhere to scroll, regardless of how much of the scrollable area is in use.
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
Thanks for the vid.Taifunk wrote:Thanks jo ,then perhaps there is a problem, I send a video
Note that the "Synth Module..." IO modules should be named "PolySynth ...".
They're renamed in the next version which will be available soon.
These "PolySynth ..." IO modules can only be used in the PolySynth.
Currently that is PolySynth Event Input, PolySynth Modulation Input and PolySynth Audio Output.
In the next version the other listed PolySynth IO modules have been removed as they're not relevant and thus them being listed was confusing. Thx for reporting these things.
- KVRAF
- 3156 posts since 28 Mar, 2008 from a Galaxy S7 far far away
I think it should show length according to current length of song plus a few bars.mutools wrote:For the composer it also defaults to showing minimum 2.5 minutes at the current tempo. Is that ok? If not feel free to make a suggestion about how to define how much must be shown upon clicking that overview button.
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
It does, but with a minimum. I'll already lower the minimum to 1 minute in the very next version. Lets see how that works.
-
- KVRian
- 877 posts since 28 Feb, 2015 from Interstella 5555
Ok thanks ,problem solvedmutools wrote: In the next version the other listed PolySynth IO modules have been removed as they're not relevant and thus them being listed was confusing. Thx for reporting these things.
- KVRAF
- 3156 posts since 28 Mar, 2008 from a Galaxy S7 far far away
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
There is a new M7.0.8 in http://www.mutools.com/galaxa/
What's changed:
OSX: Replace the existing M7 MuLab.app file by the new version in the small zip file.
Windows: Replace the existing M7 MuLab.exe and MuLab.ID files by the new versions in the small zip file.
What's changed:
- Fixed a possible app freeze when dropping a module into the modular area of one of its own deeper modules.
- In some case when adding inputs/outputs to modules in a rack this was not immediately visualized in the modular area that contains the rack. Fixed.
- Sequence editor: When hovering the piano keyboard, it shows the key in the info display.
- Fixed a bug in the step sequencer when using time offset values.
- Renamed the "Synth Module ..." IO modules to "PolySynth ...".
- Removed some currently unused PolySynth IO modules from the module list.
- Lowered the minimum composition overview length from 2.5 to 1 minute.
OSX: Replace the existing M7 MuLab.app file by the new version in the small zip file.
Windows: Replace the existing M7 MuLab.exe and MuLab.ID files by the new versions in the small zip file.
- KVRAF
- Topic Starter
- 13863 posts since 24 Jun, 2008 from Europe
There indeed was a bug. Fixed in M7.0.8.Taifunk wrote:Hi Jo, I'm having a problem with the step sequencer, creating a simple drum loop and changing something in first step etc.. also changes the offset of the last step
you can check this?
