Andrew Pask

Cycling 74 has not yet finished evaluating Mac OS 10.5, aka Leopard.

As with any new OS, you are advised to tread cautiously if you are

considering updating. We are interested in hearing any and all reports

from users, and at some later date we shall publish full details of

our compatibility. Until that time use of our software on Leopard is unsupported.

If you wish to make reports of your experience with Leopard, please send them to support at cycling74 dot com

Cycling 74 has not yet finished evaluating Mac OS 10.5, aka Leopard.
As with any new OS, you are advised to tread cautiously if you are
considering updating. We are interested in hearing any and all reports
from users, and at some later date we shall publish full details of
our compatibility. Until that time use of our software on Leopard is unsupported.

If you wish to make reports of your experience with Leopard, please send them to support at cycling74 dot com


mac-os-10-5-leopard-support

I have no formal association with Cyclic '74 so this is an independent

opinion. I NEVER upgrade to a new operating system until someone like

Andrew gives the all-clear. Please do not be impatient with them. They are

facing a very big job getting Max 5 out and making sure it is compatible

with the operating systems that people will eventually be using. Their

support is stellar. None better in the business.

On 10/26/07 11:14 AM, "Andrew Pask" wrote:

> Cycling 74 has not yet finished evaluating Mac OS 10.5, aka Leopard.

> As with any new OS, you are advised to tread cautiously if you are

> considering updating. We are interested in hearing any and all reports

> from users, and at some later date we shall publish full details of

> our compatibility. Until that time use of our software on Leopard is

> If you wish to make reports of your experience with Leopard, please send them

I have no formal association with Cyclic '74 so this is an independent
opinion.  I NEVER upgrade to a new operating system until someone like
Andrew gives the all-clear.  Please do not be impatient with them.  They are
facing a very big job getting Max 5 out and making sure it is compatible
with the operating systems that people will eventually be using.  Their
support is stellar.  None better in the business.

Cheers
Gary Lee Nelson
Oberlin College
www.timara.oberlin.edu/GaryLeeNelson

On 10/26/07 11:14 AM, "Andrew Pask"  wrote:

>
> Cycling 74 has not yet finished evaluating Mac OS 10.5, aka Leopard.
> As with any new OS, you are advised to tread cautiously if you are
> considering updating. We are interested in hearing any and all reports
> from users, and at some later date we shall publish full details of
> our compatibility. Until that time use of our software on Leopard is
> unsupported.
>
> If you wish to make reports of your experience with Leopard, please send them
> to support@cycling74.com
>
>


Ive had the opportunity to test Max/MSP and Jitter on the release 

As far as I could tell, everything worked. Custom Shaders (ahem), 

quicktime playback, my iLok loaded, etc. I tested a few MSP objects 

and all seemed kosher. Of course, huge grain of salt with this. 

Inevitably the one object you want wont work :P

I plan on upgrading ASAP as there are some lovely new features I 

really want to play with, so im happy to report back with my 

Ive had the opportunity to test Max/MSP and Jitter on the release  
candidate of 10.5 on an Intel Macbook.

As far as I could tell, everything worked. Custom Shaders (ahem),  
quicktime playback, my iLok loaded, etc. I tested a few MSP objects  
and all seemed kosher. Of course, huge grain of salt with this.  
Inevitably the one object you want wont work :P

I plan on upgrading ASAP as there are some lovely new features I  
really want to play with, so im happy to report back with my  
experiences with Max on 10.5.

I bought X.5 today. What is your opinion? Is it safe to upgrad?

I bought X.5 today. What is your opinion? Is it safe to upgrad?
best
Hans


On 31 oct. 07, at 20:02, Hans Mittendorf wrote:

> I bought X.5 today. What is your opinion? Is it safe to upgrad?

I installed 10.5 over 10.4.10 last Saturday and since had no problems 

All in all I like Leopard, Time Machine is great.

On 31 oct. 07, at 20:02, Hans Mittendorf wrote:
> I bought X.5 today. What is your opinion? Is it safe to upgrad?

I installed 10.5 over 10.4.10 last Saturday and since had no problems  
so far, especially with MaxMSP.
However I did not work with Jitter.

as for Leopard itself, the main feature i see is that more things have reflections and more windows are transparent.

Allow me to be the 3rd to 2nd that,
just installed leopard, 
and all seems to work.

