[line]

[f]
[line~]
[sig~]
[snapshot~]
[tabwrite~]
[tabwrite]
[tabsend~]
[tabread]
[tabread~]
[tabread4~]
[expr]

not vanilla:
[pack~]
[unpack~]
[unsig~]
[speedlim]

wow, can you even set this flag with [pd~]?

[tabwrite~] writes to ram
[writesf~] writes to disk.

It depends on what you want to do with the recorded sound in realtime? How fast should it be?

Generally spoken if you want to record audio over a long period of time it's common to use [writesf~] as memory space of ram is much smaller than diskspace (on PCs).

[!= 0] and [spigot]

[poly]

@GWB70
that patch should work.
But what is [bpm] doing there?

Do you receive anything with the [midirealtimein]?
Did you connect Midi virtually?
I am using Linux, so don't know about that part in Windows...

@esaruoho
The above link to pd-list with [set $1( messages should work!?
If the BCR is always forwarding the incoming data (there should be a mode that doesn't), you could easily hold back that incoming data with [t f f] [change] [spigot] ect.
Even subtracting the output from the incoming data, - for not muting the knob while data is being spit out, could be a work around.

[bang~] only goes down to a blocksize of 64 samples.
This seems to be a bug.

Any idea how to get a bang with every sample?
Maybe another way to try?

Something about us > Roland VP9000 > Variphrase

Ok, there is @katjav PD-double:

http://www.katjaas.nl/doubleprecision/doubleprecision.html

https://github.com/pd-projects/pd-double

*How about Purr-Data-double? *