Merge kit pieces of 2 kits to create 1 new one

Use this forum for Jamstix technical support questions
Post Reply
TheSystem (Archive)
Posts: 262
Joined: Wed Dec 16, 2009 4:56 am

Merge kit pieces of 2 kits to create 1 new one

Post by TheSystem (Archive) »

Hi

I have a kit I created for a 3rd party pack that I use for cymbals only. The kit is still a full kit but I have unloaded all shell samples. I would like to create a new kit with these cymbals and have Jamstix samples or other 3rd party mapped kit pieces along with these cymbals.

I know I can manually load the samples but I want to know if there is a file or files where I can copy data for cymbals only and add it to a new file and then do the same for the Jamstix kit for the drums only?

It would be cool to be able to select multiple kit pieces, save as a New Kit and then be able to Add To Kit. This way I could save cymbals only as a kit, load the new kit and then select the drums and add to the kit I just created and then save.

I have not seen Ralph much lately. Hopefully he is well and still supporting JS. If not it is still great for me in its current state.

Brian
Azimuth (Archive)
Posts: 1674
Joined: Fri Nov 19, 2010 2:16 am

Merge kit pieces of 2 kits to create 1 new one

Post by Azimuth (Archive) »

Hi Brian,
I'm not quite following you here. You could create a new .mdmap to assign the cymbal mapping to the external VSTi cymbals while leaving the Jamstix kit drum mapping untouched. Then just load that output mapping in the Kit window. Is this what you need?
TheSystem (Archive)
Posts: 262
Joined: Wed Dec 16, 2009 4:56 am

Merge kit pieces of 2 kits to create 1 new one

Post by TheSystem (Archive) »

Azimuth wrote:Hi Brian,
I'm not quite following you here. You could create a new .mdmap to assign the cymbal mapping to the external VSTi cymbals while leaving the Jamstix kit drum mapping untouched. Then just load that output mapping in the Kit window. Is this what you need?
i have created a kit with the mapping for SSD and a kit with mapping for another 3rd party already.

i now want to use the shells only mapping from the SSD kit i made AND the cymbals only for the other 3r party kit. all of the info and mapping are created and i figured that info might be in text files that i could just copy what i needed from each into a new file and be done in a couple minutes.

hope that makes sense.
Azimuth (Archive)
Posts: 1674
Joined: Fri Nov 19, 2010 2:16 am

Merge kit pieces of 2 kits to create 1 new one

Post by Azimuth (Archive) »

Hi Brian,
That information would be contained in the 2 .j2k kit files you created in their "Element" section. I'd think you could copy and paste it from the 2 .j2k files in Notepad to a 3rd new one. I've never tried it but it should work I think.
TheSystem (Archive)
Posts: 262
Joined: Wed Dec 16, 2009 4:56 am

Merge kit pieces of 2 kits to create 1 new one

Post by TheSystem (Archive) »

Azimuth wrote:Hi Brian,
That information would be contained in the 2 .j2k kit files you created in their "Element" section. I'd think you could copy and paste it from the 2 .j2k files in Notepad to a 3rd new one. I've never tried it but it should work I think.
thanks. i will give it a shot and report back.
TheSystem (Archive)
Posts: 262
Joined: Wed Dec 16, 2009 4:56 am

Merge kit pieces of 2 kits to create 1 new one

Post by TheSystem (Archive) »

after checking out the .j2k files, it think is better and quicker for me to do it the way you suggested.

i am not familiar with the Element names and how they are mapped to actual kit pieces. They all show something like this in the 2 files for the respective kits:

[Element 0]
Sound=0
Name=MIDI OUTPUT ONLY

unlike those files that use JS sounds. For example,

[Element 0]
Sound=0
Name=Kick - 22'' JS3

It would be easy enough to figure out what Elements are what kit pieces but all of this is probably not worth it.

Thanks for the help.
Azimuth (Archive)
Posts: 1674
Joined: Fri Nov 19, 2010 2:16 am

Merge kit pieces of 2 kits to create 1 new one

Post by Azimuth (Archive) »

Hi Brian,
Yes I think the mapping route would be faster and more straightforward. For future reference though Appendix B on pg. 73 of the user manual shows what the various IDs are for the elements, if the need ever arises.
Post Reply