xenakis

I am having a problem with a patch in which I do the following things.

1. Use a script command to create a buffer~ object, info~ and a pack object.

2. Use a script command to connect them all.

3. Load the buffer~ with a sound and get the infortions with the info~ object and send them in a coll.

The only thing left is the buffer~ object.

My patch works fine when used with no overdrive, but in overdrive mode I get disconnect errors. It is as if the disconnect messages come before the object is even created. I am wondering if things happen too fast in overdrive and the scheduler gets messed up at the point where the buffer~ object is being loaded.

The only thing left is the buffer~ object. 

script-connectdisconnect-error

Thank you for your ideas... Here is where I am.

1. I don't want to use sfinfo~ because I want the program the run fast. I want to avoid going to disk since I already loaded the file at this point in the buffer~, I imagine using info~ is faster.

2. I changed my patch and now use only one info~ which I don't destroy. Thanks for the type on 'set'. The program is cleaner.

3. I tried using defer in several places, but it didn't help. I don't know where I could use it??!

So, now my program goes a little like this:

-- 1. I create a buffer~ object with an original name.

-- 2. I change the name of the info~ object to reflect the one of the buffer.

-- 3. I connect the inlet of the patcher to the buffer~ and the buffer~ outlet to the info~ object.

-- 4. I load the buffer~, get the infos, pack them into a coll for safekeeping.

-- 5. I destroy the two connections in order to leave the buffer~ alone.

-- 5. I send a bang out of my patch to indicate that everything is done.

(this permits me to create many buffer~, as much as possible. I also have a routine to delete them)

When I send the object more than one file to load, the object doesn't seem to work. I get a 'replace object corrupted' error. Sometimes I get 'no object to disconnect'. Along those lines.

When I trace enable everything is fine. No messages in the wrong order. So, I imagine this as to do with the speed of execution.

Is this normal with a scripted disconnect? 

When I trace enable everything is fine. No messages in the wrong order. So, I imagine this as to do with the speed of execution. 

Is this normal with a scripted disconnect? 
Where do I defer?


script connect/disconnect error