If you dump a ton of lines into the terminal, it seems to slow down over time, until scrolling is a stuttery. Maybe it would be a good idea to cap the maximal amount of lines, or even compare with a string length and then cap the last, incomplete line, too? Since there can be long lines, e.g. dumping a base64 string preset.
oh yes, when i was trying to do CDATA dumping with Amigo, just to be able to inject the CDATA chunk back, Terminal definitely became unresponsive and slow. didn’t know what to do about it, since i needed to get in a 100,000 or 300,000 frame sample to see if it loaded back correctly.
these types of dumps are heavy on the Terminal and not sure if there can even be a solution that wouldn’t choke it eventually.
As a workaround you can always dump large output into a file instead, this comes with a bit more complexity but can be more convenient, for example for search and comparison.
1 Like
@unless is there a simple commandline of doing this?
is this the most minimal system of doing it?
(function()local f=io.open("/tmp/file.txt","w")f:write((renoise.song().selected_device or{}).active_preset_data or"")f:close()end)()
or can this be optimized somehow
You could use do ... end instead of making an anonymous function, but other than that, it’s probably pretty close.
Perhaps it’d be nice to be able to define utilities functions/aliases for use in the Terminal. Though I just use a scratch file inside my project instead of messing with the Terminal most of the time.