silly questionz but help me out bruv

does the program save the 'samples' loop data, ie: if a just keep saving the program "only" - and ive changed a loop point here n there , does the changes get saved? or do i need to save with samples (even though i did that before), sorry to be a braynerd, but its critical that i find out quick

I think you need to save the .pgm including the samples too, because the Loop points are stored in the wave data.

looping is os2 shits me, no ammount of patience can remove the clicks, then on the odd chance i do remove it, it comes back when i pitch up or down.

I'm feeling you, but didn't these clicks also appear in OS1, if you hadn't placed the loop points at a zero crossing anyways?

stan steez wrote:I think you need to save the .pgm including the samples too, because the Loop points are stored in the wave data.

this relates to a thread from a couple weeks back where i was wishing that loop info could be made a part of the PRORAM data, so you could change loop data for all your samples on the fly just by switching to a different program. remember there is all of that empty space in GPE so there is a lot of display room for this feature (toss out that useless 'general midi' display column!). i just hope that it is technically doable.

sooty i was gonna say - i have to differ, i prefer to have it with the samples, if thats defo the way it is at the mo, keeps things in the appropriate place,


but alarm!


however - sometimes i think u r right, mbe the program should hold the 'use-part-of-sample-info', then the samples would just be the basic source of the waves... like many soft samplers and DAWs work.

arebee wrote:sooty i was gonna say - i have to differ, i prefer to have it with the samples, if thats defo the way it is at the mo, keeps things in the appropriate place,


but alarm!


however - sometimes i think u r right, mbe the program should hold the 'use-part-of-sample-info', then the samples would just be the basic source of the waves... like many soft samplers and DAWs work.

yeah. my position on this sort of thing is it's always preferable to have BOTH options available, and then let the user decide how they want to use it. only probs with this are:

1. can sometimes lead to a complicated/cluttered interface
2. can be a pain in the as$ for the programmer to implement / bug-fix / etcc...

i don't propose changing the TRIM screen at all. for those who want to handle all their looping stuff from there, go for it.

BUT i would like to see at least a "loop on / off / alt " column in GPE. and a "loop position" or "loop start" column would be rad, too. that way, those who wanted to take advantage of the extra loop tweakability in GPE could do it. otherwise you could just leave the column at the default setting and the loop settings in the TRIM screen would be respected.

i've recently been going back to a bunch of my old programs that are beats constructed out of one-shot samples (bass drum hits, snare hits, etc.) and turning loop on/off while the sequencer runs to get these crazy rolls/trills much faster than 1/32 note repeat. set insanely tight loops and play with the start/end positions while the sequence plays for all sorts of crazy sounds (like a wavetable synth). thing is the TRIM screen is not a great interface for managing the loop status of a bunch of samples at once since you can only see one sample at a time and have to scroll around, etc. having this in GPE would makes things easier, plus you could save all of your best loop points in different PGM files and switch to them as you go.