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
Just reported an apparent Max 8 bug to @Cycling74 that impacts 264.sfplay~.
We depend on sflist~ outputting preload and preload_error messages to detect when a file has been loaded, but it appears that in recent versions of Max sflist~ no longer outputs these so there’s no way to detect if a file has been preloaded successfully or not.
Impact
Can’t hide a “file loading…” overlay once preloading is complete. For now, I have hidden this overlay entirely.
Can’t show the currently loaded filename once it is loaded.
Our seek functionality also relied on these messages so currently you can’t scroll to a time point with 264.sfplay~ or play from a specific position in a file as part of a cue.
Post here if you spot any other odd behaviour you think might be related!
Update, 23 Jan 2023
Confirmed the bug is only present in Max 8.3 and up. Until this is fixed, we recommend using Max 8.2!
Update, 26 Jan 2023
Response from Cycling '74 support:
I am able to reproduce this error and have brought it to the attention of engineering to take a look at.
The text was updated successfully, but these errors were encountered:
Just reported an apparent Max 8 bug to @Cycling74 that impacts
264.sfplay~
.We depend on
sflist~
outputtingpreload
andpreload_error
messages to detect when a file has been loaded, but it appears that in recent versions of Maxsflist~
no longer outputs these so there’s no way to detect if a file has been preloaded successfully or not.Impact
Can’t hide a “file loading…” overlay once preloading is complete. For now, I have hidden this overlay entirely.
Can’t show the currently loaded filename once it is loaded.
Our seek functionality also relied on these messages so currently you can’t scroll to a time point with
264.sfplay~
or play from a specific position in a file as part of a cue.Post here if you spot any other odd behaviour you think might be related!
Update, 23 Jan 2023
Confirmed the bug is only present in Max 8.3 and up. Until this is fixed, we recommend using Max 8.2!
Update, 26 Jan 2023
Response from Cycling '74 support:
The text was updated successfully, but these errors were encountered: