SmokeDoepferEveryday

recreating-a-kreidler-patch-in-max-troubleshooting

the main difference is sf* objects in Max use 0/1 for start/stop. The rest is more or less the same.

that makes sense now, I'm just getting the console error 'sfrecord~: already open' and 'sfrecord~: start requested without preceding 'open''

should I set a deferflow on the first open message?

the above was to do with having a rec1 and rec2 wav in the folder when pressing start.

So it works, but I see you've rigged it to loop the two playbacks - the other patch is rigging to pull sound from the playback back through the adc with recursive convolution from the adc dac etc

Will try and rig it for that now! thanks for the help

perhaps it's because there isn't a '0' sent back to the first sfrecord? 

perhaps it's because there isn't a '0' sent back to the first sfrecord? 
can't quite figure it out   : (

I just rearranged boxes visually, so the patchers should do the same thing. Those sf* objects are quite complex wrt exact timing (in other ways also), I/O times are hard to predict. I must admit I hardly understand what's happening under the hood – this patch should record longer and longer sound files (as there is 1/5 second delay added each time). But it doesn't. I'm curious why this is the case.

That's great with an emergency stop [I've been whacking cmd + .]

But your version is still looping a dry ping-pong for some reason - is it because it bypasses the adc after round 1?

- I slotted in the 1s and 0s on the original patch and it now convolves from speaker to mic and records the iterations which is what I expected - need to deal with some zero crossings next! 

on the del 200, yeh I though that was delaying the recording being set to stop some scheduling issue with making files etc - but I'm a newb so really uncertain - here's the convolving patch below:

- I slotted in the 1s and 0s on the original patch and it now convolves from speaker to mic and records the iterations which is what I expected - need to deal with some zero crossings next! 

on the del 200, yeh I though that was delaying the recording being set to stop some scheduling issue with making files etc - but I'm a newb so really uncertain - here's the convolving patch below:

(👆 his name is "SmokeDoepferEveryday" 😆 GENIUS! my day just got a whole lot better 😁)

Solved