just yesterday I had an issue where ardour was running at frames_per_cycle == 64 and capturing. After about 5 minutes or so (wildly random guess) I had some wierd alignment problems that caused me to be quite concerned that coming next would be the famous hammerfall hum at whatever amplitude it locked for looping. After instructing people to remove headphones quickly, I restarted ardour and all was well. To be safe, I used 128 instead of 64 and it was happier.
I have gotten strange results from ardour before, but they really started being more frequent after the mmap api changes went into alsa-lib concerning snd_mmap_commit (or whatever the call is) where it returns the number of committed frames. I noticed that rec-enabling some channels had 3 predictible random responses: 1: the correct signal is heard 2: distorted alien-like noises that sortta resemble the content appear 3: LOUD OBNOXIOUS CRACKLING IS HEARD! It is option 3 that has me most annoyed, an unsuspecting person might have hearing loss if sitting in the control room while bringing up channels--the solution is to tell ardour to roll even when there is no program material--this seems to get things moving nicely again. The option 3 is like an off by one byte issue. All this is AFTER the hw-pointer changes went into alsa-CVS. References to ardour here are audioengine ardour, not jack ardour. _J _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
