TheJames
User
Joined: 17 Apr 2005
|
Posted: Sun Apr 17 2005 00:41 A small problem concerning looped samples |
 |
This is not so much a problem as a slight annoyance, but I'd like to know what causes it if only for curiosity's sake. I first installed MadTracker on someone else's computer, and was impressed enough to install it on my own once I got home. What's puzzling me is that although my computer is superior in every relevant respect, I believe (better CPU, more RAM, non-motherboard soundcard), it appears to perform in one respect in a slightly inferior manner to the other computer I tried it on. On the other computer, when I had a looped sample playing, I could drag the loop boundary thingies (you know, the start and end markers) around and the sound would react instantaneously, making it much easier to find a particular sound, and more importantly allowing me to muck around for minutes on end just making a load of meaningless noise. My theoretically superior computer, however, does not do this. When I drag the loop boundary thingies around, the sample cuts out temporarily and doesn't come back in until I've released the boundary and the sample's called again. I've had a look through the MadTracker settings, but nothing instantly struck me as a likely solution. The only thing I can think of is that I might have had a different version on the other computer. What I currently have is the beta thing (2.5.0 RC2 with the fix), whereas at some point or other on the other computer I believe I've had both 2.5.0 and 2.3.2, and it seemed that somehow the two installations encroached on each other a little (the colour schemes got all confused, for example). The whole situation got a little confused, and to be honest I'm not entirely sure what was going on by the end of it. I know it's a very cosmetic niggle, but I'm intrigued as to why it even happens, and it would be quite nice if I could sort it out. Anyway, that's a very protracted and vague description of my conundrum, but hopefully someone will be gracious and patient enough to have a go at working out what's going on. Thanks! |
|
|