With path issues not entirely resolved, i'm going to add a small function to the wav_writer.py to create a wav_writer.ck in the current directory if it doesn't exist already. These files are 11kb, so the size isn't going to be a problem -- it may be a little untidy, there may also be scenarios where the OS won't permit the creation of wav_writer.ck.
I'm using the wav_writer frequently now to sample one-shots, copying the .ck to a new directory interrupts a workflow.
ideally wav_writer.ck resides in the same location as the chuck executable
alternatively (equally ideal) is to send the wavOut writing instructions as code along with the song in OnTheFly mode.
The on the fly method is currently not possible on windows, which is what I develop on. We are awaiting patches to be accepted for this issue.
zeffii
commented
10 years ago
i'll have to experiment with this.
With path issues not entirely resolved, i'm going to add a small function to the wav_writer.py to create a wav_writer.ck in the current directory if it doesn't exist already. These files are 11kb, so the size isn't going to be a problem -- it may be a little untidy, there may also be scenarios where the OS won't permit the creation of wav_writer.ck.
I'm using the wav_writer frequently now to sample one-shots, copying the .ck to a new directory interrupts a workflow.
The on the fly method is currently not possible on windows, which is what I develop on. We are awaiting patches to be accepted for this issue.