I tried
-some general max business
-some jitter video business
-some jitter openGL business
-some fancy jsui business

You did not notice things loading like, 12309809812401240987682 times 

On Oct 31, 2007, at 9:07 PM, batchku wrote:

> as for Leopard itself, the main feature i see is that more things 

> have reflections and more windows are transparent.

You did not notice things loading like, 12309809812401240987682 times  
faster?

>
> Allow me to be the 3rd to 2nd that,
> just installed leopard,
> and all seems to work.
>
> I tried
> -some general max business
> -some jitter video business
> -some jitter openGL business
> -some fancy jsui business
>
> no troubles.
>
> as for Leopard itself, the main feature i see is that more things  
> have reflections and more windows are transparent.
>
>
> -ali


has anyone had any issues getting soundflower to work under leopard?

after asking this list about problems were the answer was non, I installed it on a G5 2.5 MGZ and Max crashes loading!

Mail crashes loading many other apps do not work. 

I even had a message at the end of the installation procedure: your Mac could not be upgraded!!! But it launches into X.5.... 

after asking this list about problems were the answer was non, I installed it on a G5 2.5 MGZ and Max crashes loading!
Mail crashes loading many other apps do not work. 
I even had a message at the end of the installation procedure: your Mac could not be upgraded!!! But it launches into X.5.... 
Ouch
Anyone heared of this before?


Sorry Hans, but installing a .0 version of anything, and especially 

the OS is asking for trouble. In my 25 years of computer use I've 

never experienced a .0 that didn't break something.

Thousands of Leopard users are having problems right now. See 

Actually, one of the c74 crew warned against upgrading on this list.

With Max, it could be that you just need to upgrade the pace copy 

protection stuff. Search this forum for info.

Good luck. It might be time to revert to your Tiger backup.

Op 1-nov-2007, om 13:55 heeft Hans Mittendorf het volgende geschreven:

> after asking this list about problems were the answer was non, I 

> installed it on a G5 2.5 MGZ and Max crashes loading!

> Mail crashes loading many other apps do not work.

> I even had a message at the end of the installation procedure: your 

> Mac could not be upgraded!!! But it launches into X.5....

Sorry Hans, but installing a .0 version of anything, and especially  
the OS is asking for trouble. In my 25 years of computer use I've  
never experienced a .0 that didn't break something.

Thousands of Leopard users are having problems right now. See  
macfixit, macintouch etc.

With Max, it could be that you just need to upgrade the pace copy  
protection stuff. Search this forum for info.

Zip Boterbloem
Media Mechanics
Zwaluwstraat 54
2025 VR  Haarlem
The Netherlands
+31627014758
zip@knoware.nl

>
> after asking this list about problems were the answer was non, I  
> installed it on a G5 2.5 MGZ and Max crashes loading!
> Mail crashes loading many other apps do not work.
> I even had a message at the end of the installation procedure: your  
> Mac could not be upgraded!!! But it launches into X.5....
> Ouch
> Anyone heared of this before?


Hi Hans. I would suggest doing an Archive and Install option for 10.5, 

and also when booted from the DVD, make sure to verify your harddrive.

On Nov 1, 2007, at 8:55 AM, Hans Mittendorf wrote:

Hi Hans. I would suggest doing an Archive and Install option for 10.5,  
and also when booted from the DVD, make sure to verify your harddrive.

Good luck!
On Nov 1, 2007, at 8:55 AM, Hans Mittendorf wrote:

Do you have the APE on your mac? There's an issue with anything less 

than the very latest version that causes problems with X.5.

I had problems installing X.5 on my one remaining G5 - the install 

process seemed to freeze on a blue screen (blue screen of death???) 

near the end of the install. I eventually did a back up and reinstall 

(which is actually what I normally do - I was being lazy), and 

finally got it working - though the last part of the process seemed 

> On Nov 1, 2007, at 8:55 AM, Hans Mittendorf wrote:

>> after asking this list about problems were the answer was non, I 

>> installed it on a G5 2.5 MGZ and Max crashes loading!

>> Mail crashes loading many other apps do not work.

>> I even had a message at the end of the installation procedure: 

>> your Mac could not be upgraded!!! But it launches into X.5....

Do you have the APE on your mac? There's an issue with anything less  
than the very latest version that causes problems with X.5.
I had problems installing X.5 on my one remaining G5 - the install  
process seemed to freeze on a blue screen (blue screen of death???)  
near the end of the install. I eventually did a back up and reinstall  
(which is actually what I normally do - I was being lazy), and  
finally got it working - though the last part of the process seemed  
to take ages.

