Yahoo Groups archive

Analogue-sequencer

Index last updated: 2026-04-28 23:15 UTC

Thread

weird midi problem

weird midi problem

2004-09-30 by Boele Gerkes

Colin, help (or any other one on this list)

Logic controlling the P3 with midiclock:

Logic -> midicable into P3: works perfectly
Logic-> midicable into midimerger->into P3: does not work
Logic-> midicable into midimerger->into Jomox Xbase: works 
perfectly (tempo sync en stop/start messages etc.)

In other words, the midimerger filters something out that the P3 
needs, but all the other midiclock driven machines in my studio 
does not need?

WHAT can that be???

Boele

Re: [analogue-sequencer] weird midi problem

2004-09-30 by Paul Nagle

If it's any help (probably isn't but I'm in a hurry), I use one of my
P3s with a MIDI merger - a Philip Rees one - and it works fine. You do
need to make sure which of the inputs it's connected to, just a quirk
of the merger I'm using. Maybe worth a shot?

Paul



On Thu, 30 Sep 2004 14:45:43 -0000, "Boele Gerkes"
<scd@synthmusic.info> wrote:

>Colin, help (or any other one on this list)
>
>Logic controlling the P3 with midiclock:
>
>Logic -> midicable into P3: works perfectly
>Logic-> midicable into midimerger->into P3: does not work
>Logic-> midicable into midimerger->into Jomox Xbase: works 
>perfectly (tempo sync en stop/start messages etc.)
>
>In other words, the midimerger filters something out that the P3 
>needs, but all the other midiclock driven machines in my studio 
>does not need?
>
>WHAT can that be???
>
>Boele
>
>
>
>
> 
>Yahoo! Groups Links
>
>
>
> 

---
Paul Nagle / Soft Room Music
Email: paul@softroom.co.uk www.softroom.co.uk
                           www.BogusFocus.com

Re: [analogue-sequencer] weird midi problem

2004-09-30 by scd

on 30-09-2004 16:49, Paul Nagle at softroom@btinternet.com wrote:

> If it's any help (probably isn't but I'm in a hurry), I use one of my
> P3s with a MIDI merger - a Philip Rees one - and it works fine. You do
> need to make sure which of the inputs it's connected to, just a quirk
> of the merger I'm using. Maybe worth a shot?

I did that already, both inputs give the same result.
But what is so weird is that the Jomox works fine...

Bloody midi...

Thanks though Paul. Appreciated!

Anyone else?

Boele
Show quoted textHide quoted text
> 
> Paul
> 
> 
> 
> On Thu, 30 Sep 2004 14:45:43 -0000, "Boele Gerkes"
> <scd@synthmusic.info> wrote:
> 
>> Colin, help (or any other one on this list)
>> 
>> Logic controlling the P3 with midiclock:
>> 
>> Logic -> midicable into P3: works perfectly
>> Logic-> midicable into midimerger->into P3: does not work
>> Logic-> midicable into midimerger->into Jomox Xbase: works
>> perfectly (tempo sync en stop/start messages etc.)
>> 
>> In other words, the midimerger filters something out that the P3
>> needs, but all the other midiclock driven machines in my studio
>> does not need?
>> 
>> WHAT can that be???
>> 
>> Boele
>> 
>> 
>> 
>> 
>> 
>> Yahoo! Groups Links
>> 
>> 
>> 
>> 
> 
> ---
> Paul Nagle / Soft Room Music
> Email: paul@softroom.co.uk www.softroom.co.uk
> www.BogusFocus.com
> 
> 
> 
> 
> Yahoo! Groups Links
> 
> 
> 
> 
>

Re: [analogue-sequencer] weird midi problem

2004-09-30 by Robert van der Kamp

On Thursday 30 September 2004 16:45, Boele Gerkes wrote:
> Colin, help (or any other one on this list)
>
> Logic controlling the P3 with midiclock:
>
> Logic -> midicable into P3: works perfectly
> Logic-> midicable into midimerger->into P3: does not work
> Logic-> midicable into midimerger->into Jomox Xbase:
> works perfectly (tempo sync en stop/start messages etc.)
>
> In other words, the midimerger filters something out that
> the P3 needs, but all the other midiclock driven machines
> in my studio does not need?
>
> WHAT can that be???

Hey, weird! ;)

