MuLab 9.0.59 App + Plugin

[pljones]

I checked the internal screen video recorder in both M9.0.42 32 bit and 64 bit and all works as expected here.

It seems to work for short clips... When I do it in one take, it's 4,182,538,752 bytes... I've written down the steps as I do them now, so I can go back and do a short clip for each step and see if that works.

For the failed video I got and . Log file attached.

I managed to recover the video with

Code: Select all

ffmpeg -hide_banner -i AppMovie-20220709-151827.Avi -c:a copy -c:v copy -y AppMovie-20220709-151827-copy.Avi

Was there a codec that needed installing? I might have lost that (I've not tried a long recording in MuLab 8 to compare behaviour).

[MuTools]

That internal screen recorder indeed is something simple and probably still also partially 32 bit code so max 4GB total file size. But that should already give you many many minutes (10? 20?) of screen recording, depending on the codec of course. You're not using an uncompressed codec, are you?

[pljones]

"msvideo" for the video codec - yeah, it was 25 minutes, but still just under 4GB ... although I think it did get truncated, so it might have lost a final bufferload. I thought there was something different with the codec I didn't recognise when I checked. I don't remember how to change it, though.

The "full" video, as recovered, is here: WindowsMuLabJackTrip-LinuxJackTripJamulus.mkv with the edited transcript that's seen written live here: WindowsMuLabJackTrip-LinuxJackTripJamulus.txt.

[Quad]

No Gui scaling on VST frontends
The frontends of VST plugins are not effected by preference value GUI Scale.
Independently from the prefrences AND Windows scaling they start by 100% scale.
Effect sems to start after 9.029
But anyway: M9 is a great product!
Screenshots on 4K screen / 150% windows scaling on M9.9029 and M9.042
Effect is especially terrible using Dexed because there is only a VST3 which support scale changing.

[kejkz]

Isn't the VST scale size controlled by the plugin itself? I'm using the scaled Mulab, but am not expecting it will scale all my plugins to the same ratio. Actually I'm sure that all plugins I'm using have a different scale, depending on the given plugin UI layout.

[Quad]

Thanks kejkz!
Your'e principal right. The DAW should not change anything on frontend size of VSTs. But on my point of view this is exactly what M9 sind 9.03x does: My windows screen is set to a sacling of 150% because of better reading. My M9 ist set to GUI-Scale AUTO ( which mean the operating system only should control screen scaling). If nothing would happend then the frontend of th vst would be scaled from windows graphics system to 150%. This is the behavior in Mulab 7 , 8 and also until M9.029 and on other DAWs like Cakewalk etc. But you can set GUI-Scale to what you want and also any value of WIndows scaling , the VST starts always like Windows would be set to a scale of 100%. For me this seems to happen in the DAW ( lost win scaling information in env ??). Because in early M9 versions the behavior was correct ( on my point of view ), this should be possible to reactivate.
Otherwise I would have to reduce the resolution of my sccreen because there is no combination to run this VSTs with readable UI.

[MuTools]

First of all: Apologies for the maybe unexpected delay on the MuLab 9 release.
The last 2 months there have been several different events that have seriously interfered with the MuLab 9 release flow. Not ideal, but it happened.
New MuLab 9 expected release date is end of august / early september.
Anyway, MuLab 9 is fully functional so hope you're enjoying it.

Here is a preview to another MuLab 9 intro video that briefly explains the Note Action Map:

[robert_p]

Here is a preview to another MuLab 9 intro video that briefly explains the Note Action Map:

Nice one, I didn't know such a feature exist (drag a scene to the key to assign a live note action). Thanks for enlightening me:))

[wibem]

No update since a long time. Holiday or is something big coming?

[pljones]

No update since a long time. Holiday or is something big coming?

See viewtopic.php?p=8479499#p8479499 two messages above.

[Quad]

MuLab App 9.0.32 is available in https://www.mutools.com/mulab/app/latest-binary

MuLab Plugin 9.0.32 is available in https://www.mutools.com/mulab/plugin/latest-binary

What's changed:

• MuLab for Windows now is High DPI aware and takes the Windows Scale Factor into account.
  MuLab's own GUI Scale Factor preference now also has an extra option "Auto" which will use the Windows Scale Factor.
• Live Matrix: When stopping a live clip almost precisely when a new note was started, this could result into a hanging note. Fixed.
• When importing a MIDI file to new tracks, the new track's MIDI channel is properly set according to the content of the MIDI file.
• MuLab Plugin inside Reaper: Stopping a preview could lead to hanging notes. Fixed.
• MuLab Plugin: When sliding parameter knobs/sliders in some cases, also depending on the host DAW, there could be unexpected behavior. Fixed.
• Selecting tracks with same target module but different MIDI channel did not properly update MIDI Input routing. Fixed.
• Some shortcuts which were available in M8 were missing, like "Toggle Loop", "Loop Selected Parts", and others. Fixed.
• Due to a recent change, using certain VST plugins could lead to innocent yet confusing errors in the log file. Fixed.
• MuLab Plugin: The "Vst.UniqueId" will be different for each main version of MuLab Plugin.
  This is to avoid confusion in host DAWs (eg. Bidule) when multiple main versions of MUX Plugin / MuLab Plugin are installed for project compatibility reasons.
• Fixed a little issue with "Check For Updates".
• Other small improvements.

Since this version the Windows scaling has no effect anymore on VST Frontend. The Gui Scale option "Auto" may not work properly. Independend of windows scaling factor since this version the vst frontends always starts with a 100% scaling ( on 4k Screen this means nearly unreadable). There is now NO combination to correct this. Behavior on versions before 9.032 uses Windows scaling in a correct form.

[MuTools]

It seems to be a complicated topic.
As a short term 'solution' the next M9.0.43 update will have a "DPI Aware" preference that is switched on by default, but when switched off you should get the same behavior as before M9.0.32.

[MuTools]

MuLab App 9.0.43 for Windows is available in https://www.mutools.com/mulab/app/latest-binary

What's changed:

• New shortcut to add a new Live Scene.
• When adding a new Live Scene, the Live Matrix auto scrolls to the right to show the new Live Scene.
• Improved behavior for toggling the Composer Modular Area via mouse or via shortcut.
• Further finetuned behavior wrt. files in the "AutoSaved" folder.
• New color preference "Table List Column Title Color".
• New color preferences for "Wave Selection Back Color" and "Wave Selection Fore Color".
• New preference "Unselected Wave Dim Factor".
  In previous versions when selecting a section in the audio editor, all unselected audio was dimmed for 50%.
  Now that value is a user preference and can be set from 0% to 100%.
• The "Support MIDI" preference has bee removed.
  If you don't want MuLab to open any MIDI ports, simply clear everything in MuLab's MIDI Setup.
  That will have the same effec as switching off the removed "Support MIDI" preference.
• MuLab App Windows: New preference "DPI Aware". Default is On. In some cases you might want to switch this off wrt VST plugin editors.
• Further vectorization of the GUI = less dependency on external graphic files.
  More than 90% is vectorized. Goal is 100%. Step by step.
• Sequence -> Move One Step Left/Right could cause a crash when used in the Event List Editor. Fixed.
• Fixed a graphical artifact bug in a newly created empty composer editor.
• There was a tiny little chance that upon ending audio recording there could occur a crash. Fixed.
• Other small improvements.

Currently the M9.0.43 update is only available for MuLab App for Windows.
The corresponding updates for MuLab Plugin and for MacOS will follow soonish.

[Quad]

Great!
Many Thanks
This will help me a lot on my actual project

[MuTools]

Does switching off the "DPI Aware" preference and restarting MuLab 9 solve the issue?