j.simon

I'm sending some audio data from three cycle~ objects into a subpatch

containing the scrub~ object from the percolate library. When I create the

cable from the inlet of the subpatch to the input of scrub~ everything is

fine; it turns into an audio cables. But, every time I open the patch again,

the cable has mysteriously turned into a midi cable, and no sound gets from

the cycle~ objects to the scrub~ in the subpatch; I have to delete and

Any ideas? Latest version of Max/MSP on Intel, OS X.latest.

I'm sending some audio data from three cycle~ objects into a subpatch
containing the scrub~ object from the percolate library. When I create the
cable from the inlet of the subpatch to the input of scrub~ everything is
fine; it turns into an audio cables. But, every time I open the patch again,
the cable has mysteriously turned into a midi cable, and no sound gets from
the cycle~ objects to the scrub~ in the subpatch; I have to delete and
recreate the cable each time.

-- 
J. Simon van der Walt    -----     Composer


problem-with-audio-cables-turning-into-midi-ones

Quote: j.simon wrote on Thu, 19 July 2007 22:42

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

> I'm sending some audio data from three cycle~ objects into a subpatch

> containing the scrub~ object from the percolate library. When I create the

> cable from the inlet of the subpatch to the input of scrub~ everything is

> fine; it turns into an audio cables. But, every time I open the patch again,

> the cable has mysteriously turned into a midi cable,

So far this is a known problem. The connections should still work just fine, even though they are colored wrongly..

> the cycle~ objects to the scrub~ in the subpatch; I have to delete and

.. so this is strange. Could you post a patch that demonstrates this problem?

> Any ideas? Latest version of Max/MSP on Intel, OS X.latest.

Quote: j.simon wrote on Thu, 19 July 2007 22:42
----------------------------------------------------
> I'm sending some audio data from three cycle~ objects into a subpatch
> containing the scrub~ object from the percolate library. When I create the
> cable from the inlet of the subpatch to the input of scrub~ everything is
> fine; it turns into an audio cables. But, every time I open the patch again,
> the cable has mysteriously turned into a midi cable, 

and no sound gets from
> the cycle~ objects to the scrub~ in the subpatch; I have to delete and
> recreate the cable each time.

>
> Any ideas? Latest version of Max/MSP on Intel, OS X.latest.
>
> Thanks,
>
>
> -- 
> J. Simon van der Walt    -----     Composer
>
>
>
>
>
>
>
----------------------------------------------------


>I'm sending some audio data from three cycle~ objects into a subpatch

>containing the scrub~ object from the percolate library. When I create the

>cable from the inlet of the subpatch to the input of scrub~ everything is

>fine; it turns into an audio cables. But, every time I open the patch again,

>the cable has mysteriously turned into a midi cable, and no sound gets from

>the cycle~ objects to the scrub~ in the subpatch; I have to delete and

>Any ideas? Latest version of Max/MSP on Intel, OS X.latest.

if by audio/midi you mean yellow/black and black, it does no 

difference, really (only the look is different)

then if you say no sound travels through them it's a different problem

>I'm sending some audio data from three cycle~ objects into a subpatch
>containing the scrub~ object from the percolate library. When I create the
>cable from the inlet of the subpatch to the input of scrub~ everything is
>fine; it turns into an audio cables. But, every time I open the patch again,
>the cable has mysteriously turned into a midi cable, and no sound gets from
>the cycle~ objects to the scrub~ in the subpatch; I have to delete and
>recreate the cable each time.
>
>Any ideas? Latest version of Max/MSP on Intel, OS X.latest.

if by audio/midi you mean yellow/black and black, it does no 
difference, really (only the look is different)

then if you say no sound  travels through them it's a different problem

kasper
-- 
  Kasper T. Toeplitz
noise, composition, bass, computer
http://www.sleazeArt.com

Thanks for both sending (more or less) the same answer! You're right, the

problem in my patch was elsewhere; I had a coll with data in it needed for

the patch to work, and I'd forgotted to tick 'save with patch'. The wrongly

coloured cables led me astray, I thought that was the problem...

Thanks for both sending (more or less) the same answer! You're right, the
problem in my patch was elsewhere; I had a coll with data in it needed for
the patch to work, and I'd forgotted to tick 'save with patch'. The wrongly
coloured cables led me astray, I thought that was the problem...

Quote: j.simon wrote on Fri, 20 July 2007 06:32

> coloured cables led me astray, I thought that was the problem...

Yeah, little glitches like this might seem harmless, the standard reply is 'don't worry, it's not a real problem'. But they can cause a lot of confusion (= real debug time (= real money, in my case)).

Quote: j.simon wrote on Fri, 20 July 2007 06:32
----------------------------------------------------
The wrongly
> coloured cables led me astray, I thought that was the problem...

>
> Cheers,
>
> JS
>
>
>
>
----------------------------------------------------


>Quote: j.simon wrote on Fri, 20 July 2007 06:32

>----------------------------------------------------

>> coloured cables led me astray, I thought that was the problem...

>Yeah, little glitches like this might seem harmless, the standard 

>reply is 'don't worry, it's not a real problem'. But they can cause 

>a lot of confusion (= real debug time (= real money, in my case)).

but it can be only due to the order of patching: if you patch a 

simple sub-patch with just an in and an out - and line in between - 

it has no way to know if it will be passing audio or control - and it 

will be black. Connect an audio object on top, the lines patched 

>Quote: j.simon wrote on Fri, 20 July 2007 06:32
>----------------------------------------------------
>The wrongly
>>  coloured cables led me astray, I thought that was the problem...
>
>Yeah, little glitches like this might seem harmless, the standard 
>reply is 'don't worry, it's not a real problem'. But they can cause 
>a lot of confusion (= real debug time (= real money, in my case)).

but it can be only due to the order of patching: if you patch a 
simple sub-patch with just an in and an out - and line in between - 
it has no way to know if it will be passing audio or control - and it 
will be black. Connect an audio object on top, the lines patched 
before will stay black

Quote: Kasper T Toeplitz wrote on Fri, 20 July 2007 11:26

> but it can be only due to the order of patching: if you patch a 

> simple sub-patch with just an in and an out - and line in between - 

> it has no way to know if it will be passing audio or control - and it 

> will be black. Connect an audio object on top, the lines patched 

Umm, this is exactly the kind of reply that was criticizing 1 post ago. Or is it a joke?

Quote: Kasper T Toeplitz wrote on Fri, 20 July 2007 11:26
----------------------------------------------------
> but it can be only due to the order of patching: if you patch a 
> simple sub-patch with just an in and an out - and line in between - 
> it has no way to know if it will be passing audio or control - and it 
> will be black. Connect an audio object on top, the lines patched 
> before will stay black
>
> yes, harmelss

>
> best
>
> kasper
>
----------------------------------------------------


you could use a send~ receive~ pair 
"for yellow cables"


Problem with audio cables turning into midi ones?