Ollie Bown

I am getting a freeze which appears to be caused by the problem with sfrecord~ described in this post:

https://cycling74.com/forums/problems-in-sfrecord

I have tried a few workarounds including alternating between 2 sfrecord~s and using buffer~ and record~ instead. The latter is problematic because the extra RAM required by this approach appears to be an issue. The former didn't fix the problem.

I am writing files between 5 and 20 minutes long, aiff format, using MaxForLive. Files are written one after the other. I put a long pause between closing one file and starting the next one (e.g., 15s), and between opening the file and starting the recording. The freeze (spinning wheel) occurs about 1 hour in.

I'm just wondering if there has been any development on this problem, or if anyone can offer an alternative object to sfrecord~ which basically performs the same function.

PS: a more radical workaround is to write a script that force-quits Live and reboots it, but the problem with this is that Live opens with a dialog box after a force-quit which requires user input.

is-sfrecord-hang-fixed-noted-is-there-an-alternative-to-sfrecord

Do you happen to have a workaround for this issue ?

Try sending a "resample 1." message before starting each recording, aka before sending a new open message. I think it's a buffer-full problem (better say a buffer greater than 2 Gb). Another solution is to send a delete obj message and a script create sfrecord + connections. This way is not so easy but works, because the obj will be reinitialized completely. See the thispatcher obj in the p script infos. The sfrecord obj should have a Scripting Name, and in the same way, also all other objects connected to him.

Try sending a "resample 1." message before starting each recording, aka before sending a new open message. I think it's a buffer-full problem (better say a buffer greater than 2 Gb). Another solution is to send a delete obj message and a script  create sfrecord + connections. This way is not so easy but works, because the obj will be reinitialized completely. See the thispatcher obj in the p script infos. The sfrecord obj should have a Scripting Name, and in the same way, also all other objects connected to him.

Is sfrecord~ hang fixed / noted? Is there an alternative to sfrecord~?