Buffer releasing in build from 'next' branch

Issue #92 resolved
Former user created an issue

I am using a set of externals compiled from Alex's latest 'next' branch. I cannot replicate the issues on an older set of compiled externals - namely the ones that went out with the latest tester release.

The problem is as follows:

  • fl.read~ refers to a named buffer~ filled with an audio file.

  • You attempt to read from it which works fine.

  • You change the audio file by typing into the object box which throws the error - "can't read file now".

  • This error can't be reproduced with ibuffers~ which work normally.

Comments (3)

  1. Former user Account Deleted reporter

    Further development

    This can be replicated on the 2.0 release that was given to the tester list. It seems to be audio file specific. It is possible to change the size of a buffer and record into it without any problems or receiving the aforementioned error.

  2. Former user Account Deleted reporter

    I went back to Alpha 0.6 to see if the issue had been lurking since a long time. I have been able to replicate it in a version as early as this. Perhaps it has been there for a while.

  3. Former user Account Deleted reporter

    As with issue #94 I think that this has either dissapeared in the latest build or was an issue specific to my install and a bad interaction with another external or otherwise.

  4. Log in to comment