Yahoo Groups archive

Analogue-sequencer

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

Thread

Quick SysEx question

Quick SysEx question

2005-09-10 by jimcombsus

I'm trying to backup my P3 data into SysEx and am having a problem
getting the program to capture the data.

Capturing the P3 dump worked for me last weekend and I used the SysEx
program to update my firmware last night, so connections and
transmissions seem to be ok.

Any helpful hints anyone can throw at me would be appreciated.

BTW, I'm using SysEx v4.8.0 on a Mac on OS9.1

-Jim

Re: Quick SysEx question

2005-09-10 by jimcombsus

--- In analogue-sequencer@yahoogroups.com, "jimcombsus" <jwcombs@b...>
wrote:
> I'm trying to backup my P3 data into SysEx and am having a problem
> getting the program to capture the data.

I solved the issue by disconnecting the P3 from all midi devices,
recabling from channel 7 to channel 8 on my MOTU MIDI Timepiece AV. It
was probably either a cable connection issue or I need to investigate
channel 7 on the MTP.

Oh well, onward and upward. To Different Skies!

-Jim
 www.touchxtone.com

thru issue

2005-09-10 by Richard Scott

Hi

I'm using the P3 partly as a midi thru box between an IBKcontrol 10 midi controller, which is controlling an Eventide Eclipse via midi channel 1. With the P3 not running but set to midi thru F1 sometimes the CC#s from the ibk are not properly recognised by the Eclipse. If I take the P3 out of the chain the messages are transmitted perfectly.

Is there any setting or reason internal to the P3 which could possibly have this effect??

Richard

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

Re: [analogue-sequencer] thru issue

2005-09-10 by Richard Scott

Hi Colin

I'm still on 3.1.005 but will attempt the beta, its a mysterious issue but tangibly a problem - tried new leads, intialised bank, different outputs, rebooting etc. but for some reason the P3 is not passing the data thru intact. I'll try the beta version tommorrow...

I just recorded my first P3 piece, sound like Autechre eating Rice Krispies :) that'll do me man


Richard
Show quoted textHide quoted text
  ----- Original Message ----- 
  From: Colin f 
  To: analogue-sequencer@yahoogroups.com 
  Sent: Saturday, September 10, 2005 8:08 PM
  Subject: RE: [analogue-sequencer] thru issue



  > I'm using the P3 partly as a midi thru box between an 
  > IBKcontrol 10 midi controller, which is controlling an 
  > Eventide Eclipse via midi channel 1. With the P3 not running 
  > but set to midi thru F1 sometimes the CC#s from the ibk are 
  > not properly recognised by the Eclipse. If I take the P3 out 
  > of the chain the messages are transmitted perfectly.
  > 
  > Is there any setting or reason internal to the P3 which could 
  > possibly have this effect??

  Are you still on the release version 3.1.005, or the newer beta ?
  There have been no reports of thru problems in the release version.
  Paul N thought he might have had a problem with the .006 beta, which added a
  fair bit of complexity to the thru code since it's now handling a single
  channel for record. I decided to re-write it in the most recent build,
  because it had got a bit too complex for my liking, so it would be
  interesting to know if you get the same problem with that build.
  It could be there was a subtle problem in the release version that still
  affected the previous beta.
  We're approaching a release version, but if you want to see if the current
  beta fixes your problem, it would be useful to know.

  While I'm on the subject, the latest build adds 'groups' to make the
  selection of aux events simpler.
  By pressing FUNC while selecting an aux event, you toggle between the events
  and higher level groups of events.
  When selecting an event, the members of each group are spread over the whole
  DATA knob, making it easier to find and select each one.

  Best regards,
  Colin Fraser
  Sequentix Music Systems Ltd
  http://www.sequentix.com




------------------------------------------------------------------------------
  YAHOO! GROUPS LINKS 

    a..  Visit your group "analogue-sequencer" on the web.
      
    b..  To unsubscribe from this group, send an email to:
     analogue-sequencer-unsubscribe@yahoogroups.com
      
    c..  Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. 


------------------------------------------------------------------------------



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

Re: [analogue-sequencer] thru issue

2005-09-10 by Richard Scott

Hi Colin, it occurs to me something else could be pumping the same  CC#s thru the P3 on a different channel and causing the problemard. Will experiment and tell you for sure before trying the new beta

