M3 Tests

Official support for: mutools.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Jo,

Great to see that we can now remove plugins from the VST Plugin Manager by the right-click menu. I have 2 little requests concerning the Plugin Manager that could be quite handy and might not be too difficult to implement.

I have all my vst's in a a folder called "c:\program files\vstPlugins" When I install a new plugin I go to Plugin Manager and click "Add VST Plugins" than the default folder from where it starts is always "c:\program\files". Could it be implemented that MU.LAB defaults with the folder that was last scanned? That way I could always leave it at the "Home" folder "c:\program files\vstPlugins" and rescan from there for new plugins.

Also it would be very handy when under "Options" in the Plugin Manager there was an option to quickly rescan the last scanned folder. That would work even faster :)

Would save me (and others) some manual clicking and browsing :wink:
No band limits, aliasing is the noise of freedom!

Post

One more little workflow thing. Drag-and-drop support, is it possible in MU.LAB? It would be very handy to be able to drag a sample in a track from the file manager :)
No band limits, aliasing is the noise of freedom!

Post

Nielzie wrote:I have all my vst's in a a folder called "c:\program files\vstPlugins" When I install a new plugin I go to Plugin Manager and click "Add VST Plugins" than the default folder from where it starts is always "c:\program\files". Could it be implemented that MU.LAB defaults with the folder that was last scanned? That way I could always leave it at the "Home" folder "c:\program files\vstPlugins" and rescan from there for new plugins.
MU.LAB does remember the last scan folder. Not on your system?

Post

mutools wrote:
Nielzie wrote:I have all my vst's in a a folder called "c:\program files\vstPlugins" When I install a new plugin I go to Plugin Manager and click "Add VST Plugins" than the default folder from where it starts is always "c:\program\files". Could it be implemented that MU.LAB defaults with the folder that was last scanned? That way I could always leave it at the "Home" folder "c:\program files\vstPlugins" and rescan from there for new plugins.
MU.LAB does remember the last scan folder. Not on your system?
Nope, not on my systems, both Windows XP and Windows Vista
No band limits, aliasing is the noise of freedom!

Post

Nielzie wrote:
mutools wrote:
Nielzie wrote:I have all my vst's in a a folder called "c:\program files\vstPlugins" When I install a new plugin I go to Plugin Manager and click "Add VST Plugins" than the default folder from where it starts is always "c:\program\files". Could it be implemented that MU.LAB defaults with the folder that was last scanned? That way I could always leave it at the "Home" folder "c:\program files\vstPlugins" and rescan from there for new plugins.
MU.LAB does remember the last scan folder. Not on your system?
Nope, not on my systems, both Windows XP and Windows Vista
it works fine here, both Windows XP and Vista

Post

I have MULAB installed on my PC at work, where I use it with the MME audio interface, and I have no more sound with 3.0.14.

I don't remember with version was installed before 3.0.10 or 3.0.11, but there was no problem...

EDIT : in fact, it works well if I put a mulab synth, but I have no sound with a VSTi ?!!!
Last edited by pquenin on Wed Jan 27, 2010 12:08 pm, edited 1 time in total.

Post

Nielzie wrote:One more little workflow thing. Drag-and-drop support, is it possible in MU.LAB? It would be very handy to be able to drag a sample in a track from the file manager :)
Yes drag and drop is supported at various places.

You can drag drop audio files onto the composer and so they'll be inserted as audio parts.

You can also drag drop audio files on the Sampla and the Multisample editors and so they'll be used as samples.

Please note the difference between MU.LAB's 'audio files' and 'samples':

Audio files are streamed from disk at the audio engine's samplerate. They cannot be pitched up or down. But they can be very long, up to hours, no problem.

Samples are loaded into RAM and can be played at various pitches. But it's best to not load too many/long samples in RAM as then you might run out of RAM which can cause troubles.

Post

Nielzie wrote:
mutools wrote:
Nielzie wrote:I have all my vst's in a a folder called "c:\program files\vstPlugins" When I install a new plugin I go to Plugin Manager and click "Add VST Plugins" than the default folder from where it starts is always "c:\program\files". Could it be implemented that MU.LAB defaults with the folder that was last scanned? That way I could always leave it at the "Home" folder "c:\program files\vstPlugins" and rescan from there for new plugins.
MU.LAB does remember the last scan folder. Not on your system?
Nope, not on my systems, both Windows XP and Windows Vista
It does on my system, Windows XP.

In Mulab/Settings there is a file PreferredFilesAndFolders.txt

Doesn't that one include a line LastVstPluginBrowsePath=X where X is the last folder you scanned?

Post

pquenin wrote:I have MULAB installed on my PC at work, where I use it with the MME audio interface, and I have no more sound with 3.0.14.

I don't remember with version was installed before 3.0.10 or 3.0.11, but there was no problem...

EDIT : in fact, it works well if I put a mulab synth, but I have no sound with a VSTi ?!!!
I hope it's not the same with ASIO. Will check this at home tonight...

Post

