since MPT recognizes the cues in wav data, it could be nice to be able to trigger a specific part of a sample with an effect such as S7D...
for instance S7D would trigger the sample from cue #1, S7E from cue #2 etc....
it would make OMPT better on the sample handling, making easier to remap a sample regarding the BPM, changing the melody without cut/past edit in the sample editor ... which increases the number of samples used in a track...
What do you think about that?
MPT recognizing cues in wavs ? I never heard about it.. If so, it might be quite useful I guess.
Are these cues also shown in the sample tab ?
it seems it only regconizes loop point created by ompt itself.... but that cue is recognized by audio apps... maybe there's still hope, anyway I thought i'd have been a nice feature...
Just a hint: These Loop Points are also recognized by Wavelab...
So actually it's already the other way around. OMPT loop points can be read by other wav-apps.
BTW : there can be only 2 loop points in a wav. Begin and end of the loop. Cues in wav-files can be as many as necessary.
It would be cool if OpenMPT would atleast show the Cues even if you can't do anything else with them. Atleast you can use this to add markers from an external wave editor so you can see them in OpenMPT.
But indeed, it could be cool to allow the insert of certain cue's and have an instrument that plays the same sample but different cue positions, based on the note you play. Like a beat slicer.
to go abit further, it would be really cool if you could trigger instrument events based on sample cues. so if the sample reaches a certain cue, a note off could simulated...
I'm sure there're some interesting issues to develop for modplug with the cue points and I'm glad to read that the topic brings some nice ideas!
Quote from: "le_parasite"since MPT recognizes the cues in wav data, it could be nice to be able to trigger a specific part of a sample with an effect such as S7D...
for instance S7D would trigger the sample from cue #1, S7E from cue #2 etc....
That is just brilliant. I never even thought about it, but its simply brilliant. Who needs inaccurate sample offsets after a feature like this? Not even beginning to talk about the difference in usability.
Just checked. Cool shows the loop points made with OMPT too.
Quote from: "Sam_Zen"Just checked. Cool shows the loop points made with OMPT too.
it even reads "loop point" lol
Yeah. As a matter of fact I wondered about that because I'm only familiar with the 'cue' points.
Obviously it's a regular Cool thing too. This asks for investigation.
yes! fantastic idea, it bridges the gap between using fiddly offsets (which i consider bad practice because it's just not accurate enough) and completely chopping the beat up into component parts (which is more effort than a lot of people like to go into). oh, and i think this would mean you could easily pitch up and down drum loops as if they were composed of individual hits.
THIS IS THE FUTUR! lol
what the technical dudes think about that feature?
So basically what you're looking for is some sampler capability from mpt... What sort though? Do you want beatmachine style sampling, where the sample is sliced into a whole bunch of little "sections", each of which can be individually played back? Or do you want a slightly more loopier system, where you can "snap" the cues to the beats? That is, you can tell mpt where each beat of the bar (or subbeat, or whatever) is, and it'll make sure that no matter what tempo the sample is played back, those cues are hit at the right time?
It sounds like you want to turn the sampler-ness of mpt into something a bit more serious than just playback, and I'm all for it. Another idea: why not integrate it with instruments? I'm guessing that this'll be mostly useful for pre-recorded beats/melodic phrases, which'll tend to be played at about the same pitch, right? So, assuming the beatmachine sampling above, why not assign a different note to each cue? For example, you could have normal notes C4..B6, then have cue 1 triggered by C6, cue 2 by C#6, and so on. That'd be a bit easier than using effects, and it's the way that most samplers seem to work, which would make it more "plug and play" friendly...
While you're waiting for this feature to be implemented, it might be worthwhile trawling the net for some sampler vstis, just to get a feel of what can be done, and how. I personally use Kontakt, which offers a whole lot more than I've outlined above, but there's a whole raft of other samplers available out there.
I wasn't so much thinking about MPT having sampler capability. Imo a step too far for the moment.
As far as I'm concerned, this is about enhancements of the sample tab.
Having cue points beside the loop points would be nice. Not only for finding beats in a complete bar, but also with 'single' samples.
Of course one can make a cue in a sample by using the offset-effect code. But that's based on ticks-value.
Quote from: "Sam_Zen"Of course one can make a cue in a sample by using the offset-effect code. But that's based on ticks-value.
Actually it's not based on ticks, it's based on samples (a sample consists of a set of digital values, each value is also called a sample.) This may seem an irrelevant point to make, but I think it can be helpful to realize that the offset command works with space, not time.
Sorry bvanoudtshoorn I didn't see your post...
Quote from: "bvanoudtshoorn"So basically what you're looking for is some sampler capability from mpt... What sort though? Do you want beatmachine style sampling, where the sample is sliced into a whole bunch of little "sections", each of which can be individually played back?
It's the way I see it, but I guess a simple step in dev. with cue triggering would give an extra interest for musician who love to rearrange audio sample in a recycle way...
Quote from: "bvanoudtshoorn"Or do you want a slightly more loopier system, where you can "snap" the cues to the beats?
if the pitch tempo lock still work witha cue triigering feature, it will like that I guess
Oops, forgot to close this one. With the improved volume-column oxx behaviour in OpenMPT 1.24, WAV cue points are automacially imported for usage with the oxx command!