bachproject.net

Great! Thanks!

Dear Daniele and Andrea, I was wondering: would it be feasible for you to implement an attribute to [bach.comb] similar to the @maxcount present in [bach.perm]? It would come in handy, since it would prevent long computation times while allowing big input lllls. Do you know what would be great for b...

Hi everyone! I'm aware that bach objects do not suffer from the same limit to number of characters in a message that regular max objects have. But I'd never witnessed what would happen in a situation where a message going from bach to max exceeded that limit. Today, I found something in this regard ...

Great! I'm glad I could be of help! And I'm happy with the terminology, too!

Hello again, I forgot to say: I'm on a MacBook Pro late 2009 running Yosemite. I've just confirmed on a PC running Windows 10 Home 32-bit version 1709 and the behaviour is exactly the same. Just to be clear: currently, "select note if voice == 1 && onset >= 2000 && onset <= 3000" does the same thing...

Yes, indeed: the one I pasted on the third post of this topic.

Although, if you don’t make it account for parts, I’m afraid you’ll end up with a discrepancy:
- in “select 2000 3000 nil nil 1”, the 1 refers to voice (voiceensemble);
- in “select chord 1 -1”, the 1 refers to part (and it seems fast to me);
Well, no big deal. It’s just a thought.

OK, I totally see your point...

Thanks for replying. Your solution is an elegant one! However, the 'direct selection' (as I call it) is quite faster than the 'conditional selection' – like tenfold, according to my measurements (check my patch). It might have an impact, in a realtime context. Would you consider applying the 'select...

Hey guys! How does one select notes in specific parts? The old syntax 'sel nil nil nil nil 1' only seems to work when parts are expanded as voices. I came up with a solution but it's clearly an inefficient one... A great 2018 for you all! Pedro Louzeiro <pre><code> ----------begin_max5_patcher------...