Richard
Show quoted textHide quoted text
----- Original Message ----- 
  From: Richard Scott 
  To: analogue-sequencer@yahoogroups.com 
  Sent: Saturday, September 10, 2005 7:22 PM
  Subject: Re: [analogue-sequencer] thru issue


  Hi Colin

  I'm still on 3.1.005 but will attempt the beta, its a mysterious issue but tangibly a problem - tried new leads, intialised bank, different outputs, rebooting etc. but for some reason the P3 is not passing the data thru intact. I'll try the beta version tommorrow...

  I just recorded my first P3 piece, sound like Autechre eating Rice Krispies :) that'll do me man


  Richard
    ----- Original Message ----- 
    From: Colin f 
    To: analogue-sequencer@yahoogroups.com 
    Sent: Saturday, September 10, 2005 8:08 PM
    Subject: RE: [analogue-sequencer] thru issue



    > I'm using the P3 partly as a midi thru box between an 
    > IBKcontrol 10 midi controller, which is controlling an 
    > Eventide Eclipse via midi channel 1. With the P3 not running 
    > but set to midi thru F1 sometimes the CC#s from the ibk are 
    > not properly recognised by the Eclipse. If I take the P3 out 
    > of the chain the messages are transmitted perfectly.
    > 
    > Is there any setting or reason internal to the P3 which could 
    > possibly have this effect??

    Are you still on the release version 3.1.005, or the newer beta ?
    There have been no reports of thru problems in the release version.
    Paul N thought he might have had a problem with the .006 beta, which added a
    fair bit of complexity to the thru code since it's now handling a single
    channel for record. I decided to re-write it in the most recent build,
    because it had got a bit too complex for my liking, so it would be
    interesting to know if you get the same problem with that build.
    It could be there was a subtle problem in the release version that still
    affected the previous beta.
    We're approaching a release version, but if you want to see if the current
    beta fixes your problem, it would be useful to know.

    While I'm on the subject, the latest build adds 'groups' to make the
    selection of aux events simpler.
    By pressing FUNC while selecting an aux event, you toggle between the events
    and higher level groups of events.
    When selecting an event, the members of each group are spread over the whole
    DATA knob, making it easier to find and select each one.

    Best regards,
    Colin Fraser
    Sequentix Music Systems Ltd
    http://www.sequentix.com




  ------------------------------------------------------------------------------
    YAHOO! GROUPS LINKS 

      a..  Visit your group "analogue-sequencer" on the web.
        
      b..  To unsubscribe from this group, send an email to:
       analogue-sequencer-unsubscribe@yahoogroups.com
        
      c..  Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. 


  ------------------------------------------------------------------------------



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



  SPONSORED LINKS Sampler  Electronic instrument  Synthesizer  
        Synthesizer music  Electronic music  Midi sequencer  


------------------------------------------------------------------------------
  YAHOO! GROUPS LINKS 

    a..  Visit your group "analogue-sequencer" on the web.
      
    b..  To unsubscribe from this group, send an email to:
     analogue-sequencer-unsubscribe@yahoogroups.com
      
    c..  Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. 


------------------------------------------------------------------------------



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

RE: [analogue-sequencer] thru issue

2005-09-10 by Colin f

> I'm using the P3 partly as a midi thru box between an 
> IBKcontrol 10 midi controller, which is controlling an 
> Eventide Eclipse via midi channel 1. With the P3 not running 
> but set to midi thru F1 sometimes the CC#s from the ibk are 
> not properly recognised by the Eclipse. If I take the P3 out 
> of the chain the messages are transmitted perfectly.
> 
> Is there any setting or reason internal to the P3 which could 
> possibly have this effect??

Are you still on the release version 3.1.005, or the newer beta ?
There have been no reports of thru problems in the release version.
Paul N thought he might have had a problem with the .006 beta, which added a
fair bit of complexity to the thru code since it's now handling a single
channel for record. I decided to re-write it in the most recent build,
because it had got a bit too complex for my liking, so it would be
interesting to know if you get the same problem with that build.
It could be there was a subtle problem in the release version that still
affected the previous beta.
We're approaching a release version, but if you want to see if the current
beta fixes your problem, it would be useful to know.

While I'm on the subject, the latest build adds 'groups' to make the
selection of aux events simpler.
By pressing FUNC while selecting an aux event, you toggle between the events
and higher level groups of events.
When selecting an event, the members of each group are spread over the whole
DATA knob, making it easier to find and select each one.

Best regards,
Colin Fraser
Sequentix Music Systems Ltd
http://www.sequentix.com

RE: [analogue-sequencer] thru issue

2005-09-10 by Colin f

> I just recorded my first P3 piece, sound like Autechre eating 
> Rice Krispies :) that'll do me man

Well I hope you're going to post a snippet somewhere ;-)
Aside from one hugely disappointing recent live appearance, I'm still a big
autechre fan...

Best regards,
Colin Fraser
Sequentix Music Systems Ltd
http://www.sequentix.com

Re: [analogue-sequencer] thru issue

