search

stretta / BEAP

BEAP Modular. Berklee Electro Acoustic Pedagogy
300 stars 50 forks source link

How to incorporate updates... #5

Closed tildebyte closed 10 years ago

tildebyte commented 10 years ago

So I just cloned the repo so I can play around and have my changes available on both of my machines. In the process, it occurred to me that, after pulling from master (my tree or yours)... none of the changes will affect any "racks" I've already created (panic). Is that the case? Or have I missed some clever way of making sure my "racks" are automagically updated following changes in the bp.* patches?

stretta commented 10 years ago

Well. I thought about this quite a bit and I opted to paste the contents into your document instead of referencing the latest module. This would do two things: 1) ensure your patch would continue running as you'd expect, even if you update the Beap library and 2) give you the ability to select a Beap patch and select copy compressed... and paste the thing into an email. Anyone could use the Beap patch (in the Max runtime) without having the Beap library installed.

Now that Beap has matured a bit, I'm beginning to consider linking to module references. Still torn.

If you decide you really want the latest, you could update the bpatchers (of each module) to the new version.

tildebyte commented 10 years ago

I completely agree with your decision to make patches portable and self-contained. I don't see this being an issue, unless you were to make significant enough changes to a module to require updating all of one's patches. It seems to me that BEAP is reliable enough for that not to be an issue. In any case, I updated a patch with the latest Phase Vocoder, and it wasn't too painful. If I'd had more than a few presets, though... :)