Originally Posted by DeaconBlues09
....Fact is that I'm dying to test out all these scripts and stuff, but everything I install, and nearly every script I run in Reaper, seems to leave something somewhere in my C drive. I'm down to my last 20 GBs on my C/ drive and I can't afford to give up an inch of it or my PC will stop operating properly. (Yes, I know, I need to get a new, larger drive,...)
Reaper won't fill up hard drive unless you check the Copy all media box in the Reaper Save dialog. Don't select copy or move as it will just save the wav instructions only and the Reaper project file will be tiny.

Unrelated follow-up question; in the GIF, the tracks/time selections you import from the SGU seem to be automatically segmented into discrete items complete with stretch markers upon import. Am I interpreting that correctly?
Yes, this is how it works, you can fine tune the riffs this way by making the items longer or shorter, you can't do this with a consolidated wav file.
The stretch markers allow you to change the tempo in Reaper and the tracks will follow or you may have a varying tempo map.

P.S. Not marking this as resolved yet, as I'm still interested to know about how to go about rendering and exporting a time selection from within the main program...
See pic

DB09

It won't fill the C: drive up as it reads and plays the wav instructions direct from E: drive.

[Linked Image - Only viewable when logged in]

Generate up your song in Biab, freeze all the tracks and Save.
Run the "Script: Import frozen SGU MGU realtracks drums tracks GUI.lua" in Reaper, open the frozen SGU, Import Chords if needed, Reload Tracks.
So I just erase the original soloist track in Biab then just generate up the section/Bars I need, save track frozen as before, then Reload Tracks in Reaper GUI and insert in selected track.
[Linked Image - Only viewable when logged in]