Some things I ran into today (M5)

[megalodonnl]

- How to cancel te creation of a sequence in the Browser when I cancel a
midi recording? I notice that even though I have chosen 'cancel' the
sequence is saved (though not shown in composer, but you can still find it
in the browser). So say if I have a BassP1 sequence and I want to record
BassP2 but screw up and thus cancel the recording...then the next take I
can't use that BassP2 name anymore because it's already taken by the
previous file, even though I cancelled it and therefore I am forced to
either accept the new name (BassP2(2)) or to delete the BAssP2 in Browser and
rename the file to BassP2. But that's a little annoying. If I cancel a
recording, no file should be created in my opinion...

- How to select and delete multiple sequences in browser?

- In Mixdown Options, it would be nice if can instantly create a new file
by just typing a new filename in the box instead of having to press a 'new
file'-button in another window.

- I'd also like to be able to Mixdown in 24bit, since that's what I need to be able to import in my Zoom R8 (hardware). Now I had to batch convert with Reaper.

So overall, this slows down the workflow (unless I'm overlooking something).

[MuTools]

- How to cancel te creation of a sequence in the Browser when I cancel a
midi recording? I notice that even though I have chosen 'cancel' the
sequence is saved (though not shown in composer, but you can still find it
in the browser). So say if I have a BassP1 sequence and I want to record
BassP2 but screw up and thus cancel the recording...then the next take I
can't use that BassP2 name anymore because it's already taken by the
previous file, even though I cancelled it and therefore I am forced to
either accept the new name (BassP2(2)) or to delete the BAssP2 in Browser and
rename the file to BassP2. But that's a little annoying. If I cancel a
recording, no file should be created in my opinion...

I can't repeat this. Maybe i'm missing something. Which MuLab version are you using?

How to select and delete multiple sequences in browser?

Not supported yet. It's on the wishlist.
Note that there is a function "Delete Unused Sequences" in the options menu.

[megalodonnl]

- How to cancel te creation of a sequence in the Browser when I cancel a
midi recording? I notice that even though I have chosen 'cancel' the
sequence is saved (though not shown in composer, but you can still find it
in the browser). So say if I have a BassP1 sequence and I want to record
BassP2 but screw up and thus cancel the recording...then the next take I
can't use that BassP2 name anymore because it's already taken by the
previous file, even though I cancelled it and therefore I am forced to
either accept the new name (BassP2(2)) or to delete the BAssP2 in Browser and
rename the file to BassP2. But that's a little annoying. If I cancel a
recording, no file should be created in my opinion...

I can't repeat this. Maybe i'm missing something. Which MuLab version are you using?

Hmmm...I can't either right now. I think it had to do with creating copies of sequences, then forgetting about them, and trying to rename, etc.. Thanks for the hint "Delete Unused Sequences" in the Browser's options menu.

I did ran into new things:

1. sometimes Mulab (5.1.0 x64) does not ask me whether to save a new MIDI recording.
2. sometimes, after opening (floating) browser, if Sequences was already selected, sequences are not shown. I first have to select another category (like Audio) and then select Sequences again, and then the sequences are actually displayed.

[MuTools]

1. sometimes Mulab (5.1.0 x64) does not ask me whether to save a new MIDI recording.

You'll only get a question alert when you selected a part prior to recording then you can choose between Overwrite - Merge - Punch - New Part - Cancel.

When no part is selected the new recording is stored in a new part. If you don't like the recording you then use Undo which will remove the recorded part.

2. sometimes, after opening (floating) browser, if Sequences was already selected, sequences are not shown. I first have to select another category (like Audio) and then select Sequences again, and then the sequences are actually displayed.

Will check.

[megalodonnl]

Also, ML won't recognize the audio .wav created with the Zoom R8. Could this be because it's a 24bit wave? Haven't tested with 16bit yet...

[MuTools]

I assume this is the same issue as dakkra reported some weeks ago. Please mail me such (short) wave file so i can check it.

[megalodonnl]

I assume this is the same issue as dakkra reported some weeks ago. Please mail me such (short) wave file so i can check it.

Hey, Megalodonnl again here...

Just sent my mail. Doesn't matter whether I make 16- or 24bit recording (just tested).

I first thought 24bit may be the problem cause when I converted a 24bit wav to 16bit with Audacity, Mulab loaded it fine.

Conclusion: something else is changed while such a conversion by Audacity as well, don't know that.

BTW: it would be nice to have the option to Mixdown to a (24bit) MONO file.

[MuTools]

sometimes, after opening (floating) browser, if Sequences was already selected, sequences are not shown. I first have to select another category (like Audio) and then select Sequences again, and then the sequences are actually displayed.

Will check.

Checked but can't repeat this. If you have a step by step how to repeat this pls let me know. Thx.

[MuTools]

Just sent my mail. Doesn't matter whether I make 16- or 24bit recording (just tested).

There is something wrong with the LIST chunk in that file, imho. So why do other apps don't bother about it? Well it will depend on the app, i'm sure some other apps will have a prob with it too. It depends on how the app parses the wave file.

[MuTools]

PS: I've changed the way wave files are read. LIST chunks are ignored now. This widens compatibility. Eventhough i think that that wave file you emailed me is technically invalid, but making music is everything

I'll soon also add support for those other wave files, cfr dakkra's report some weeks ago.

[megalodonnl]

PS: I've changed the way wave files are read. LIST chunks are ignored now. This widens compatibility. Eventhough i think that that wave file you emailed me is technically invalid, but making music is everything

I'll soon also add support for those other wave files, cfr dakkra's report some weeks ago.

Could this have anything to do with the fact that I used the LOOP function on the Zoom? So basically, the file I sent you was a 'loop-part' that I defined on the Zoom. Perhaps when I make a normal recording it won't have the invalid chunk. Might be interesting to check when I get around to it. But indeed; music making is everything and I don't want to quit using the loop function on the Zoom, so thanks for the ignore thing. So that will be in the next update? My workaround is putting files through Audacity, which I'll need to have more elaborate conversion options anyway (24bit bit depth, mono/stereo, etc.).

[MuTools]

thanks for the ignore thing. So that will be in the next update?

Yes.