> On Nov 1, 2007, at 8:55 AM, Hans Mittendorf wrote:
>
>>
>> after asking this list about problems were the answer was non, I  
>> installed it on a G5 2.5 MGZ and Max crashes loading!
>> Mail crashes loading many other apps do not work.
>> I even had a message at the end of the installation procedure:  
>> your Mac could not be upgraded!!! But it launches into X.5....
>> Ouch
>> Anyone heared of this before?


My experience with Leopard lasted exactly one week. I figured I'd take the fall for everyone on the fence.

While Max seemed stable, the plugins I used were decidedly not. Notably, Izotope plugs (Phatmatik Pro & Vinyl) & NI plugs (Vokator and Kontakt 3) crashed everything.

Logic, one of Apple's own, was the least stable of all.

And then, I popped SuperDuper open and did my own personal "Time Machine" back to 10/26/07.

While Max seemed stable, the plugins I used were decidedly not. Notably, Izotope plugs (Phatmatik Pro & Vinyl) & NI plugs (Vokator and Kontakt 3) crashed everything. 

Logic, one of Apple's own, was the least stable of all. 

Interfaces:
Ultralite: Worked
RME Fireface 400: Worked

I have reinstalled Tiger. I do not recommend to install Leopard on a Power PC based computer. I think on an Intel computer it will be easier to upgrade.

I have had no problems with my Intel mac so far...

Midi is broken on TC Electronic Konnekt 24D and MOTU Fastlane. It works fine on Presonus Firebox.

I tried to run a Jitter standalone app on a MacBook Pro with Leopard. It did not work.

Has anyone been able to run a standalone successfully?

I tried to run a Jitter standalone app on a MacBook Pro with Leopard.  It did not work.

> I tried to run a Jitter standalone app on a MacBook Pro with 

> Has anyone been able to run a standalone successfully?

I've successfully created a standalone, which runs fine on Leopard 

> I tried to run a Jitter standalone app on a MacBook Pro with  
> Leopard.  It did not work.
>
> Has anyone been able to run a standalone successfully?

I've successfully created a standalone, which runs fine on Leopard  
with the following patch.

My experience so far, is good: MaxMSP/Jitter 4.6.3 is running just fine on a

1.33 Ghz iBook G4, upgraded from 10.4.11 to 10.5.1. Only thing that's a bit

"funny" is that screen redraws are not so smooth - resizing a bpatcher left

some "debris" on the screen (cleared up when I locked the patch.)

On Nov 24, 2007 3:29 PM, Emmanuel Jourdan wrote:

> > I tried to run a Jitter standalone app on a MacBook Pro with

> > Has anyone been able to run a standalone successfully?

> I've successfully created a standalone, which runs fine on Leopard

> #P user jit.pwindow 31 121 322 242 0 1 0 0 1 0;

> #P flonum 128 37 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

> #P flonum 73 37 35 9 0.5 0 1 3 0 0 0 221 221 221 222 222 222 0 0 0;

> #P newex 32 94 103 196617 jit.qt.movie 320 240;

http://www.flickr.com/photos/east_asia_photo_gallery/

http://picasaweb.google.com/maxmsp/KoreaKoreaKoReverendAlGreen

My experience so far, is good: MaxMSP/Jitter 4.6.3 is running just fine on a
1.33 Ghz iBook G4, upgraded from 10.4.11 to 10.5.1.  Only thing that's a bit
"funny" is that screen redraws are not so smooth - resizing a bpatcher left
some "debris" on the screen (cleared up when I locked the patch.)

On Nov 24, 2007 3:29 PM, Emmanuel Jourdan  wrote:

