Ah deleting the sequence while auto-previewing it, yes i can repeat that crash, will further research and fix. Thanks!Trancit wrote:But I could narrow it down:
It's related to the "Autopreview" function... if turned off or the autopreview is already finished, nothing happens...that's the reason, why it didn't happen with the factory clips... they are too short and playback is already done...
So to test you need clips, which are long enough (I tested with 4 bars clips) that they still play if you rightclick and choose delete...
MuLab 5.0.31 Test
-
- KVRAF
- Topic Starter
- 13860 posts since 24 Jun, 2008 from Europe
-
- KVRAF
- Topic Starter
- 13860 posts since 24 Jun, 2008 from Europe
Euh, the fix was about "Couldn't open preset". That problem has gone, right?sl23 wrote:Thanks for fixing that Jo, but it still hasn't solved the problem I had.
Just to avoid confusion: A session does not contain presets. A preset is a separately saved file eg a MUX preset has the extension .Mux.Here's what happens now:
I load my Session with my Presets.
When you would edit a MUX to state A and save it as a preset, then you further edit that MUX to state B and save the session, then when you load the session it will have state B. But if you load the preset it will be state A. Hope you see what i mean.
The preset or the session?I remove all association with MP's for a particular parameter and replace it with a knob straight from the source.
I save the preset.Then restart MuLab and the preset appears as it did before I edited it.
When loading a preset it should be as when you saved the preset.
When loading a session it should be as when you saved the session.
A session and a preset are two independent things.Just checked if saving the session would 'update' the info regarding these presets and it does. It seems that if a session contains a preset it contains the actual details of that preset. So if you edit that preset and save it, the session still thinks you're using the old version unless you save the session as well.
I absolutely disagree. Imagine you use preset A in session X and also in session Y. Now you're working on session X and you tweak the loaded preset a bit so it matches session X. Then do you want session Y to automatically change sound? No!!Is that intentional? I don't think it should be if it is. A session should simply contain the path to the preset.
Hope this clarifies things.
-
- KVRAF
- Topic Starter
- 13860 posts since 24 Jun, 2008 from Europe
PS: In case you would want to copy the tweaked sound in session X also to session Y, then save it as a preset and load the preset in session Y. Or use copy-paste while both sessions are opened.
-
- KVRAF
- 3140 posts since 28 Mar, 2008 from a Galaxy S7 far far away
Sorry, yes it did solve the Couldn't Open Preset problem.
I understand, and my next question is answered too, aren't you a clever chappie! ie How to reuse a tweaked sound. I assume when you say 'save it as a preset' that means use the 'save as' command, yes?
Now I understand how it works I do agree with how it's done, sorry, just my confusion. All sorted now except the R-click thing! Although, that doesn't seem so bad as before? Oh well. Thanks for sorting that out, it put me on hold for a bit! Great job.
This is how I poorly explained itWhen you would edit a MUX to state A and save it as a preset, then you further edit that MUX to state B and save the session, then when you load the session it will have state B. But if you load the preset it will be state A. Hope you see what i mean.
I understand, and my next question is answered too, aren't you a clever chappie! ie How to reuse a tweaked sound. I assume when you say 'save it as a preset' that means use the 'save as' command, yes?Now I understand how it works I do agree with how it's done, sorry, just my confusion. All sorted now except the R-click thing! Although, that doesn't seem so bad as before? Oh well. Thanks for sorting that out, it put me on hold for a bit! Great job.
-
- KVRian
- 505 posts since 30 Jan, 2007
This isn't a bug fix, but a suggestion for upgrading the documentation to make things easier for new users:
Add a full section to the docs (listed in the table of contents - that's important) for time signature and quantization. These are things most musicians would need to know, and for new users, finding them in MuLab isn't as easy and obvious as it could be.
Items in the section would include:
a - setting time signature and other items in the Edit Properties menu
b - (if possible) how to include time signature changes within a composition
c - turning off auto quantize using the record events settings
d - how to quantize a previously recorded MIDI part
e - manually adjusting the position/duration of specific notes
and perhaps also tempo changes within a composition.
Two other possible minor changes that could also help: first, use "no grid" as the default so that the auto-quantize is initially turned off. Second, in the Record Events settings, change the name of "Event Recording Grid" to something that makes it more clear that it's about quantization. "Event Quantize Grid", perhaps.
It's obviously easy for us to turn off or change the auto quantize - once we know. But I'm thinking about new users starting out with MuLab. When you see "grid", you would think it's a setting to change the spacing of the lines on the composer screen, not a quantization setting.
And when the new user goes to the docs, there's nothing in the Table of Contents that looks like it would help. If you use the Google search to look for "turn off quantize", you get nothing. If you try just plain "quantize", you do find the section on recording MIDI events. It says that here you can set whether notes are automatically quantized - but it doesn't explain to the new user how to do it.
Add a full section to the docs (listed in the table of contents - that's important) for time signature and quantization. These are things most musicians would need to know, and for new users, finding them in MuLab isn't as easy and obvious as it could be.
Items in the section would include:
a - setting time signature and other items in the Edit Properties menu
b - (if possible) how to include time signature changes within a composition
c - turning off auto quantize using the record events settings
d - how to quantize a previously recorded MIDI part
e - manually adjusting the position/duration of specific notes
and perhaps also tempo changes within a composition.
Two other possible minor changes that could also help: first, use "no grid" as the default so that the auto-quantize is initially turned off. Second, in the Record Events settings, change the name of "Event Recording Grid" to something that makes it more clear that it's about quantization. "Event Quantize Grid", perhaps.
It's obviously easy for us to turn off or change the auto quantize - once we know. But I'm thinking about new users starting out with MuLab. When you see "grid", you would think it's a setting to change the spacing of the lines on the composer screen, not a quantization setting.
And when the new user goes to the docs, there's nothing in the Table of Contents that looks like it would help. If you use the Google search to look for "turn off quantize", you get nothing. If you try just plain "quantize", you do find the section on recording MIDI events. It says that here you can set whether notes are automatically quantized - but it doesn't explain to the new user how to do it.
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
You loaded Pure into Free, got the soft noise during playback, then started a New session first? I'm pretty sure that's part of the problem. I'll try it in .28 shortly.mutools wrote:Can't repeat it. I'm playing with the browser factory muclips for about 10 min now, no noise. Hope you can find a repeatable way.pljones wrote:I'll have to try being a bit more patient but yes I'm fairly sure I'd been playing with the browser for over 5 minutes after doing New Session and it was still happening. I even checked again whilst posting the message to be sure.mutools wrote:It's not. But if you have crossed the bounds recently and then start a new session, then it can still take a couple of minutes before the demo noise disappears. Or do you mean that the demo noise comes even more than say 5 minutes after returning inside the limits?
-
- KVRAF
- Topic Starter
- 13860 posts since 24 Jun, 2008 from Europe
MUX -> context menu -> Presets -> Save Preset As...sl23 wrote:I assume when you say 'save it as a preset' that means use the 'save as' command, yes?
-
- KVRAF
- 3140 posts since 28 Mar, 2008 from a Galaxy S7 far far away
-
- KVRAF
- Topic Starter
- 13860 posts since 24 Jun, 2008 from Europe
First i didn't first load Pure, now i did in another test, but still no noise when switched to new session and playing with the browser. (except for some initial 'fade' time which is maximum a couple of minutes)pljones wrote:You loaded Pure into Free, got the soft noise during playback, then started a New session first? I'm pretty sure that's part of the problem. I'll try it in .28 shortly.mutools wrote:Can't repeat it. I'm playing with the browser factory muclips for about 10 min now, no noise. Hope you can find a repeatable way.
Just checking: You didn't open a new session as an extra session with Pure still in the background, did you? As that could explain it.
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
I've just retested with .28.
Run MuLab
Load Pure Demo and play till the demo noise sounds. Stop.
New Session into This (i.e. replace Pure with the New session, so Pure isn't loaded).
Click the MuClip Bassline and let it play. After a while the demo noise sounds.
Leave MuLab for 15 minutes doing nothing.
Click the MuClip Bassline and let it play. After a while the demo noise sounds.
Close MuLab
Run MuLab
Play Birds of Io Demo -- no demo noise sounds. Stop once it's played once.
New Session into This (i.e. replace Birds of Io with the New session, so Birds of Io isn't loaded).
Click the MuClip Bassline and let it play. After a while the demo noise sounds.
Run MuLab
Load Pure Demo and play till the demo noise sounds. Stop.
New Session into This (i.e. replace Pure with the New session, so Pure isn't loaded).
Click the MuClip Bassline and let it play. After a while the demo noise sounds.
Leave MuLab for 15 minutes doing nothing.
Click the MuClip Bassline and let it play. After a while the demo noise sounds.
Close MuLab
Run MuLab
Play Birds of Io Demo -- no demo noise sounds. Stop once it's played once.
New Session into This (i.e. replace Birds of Io with the New session, so Birds of Io isn't loaded).
Click the MuClip Bassline and let it play. After a while the demo noise sounds.
-
- KVRAF
- Topic Starter
- 13860 posts since 24 Jun, 2008 from Europe
Does the demo noise also comes when simply starting MuLab -> New Session -> preview Bassline? Maybe you have more than 1 MIDI in or out selected? (please check MULAB -> MIDI Setup) Meanwhile i'm still trying to repeat this, no 'luck' so far.
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Ah yes, I do have more than 1 MIDI input... So many things to remember to turn off 
. -EDIT: That does appear to have been the cause /-
Hmm but no noise during playback of Birds of Io? I'll have to listen harder to see if I just missed it. -EDIT: Hah! It's just short enough that played from a fresh start, it completes once! Leave it looping and the noise sounds /-
. -EDIT: That does appear to have been the cause /-Hmm but no noise during playback of Birds of Io? I'll have to listen harder to see if I just missed it. -EDIT: Hah! It's just short enough that played from a fresh start, it completes once! Leave it looping and the noise sounds /-
Last edited by pljones on Sat Dec 29, 2012 7:07 pm, edited 1 time in total.
-
- KVRAF
- Topic Starter
- 13860 posts since 24 Jun, 2008 from Europe
Shall i send you your M5 key?pljones wrote:Ah yes, I do have more than 1 MIDI input... So many things to remember to turn off
Yes i assume you Birds Of Io played just shortly, in between the demo noises?Hmm but no noise during playback of Birds of Io? I'll have to listen harder to see if I just missed it.
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
I'm not sure how much time I'll have to play with MuLab this cycle, unfortunately. Far too many goodies in it - and I've hardly started learning M4 properly...mutools wrote:Shall i send you your M5 key?
Yes, it completes a single playback in just under the time!mutools wrote:Yes i assume you Birds Of Io played just shortly, in between the demo noises?