Mountain Lion is here – Any problems?

incubo's picture

Subject says pretty much it all.

Have you updated? Do things work? Do I dare to update in the middle of developing an important QC project? Was updating as easy as it was between Snow Leopard and Lion? And most importantly – any good new features QC wise?

Aku

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

mattgolsen's picture
Re: Mountain Lion is here – Any problems?

I just installed it, rebooted and first thing I attempted to do was run QC. Prompted me with a dialog that said I need to install X11 from http://xquartz.macosforge.org/landing/ . Not exactly sure what's up with that.

vade's picture
Re: Mountain Lion is here – Any problems?

Did you install Xcode 4.4?

franz's picture
Re: Mountain Lion is here – Any problems?

Updating in the middle of a critical project is stupid, don't do that. Getting yourself an external HDD and installing ML on it seems a better idea to me.

Peter's picture
Re: Mountain Lion is here – Any problems?

My experience so far:

  • Performance boost, especially using GLSL shaders
  • Flickering and strange artifacts when combining different CI kernels
  • Two compositions accessing the video input patch results in a crash for me (bug #11876356)

-Peter

vade's picture
Re: Mountain Lion is here – Any problems?

Yup, as well as much slower Core Image processing (check the CMYK Filter, even though reported FPS is high, its 100% not at the reported framerate).

On the plus sides, some bugs seem to have been fixed, and it looks like float support is a bit better? I need to do some more tests on that to make sure.

cybero's picture
Re: Mountain Lion is here – Any problems?

@ mattgolsen - That is very interesting. That did not happen with the previews of ML at all.

cybero's picture
Re: Mountain Lion is here – Any problems?

@ franz - echo that and make it an fw or ssd for speed

gtoledo3's picture
Re: Mountain Lion is here – Any problems?

cybero wrote:
@ mattgolsen - That is very interesting. That did not happen with the previews of ML at all.

This happened to me with preview 1, and I did something that stopped it from happening, but I can't remember what. Some likely candidates include restarting the system, and/or pulling plugins.

cybero's picture
Re: Mountain Lion is here – Any problems?

Perhaps both you and matt installed atop of a prior distro? My ML install was fresh. If that isn't the significant factor then is it hardware specific? Seems like a prior framework issue to me though [just guessing].

jersmi's picture
Re: Mountain Lion is here – Any problems?

Any report on QC editor issues, like port publishing slowness, scrambled graphics, etc.?

usefuldesign.au's picture
Re: Mountain Lion is here – Any problems?

Or partiton your HD that's what I've done but yet to install ML.

usefuldesign.au's picture
Re: Mountain Lion is here – Any problems?

^ ^ ___ /
- - \ \ \ \ |
o .m. .m

cybero's picture
Re: Mountain Lion is here – Any problems?

Pardon me asking but what does ....

Quote:
^ ^ ___ / - - \ \ \ \ | o .m. .m

actually mean ?

dust's picture
Re: Mountain Lion is here – Any problems?

not sure if i should upgrade my dev machine yet or not as well. i just got everything working the way i like and not looking forward to setting it all up again. i might try to just upgrade and see how things are working before doing a clean install migration type of thing ? looking forward to messing with scene kit some more.

mattgolsen's picture
Re: Mountain Lion is here – Any problems?

It was definitely an upgrade from Lion, I usually check the effects of this stuff prior to integrating it with the rest of our development environment.

Here is something interesting around Core Image. I've attached a part of a composition that was previously created by Cwright, creating a polar graph with Core Image. After the ML upgrade, it behaves entirely differently. I don't know enough about Core Image to figure out what's going on, but basically it's rendering the polar graph inverted from how it worked on Lion, and it's not calculating the angle properly. Any ideas?

edit - I just remembered that I uncommented line 13 (alphaAngle = alphaAngle<0.0 ? alphaAngle+ 3.15*2.0 : alphaAngle;) which I just figured out is part of the problem, when it is commented out, the first 90 degrees does not render.

PreviewAttachmentSize
CoreImage - Polar.qtz34.38 KB

mattgolsen's picture
Re: Mountain Lion is here – Any problems?

Also, just had a friend send me a composition he's working on. Thought this was fun. This happens when attempting to open the comp from my browser (in this case, Chrome), but does not occur when opening the file from within QC.

PreviewAttachmentSize
Screen Shot 2012-07-26 at 11.39.59 AM.png
Screen Shot 2012-07-26 at 11.39.59 AM.png38.09 KB

photonal's picture
Re: Mountain Lion is here – Any problems?

cybero wrote:
Pardon me asking but what does ....

Quote:

^ ^ ___ / - - \ \ \ \ | o .m. .m

actually mean ?

I think it means a scottish terrier - not sure of the relevance to the thread tho ;-)

