Hi Os,
I have an issue when using tap record in the Augustus 2.1.2 AU-plugin. It appears that Tap record does not start recording when you have fired a clear loop command just before the Tap record command. It does work normal when not using clear loop.
Sjaak
Augustus - issue with tap record
-
- KVRer
- 5 posts since 28 Jan, 2009
-
- KVRian
- 1417 posts since 22 Mar, 2002 from UK
Clear Loop takes a certain amount of time to complete - you can't Tap Record immediately after starting a clear. (This is mentioned in the manual.)
Not sure if this helps but one of the auto-fade modes fires a clear loop immediately after the loop completely fades out.
Not sure if this helps but one of the auto-fade modes fires a clear loop immediately after the loop completely fades out.
-
- KVRer
- Topic Starter
- 5 posts since 28 Jan, 2009
Would it be possible to implement a immediate clear loop in V3?
PS Just curious, what is the reason why it works as it works? It now takes several seconds before you can continue with the next loop.
Sjaak
PS Just curious, what is the reason why it works as it works? It now takes several seconds before you can continue with the next loop.
Sjaak
-
- KVRian
- 1417 posts since 22 Mar, 2002 from UK
It's implemented the way it is because clearing such a large memory buffer does take a while, and rather than generating a massive CPU spike it seemed better to try to maintain CPU usage at the normal operating level and spread the clear operation out over time.
Possibly this could be revisited - technology has moved on since Augustus was first written. Maybe it would be OK to do it instantly now. I could certainly try putting in an option.
An alternative would be to have multiple buffers - then rather than clearing the current buffer, it could jump immediately to using a new, fresh buffer. The obvious downside being that this would double the memory usage.
Possibly this could be revisited - technology has moved on since Augustus was first written. Maybe it would be OK to do it instantly now. I could certainly try putting in an option.
An alternative would be to have multiple buffers - then rather than clearing the current buffer, it could jump immediately to using a new, fresh buffer. The obvious downside being that this would double the memory usage.
-
- KVRer
- Topic Starter
- 5 posts since 28 Jan, 2009
Thanks for the update, there's always a reason why something has been implemented the way it has been implemented. I suggest you leave it as it is, "it works as designed".os wrote:It's implemented the way it is because clearing such a large memory buffer does take a while, and rather than generating a massive CPU spike it seemed better to try to maintain CPU usage at the normal operating level and spread the clear operation out over time.
Possibly this could be revisited - technology has moved on since Augustus was first written. Maybe it would be OK to do it instantly now. I could certainly try putting in an option.
An alternative would be to have multiple buffers - then rather than clearing the current buffer, it could jump immediately to using a new, fresh buffer. The obvious downside being that this would double the memory usage.
Sjaak