Open kmatheussen opened 8 years ago
Good question. I would think no, not that important. Because the main thing is that it is easy to save/load note patterns and melody lines for later use in a quick fashion.
Of course it would be of advantage if you have a pattern that is bound to a specific instrument/sample so that you can load it directly complete, but we have a preset system now for instruments and whole groups of modules so it is quite easy to work around that "limitation" by just saving all good sounds/module networks anyways.
Saving/loading note data is not that easy to workaround. Especially not if you want to test multiple things from multiple templates/songs.
Another thing would be how to deal with automation data. I think that it is only possible to include automation data in save/load track/block when the instrument is included? (Or there could be an option to "reassign fx text automation to xyz?)
But again, note data and multi-track note data (patterns) save/load is in my mind much more important.
Hmm. Both instruments and imported automation is handled when pasting blocks, even when pasting a block or track copied from an earlier session. I remember vaguely that it was tricky to make work, but hopefully it should be possible to reuse this functionality to save/load blocks and tracks.
On Wed, Apr 19, 2017 at 9:04 PM, Lykdraft notifications@github.com wrote:
Another thing would be how to deal with automation data. I think that it is only possible to include automation data in save/load track/block when the instrument is included? (Or there could be an option to "reassign fx text automation to xyz?)
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/kmatheussen/radium/issues/462#issuecomment-295393755, or mute the thread https://github.com/notifications/unsubscribe-auth/ABF9p87pEHQQsY5Xx3NAmc9XR3hiSRe3ks5rxlqsgaJpZM4IDzv6 .
If it would be possible that would just be icing on the cake.
Maybe you just need a format to save the copied block/track to disk like you did with the .rec / .mrec? (i.e. a menu entry: load/save clipboard data from/to disk maybe?)
I've implemented loading and saving of blocks and tracks now, but when loading blocks and tracks, all instruments and automation is stripped of. So it's a first step.
Is it important that the saved blocks/tracks include instruments?