So here is my rack rig:
4 RU rack case
Gigabyte GA-Z68X-UD3H-B3 F10
i7 2600k 3.4
16 gig ram
2x Ocz Agility 3 AGT3-25SAT3-120 120GB SATA SSD Drives- One for windows, one for osx
2x 1tb Barracuda 7200rpm Sata storage drives, one NTFS for windows, the other Formated mac extended.
EVGA NVIDIA GeForce GTX 560 Superclocked 2048MB GDDR5 PCIe
Antec High Current Gamer Series 750W
3x Black Magic Intensity Pro Capture Cards
Ton of fans and a Ti FW card.
Ran all of the above on osx 10.73. Seemed solid, and it was but was getting random crashes, usually when going between decks.
My comps- 1920x1080- Around 14 decks, all with about 48 clips over 3 layers (16 clips a layer), all clips are Quicktime h.264 1920x1080 8.8mbps bit rate. Works fine for a while.. Then R4.01 crashes, Osx keeps going. Thought it was the HDD/ or computer but was able to get the same crash on my Macbook Pro.
I dont really think its R4s fault, I think it is the HD 1080 being too much to handle. Maybe the h.264 taxing the cpu. Edited the comp down to just 2 layers and the MBP now does not crash.
Got Home booted into the Windows7 drive in the rack, tried the 3 layer comps with all the decks and clips, seems to be ok.
So seems that you really need to watch your layers and FPS.. How can I get better FPS?
I know you recommend DXV but I cant get smooth playback with that and would take up 6-8tb for my clips so DXV is not an option for me...
How can I get more FPS and no crashes- 1080
How can I get more FPS and no crashes- 1080
Last edited by asperi on Thu May 24, 2012 00:36, edited 3 times in total.
Re:
here is the original crash report:
Thread 8 Crashed:
0 com.apple.GeForceGLDriver 0x8f0c8f7a 0x8f0c6000 + 12154
1 com.apple.GeForceGLDriver 0x8f0c86cd 0x8f0c6000 + 9933
2 com.apple.GeForceGLDriver 0x8f14caf6 glrCompExecuteKernel + 388454
3 com.apple.GeForceGLDriver 0x8f14d0e0 glrCompExecuteKernel + 389968
4 com.apple.GeForceGLDriver 0x8f14d323 glrCompExecuteKernel + 390547
5 com.apple.GeForceGLDriver 0x8f1755a0 glrCompExecuteKernel + 555024
6 com.apple.GeForceGLDriver 0x8f1d44bd gldModifyTexSubImage + 6557
7 GLEngine 0x1598925b glTexSubImage2D_Exec + 950
8 libGL.dylib 0x93ec9570 glTexSubImage2D + 87
9 com.resolume.avenue 0x001ecc75 juce::Array<__CVBuffer*, juce::DummyCriticalSection>::remove(int) + 391153
10 com.resolume.avenue 0x001ed539 juce::Array<__CVBuffer*, juce::DummyCriticalSection>::remove(int) + 393397
11 com.resolume.avenue 0x001e9ad9 juce::Array<__CVBuffer*, juce::DummyCriticalSection>::remove(int) + 378453
12 com.resolume.avenue 0x001ea6f5 juce::Array<__CVBuffer*, juce::DummyCriticalSection>::remove(int) + 381553
13 com.resolume.avenue 0x001df7b2 juce::Array<__CVBuffer*, juce::DummyCriticalSection>::remove(int) + 336686
14 com.resolume.avenue 0x001e4d39 juce::Array<__CVBuffer*, juce::DummyCriticalSection>::remove(int) + 358581
15 com.resolume.avenue 0x001e5c94 juce::Array<__CVBuffer*, juce::DummyCriticalSection>::remove(int) + 362512
16 com.resolume.avenue 0x004524b3 juce::LinkedListPointer<juce::XmlElement>::addCopyOfList(juce::LinkedListPointer<juce::XmlElement> const&) + 1521
17 com.resolume.avenue 0x0043559a juce::HeapBlock<char>::allocate(unsigned long, bool) + 36356
18 libSystem.B.dylib 0x95225259 _pthread_start + 345
19 libSystem.B.dylib 0x952250de thread_start + 34
Thread 8 Crashed:
0 com.apple.GeForceGLDriver 0x8f0c8f7a 0x8f0c6000 + 12154
1 com.apple.GeForceGLDriver 0x8f0c86cd 0x8f0c6000 + 9933
2 com.apple.GeForceGLDriver 0x8f14caf6 glrCompExecuteKernel + 388454
3 com.apple.GeForceGLDriver 0x8f14d0e0 glrCompExecuteKernel + 389968
4 com.apple.GeForceGLDriver 0x8f14d323 glrCompExecuteKernel + 390547
5 com.apple.GeForceGLDriver 0x8f1755a0 glrCompExecuteKernel + 555024
6 com.apple.GeForceGLDriver 0x8f1d44bd gldModifyTexSubImage + 6557
7 GLEngine 0x1598925b glTexSubImage2D_Exec + 950
8 libGL.dylib 0x93ec9570 glTexSubImage2D + 87
9 com.resolume.avenue 0x001ecc75 juce::Array<__CVBuffer*, juce::DummyCriticalSection>::remove(int) + 391153
10 com.resolume.avenue 0x001ed539 juce::Array<__CVBuffer*, juce::DummyCriticalSection>::remove(int) + 393397
11 com.resolume.avenue 0x001e9ad9 juce::Array<__CVBuffer*, juce::DummyCriticalSection>::remove(int) + 378453
12 com.resolume.avenue 0x001ea6f5 juce::Array<__CVBuffer*, juce::DummyCriticalSection>::remove(int) + 381553
13 com.resolume.avenue 0x001df7b2 juce::Array<__CVBuffer*, juce::DummyCriticalSection>::remove(int) + 336686
14 com.resolume.avenue 0x001e4d39 juce::Array<__CVBuffer*, juce::DummyCriticalSection>::remove(int) + 358581
15 com.resolume.avenue 0x001e5c94 juce::Array<__CVBuffer*, juce::DummyCriticalSection>::remove(int) + 362512
16 com.resolume.avenue 0x004524b3 juce::LinkedListPointer<juce::XmlElement>::addCopyOfList(juce::LinkedListPointer<juce::XmlElement> const&) + 1521
17 com.resolume.avenue 0x0043559a juce::HeapBlock<char>::allocate(unsigned long, bool) + 36356
18 libSystem.B.dylib 0x95225259 _pthread_start + 345
19 libSystem.B.dylib 0x952250de thread_start + 34
Last edited by asperi on Thu May 24, 2012 00:38, edited 2 times in total.
Re: Please help!! CRASHES- on all OS, many builds
Hello Asperi, may be is better to send the crash log file to Resolume team with the feedback tool... Most of us are not coders...
It will be good to know what happens when you'll tried with Windows. I'm thinking on build a hackintosh too, but I began to hear about inestability of the system and I'm not so sure to do it at the moment...
IMO DXV must be your choice, if you don't have enough space in your disks, may be you Can do a selection for every gig...
It will be good to know what happens when you'll tried with Windows. I'm thinking on build a hackintosh too, but I began to hear about inestability of the system and I'm not so sure to do it at the moment...
IMO DXV must be your choice, if you don't have enough space in your disks, may be you Can do a selection for every gig...
Re: How can I get more FPS and no crashes- 1080
We cannot provide support for Hackintosh models, but if you can recreate this on your MBP, we'd love to see the logs for that (mail@resolume.com).
Re: How can I get more FPS and no crashes- 1080
Yeah back to windows7.. Sent log from the MBP crash, will try to recreate with photo jpg renders. Guessing its crashing due to processing the h.264 on the cpu.. Will let you know when renders and test are done. Nature of the beast sort of.
just wanted to say that R4 is still super awesome :]
just wanted to say that R4 is still super awesome :]