Well, fantom g owners... I'm sorry to say it, but i think multisamples are out of scope for this project..
Here's how it works so far:
1: Hook the fantom up to the Fantom G editor & load the desired studio set from the SOURCE PROJECT.
2: Choose file-> export SMF-> (studio set + patch).
3: copy the newly created midi to the SOURCE project's SEQ/SMF directory.
4: run this program. specify the midi file as the 'source' & the destination project directory as the 'destination'.
Each of the necessary samples are copied to the destination project's SMPL directory. They are renamed according to the lowest available (nonexistent sample file).
A 'new' midi file will be created inside the destination project's SEQ/SMF directory. It contains the updated version of the studio set.
5: Now, all you need to do is load your destination project & play the SMF.
At this point, you still may have to save each patch & save the studio set in the desired locations. If you are using the studio set for a song, you can simply save the song.
The program is a java application so it will run the same on windows/mac/linux. It is a 'console' application. You can run the program from your command prompt. Shell scripts will be provided for each platform to simplify it's use.
Sorry i haven't attached it for you to see yet. i ran out of time today & it's still not 'nice'. Hopefully my next reply will be saying: "here it is!.."
This next part is just me rambling...
As you can see above, i am using midi messages to set parameters in real time. This has advantages & disadvantages. The good thing is, this program doesn't edit any of the fantom g system files. Therefore, bad things are less likely to happen. Also, it makes the data easier for me to work with & makes it quite portable. The bad part is, you can only edit data which can be transmitted or received as a midi message..
For this reason, i think multi samples will require a different approach altogether. I still intend to make app for them if i can.
I'd also like to make one for RPS/RHYTHM pad sets & associated phrases. (This looks promising)
Finally, i'd like to make one that does something similar for songs. This looks more difficult. At very least, i'd like to be able to update audio tracks & associated samples.
More ideas for this app..
- support live sets & single patches. This is a must & may be part of the first release. Total time 1 day.
- Persist data (if a sample has already been copied from project A to B, rather than make a 'new' sample. Instead, overwrite the existing sample. This will allow later changes to project 'A' samples to be reflected in project 'B' samples. It will also allow for multiple live/studio/single sets to be copied at different times, during different sessions without creating a new sample when it is not necessary. Total time: 1.5 days.
- Reverse operation (i.e. copy 'new' samples back to original project.)
- delete samples ( delete samples previously copied from A to B.)