> On 25 nov. 07, at 00:19, Jason wrote:
>
> > I tried to run a Jitter standalone app on a MacBook Pro with
> > Leopard.  It did not work.
> >
> > Has anyone been able to run a standalone successfully?
>
>
> I've successfully created a standalone, which runs fine on Leopard
> with the following patch.
>
> ej
>
>
> #P user jit.pwindow 31 121 322 242 0 1 0 0 1 0;
> #P window setfont "Sans Serif" 9.;
> #P flonum 128 37 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P window linecount 1;
> #P message 128 57 42 196617 rate $1;
> #P message 188 37 28 196617 read;
> #P flonum 73 37 35 9 0.5 0 1 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P toggle 32 37 15 0;
> #P newex 32 57 51 196617 qmetro 2;
> #P newex 32 94 103 196617 jit.qt.movie 320 240;
> #B color 5;
> #P connect 2 0 1 0;
> #P fasten 1 0 0 0 37 87 37 87;
> #P fasten 4 0 0 0 193 84 37 84;
> #P fasten 5 0 0 0 133 84 37 84;
> #P connect 0 0 7 0;
> #P connect 3 0 1 1;
> #P connect 6 0 5 0;
> #P window clipboard copycount 8;
>
>

-- 
arliss renwick
http://www.myspace.com/radiopellucid
http://www.flickr.com/photos/east_asia_photo_gallery/
http://picasaweb.google.com/maxmsp/KoreaKoreaKoReverendAlGreen

I actually got my app working on Leopard. The problem was in including the Quitcktime files in the build. I did a build w/o the .movs and it works fine. Requires an extra step, but it's OK for now I guess.

I actually got my app working on Leopard.  The problem was in including the Quitcktime files in the build.  I did a build w/o the .movs and it works fine.  Requires an extra step, but it's OK for now I guess.


I am recently using my patch for multi speaker sound distribution,

where i route sound from Ableton Live trough Soundflower to MSP.

On tiger worked fine, but since upgrade to leopard i encountered a strange problem with DSP. I am getting cracking distorted output, similar to CPU overload. When I switch on/off the DSP it works fine for few minutes, than starts again. Very annoying during performance a continues switching on/off the DSP.

I updated the OS to 10.5.1 but the same thing happens.

I am recently using my patch for multi speaker sound distribution,
where i route sound from Ableton Live trough Soundflower to MSP.

I updated the OS to 10.5.1 but the same thing happens. 

I get this "debris" once in a while on 10.4.11 with 4.6.3. It's not much, but the same solution fixes it for me.

I get this "debris" once in a while on 10.4.11 with 4.6.3.  It's not much, but the same solution fixes it for me.


MOTU Fastlane now works with the new drivers

The Finder wouldn't let me do this, I had to do the sudo mv thing in Terminal

Midi update
MOTU Fastlane now works with the new drivers
As for Konnekt 24D - from TC support:
Go to: ../Library/Audio/MIDI Drivers/
Find the file called: "TCNear.bundle"
Rename this file to: "TCNear.plugin"
Reboot
The Finder wouldn't let me do this, I had to do the sudo mv thing in Terminal
All good now :-)


I noticed one thing with tracing ... after trace is finished the menu will not open on mouseclick anymore. have to restart Max.

I noticed one thing with tracing ... after trace is finished the menu will not open on mouseclick anymore. have to restart Max.
macbook pro

a buffer problem or timer mismatch. making soundflower useless.

have been looking inside the open-sourced code, but couldn't see any 

direct problems. then again, i'm not a c++ writer

the Apple AudioReflectorDriver is a bit more up to date and could be 

but this would make soundflowebed menu useless.

dear cycling74, is it possible to open-source the soundflowerbed code?

On 26 Nov 2007, at 10:23, Robert Pravda wrote:

> I am recently using my patch for multi speaker sound distribution,

> where i route sound from Ableton Live trough Soundflower to MSP.

> On tiger worked fine, but since upgrade to leopard i encountered a 

> strange problem with DSP. I am getting cracking distorted output, 

> similar to CPU overload. When I switch on/off the DSP it works fine 

> for few minutes, than starts again. Very annoying during performance 

> I updated the OS to 10.5.1 but the same thing happens.

the same happens here,
over and over again.

have been looking inside the open-sourced code, but couldn't see any  
direct problems. then again, i'm not a c++ writer
the Apple AudioReflectorDriver is a bit more up to date and could be  
used to rewrite the soundflower code.
that might solve the problem.

dear cycling74, is it possible to open-source the soundflowerbed code?
for santa...

>
>
> I am recently using my patch for multi speaker sound distribution,
> where i route sound from Ableton Live trough Soundflower to MSP.
>
> On tiger worked fine, but since upgrade to leopard i encountered a  
> strange problem with DSP. I am getting cracking distorted output,  
> similar to CPU overload. When I switch on/off the DSP it works fine  
> for few minutes, than starts again. Very annoying during performance  
> a continues switching on/off the DSP.
>
> I updated the OS to 10.5.1 but the same thing happens.
>
> Did anybody had the same?
>
>
> Intel 2,4 Ghz MacBook Pro,4Gb ram
>
>
>


