Forums > MaxMSP

Float32: bad number jit.freenect.grab

September 5, 2013 | 10:56 pm

I was using the jit.freenect.grab yesterday, and for some reason every time I try to start the patch i get this error message: float32:bad.

Now I have no idea why the jit.freenect.grab has suddenly started to send me this message, but could it be a compatibility problem?

on macbook pro retina from 2012 2.6gh
Mountain lion 10.8.4
Max/MSP jitter 6.1.3

<code>

– Pasted Max Patch, click to expand. –

</code>


September 5, 2013 | 10:58 pm

i am currently running 32bit version


September 7, 2013 | 5:32 am

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000001cbc0000

VM Regions Near 0x1cbc0000:
shared memory 000000001cabf000-000000001cbc0000 [ 1028K] r–/r– SM=SHM
–>
MALLOC_LARGE 000000001cea1000-000000001cfce000 [ 1204K] rw-/rwx SM=PRV

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.jmp.jit.freenect.grab 0x1a58b2d8 copy_rgb_data + 186
1 com.jmp.jit.freenect.grab 0x1a58ad26 jit_freenect_grab_matrix_calc + 931
2 com.cycling74.Max 0x000c917b object_method_imp + 821
3 com.cycling74.JitterAPI 0x0c5e2fe6 jit_object_method + 143
4 com.jmp.jit.freenect.grab 0x1a58b810 max_jit_freenect_grab_outputmatrix + 339
5 com.cycling74.JitterAPI 0x0c6044b6 max_jit_usurp_qfn + 107
6 com.cycling74.JitterAPI 0x0c60016c max_jit_usurp_method + 116
7 com.cycling74.Max 0×00020267 typedmess_fun + 103
8 com.cycling74.Max 0x0002051d typedmess + 68
9 com.cycling74.MaxAPI 0×02705402 typedmess + 82
10 com.cycling74.JitterAPI 0x0c618da5 max_jit_mop_bang + 51
11 com.cycling74.Max 0x0006af9e outlet_bang + 901
12 com.cycling74.metro 0×15784700 metro_out + 99
13 com.cycling74.Max 0x000315ab sched_dequeue + 284
14 com.cycling74.Max 0x000123f6 max_tick + 91
15 com.cycling74.Max 0x0037f2ed juce::InternalTimerThread::callTimers() + 133
16 com.cycling74.Max 0x0037f094 non-virtual thunk to juce::InternalTimerThread::handleMessage(juce::Message const&) + 20
17 com.cycling74.Max 0x0037e14b juce::MessageManager::deliverMessage(juce::Message*) + 137
18 com.cycling74.Max 0x00475c4a juce::AppDelegateRedirector::runLoopCallback() + 116
19 com.apple.CoreFoundation 0x98f0c04f __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 15
20 com.apple.CoreFoundation 0x98f0ba79 __CFRunLoopDoSources0 + 233
21 com.apple.CoreFoundation 0x98f31826 __CFRunLoopRun + 934
22 com.apple.CoreFoundation 0x98f3101a CFRunLoopRunSpecific + 378
23 com.apple.CoreFoundation 0x98f30e8b CFRunLoopRunInMode + 123
24 com.apple.HIToolbox 0x9460cf5a RunCurrentEventLoopInMode + 242
25 com.apple.HIToolbox 0x9460ccc9 ReceiveNextEventCommon + 374
26 com.apple.HIToolbox 0x9460cb44 BlockUntilNextEventMatchingListInMode + 88
27 com.apple.AppKit 0x9951993a _DPSNextEvent + 724
28 com.apple.AppKit 0x9951916c -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 119
29 com.apple.AppKit 0x9950f5cc -[NSApplication run] + 855
30 com.cycling74.Max 0×00467097 juce::MessageManager::runDispatchLoop() + 731
31 com.cycling74.Max 0x00328e00 juce::JUCEApplication::main(juce::StringArray const&) + 68
32 com.cycling74.Max 0x00328f23 juce::JUCEApplication::main(int, char const**) + 73
33 com.cycling74.Max 0x002516f6 main + 486
34 com.cycling74.Max 0x00002ed9 _start + 208
35 com.cycling74.Max 0x00002e08 start + 40


September 18, 2013 | 5:21 am

I’m seeing the same message. It looks more like a warning than an error (yellow, not red), and the object appears to run as normal.


June 26, 2014 | 3:43 am

I also recognise this issue, even in the help file of the jit.freenect.grab appear a yellow message: float32 bad number. I would like to know why


Viewing 5 posts - 1 through 5 (of 5 total)