Maybe the MIDI signal level drops below a magic threshold 
after the midimerger?

- Robert

RE: [analogue-sequencer] weird midi problem

2004-09-30 by Colin f

Very weird problem.
My first thought was that the merger should only be accepting midi clock
from one input. Depending on how it decides to switch between which input is
active for clock, you may not always have clock passing through the merger
as you expect.
Assuming that's not the case, have you tested whether notes are passing
through P3 OK ?
Is it actually receiving anything from the merger ?

Cheers,
Colin f

Re: weird midi problem

2004-10-01 by ch.³l

> In other words, the midimerger filters something out that the P3 
> needs, but all the other midiclock driven machines in my studio 
> does not need?

have you checked the manual for the merger? and is it only using this 
one merger or with every merger? i have mine running through a roland 
a880 and it's all working fine..maybe you can get in touch with the 
company that built the merger?

grtz Chiel

RE: [analogue-sequencer] weird midi problem

2004-10-01 by MAG

hi,
 
have you ever tried it with a usb midi thing?
(it dont know what a merger is, I'm using unitor8 and it works very well),
our chain the p3 behind the jomox and also check that you don't mess around 
with the midi control ch numbers, for test purpose you should use ch1 on all devices.
 
hope this helps...
 
grz mag
www.magdesign.ch 

		
---------------------------------
Do you Yahoo!?
vote.yahoo.com - Register online to vote today!

[Non-text portions of this message have been removed]

Re: [analogue-sequencer] weird midi problem

2004-10-01 by scd

on 01-10-2004 08:42, MAG at magdesign_uk@yahoo.com wrote:

Hi Mag,

A midimerger merges two incoming midi signals (so really two cables) and
outputs one.
In my case, in the end, I want to merge the midiclock from my
softwaresequencer with the note on/note off info from a controller keyboard,
which is NOT attached to Logic (to be able to arp with the P3).

It has nothing to do with channels afaik because
1: the P3 works fine when attached directly to Logic
2: the other drummachines work fine when the midimerger is in between.

So it looks like the merger is filtering out something which the P3 needs,
but which the other drummachines don't need.

But I don't know much about this stuff...

Colin??? Please???

:-)) Boele
Show quoted textHide quoted text
> hi,
> 
> have you ever tried it with a usb midi thing?
> (it dont know what a merger is, I'm using unitor8 and it works very well),
> our chain the p3 behind the jomox and also check that you don't mess around
> with the midi control ch numbers, for test purpose you should use ch1 on all
> devices.
> 
> hope this helps...
> 
> grz mag
> www.magdesign.ch 
> 
> 
> ---------------------------------
> Do you Yahoo!?
> vote.yahoo.com - Register online to vote today!
> 
> [Non-text portions of this message have been removed]
> 
> 
> 
> 
> 
> Yahoo! Groups Links
> 
> 
> 
> 
>

Re: [analogue-sequencer] weird midi problem

2004-10-01 by Oakley Sound

Try this using the drum machine as a buffer to 'boost' the signal:

midi merger -> drum machine -> P3 -> to wherever

I think the midi merger's signal is close the limits set by the midi
spec. Some machines will work well with it. However, the P3's opto may
not be quiet fast enough to recover the midi clock signal to work the P3
correctly. Your drum machine may boost the signal level.

You could insert any 'midi through box' like a synth or whatever in
place of the drum machine too.

Regards,

Tony Allgood                           www.oakleysound.com

Oakley Modular Synthesisers      Penrith, Cumbria, England

Re: [analogue-sequencer] weird midi problem

2004-10-01 by scd

on 01-10-2004 11:53, Oakley Sound at oakley@techrepairs.freeserve.co.uk
wrote:

> Try this using the drum machine as a buffer to 'boost' the signal:
> 
> midi merger -> drum machine -> P3 -> to wherever
> 
> I think the midi merger's signal is close the limits set by the midi
> spec. Some machines will work well with it. However, the P3's opto may
> not be quiet fast enough to recover the midi clock signal to work the P3
> correctly. Your drum machine may boost the signal level.
> 
> You could insert any 'midi through box' like a synth or whatever in
> place of the drum machine too.

Good thinking! Thanks. Gonna try that this afternoon and will let know if it
works.

Regards, Boele

RE: [analogue-sequencer] weird midi problem

2004-10-01 by Colin f

> > You could insert any 'midi through box' like a synth or whatever in
> > place of the drum machine too.
> 
> Good thinking! Thanks. Gonna try that this afternoon and will 
> let know if it
> works.

If itturns out to be an incompatibility between the merger output and P3
input, removing one of the resistors on the opto can resolve this. Some
6N139s work perfectly in the circuit, others can be fine for normal messages
and hokey at sysex. A very few just wont work.
I'll be switching to a different opto in future.

Cheers,
Colin f

Re: [analogue-sequencer] weird midi problem

2004-10-01 by Boele Gerkes

Hey Tony,

Your suggestion did the trick! Thanks.

Colin,

How difficult is it to remove that resistor? Can you tell me which one 
it is? I'll ask Robert to remove it for me :-)

Although it works now, in the end I really want the P3 on it's own 
midi-port, so not shared with any other instrument.

Boele


Op 1-okt-04 om 11:53 heeft Oakley Sound het volgende geschreven:
Show quoted textHide quoted text
> Try this using the drum machine as a buffer to 'boost' the signal:
>
> midi merger -> drum machine -> P3 -> to wherever
>
> I think the midi merger's signal is close the limits set by the midi
> spec. Some machines will work well with it. However, the P3's opto may
> not be quiet fast enough to recover the midi clock signal to work the 
> P3
> correctly. Your drum machine may boost the signal level.
>
> You could insert any 'midi through box' like a synth or whatever in
> place of the drum machine too.
>
> Regards,
>
> Tony Allgood                           www.oakleysound.com
>
> Oakley Modular Synthesisers      Penrith, Cumbria, England
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>

RE: [analogue-sequencer] weird midi problem

2004-10-01 by Colin f

> How difficult is it to remove that resistor? Can you tell me 
> which one 
> it is? I'll ask Robert to remove it for me :-)

The resistor in question is R3.
Try just snipping it off at the leads.

Cheers,
Colin f

Re: [analogue-sequencer] weird midi problem

2004-10-01 by Boele Gerkes

Colin, never mind my private mail to you. It is working fine now. I 
removed R3.

My first DIY action on the P3 ;-) LOL!

