I end up spending a lot of time working on KP3 generated loops, which need to be manually trimmed and looped in an audio editor.
Not to mention using the KP3 editor is not the most fun way to export 100 sample loops from a memory card.
I have begun investigating building a batch converter application. I would also like to export the loops properly trimmed also (if possible).
Has anyone already worked out the KP3 audio format? I know it stores the measure length, BPM, etc. But I am not sure if it stores a "marker" which indicated the first beat of a loop (in relation) to the start of the file itself.
I didn't think it did, because the align function will cause bad looping if the samples were recorded in different "sessions".
Anyone?
cheers
ripe
Anyone interested in building a batch KP3 to .wav converter?
Moderators: Sharp, X-Trade, Pepperpotty, karmathanever
This would be a PC only app that would read the files directly off memory card.
I would be reverse engineering the format using a hex editor, and just converting the file over to .wav format. This shouldn't be too difficult.
I'm not sure about the sysex, it would be easy to monitor any sysex using a MIDI monitor, but writing code for an app that uses MIDI is not my expertise...
cheers
ripe
I would be reverse engineering the format using a hex editor, and just converting the file over to .wav format. This shouldn't be too difficult.
I'm not sure about the sysex, it would be easy to monitor any sysex using a MIDI monitor, but writing code for an app that uses MIDI is not my expertise...
cheers
ripe
It sure sounds possible. I have done those sort of things in the past iin the good old college days.
Maybe I'll give it a shot for my self esteem.
It should be quick to find where all the parameters are stored. Hopefully the audio data is just tacked on at the end. Maybe it will have a header to identify the type of file.
What I would to is take a audio file and stort it in a kp3 file using an editor. Then I would increment each parameter by 1 and save it in another file. Then using a "diff" program to compare the two files should show you where the audio data is.
Then I would modify each parameter one by one and store in a kp3 file named after the parameter. Comparing each of those files should show where each parameter is stored.
After that is done, a program to convert kp3 to wav or whatever should be too difficult.
Maybe I'll give it a shot for my self esteem.
It should be quick to find where all the parameters are stored. Hopefully the audio data is just tacked on at the end. Maybe it will have a header to identify the type of file.
What I would to is take a audio file and stort it in a kp3 file using an editor. Then I would increment each parameter by 1 and save it in another file. Then using a "diff" program to compare the two files should show you where the audio data is.
Then I would modify each parameter one by one and store in a kp3 file named after the parameter. Comparing each of those files should show where each parameter is stored.
After that is done, a program to convert kp3 to wav or whatever should be too difficult.
I got contact with one of the guys over at Korg. He's the poor bastard who gets my KP3 2.5 wish lists. 
I know nothing of coding or its language, but I can forward a bunch of questions that would be understood by the right person at Korg.
If they are willing to release that info or not is another thing, but it's worth a try.
They did listen to wish list 2.0
I know nothing of coding or its language, but I can forward a bunch of questions that would be understood by the right person at Korg.
If they are willing to release that info or not is another thing, but it's worth a try.
They did listen to wish list 2.0
