Yes, I would call this a bug! ... Only if I would be able to reproduce it. The merge objects now, works like it did always, (except that the "soft" loop it kept, if set) ... No turning loops to real copies anymore. This happened the other night and I cant reproduce it. So its fine now (why it wasn't I don¹t know) and actually _you_ would call it a bug now, since its actually working my way! ;) Uli. > uswitalski@... writes: >> now with 5.0 "merge objects" and "merge objects by tracks" >> will also turn loops to real copies and merge... > > You call that a bug? That's most definitely a good feature. > It makes no logical sense to *not* do it this way. > > If you really don't want the "virtual" data (ie... what is looped) > to be included in the merge, then turn the loop OFF. > > The only time you don't want this to happen is when you > are merging two loops on different tracks that start and > end at exactly the same time. Why? Because now the loop > can be turned ON for this merged region and musically it > will be the same as before when it was two parallel loops.