FYI, Jack OS X has available a beta including Leopard support, as 

http://tech.groups.yahoo.com/group/jackosx/message/1857

At 2:28 PM +0100 12/5/07, Jan Mast wrote:

>a buffer problem or timer mismatch. making soundflower useless.

>have been looking inside the open-sourced code, but couldn't see any 

>direct problems. then again, i'm not a c++ writer

>the Apple AudioReflectorDriver is a bit more up to date and could be 

>but this would make soundflowebed menu useless.

>dear cycling74, is it possible to open-source the soundflowerbed code?

>On 26 Nov 2007, at 10:23, Robert Pravda wrote:

>>I am recently using my patch for multi speaker sound distribution,

>>where i route sound from Ableton Live trough Soundflower to MSP.

>>On tiger worked fine, but since upgrade to leopard i encountered a 

>>strange problem with DSP. I am getting cracking distorted output, 

>>similar to CPU overload. When I switch on/off the DSP it works fine 

>>for few minutes, than starts again. Very annoying during 

>>performance a continues switching on/off the DSP.

>>I updated the OS to 10.5.1 but the same thing happens.

202 Hack / PC-1600 User / VSTi Host / OMS Convert / Jack OS X / Major 

FYI, Jack OS X has available a beta including Leopard support, as 
well as better multi-processor support:

At 2:28 PM +0100 12/5/07, Jan Mast wrote:
>the same happens here,
>over and over again.
>
>a buffer problem or timer mismatch. making soundflower useless.
>
>have been looking inside the open-sourced code, but couldn't see any 
>direct problems. then again, i'm not a c++ writer
>the Apple AudioReflectorDriver is a bit more up to date and could be 
>used to rewrite the soundflower code.
>that might solve the problem.
>
>but this would make soundflowebed menu useless.
>
>dear cycling74, is it possible to open-source the soundflowerbed code?
>for santa...
>
>is any update in progess ?
>
>makes things possibly faster / easier
>
>mac pro 2,66
>
>
>
>On 26 Nov 2007, at 10:23, Robert Pravda wrote:
>
>>
>>
>>I am recently using my patch for multi speaker sound distribution,
>>where i route sound from Ableton Live trough Soundflower to MSP.
>>
>>On tiger worked fine, but since upgrade to leopard i encountered a 
>>strange problem with DSP. I am getting cracking distorted output, 
>>similar to CPU overload. When I switch on/off the DSP it works fine 
>>for few minutes, than starts again. Very annoying during 
>>performance a continues switching on/off the DSP.
>>
>>I updated the OS to 10.5.1 but the same thing happens.
>>
>>Did anybody had the same?
>>
>>
>>Intel 2,4 Ghz MacBook Pro,4Gb ram
>>
>>
>>
>

-- 
Dan Nigrin
Defective Records
202 Hack / PC-1600 User / VSTi Host / OMS Convert / Jack OS X / Major 
Malfunction
http://www.defectiverecords.com
http://www.jackosx.com


1) Asking is someone working on a soundflower update for Leopard?

2) is soundflowerbed source available? (Then we could maybe help!)

1) Asking is someone working on a soundflower update for Leopard?
2) is soundflowerbed source available?  (Then we could maybe help!)

I'm running Leopard and have the same problem, after using soundflower once. Mine's so bad that audio simply halts sometimes. Sometimes the playhead (in logic, quicklook, itunes, etc) will be moving, with no audio.. Other times the play head will choke and stop. Especially during application switching... like it's running out of "audio ram" or something. Nothing else seems to be choking however.

The kicker is that this continues to happen after I've uninstalled Soundflower, after rebooting, after resetting parameter ram a number of times.

Anyone have a solution that doesn't involve installing more software?

Quote: MonoD wrote on Mon, 26 November 2007 03:23

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

> On tiger worked fine, but since upgrade to leopard i encountered a strange problem with DSP. I am getting cracking distorted output, similar to CPU overload. When I switch on/off the DSP it works fine for few minutes, than starts again. Very annoying during performance a continues switching on/off the DSP.

Mac OS 10.5 Leopard Support