[but it doesn't like being quoted!]

balam's picture
Re: Mountain Lion is here – Any problems?

so far not much of a issues I am testing comps without Kineme plugins how ever I can not find the examples folder, where has it been move is it part of the Xcode app pkg?

gtoledo3's picture
Re: Mountain Lion is here – Any problems?

balam wrote:
so far not much of a issues I am testing comps without Kineme plugins how ever I can not find the examples folder, where has it been move is it part of the Xcode app pkg?

Nowdays there's isn't a developer install. There's an Xcode app. Then, all of the additional apps are available via fiddling around in the menu... somewhere there's a selection for downloading them, or you can go to the ADC website and download the usual apps (QC, Instruments, OpenGL Profiler, Icon Composer, etc.)

The easiest way at this point to find pertinent sample projects is just by reading / dl'ing Xcode documentation, and clicking on the pertinent sample project links, or going straight to the ADC website and searching.

jersmi's picture
Re: Mountain Lion is here – Any problems?

For QC examples, how about right click > Show Package Contents, then Contents > Resources > Examples? Still there?

gtoledo3's picture
Re: Mountain Lion is here – Any problems?

No kidding, that's cool to know :D In Xcode or QC? It seems like there must be a way to get to those files without going into the app contents(?).

jersmi's picture
Re: Mountain Lion is here – Any problems?

QC -- I don't touch Xcode unless it's to compile someone else's work. That's why I'm asking about the new versions editor -- the editor malfunctions in 10.7 are disheartening.

You'd think there would be a way to access the examples. Maybe there's a future plan, based on seeing other stuff in the contents folder, icons for menu items not implemented, etc. I appreciate these, makes me feel like Quartz Composer has a future. I'm fine in the meantime getting to them with a right click. :)

cybero's picture
Re: Mountain Lion is here – Any problems?

Examples still there indeed inside of QC - one caveat - copy and paste these to a location external to the Package Contents folder for safe examination / experimentation.

conanp's picture
Re: Mountain Lion is here – Any problems?

Incidentally I ran into a very specific performance issue after upgrading to Mountain Lion. Most of my compositions run fine but one in particular that relies on the "Page Curl" and "Dissolve" transition patches took a significant performance hit after updating.

I have two workstations running identical hardware (2009 8-core MacPro, 24GB, Radeon 5770 1GB).

The system that was updated to ML now runs the Page Curl and Dissolve transitions at 1,280x720 at about 12fps in Quartz Composer, in QuickLook and QuickTime Player they appear to run 60fps.

The system running 10.7 runs the transitions at 60fps in Quartz Composer. A 2011 Mac Mini (Intel HD 3000) running 10.7 runs the same transitions at 30fps.

I created a new composition that only contains the "Page Curl" patch and supporting images, same issue. Anyone else running 10.8 want to try it and let me know if it's just me?

PreviewAttachmentSize
pageCurlTest.zip289.98 KB

cybero's picture
Re: Mountain Lion is here – Any problems?

I tried the composition you posted conanp and found on identical hardware that I didn't experience your reported problem in both 10.7 and 10.8 I got pretty much identical results at HD 720 [1280 * 720] - 60 fps pre transit and 30 fps in curl transition mode.

Test Bed Model iMac 24-inch, Early 2009 Processor 2.66 GHz Intel Core 2 Duo Memory 4 GB 1067 MHz DDR3 Graphics NVIDIA GeForce 9400 256 MB

Both Lion and ML are clean installations - not upgrades.

offonoll's picture
Re: Mountain Lion is here – Any problems?

I have a huge problem with QC. I can't turn it on. I sent my Log text to the list. Does anyone has same problem?

http://lists.apple.com/archives/quartzcomposer-dev/2012/Jul/msg00021.html

cybero's picture
Re: Mountain Lion is here – Any problems?

Without looking at the offending [for you] composition I couldn't possibly say. I am suspecting one of the common threads to a lot of ML woes is that to do with users who have upgraded and not done a fresh installation. Does that also apply in this case? Interaction patches do work AOK for me in QC 4.6 BTW. No crashes to report as you obviously do have.

offonoll's picture
Re: Mountain Lion is here – Any problems?

My installation was fresh. I wipe it before installing ML. hug!

Adding: I remember doing some changes to my preferences in edition. Any way to revert those changes by deleting any file?

offonoll's picture
Re: Mountain Lion is here – Any problems?

Fix it by deleting com.apple.QuartzComposer.editor.plist under /Users/XXX/Library/Preferences

:D

EDIT/ADD: I found out that kineme core was making me crash QC . to me is not working.

mennob's picture
Re: Mountain Lion is here – Any problems?

Quartz is running fine.

For some reason i can't use the Datatools anymore. They don't show up in the library. Artnet, GL, Audio tools are working.

Any idea?

Thanks

cybero's picture
Re: Mountain Lion is here – Any problems?

Data Tools - Not 10.8 compatible - as yet ......

Emer Värk's picture
Re: Mountain Lion is here – Any problems?

Same problem with Kineme Core.

leolodreamland's picture
Re: Mountain Lion is here – Any problems?

yep just installed kineme core and it instantly crashes qc when i click or try to drag cords from outputs

vade's picture
Re: Mountain Lion is here – Any problems?

You guys all know Kineme has stated publicly that 10.8 compatibility is not a priority right?

"We do not guarantee that Kineme Plugins and Apps will function on Mac OS 10.8 as they did in prior OS versions.

We do not intend to update products for Mac OS 10.8 at this time, but we welcome patches to our open source projects."

http://kineme.net/node/11221

gtoledo3's picture
Re: Mountain Lion is here – Any problems?

I mentioned this to kineme re: datatools when ml prev 1 dropped.

Fwiw, there just one (or a few?) lines that need to be changed to get it working in 10.8; the max version stuff. That said, I'm not sure if all of the patches work correctly or not, I haven't tested any besides structure maker and directory scanner blocking.

It would be interesting to see kinemecore get open sourced since it seems like it hasn't had any extensive feature additions in a long time, and mostly regressions.

leolodreamland's picture
Re: Mountain Lion is here – Any problems?

i do now. it doesn't help.

usefuldesign.au's picture
Re: Mountain Lion is here – Any problems?

Art doesn't have to mean something does it? This is possibly the first post-modern-proofed-terrier in existence ;-)

usefuldesign.au's picture
Re: Mountain Lion is here – Any problems?

I hope this isn't the wiff of Sony Corp getting established at Apple corp. There's been quite a few decisions to make for unease of late. While signed code is fine, the over-zealous application of constrains is not.

vade's picture
Re: Mountain Lion is here – Any problems?

I am very confused what this has to do with anything.

leolodreamland's picture
Re: Mountain Lion is here – Any problems?

meatu

usefuldesign.au's picture
Re: Mountain Lion is here – Any problems?

This will kill the mystery but I double posted and needed to clean it up with something. I can't remember the context but was entirely personal I'm sure.

It's actually whatever beastie you want it to be, a bunyip perhaps, but I saw a mountain lion not a terrier, the ears we all can agree are just exquisite and very ML like ;-)

prgrms's picture
Re: Mountain Lion is here – Any problems?

Heya, bit of a noob here. Just wondering if there is some place I should put the graphics tools package... or is it fine anywhere in Applications. I get a crash when I click on the 'mesh' template at the splash page... Looks fun and don't remember seeing that on Snow...

initi's picture
Re: Mountain Lion is here – Any problems?

hi, is alpha blend working in mountain lion? thanx. d.

jrs's picture
Re: Mountain Lion is here – Any problems?

Another vote for the open sourcing of kineme core - I find the publish all and publish to root functions extremely handy and would look into getting these working under 10.8 if the code was available.

jrs's picture
Re: Mountain Lion is here – Any problems?

Has anyone else had problems with Kineme 3D not working under 10.8?

1.5 was half working for me and I upgraded to 1.6 and now I get nothing......back to 10.7 I guess

smokris's picture
Re: Mountain Lion is here – Any problems?

In KinemeCore-0.6.0 on 10.8.1, I'm able to "Publish to Root" without any trouble. What's not working for you?

Likewise, Kineme3D-1.6 on 10.8.1 has been working just fine for me — I tested it extensively a couple weeks ago. What's not working for you? What do you mean by "get nothing"? (If you mean Kineme3D not rendering anything on 10.8.1 when the same composition is rendering something on another machine, that might be because the license is invalid — delete /Users/<you>/Library/Preferences/net.kineme.Kineme3D.plist and restart QC and enter your license key again.)

jrs's picture
Re: Mountain Lion is here – Any problems?

Disabling the "QC Edit Compositions" setting in the hidden preferences enabled me to get kineme3d 1.6 half working again - before none of the kineme 3d patches would load. The thing that's broken for me is texturing an fbx model - the model loads fine but as soon as I connect the texture all the vertices go haywire and I get under 1 FPS.

smokris's picture
Re: Mountain Lion is here – Any problems?

Please attach (or email us) the composition and we'll help you figure it out.

gtoledo3's picture
Re: Mountain Lion is here – Any problems?

Please report back if it in fact turns out to be consistent across installs that qceditcompositions doesn't work with kineme3d in 10.8. Thanks in advance.

jrs's picture
Re: Mountain Lion is here – Any problems?

Hi Steve,

After reading all of the above and all the comments about how your not supporting 10.8 I didn't think to check for a new version of kineme core - I installed a fresh version and its working fine. As for the fbx model texturing I've emailed you a test case.

Cheers James

jrs's picture
Re: Mountain Lion is here – Any problems?

I just re-enabled "QCEditCompositions" and kineme 3d is still working - not sure what the problem was as I completely cleaned out my preferences and plugins and redid everything. Does anyone know what this setting actually does?

gtoledo3's picture
Re: Mountain Lion is here – Any problems?

Search my Vimeo account for qcedit compositions stuff, or maybe even here.

First, it gives you a list of all compositions currently loaded by the app that's currently "in focus"/topmost. So, if an app is using qc, it's obvious.

If you double click on a file in the list it will spawn a new editor. If you investigate the edges of the editor you will find that it's a drawer that allows you to reveal a patch library. All old style tiger look accept for the patch look itself.

There's a couple of interesting quirks like being able to use that patch editor with the qc editor app, or pull off the little icon at the top to desktop or other composition to save file or create a macro (this stopped working in qc after tiger I think). If you really dig the old style patch library with categories listed at the side, you can open up an instance and shrink the drawers to just show the old patch creator. Then ya got an extra old style patch creator hanging around.

Awhile back I was kind of concerned about this and went on a successful quest to figure out how to code a patch that is able to be accessed in a qtz by "my app" but not actually QC- which prevents people from cut and pasting stuff since patches won't restore.

usefuldesign.au's picture
Re: Mountain Lion is here – Any problems?

This simple composition uses Data Tools. Worked for someone on a MBP with 10.8.2 but not for my client the Structure Maker and Breakout patches will not restore on opening the file. Any ideas why the discrepancy across 10.8 installs?

PreviewAttachmentSize
mountain lion test BKGDs composition.qtz7.16 KB

cybero's picture
Re: Mountain Lion is here – Any problems?

Not sure about the discrepancy, but have you tried the workaround for QCEditCompositions enablement that facilitated Kineme 3D on ML as mentioned earlier in this thread?

mc's picture
Re: Mountain Lion is here – Any problems?

Yes, pretty big problems. Opened new topic 'Frequent crashes on Mountain Lion with official example patch!', since it looks like a pretty specific, though generally disrupting problem.

voxdeserti's picture
Re: Mountain Lion is here – Any problems?

Got an access to QC's 4.6 hidden preferences. Checked multisampling on and (do not remember) off. QC doesn't start and reports unexpected quit. The thing remained after erasing it and downloading again.

gtoledo3's picture
Re: Mountain Lion is here – Any problems?

mc wrote:
Yes, pretty big problems. Opened new topic 'Frequent crashes on Mountain Lion with official example patch!', since it looks like a pretty specific, though generally disrupting problem.

You may wish to chill out. Your problem is really basic; you aren't familiar with QC.

The patch you're talking about has been deprecated since Tiger, replaced with a newer Javascript patch. It's been nice that it's worked even in Lion, but it can hardly be expected to have worked, let alone in ML.

gtoledo3's picture
Re: Mountain Lion is here – Any problems?

voxdeserti wrote:
Got an access to QC's 4.6 hidden preferences. Checked multisampling on and (do not remember) off. QC doesn't start and reports unexpected quit. The thing remained after erasing it and downloading again.

Does your computer's graphics card support MSAA? When I try this on computers with GPUs that don't support that extension, the same thing happens.

It's probably also worth noting that MSAA isn't technically supported functionality - all of the option+preferences are private API and unsupported.

mc's picture
Re: Mountain Lion is here – Any problems?

Ghee, nice comment! The sample patch might be outdated, but, as i said, it DOES RUN perfectly well with 10.8.2 on my MacBook Pro. I just grabbed that 'next best example patch' since it helps to discriminate the cases.

My case however seems to belong to a known issue affecting only macs with a certain graphics hardware (see the helpful comment on the separate thread) that prevents those lucky ones owning it from doing anything useful with QC on ML at all!

So now, and in regards of the expectable, after a day of downgrading my iMac to Lion 10.7.5, i will let go and chill out ... hoping that possible others reading this thread may not need to take my way in order to do so.

voxdeserti's picture
Re: Mountain Lion is here – Any problems?

I got a new retina macbook pro with 10.8 and it had already bring me much headache. I've noticed that it crashes patches containing openCL or meshes. + that hidden prefs - they were simply unavailable in QC 4.5. And by the way I cannot downgrade to 10.7. I'll try to downgrade from the same machine with 10.7.4. - perhaps it will give any result...

joseph's picture
Re: Mountain Lion is here – Any problems?

Hi: I have a strange problem: when I select a Quartz Composer file in the Finder with the mouse, the Finder crash. This happens quite often and is a headache. Here is the crash log. http://pastebin.com/AJ9Va0nU

Anybody can help me? In this way is impossible to work. Thanks

cybero's picture
Re: Mountain Lion is here – Any problems?

@joseph

Is it the case that the mouse select of a QC file preceding a Finder crash occurs with any QC file for you in QC?

Is it only at the desktop that this happens or is at any folder level in a Finder window?

I wonder if this workaround might also help in case this is yet another QuickLook annoyance - http://forums.macrumors.com/showthread.php?t=1463364 - you would need to adapt the Sandbox regex from

(deny file-read* (regex #"^.*.mkv$"))

to become (deny file-read* (regex #"^.*.qtz$"))

jersmi's picture
Re: Mountain Lion is here – Any problems?

Quote:
when I select a Quartz Composer file in the Finder with the mouse, the Finder crash.

Fix permissions? Relaunch finder?

joseph's picture
Re: Mountain Lion is here – Any problems?

cybero: Yes, with any file qtz and at any level of the hierarchy of folders in the Finder Windows . I read the QTKitServer problem, but I'm not used to modify system files; I don't know modify the file. Where to type??

jersmi: Yes, the Finder is relaunched; even when I have two Finder windows open. Thanks!!

Serious Cyrus's picture
Re: Mountain Lion is here – Any problems?

Just got a new MBP and going through my compositions and seeing what works and upgrading.

I get strange behaviour with images, when I hover over outputs of certain image providers, the image appears to be 4 times the size they should be, with the image proper in the bottom left corner, the rest black. In the QC editor, they seem to render fine to a sprite, but when opening in another application (Mix Emergency), the sprite displays the larger image with black, with the actual image shrunk to the bottom left corner of the sprite.

I tried cropping the image, but that doesn't work as expected on these images, origin x,y for the crop don't seem to line up with 0,0 of the image, so the image comes out the right size, but the left and bottom edges are chopped off.

Serious Cyrus's picture
Re: Mountain Lion is here – Any problems?

Serious Cyrus wrote:
Just got a new MBP and going through my compositions and seeing what works and upgrading.

I get strange behaviour with images, when I hover over outputs of certain image providers, the image appears to be 4 times the size they should be, with the image proper in the bottom left corner, the rest black. In the QC editor, they seem to render fine to a sprite, but when opening in another application (Mix Emergency), the sprite displays the larger image with black, with the actual image shrunk to the bottom left corner of the sprite.

I tried cropping the image, but that doesn't work as expected on these images, origin x,y for the crop don't seem to line up with 0,0 of the image, so the image comes out the right size, but the left and bottom edges are chopped off.

Was misinterpreting my results, the images do seem to render correctly. I'm getting some other problems with my qc files in mix emergency, but they still seem to work in QC.

Anyone have problems with the composition loader, render in image or replicate in space patches when used outside of the QC editor? My problem QC files seem to have these in common.

Serious Cyrus's picture
Re: Mountain Lion is here – Any problems?

Autosaves with the tild are very annoying, especially if editing custom patches, I get 2 entries in the library if I forget to clean the autosaved files, why aren't they cleaned up like the previous autosaves?

bezier's picture
Re: Mountain Lion is here – Any problems?

I am experiencing the same problems that a few people had here.

When i open the Mesh Filter template patch, qc crashes, same with many mesh compositions.

Does anyone have a solution for this?

magnetmus's picture
Re: Mountain Lion is here – Any problems?

Serious Cyrus, I'm having the same Finder crash problem, could you figure out how to fix this?