You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have what feels like a strange issue. I was messing with live.ppooll.amxd and having a great time, trying things out within Live. Then I used an x_y@ (from the community contributions) to control a flop@ start and length, making some fun glitchy sounds. Since then, the behavior of some acts (flop@ and gg.rainer@ being the ones I've tried) are not working correctly. flop@ doesn't track start and stop with buffer selection, and gg.rainer@ only makes sound if grain size is super small. I've tried deleting and reinstalling everything several times, and tried different versions of Max. Note: things are working as expected in the standalone ppooll in Max. Using the latest update on Live 11. I am attaching a video for reference, hopefully that helps. Thanks for all your hard work!
Screen.Recording.2023-11-11.at.11.32.37.AM.mov
The text was updated successfully, but these errors were encountered:
Thanks for writing all this up & the vid, very helpful. Were flop & gg behaving fine before loading that x_y act? I dont even have that on my computer so I'll have to find it somewhere
Hi there,
I have what feels like a strange issue. I was messing with live.ppooll.amxd and having a great time, trying things out within Live. Then I used an x_y@ (from the community contributions) to control a flop@ start and length, making some fun glitchy sounds. Since then, the behavior of some acts (flop@ and gg.rainer@ being the ones I've tried) are not working correctly. flop@ doesn't track start and stop with buffer selection, and gg.rainer@ only makes sound if grain size is super small. I've tried deleting and reinstalling everything several times, and tried different versions of Max. Note: things are working as expected in the standalone ppooll in Max. Using the latest update on Live 11. I am attaching a video for reference, hopefully that helps. Thanks for all your hard work!
Screen.Recording.2023-11-11.at.11.32.37.AM.mov
The text was updated successfully, but these errors were encountered: