Also I've noticed if I hide MuLab and bring another application to the front, or change views, the VI interface "goes white" (MuLab bar remains at top) and I have to close it and reopen to adjust the VI? Didn't do that before... Started after new version I believe.
Drag and drop midi clips bpm...
- KVRAF
- 2874 posts since 22 Oct, 2002 from "somewhere between digital and analog"
I just noticed that when you fixed the drag and drop on the OSX version that when dragging clips into a session - the clips change the "session bpm" to the clip... rather than the clip acquiring the session tempo? That's not the way it's supposed to work... clips acquire the session/song tempo in Logic etc.
Also I've noticed if I hide MuLab and bring another application to the front, or change views, the VI interface "goes white" (MuLab bar remains at top) and I have to close it and reopen to adjust the VI? Didn't do that before... Started after new version I believe.
Also I've noticed if I hide MuLab and bring another application to the front, or change views, the VI interface "goes white" (MuLab bar remains at top) and I have to close it and reopen to adjust the VI? Didn't do that before... Started after new version I believe.
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
You can load MuClips in Logic, then? Wow!
- KVRAF
- 13863 posts since 24 Jun, 2008 from Europe
I think DHR meant MIDI files. When dropping MIDI files onto the composer the tempo events of the MIDI clip are merged into the tempo track. Maybe it would be better if there was a popup option alert: "Merge Imported Tempo Events" - "Ignore Imported Tempo Events". What do you think?
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Ah.... yeah, actually, I had this issue too with MIDI files: ignoring the tempo in the dropped file is probably what you'd want by default.
Just to be clear: a 4/4 file imported into a 4/4 project should have "1" of each bar imported aligned to "1" of the project (allowing for any drop offset), regardless of the tempo of the imported MIDI file or the project. (Dropping a 6/8 - or whatever time signature - file into a 4/4 - or whatever time signature - project means still aligning "1" of each bar.)
Just to be clear: a 4/4 file imported into a 4/4 project should have "1" of each bar imported aligned to "1" of the project (allowing for any drop offset), regardless of the tempo of the imported MIDI file or the project. (Dropping a 6/8 - or whatever time signature - file into a 4/4 - or whatever time signature - project means still aligning "1" of each bar.)
- KVRAF
- Topic Starter
- 2874 posts since 22 Oct, 2002 from "somewhere between digital and analog"
Yep midi files. Most of my clips from the drum synths (I use) are 4/4, although I haven't tried anything in odd time signatures? It is kind of interesting to allow the session bpm to change per clip though... kind of like a tempo change! Hmmm... Might be a cool feature. 
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
I guess if there are multiple embedded tempo marks, then it's likely to be important (i.e. if the tempo of the MIDI file changes). You might have a MIDI file just for "Accelerando 100bpm to 120bpm in 1 bar 4/4".
How about some kind of "Absolute / Relative" change? With "Absolute", the initial imported tempo would take effect but with "Relative", it wouldn't - with any later ones being adjusted (either percentage-wise (e.g. above: 20% increase)? offset-wise (e.g. above: 20bpm increase)).
How about some kind of "Absolute / Relative" change? With "Absolute", the initial imported tempo would take effect but with "Relative", it wouldn't - with any later ones being adjusted (either percentage-wise (e.g. above: 20% increase)? offset-wise (e.g. above: 20bpm increase)).