2005-09-10 by Richard Scott

Hi Colin

I've satisfied myself that nothing else is causing the midi CC# discrepency - with all other units switched out or unplugged the IBK knobs send out incorrect data and are slower than usual when the P3 is attached as a thru. Will try with the latest beta when i get a chance....

P.S. i'd be happy to up some of my distorted groovy P3 creation but I don't have a website and haven't a clue how to go about it - BTW autechre have been hugely important to me this year (I'm a late convert) and have led pretty much directly to my P3 purchase. I always liked stockhausen and I love funk, autechre put those two elements together (with maths, which I'm less keen on) in a way I find pretty compelling. I'm very much about trying to work out how to compose and freely improvise with those kinds of materials - as i am too thick/anti computer to really ever figure out my Nord G2 engine I believe the P3 is gonna be a goddam dream in this regard
Show quoted textHide quoted text
From: Richard Scott 
  To: analogue-sequencer@yahoogroups.com 
  Sent: Saturday, September 10, 2005 7:35 PM
  Subject: Re: [analogue-sequencer] thru issue


  Hi Colin, it occurs to me something else could be pumping the same  CC#s thru the P3 on a different channel and causing the problemard. Will experiment and tell you for sure before trying the new beta

  Richard

  ----- Original Message ----- 
    From: Richard Scott 
    To: analogue-sequencer@yahoogroups.com 
    Sent: Saturday, September 10, 2005 7:22 PM
    Subject: Re: [analogue-sequencer] thru issue


    Hi Colin

    I'm still on 3.1.005 but will attempt the beta, its a mysterious issue but tangibly a problem - tried new leads, intialised bank, different outputs, rebooting etc. but for some reason the P3 is not passing the data thru intact. I'll try the beta version tommorrow...

    I just recorded my first P3 piece, sound like Autechre eating Rice Krispies :) that'll do me man


    Richard
      ----- Original Message ----- 
      From: Colin f 
      To: analogue-sequencer@yahoogroups.com 
      Sent: Saturday, September 10, 2005 8:08 PM
      Subject: RE: [analogue-sequencer] thru issue



      > I'm using the P3 partly as a midi thru box between an 
      > IBKcontrol 10 midi controller, which is controlling an 
      > Eventide Eclipse via midi channel 1. With the P3 not running 
      > but set to midi thru F1 sometimes the CC#s from the ibk are 
      > not properly recognised by the Eclipse. If I take the P3 out 
      > of the chain the messages are transmitted perfectly.
      > 
      > Is there any setting or reason internal to the P3 which could 
      > possibly have this effect??

      Are you still on the release version 3.1.005, or the newer beta ?
      There have been no reports of thru problems in the release version.
      Paul N thought he might have had a problem with the .006 beta, which added a
      fair bit of complexity to the thru code since it's now handling a single
      channel for record. I decided to re-write it in the most recent build,
      because it had got a bit too complex for my liking, so it would be
      interesting to know if you get the same problem with that build.
      It could be there was a subtle problem in the release version that still
      affected the previous beta.
      We're approaching a release version, but if you want to see if the current
      beta fixes your problem, it would be useful to know.

      While I'm on the subject, the latest build adds 'groups' to make the
      selection of aux events simpler.
      By pressing FUNC while selecting an aux event, you toggle between the events
      and higher level groups of events.
      When selecting an event, the members of each group are spread over the whole
      DATA knob, making it easier to find and select each one.

      Best regards,
      Colin Fraser
      Sequentix Music Systems Ltd
      http://www.sequentix.com




    ------------------------------------------------------------------------------
      YAHOO! GROUPS LINKS 

        a..  Visit your group "analogue-sequencer" on the web.
          
        b..  To unsubscribe from this group, send an email to:
         analogue-sequencer-unsubscribe@yahoogroups.com
          
        c..  Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. 


    ------------------------------------------------------------------------------



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



    SPONSORED LINKS Sampler  Electronic instrument  Synthesizer  
          Synthesizer music  Electronic music  Midi sequencer  


  ------------------------------------------------------------------------------
    YAHOO! GROUPS LINKS 

      a..  Visit your group "analogue-sequencer" on the web.
        
      b..  To unsubscribe from this group, send an email to:
       analogue-sequencer-unsubscribe@yahoogroups.com
        
      c..  Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. 


  ------------------------------------------------------------------------------



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



------------------------------------------------------------------------------
  YAHOO! GROUPS LINKS 

    a..  Visit your group "analogue-sequencer" on the web.
      
    b..  To unsubscribe from this group, send an email to:
     analogue-sequencer-unsubscribe@yahoogroups.com
      
    c..  Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. 


------------------------------------------------------------------------------



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

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.