Re: [Loopdub-devel] loopdub question

[Stephen S. <rad...@gm...>]

Hi, thanks for the test samples.  Here are my results.

with git version:

- ALSA, all loops play correctly.
- Jack 44100, all loops play correctly.
- Jack 48000, all loops play correctly.

(This involved editing .loopdub.conf between Jack sessions of course.)

I noticed some definite looping problems that happen sometimes (but
not every time?) if you first load a 48 kHz loop then a 44.1 kHz loop
and vice-versa, so that maybe needs looking at.  But in general it
works as expected.  I didn't notice any double-speed problems.

with version 0.3:

- ALSA, all samples play correctly but it obviously plays 48 kHz loops
at a different pitch than 44.1 kHz loops.
- Jack 44100, doesn't work.  It is hardwired to request 48 kHz.
- Jack 48000, all loops play correctly for me.  I didn't get this
double-speed problem you describe.

So.. there must be some difference between our systems.  I think it'd
be best to try the latest version, so that at least we're talking
about the same thing, but I still find it confusing as I can't
reproduce it even on version 0.3.  It may even come down to having
different sound hardware, which demands different Jack settings, etc.

Your autoconf problem is unexpected, I looked it up and it seems
related to my use of AC_DEFUN before AC_INIT.  Can you tell me which
version of autoconf you are using?  (autoconf -V)  Also which OS are
you using?

Two things you could do: In configure.ac, try changing the word
"AC_DEFUN" to "m4_define" and tell me if it still breaks.  If it is
still a problem, you should be able to at least side-step the problem
by just removing this line and replacing the word "LOOPDUB_VER" with
"0.4-git" or something similar everywhere in the file.  (and rerunning
autogen.sh.)

Let me know how it goes.  Thanks again for all your testing, it's very helpful!

Steve


On Sun, Mar 14, 2010 at 6:50 AM, Hugh Lovette <hug...@gm...> wrote:
> No problem about cross posting, we can move the whole discussion there
> if you like, but I'll use email this one last time and wait until
> you've copied these over.
>
> You are right, I'm running the 3.0 compiled from source. When I
> grabbed the latest from git I remembered that I had to edit
> bootstrap.sh to point to local, more recent versions of rtmidi and
> rtaudio since the included links were out of date.
>
> I'm attaching files as requested. They're random drum loops from some
> torrent or the other. I stayed lazy in created additional test samples
> just using a demo pattern in hydrogen recorded with jack_capture, then
> made a resampled copy in audacity. They also play way too fast when
> jack is running. Oh, and the original tests (C01.4*.wav) were mono,
> the new (test4*.wav)  stereo.
>
> I just tried the latest fro git and ran onto the following, not sure
> what to try:
> ../LoopDub$ ./autogen.sh
> libtoolize: putting auxiliary files in `.'.
> libtoolize: linking file `./ltmain.sh'
> libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
> libtoolize: linking file `m4/libtool.m4'
> libtoolize: linking file `m4/ltoptions.m4'
> libtoolize: linking file `m4/ltsugar.m4'
> libtoolize: linking file `m4/ltversion.m4'
> libtoolize: linking file `m4/lt~obsolete.m4'
> libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
> configure.ac:4: error: m4_divert_push: cannot change diversion to
> `GROW' inside m4_expand
> configure.ac:4: the top level
> autom4te: /usr/bin/m4 failed with exit status: 1
> aclocal: autom4te failed with exit status: 1
> Error running aclocal.
>
>
> Thanks - let me know what I can do to test
>