>> 1) my experience, as i mentioned before, is that the GUI for complex
>> audio+MIDI applications, is at least 2/3 of the code, and at least
>> that much of the effort. since its unlikely that xrazor was written
>> using any kind of cross-platform toolkit, porting such a beast (if
>> the code was available) would be a difficult undertaking.
>The GUI is relatively simple...
I take it you are kidding. Any time you mess around with waveforms,
particular when they are drawn with frames_per_pixel != 1, and then
add lots of interconnected buttons and features, its never
simple.
>signal. The patented Beat Munging algorithm looks at the energy in
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Danger Will Robinson!
>I think it would be better to have a beat-slicer as a separate app,
>because its purpose is also to find loops, and you could prepare your
>samples for use in an ardour session...
you don't think being able to find loops within a multitrack,
multichannel DAW is useful? i'm not against standalone apps, but this
seems like a definite feature. ProTools has "BeatDetective" precisely
for this purpose.
>> a framework for sample dumps and MIDI note maps would be needed.
>maybe we could ask the author of XRazor...
Oh, its not hard. Its just more work :) Like I don't have enough ...
--p
