MuLab 9.1.27 [released]

[pljones]

"ACID" files have tempo information encoded - the DAW can only "determine the tempo" if the file contains the tempo.

[crossovercable]

Yes that is normal. If there is no embedded tempo info and you drop a 120bpm drum track in using stream it will fit the 120bpm project no problem, but now when I change the project bpm the audio should change accordingly same as the midi does.
This is a bleeding obvious thing in any DAW, they even have an option to set the original bpm of the file so if I drag a 120bpm drum track in and the project is 110bpm you set the source file bpm to 120 and it will instantly fit the project tempo of 110bpm and if you have a varying decimal tempo map it will fit to it.

[crossovercable]

Also with a "^" caret in the file name this will work in any DAW or JUCE.

[MuTools]

So what are you missing in those other DAWs that you're checking out MuLab?

[crossovercable]

Why have so many DAWs if they are all the same?

I use them to beta test plugins.

Reaper can do all of that if that's what you want to do.
It's not a competition, I'm trying to get it all working in Band In A Box so Biab users can use it without issue as Biab is behind in the non destructive editing. I purchased the Plugin for that reason, I don't need it for myself I only want to give them a way to edit directly in Biab, I'm not making any money out of it, MuTools make money when they sell their products.
Does that all make sense now as to why I post what I post ?

[FabBad]

Hi, reporting two little bugs

1. Event monitor module: the lines of info shows truncated and the rest is wasted.
Tested with Note Length Modifier by turning it off, to reproduce.
This also could be resizable, isn't?

M9.1.27 - event monitor GUI.jpg

2. GUI > cables: the mute doesn't reflect its changes when reopen by double click on it.
This can be particularly confusing when open multiple of them.

M9.1.8 beta - muted cables doesn't show its state.gif

[crossovercable]

Here's a demo using the MuLab Plugin in Band In A Box.
It allows users to build up a song in MuLab or add tracks to existing session recording, allows non destructive editing of the Biab tracks allowing you to edit the drum track or soloist tracks in MuLab easily.
The two issues are the "^" caret in the file names prevents drag n drop.
The imported audio track don't follow tempo changes.

MuLab is the only Plugin on the planet that works in Biab to give it all these features.
If you are using a DAW you need to always drag a file out to see if it will fit where as with MuLab you can play the Biab tracks along with the tracks in MuLab then if the track fits you drag export.

Once it's fixed I will make videos to promote MuLab for Biab users to allow mix and mastering directly in Biab.

Full Screen

[Michael L]

the "^" caret in the file names prevents drag n drop.

You can select file names and delete carets or replace with something acceptable using Find & Replace.

[syntonica]

the "^" caret in the file names prevents drag n drop.

You can select file names and delete carets or replace with something acceptable using Find & Replace.

People shouldn't use funky characters when naming files, especially samples which are going to be loaded on some random machine with unknown file handling capabilities. Using special characters doesn't make the file name look cool, it just makes you look like a n00b. I've been fighting with this since file systems were first created.

All files should be named with letters, numbers, dashes and underscores and nothing else. Just because your system lets you do it doesn't mean every system will accept it.

\rant off

[crossovercable]

The first plugin in the gif didn't import files with ^ at first but now it does.
The other DAW's have no problem with carets and they show a stereo waveform.

Full Screen

[crossovercable]

The carets in the names are to say the drums have sub styles:

[MuTools]

1. Event monitor module: the lines of info shows truncated and the rest is wasted.
Tested with Note Length Modifier by turning it off, to reproduce.

I can't repeat this.
Which steps do i have to take to see the Event Monitor with clipped text lines?

This also could be resizable, isn't?

Yes indeed, will do.

2. GUI > cables: the mute doesn't reflect its changes when reopen by double click on it.
This can be particularly confusing when open multiple of them.
M9.1.8 beta - muted cables doesn't show its state.gif

Thx for reporting this. Will be fixed.

[MuTools]

People shouldn't use funky characters when naming files, especially samples which are going to be loaded on some random machine with unknown file handling capabilities. Using special characters doesn't make the file name look cool, it just makes you look like a n00b. I've been fighting with this since file systems were first created.

All files should be named with letters, numbers, dashes and underscores and nothing else. Just because your system lets you do it doesn't mean every system will accept it.

\rant off

I completely agree with this.

That said i forgot which system could have an issue with carets in folder/file names.
Anyone remembers?

[Michael L]

The carets in the names are to say the drums have sub styles:

Find & Replace ^ with "sub styles" and it will be more #%@$! meaningful.

[syntonica]

That said i forgot which system could have an issue with carets in folder/file names.
Anyone remembers?

I think all the modern file systems accept UTF-8 now and you can just avoid the punctuation that has meaning in your file system, but if you have to put ill-named samples on a FAT12 formatted smart card for your hardware sampler, you're screwed! Hardware devices didn't have terribly robust file system implementations.

As an example, the old Mac HFS used the colon (:) as the path name separator (instead of / or \) and it was common practice for devs to put a " f" (space followed by an f that was a special kind of non-7-bit ASCII curly f) to mark folders. Fun was had by all. I think carats were verboten, but it's been ages since I've dealt with it.