nathaniel.stern

Just got a new macbook air, 1.7 GHz Intel Core i7, 8GBs of RAM, running the very latest version of Max, and I can't get a video channel open with either jit.grab or jit.qt.grab. I've tried the bare minimum from the tutorials. I know my built in iSight works, as I can open it with Photo Booth. I coped my whole drive from my Macbook Pro, which worked just fine - and I reinstalled Max just now when it didn't work, same issue.

PS just tested, and it seems to work in 64-bit mode, but not 32-bit mode - though I prefer 32-bit, so I can still use externals... for now.

Just got a new macbook air, 1.7 GHz Intel Core i7, 8GBs of RAM, running the very latest version of Max, and I can't get a video channel open with either jit.grab or jit.qt.grab. I've tried the bare minimum from the tutorials. I know my built in iSight works, as I can open it with Photo Booth. I coped my whole drive from my Macbook Pro, which worked just fine - and I reinstalled Max just now when it didn't work, same issue.
Any known problems or patches? Thanks!

PS just tested, and it seems to work in 64-bit mode, but not 32-bit mode - though I prefer 32-bit, so I can still use externals... for now.


jit-qt-grab-could-not-create-video-channel-9405

A good method (IMHO) to test hardware/MAX connexions is do it via the max helpfiles, e.g. in your case helpfile of jit.qt.grab -> activate the helppatch.

A good method (IMHO) to test hardware/MAX connexions is do it via the max helpfiles, e.g. in your case helpfile of jit.qt.grab -> activate the helppatch.
Best
Helmuth


Thanks, yes, same thing for help patch and tutorials and anything else I've tried. The camera works in 64-bit but not 32-bit mode. This is going to prove problematic for all my patches that use externals. Running 10.8.4. Is no one else having this problem on the new Airs?

Hi Helmuth,
Thanks, yes, same thing for help patch and tutorials and anything else I've tried. The camera works in 64-bit but not 32-bit mode. This is going to prove problematic for all my patches that use externals. Running 10.8.4. Is no one else having this problem on the new Airs?

Bump. Anyone have any clues here? Like I said, the camera works with other apps, and in 64 bit mode, so not sure why nothing is working in 32-bit. Thanks!

I'd try restarting, and then trashing Quicktime preferences (which should be in ~/Library/Preferences/).

If you are still having problems, please email support at cycling74 dot com.

This is unfortunately a known issue with 32bit Max 6 and the 2013 MacBook Airs - we have an engineering ticket for it.

oy. ok. i'll keep an eye out for a fix. thanks.

any news? i got same problem with new haswell 15" macbook

any news? i got same problem with new haswell  15" macbook


jit.qt.grab: could not create video channel -9405

jit.qt.grab: error opening device for grab.

Just discovered the same problem:
MacBook Pro 11.3, OS X 10.9 (13A3017)
jit.qt.grab: could not create video channel -9405
jit.qt.grab: error opening device for grab.

I also would love some news about this issue... also because as I read STEFANO test that

"is seems a genera jit.pwindow problem, also with a common qt.movie, the pwindow suck an amazing amount of power specially when more than one. no problem with jit.window

i thought could be a retina screen issue but this does not happen on the first generation retina MBP"

so wandering if is just issue with grab or more a matrix related issue..

I also would love some news about this issue... also because as I read STEFANO test that 

"is seems a genera jit.pwindow problem, also with a common qt.movie, the pwindow suck an amazing amount of power specially when more than one. no problem with jit.window
i thought could be a retina screen issue but this does not happen on the first generation retina MBP"

so wandering if is just issue with grab or more a matrix related issue..


News: we can reproduce the -9405-iSight-not-working problem and are preparing a surgical strike.

@martina.menegon your issue sounds like the fact that retina displays require rendering 4x the amount of pixels in the patcher. As mentioned in previous threads and in the advanced scheduler settings vignette of the max documentation, you may wish to "Open in Low Resolution" to reclaim your expected performance.

https://cycling74.com/forums/retina-performance/

On a Retina Macbook, if you have a patch that is performing a lot of user interface drawing, such as rapid updates to JSUI, you are possibly backlogging the queue, which can have an effect on scheduler performance. On these machines, GUI rendering costs are roughly 4x expensive, unless you disable high resolution support (patchers will look worse). To turn off high resolution support for Max, go to the Finder, and Get-Info (cmd+i) on the Max application icon and check the “Open in Low Resolution” box.

@martina.menegon your issue sounds like the fact that retina displays require rendering 4x the amount of pixels in the patcher. As mentioned in previous threads and in the advanced scheduler settings vignette of the max documentation, you may wish to "Open in Low Resolution" to reclaim your expected performance. 

On a Retina Macbook, if you have a patch that is performing a lot of user interface drawing, such as rapid updates to JSUI, you are possibly backlogging the queue, which can have an effect on scheduler performance. On these machines, GUI rendering costs are roughly 4x expensive, unless you disable high resolution support (patchers will look worse). To turn off high resolution support for Max, go to the Finder, and Get-Info (cmd+i) on the Max application icon and check the “Open in Low Resolution” box.


i was totally sure it was just a late retina problem, i have a friend with old retina and he don't have this problem and he probably just forgot to have switched on the low resolution option while we were making the comparison.

the last curious behavior that max still has is with the pays.multiple.mesh patch:

