Navichord update v 2.0.6 and v 2.0.7

wim

Pressing Play also does nothing when Navichord is loaded I'm AudioBus.

Navichord

Hi @wim , Link runs together with audio, can you try Navichord internal instruments, is there any sound?

Kaikoo2

@wim said:
Pressing Play also does nothing when Navichord is loaded I'm AudioBus.

I am doing so well with Navichord midi channel to Mersenne. Both apps have Link and seated in Audiobus chain.

Just a test.

Why don't you say which if your app has problem with?

wim

@Kaikoo2 said:

What is the other Link enabled app?

So far I've tried with StepPolyArp, Fugue Machine, IElectribe, and ElasticDrums.

wim

@Kaikoo2 said:

Why don't you say which if your app has problem with?

I don't have your multi tasking super powers. Can't test and type at the same time.

@Navichord said:
Hi @wim , Link runs together with audio, can you try Navichord internal instruments, is there any sound?

Working on it. I'm having trouble getting anything consistent to report. I enabled audio and there was none. Disabled MIDI, no change. Unloaded, reloaded in AudioBus and audio and play worked. Enabled midi audio stopped working. Reloaded again and audio and Midi out worked, but the tempo change problem was still there ....

Let me see if I can come up with a consistent chain of events, if Mr. Kaikoo2 isn't seeing the same then it should be something local. I'll check back when I have better data.

Thanks for the incredibly swift response!

Kaikoo2

@win ,

Just slowly verify one by one.

One synth with Navichord at a time, then insert both to Audiobus. Then verify 3 of them together. Of course, Link enabled.

Mersenne, Laplace, Lorentz or any Link synth. Not drum app.

wim

@Kaikoo2 said:
@win ,

Just slowly verify one by one.

One synth with Navichord at a time, then insert both to Audiobus. Then verify 3 of them together. Of course, Link enabled.

Mersenne, Laplace, Lorentz or any Link synth. Not drum app.

Thanks. I know how to troubleshoot. Its one of the things I do it for a living.

I don't agree that drum apps shouldn't be part of the equation. They need to follow link tempo just like any other app. Of course, I shouldn't be sending MIDI to them from Navichord, but NaviChord should be able to control their tempo via Link.

I'm not in the right frame of mind for methodical testing after a 14 hour work day. Will pick it up tomorrow and wait until I have a repeatable scenario.

wim

@Navichord

I can reproduce the problem consistently. The problem happens every time NaviChord is the first app loaded in AudioBus.

1. Open AudioBus
2. Load NaviChord (Ableton Link enabled)
3. Pressing play starts the chord pads playing normally.
4. Load another Link enabled app. (Ex. Moog Model 15)
5. Switch back to NaviChord. Play no longer works.
6. Change tempo in NaviChord to something you know is different from the other app.
7. Switch to the other app. Tempo has not been changed
8. Switch back to NaviChord. NaviChord's tempo has now been changed to the other apps tempo from its original tempo.

Next:

1. Unload NaviChord from AudioBus.
2. Re-add it to AudioBus.
3. Play now works, and tempo changes are recognized in the other app

Finally:

1. Close all apps and AudioBus, then re-open Audiobus.
2. Load the same app as above, not NaviChord, in AudioBus.
3. Load NaviChord in AudioBus.
4. Play works normally, and tempo changes are recognized in the other app.

I tried several apps and combinations. I rebooted the iPad. I uninstalled and re-installed AudioBus. Nothing changed the above behavior. It was 100% reproducible.

(BTW, it does not matter if the second app loaded is Link enabled or not, the Play button and Link Sync still fail. The deciding factor is whether NaviChord is the first app loaded into AudioBus or not.)

If you can't reproduce it, no worries. I know the workaround, and it wouldn't be the first time I've had a repeatable problem that no one else seems to have.

kin

I had this problem too in Audiobus last night but as i have very little experience didn't know whether it was me doing something wrong.
Will try your workaround tonight , thanks @wim

wim

@kin said:
I had this problem too in Audiobus last night but as i have very little experience didn't know whether it was me doing something wrong.
Will try your workaround tonight , thanks @wim

Thanks. I hate it when I'm the only one that can produce these things.

@Navichord and @Kaikoo2
Interestingly, Laplace does not cause the behavior above. It's the only app I tested that doesn't.

Navichord

@wim thank you, I will test it on my side.

Kaikoo2

@wim said:

@kin said:
I had this problem too in Audiobus last night but as i have very little experience didn't know whether it was me doing something wrong.
Will try your workaround tonight , thanks @wim

Thanks. I hate it when I'm the only one that can produce these things.

@Navichord and @Kaikoo2
Interestingly, Laplace does not cause the behavior above. It's the only app I tested that doesn't.

I tested it and found that is the problem with Audiobus and Link; described from the above.

Navichord

@wim I can also reproduce this behavior, thank you for your very clear instructions, I will try to cover it in the next release.

JohnnyGoodyear

Selflessly good work Mister @wim (ok, ok, a little self-interest, but still for the herd's benefit )

wim

@JohnnyGoodyear said:
Selflessly good work Mister @wim (ok, ok, a little self-interest, but still for the herd's benefit )

Heh. Nothing compared to having to fix it! Thanks @Navichord!