pquenin wrote:I have MULAB installed on my PC at work, where I use it with the MME audio interface, and I have no more sound with 3.0.14.

I don't remember with version was installed before 3.0.10 or 3.0.11, but there was no problem...

EDIT : in fact, it works well if I put a mulab synth, but I have no sound with a VSTi ?!!!
I checked 3.0.14 with MME and a VSTi, and it works fine here.

Are you sure you're not overlooking something? Sorry to ask. It's just so strange.

Post

mutools wrote:
pquenin wrote:I have MULAB installed on my PC at work, where I use it with the MME audio interface, and I have no more sound with 3.0.14.

I don't remember with version was installed before 3.0.10 or 3.0.11, but there was no problem...

EDIT : in fact, it works well if I put a mulab synth, but I have no sound with a VSTi ?!!!
I checked 3.0.14 with MME and a VSTi, and it works fine here.

Are you sure you're not overlooking something? Sorry to ask. It's just so strange.
I create a new session, put a synthia in the first slot of the first rack : OK
I replace the synthia with a VSTi : no sound
I put the synthia back (or a musynth) : OK
I try with another VSTi : no sound3

EDIT : very strange, the TAL-Elek7ro VSTi works, but I have no sound with any other VSTi I've tried..

Post

mutools wrote: In Mulab/Settings there is a file PreferredFilesAndFolders.txt

Doesn't that one include a line LastVstPluginBrowsePath=X where X is the last folder you scanned?
This is really strange. My file looks like this and stays the same after I have browsed to c:\Program Files\VstPlugins\ and scanned from there for new plugins (the plugins are from there in their own folders like "CamelSpace" "CamelPhat", etc.):
LastVstPluginBrowsePath=/C:/Program Files
But.. when I scan for a plugin in a folder beneath for the particular plugin by browsing to for instance "c:\Program Files\VstPlugins\CamelSpace" it does remember that last path "c:\Program Files\VstPlugins\CamelSpace"

:?

Why can't I make it remember "c:\Program Files\VstPlugins" for searching all folders below??
Last edited by Nielzie on Wed Jan 27, 2010 1:32 pm, edited 1 time in total.
No band limits, aliasing is the noise of freedom!

Post

mutools wrote: Yes drag and drop is supported at various places.

You can drag drop audio files onto the composer and so they'll be inserted as audio parts.

You can also drag drop audio files on the Sampla and the Multisample editors and so they'll be used as samples.

Please note the difference between MU.LAB's 'audio files' and 'samples':

Audio files are streamed from disk at the audio engine's samplerate. They cannot be pitched up or down. But they can be very long, up to hours, no problem.

Samples are loaded into RAM and can be played at various pitches. But it's best to not load too many/long samples in RAM as then you might run out of RAM which can cause troubles.
I did indeed go to File --> "Add a Sample'" and tried to drag and drop a .wav file to the composer. That seemed pretty natural to me, but I guess that's me.. :shrug: Maybe also put a File --> "Add an Audio File" option (with support for drag/drop)?

So how do I browse to and drag a .wav audio file to the composer easily?

I also don't understand how the Audio File Manager works.. It's empty and I can't seem to put in a default path to my audio files? What's the purpose?
No band limits, aliasing is the noise of freedom!

Post

pquenin wrote:
mutools wrote:
pquenin wrote:I have MULAB installed on my PC at work, where I use it with the MME audio interface, and I have no more sound with 3.0.14.

I don't remember with version was installed before 3.0.10 or 3.0.11, but there was no problem...

EDIT : in fact, it works well if I put a mulab synth, but I have no sound with a VSTi ?!!!
I checked 3.0.14 with MME and a VSTi, and it works fine here.

Are you sure you're not overlooking something? Sorry to ask. It's just so strange.
I create a new session, put a synthia in the first slot of the first rack : OK
I replace the synthia with a VSTi : no sound
I put the synthia back (or a musynth) : OK
I try with another VSTi : no sound3

EDIT : very strange, the TAL-Elek7ro VSTi works, but I have no sound with any other VSTi I've tried..
:o

Anyone else having this issue?

Post

Nielzie wrote:
mutools wrote: In Mulab/Settings there is a file PreferredFilesAndFolders.txt

Doesn't that one include a line LastVstPluginBrowsePath=X where X is the last folder you scanned?
This is really strange. My file looks like this and stays the same after I have browsed to c:\Program Files\VstPlugins\ and scanned from there for new plugins (the plugins are from there in their own folders like "CamelSpace" "CamelPhat", etc.):
I forgot to say that PreferredFilesAndFolders.txt only changes after quitting MU.LAB. MU.LAB writes it on exit so to memorize things next time.
But.. when I scan for a plugin in a folder beneath for the particular plugin by browsing to for instance "c:\Program Files\VstPlugins\CamelSpace" it does remember that last path "c:\Program Files\VstPlugins\CamelSpace"

:?

Why can't I make it remember "c:\Program Files\VstPlugins" for searching all folders below??
MU.LAB simply remembers the last folder you selected.

Post Reply

Return to “MuTools”