Thanks for all the replies guys!

Boele


Op 1-okt-04 om 18:16 heeft Colin f het volgende geschreven:
Show quoted textHide quoted text
>
>> How difficult is it to remove that resistor? Can you tell me
>> which one
>> it is? I'll ask Robert to remove it for me :-)
>
> The resistor in question is R3.
> Try just snipping it off at the leads.
>
> Cheers,
> Colin f
>
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>

Re: weird midi problem

2004-10-05 by ch.³l

--- In analogue-sequencer@yahoogroups.com, "Colin f" <colin@c...> 
wrote:
> > How difficult is it to remove that resistor? Can you tell me 
> > which one 
> > it is? I'll ask Robert to remove it for me :-)
> 
> The resistor in question is R3.
> Try just snipping it off at the leads.
> 
> Cheers,
> Colin f

hmmm... i appear to have developed a similar problem all of a sudden. 
i have a chain starting with a microkontrol keyboard, passing through 
P3a, then to P3b, to a roland a880 where it's all merged with a 
drehbank and sent to the boxes. notes played on the microkontrol come 
through both P3's just fine, but controllers don't come through 
either one. i've tried starting the chain with the drehbank to no 
avail, and i've tried prety much every other possible configuration, 
but there's no controllers coming through except those generated by 
the last P3 in the chain..can this also be fixed by snipping out the 
resistors? and if so, can i just leave them out or should i replace 
them?

grtz Chiel

RE: [analogue-sequencer] Re: weird midi problem

2004-10-05 by Colin f

> hmmm... i appear to have developed a similar problem all of a sudden. 
> i have a chain starting with a microkontrol keyboard, passing through 
> P3a, then to P3b, to a roland a880 where it's all merged with a 
> drehbank and sent to the boxes. notes played on the microkontrol come 
> through both P3's just fine, but controllers don't come through 
> either one.

That's unlikely to be the opto - the controller messages are the same length
as the note messages. The opto problem would affect both equally, but more
often only affects sysex dumps, where there are several hundred contiguous
data bytes.

I'm wondering if this problem could be related to the newer controller
pass-thru code.
I'll have a little look.

Cheers,
Colin f

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.