the patch runs 22 fps on old retina, 30 on new retina, 52 on old 2010 13" MBP,

Don't know if in this case has sense but i will try a SMC reset as suggested by Karl Kliem in the 

@joshua
my god thanks, was so simple...
i was totally sure it was just a late retina problem, i have a friend with old retina and he don't have this problem and he probably just forgot to have switched on the low resolution option while we were making the comparison.
the last curious behavior that max still has is with the pays.multiple.mesh patch:
the patch runs 22 fps on old retina, 30 on new retina, 52 on old 2010 13" MBP,
Don't know if in this case has sense but i will try a SMC reset as suggested by Karl Kliem in the https://cycling74.com/forums/retina-performance/
thanks everybody for the support


Many Thanks for news of impending iSight strike

& "Open in Low Res" option: I'd been getting low fps (13-15) playing Qts, now it's up to 30.

Many Thanks for news of impending iSight strike
& "Open in Low Res" option: I'd been getting low fps (13-15) playing Qts, now it's up to 30.


I'm on a new Retine Macbook Pro with OSX 10.9, and I also get the following messages:

jit.qt.grab: error opening device for grab

Is there any news on this issue?
Or is anyone aware of a workaround?

I'm on a new Retine Macbook Pro with OSX 10.9, and I also get the following messages:
jit.qt.grab: could not create video channel -9405
jit.qt.grab: error opening device for grab


@KAJDDAVID the only solution so far is opening max in 64, then u can open your grab...

not the best, but is a temporary solution if u need to work :)

@KAJDDAVID the only solution so far is opening max in 64, then u can open your grab...
not the best, but is a temporary solution if u need to work :)


Hi Martina - Thanks, I've tried that. And then grab works, but the rest of the patch has many errors.

It's not my patch, so I can't edit it for 64bit use - I'm doing the live electronics at a concert in a little over a week - looks like it might be a no-live-video-affair, unfortunately...

Hi Martina - Thanks, I've tried that. And then grab works, but the rest of the patch has many errors.
It's not my patch, so I can't edit it for 64bit use - I'm doing the live electronics at a concert in a little over a week - looks like it might be a no-live-video-affair, unfortunately...


@Martina - Thanks, I've tried that. And then grab works, but the rest of the patch has many errors.

@Martina - Thanks, I've tried that. And then grab works, but the rest of the patch has many errors.
It's not my patch, so I can't edit it for 64bit use - I'm doing the live electronics at a concert in a little over a week - looks like it might be a no-live-video-affair, unfortunately...


I have had the -9405 error when using Max6. When reverting to work with Max5 it worked. So if you can get back to Max5 you should be OK.

For me jit.qt.grab cannot access the iSight camera in either Max 5 and 6 (32bit mode)

though I can access DV camera connected through firewire/thunderbolt adapter.

64bit is not a practical option at the moment

MacBook Pro Retina 11.3, OS X 10.9 (13A3017)

For me jit.qt.grab cannot access the iSight camera in either Max 5 and 6 (32bit mode)
though I can access DV camera connected through firewire/thunderbolt adapter.
64bit is not a practical option at the moment

MacBook Pro Retina 11.3, OS X 10.9 (13A3017)


Thanks Foxley - I hadn't tried using an external camera.

It works for me with a USB webcam. Great.

(I can't get the iSight open in Max 5 or 6)

Thanks Foxley - I hadn't tried using an external camera.
It works for me with a USB webcam. Great.

(I can't get the iSight open in Max 5 or 6)


Thanks for the fix in 6.1.6!
iSight working fine now!


Already happened to me occasionally on a non retina mbp with max 6, so there must be something else.

Maybe it's also Mavericks related. In About this mac > System report > Camera, I still get "There was an error while scanning for video devices". (It happens with Audio too).

Initially, I thought the iSight problems were related to an app I installed on my iPhone called iWebCamera. The drivers, needed to stream the phone camera output to the MBPro, very aggressively prevented any software from connecting to the built-in iSight on my previous pre-retina MBPro.

I had to remove everything iWebCamera-related to be able to connect to the iSight.

I figured this out after migrating to the new Retina MBPro and was hoping that purging it of IWebCamera stuff would solve the problem, but it didn't. Hope this is of use.

Maybe it's also Mavericks related. In About this mac > System report > Camera, I still get "There was an error while scanning for video devices". (It happens with Audio too).  

Initially, I thought the iSight problems were related to an app I installed on my iPhone called iWebCamera. The drivers, needed to stream the phone camera output to the MBPro, very aggressively prevented any software from connecting to the built-in iSight on my previous pre-retina MBPro.
I had to remove everything iWebCamera-related to be able to connect to the iSight.

I figured this out after migrating to the new Retina MBPro and was hoping that purging it of IWebCamera stuff would solve the problem, but it didn't.  Hope this is of use.


the new version of max uses QTKit, you have to do this to get the ps3eye working (max 32 bits and macam driver):

3. new message box with “; jit usealtgrab 0″

https://cycling74.com/forums/max-6-1-6-released

the new version of max uses QTKit, you have to do this to get the ps3eye working (max 32 bits and macam driver):
1. restart Max
2. new patcher
3. new message box with “; jit usealtgrab 0″
4. lock patcher and click message box

see https://cycling74.com/forums/max-6-1-6-released