Old 09-07-2013, 10:01 AM   #1
amoretam
Human being with feelings
 
Join Date: Oct 2011
Posts: 485
Default Reaper 4.5.1 Crashing a lot

hi, reaper is crashing a lot for me, . I am working and my performance (high cpu) is not so good in OSX lion 10.7.4.. this happens while saving, muting or soloing and totally random..
I updated to 4.5.1 with the hope it would be resolved, but the same..

Can you people help me out with a crash report or something to find out the culprit of this high cpu usage and crashings..

I dont know how to generate a crash report and would like to learn to send it to cockos.

Thanks a lot
amoretam is offline   Reply With Quote
Old 09-07-2013, 05:25 PM   #2
ned
Human being with feelings
 
Join Date: Mar 2012
Posts: 331
Default

/Applications/Utilities/Console.app

Look in the side bar: Files/~/Library/Logs/CrashReporter/
You should see the reaper crash logs listed there.

Or, you could just goto the folder ~/Library/Logs/CrashReporter to find the actual files to send to cockos (actually ~/Library/Logs/DiagnosticReports, the files in the CrashReporter folder are shortcuts to the real ones) .
ned is offline   Reply With Quote
Old 09-08-2013, 08:23 AM   #3
amoretam
Human being with feelings
 
Join Date: Oct 2011
Posts: 485
Default

Quote:
Originally Posted by ned View Post
/Applications/Utilities/Console.app

Look in the side bar: Files/~/Library/Logs/CrashReporter/
You should see the reaper crash logs listed there.

Or, you could just goto the folder ~/Library/Logs/CrashReporter to find the actual files to send to cockos (actually ~/Library/Logs/DiagnosticReports, the files in the CrashReporter folder are shortcuts to the real ones) .
umm thanks... should I just send it to cockos just like that. Or should I contact Justin?
amoretam is offline   Reply With Quote
Old 09-08-2013, 09:23 AM   #4
serr
Human being with feelings
 
Join Date: Sep 2010
Posts: 7,440
Default

This was also happening before the upgrade?

Go through your plugins. FWIW, in my experience the only possible way to crash Reaper in OSX is with a misbehaving plugin installed. So... while you are trying to focus on the text of that error report... check your plugins!
serr is online now   Reply With Quote
Old 09-08-2013, 04:47 PM   #5
ned
Human being with feelings
 
Join Date: Mar 2012
Posts: 331
Default

Quote:
Originally Posted by amoretam View Post
umm thanks... should I just send it to cockos just like that. Or should I contact Justin?
You could just copy and paste the portion of the crash log with the crashed thread and post it here and see if the devs respond. The devs would probably be able to tell from that portion of the log if the crash is caused by a bug in reaper or by a buggy plugin.
ned is offline   Reply With Quote
Old 09-08-2013, 07:08 PM   #6
amoretam
Human being with feelings
 
Join Date: Oct 2011
Posts: 485
Default

Quote:
Originally Posted by ned View Post
You could just copy and paste the portion of the crash log with the crashed thread and post it here and see if the devs respond. The devs would probably be able to tell from that portion of the log if the crash is caused by a bug in reaper or by a buggy plugin.
thanks
amoretam is offline   Reply With Quote
Old 09-08-2013, 07:27 PM   #7
amoretam
Human being with feelings
 
Join Date: Oct 2011
Posts: 485
Default

Quote:
Originally Posted by ned View Post
/Applications/Utilities/Console.app

Look in the side bar: Files/~/Library/Logs/CrashReporter/
You should see the reaper crash logs listed there.

Or, you could just goto the folder ~/Library/Logs/CrashReporter to find the actual files to send to cockos (actually ~/Library/Logs/DiagnosticReports, the files in the CrashReporter folder are shortcuts to the real ones) .
ok i just check both and there is nothing there!
amoretam is offline   Reply With Quote
Old 09-08-2013, 08:15 PM   #8
ned
Human being with feelings
 
Join Date: Mar 2012
Posts: 331
Default

interesting... maybe you need to generate the crash report for a log to be made. Try to reproduce the crash and when the crash dialog window pops up click on report (instead of 'ignore'). That will bring up a window with the crash report where you can choose to send it to apple. You don't have to send it to apple and can just close the window. Check your console app again and see if there is a crash log is listed. Maybe check the /Library/Logs/CrashReporter (the main library directory not the user library).
ned is offline   Reply With Quote
Old 09-09-2013, 08:23 AM   #9
amoretam
Human being with feelings
 
Join Date: Oct 2011
Posts: 485
Default

Quote:
Originally Posted by ned View Post
interesting... maybe you need to generate the crash report for a log to be made. Try to reproduce the crash and when the crash dialog window pops up click on report (instead of 'ignore'). That will bring up a window with the crash report where you can choose to send it to apple. You don't have to send it to apple and can just close the window. Check your console app again and see if there is a crash log is listed. Maybe check the /Library/Logs/CrashReporter (the main library directory not the user library).
still nothing there... but i copied the report that should be sent to apple: Attached

Thanks a lot.... will they see it?

EDIT: ups it will not upload because it is too large??
amoretam is offline   Reply With Quote
Old 09-09-2013, 09:02 AM   #10
amoretam
Human being with feelings
 
Join Date: Oct 2011
Posts: 485
Default

pleassse. i need to upload this file, I cannot continue my project with Reaper crashing all the time!! thanks
amoretam is offline   Reply With Quote
Old 09-09-2013, 10:30 AM   #11
ned
Human being with feelings
 
Join Date: Mar 2012
Posts: 331
Default

Quote:
Originally Posted by amoretam View Post
EDIT: ups it will not upload because it is too large??
Just post the crashed thread, not the whole crash report. Scroll through the report and look for the thread heading that says 'crashed'.

Or... just copy and paste the whole report into a txt file and send it to cockos by email and explain what's happening. This is probably what you wanted to do in the first place before I made things all convoluted

BTW, you know that 4.52 is out right? But if you still have problems with that new version, maybe you should consider downgrading to the previous version you had before you started to experience the crashes so you can finish your projects.
ned is offline   Reply With Quote
Old 09-09-2013, 10:38 AM   #12
amoretam
Human being with feelings
 
Join Date: Oct 2011
Posts: 485
Default

Quote:
Originally Posted by ned View Post
Just post the crashed thread, not the whole crash report. Scroll through the report and look for the thread heading that says 'crashed'.

Or... just copy and paste the whole report into a txt file and send it to cockos by email and explain what's happening. This is probably what you wanted to do in the first place before I made things all convoluted

BTW, you know that 4.52 is out right? But if you still have problems with that new version, maybe you should consider downgrading to the previous version you had before you started to experience the crashes so you can finish your projects.
i have had no good experience (crashing, confusion and cpu) with reaper ever ! but you know ...I love Reaper...
in lion it is wasting too much cpu with no apparent reason and nobody ever gave me solutions... (check my threads if you want to)..

what is the cockos email??

sorry and thanks
amoretam is offline   Reply With Quote
Old 09-09-2013, 10:48 AM   #13
serr
Human being with feelings
 
Join Date: Sep 2010
Posts: 7,440
Default

I'm telling you, go through your plugins.
Find the one that misbehaves. Then figure out a workaround if you decide you really need to still use it.

Reaper in OSX with legitimate working plugins Does. Not. Crash.
Ever.


Start with empty inserts. Add one plugin back at a time. Repeat till you find the culprit.
serr is online now   Reply With Quote
Old 09-09-2013, 10:51 AM   #14
amoretam
Human being with feelings
 
Join Date: Oct 2011
Posts: 485
Default

Quote:
Originally Posted by serr View Post
I'm telling you, go through your plugins.
Find the one that misbehaves. Then figure out a workaround if you decide you really need to still use it.

Reaper in OSX with legitimate working plugins Does. Not. Crash.
Ever.


Start with empty inserts. Add one plugin back at a time. Repeat till you find the culprit.
imagine me trying to finish a mixing project, what do you want me to do, ? to offline all plugins and slowly making them online and wait until reaper crash?? that is crazyyyy...
amoretam is offline   Reply With Quote
Old 09-09-2013, 11:02 AM   #15
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 9,693
Default

amoretam, you can post just the top 50 or so lines of the crash report here, or mail whatever you like to support at cockos.
schwa is offline   Reply With Quote
Old 09-09-2013, 11:12 AM   #16
amoretam
Human being with feelings
 
Join Date: Oct 2011
Posts: 485
Default

ok, top first lines here: Hope someone can help me out THanks a bunch
Process: REAPER [276]
Path: /Applications/REAPER/*/REAPER.app/Contents/MacOS/REAPER
Identifier: com.cockos.reaper
Version: ??? (4.51)
Code Type: X86 (Native)
Parent Process: launchd [139]

Date/Time: 2013-09-09 11:13:28.038 -0400
OS Version: Mac OS X 10.7.4 (11E53)
Report Version: 9

Interval Since Last Report: 6339675 sec
Crashes Since Last Report: 233
Per-App Interval Since Last Report: 61356 sec
Per-App Crashes Since Last Report: 21
Anonymous UUID: EF0175B0-E10B-4DAC-8ACB-D2838F961BB6

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

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

VM Regions Near 0x4478a020:
MALLOC_SMALL 000000002e800000-000000002f000000 [ 8192K] rw-/rwx SM=PRV
-->
__TEXT 000000008fe72000-000000008fea5000 [ 204K] r-x/rwx SM=COW /usr/lib/dyld

Application Specific Information:
objc_msgSend() selector name: hasSubmenu
objc[276]: garbage collection is OFF

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libobjc.A.dylib 0x9536bd47 objc_msgSend + 23
1 com.cockos.reaper 0x003a6fd2 SWELL_SetMenuDestination(HMENU__*, HWND__*) + 242
2 com.cockos.reaper 0x003a7295 DeleteMenu(HMENU__*, int, int) + 389
3 com.cockos.reaper 0x0052d549 CustomizeMenu(char const*, HMENU__*, HWND__*) + 1561
4 com.cockos.reaper 0x004a93fe MainProc(HWND__*, unsigned int, unsigned long, long) + 14526
5 com.cockos.reaper 0x0039b58a SwellDialogDefaultWindowProc(HWND__*, unsigned int, unsigned long, long) + 74
6 com.cockos.reaper 0x00393e4c -[REAPERSwell_hwnd menuNeedsUpdate:] + 60
7 com.apple.AppKit 0x9465b77a -[NSMenu _populateFromDelegateWithEventRef:] + 318
8 com.apple.AppKit 0x9454befb -[NSMenu _populateWithEventRef:] + 99
9 com.apple.AppKit 0x9465a8bd -[NSCarbonMenuImpl _carbonPopulateEvent:handlerCallRef:] + 448
10 com.apple.AppKit 0x9465a446 NSSLMMenuEventHandler + 452
11 com.apple.HIToolbox 0x937f4dec _InvokeEventHandlerUPP(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*, long (*)(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*)) + 36
12 com.apple.HIToolbox 0x936704f3 _ZL23DispatchEventToHandlersP14EventTargetRecP14Op aqueEventRefP14HandlerCallRec + 1602
13 com.apple.HIToolbox 0x9366f970 _ZL30SendEventToEventTargetInternalP14OpaqueEventR efP20OpaqueEventTargetRefP14HandlerCallRec + 482
14 com.apple.HIToolbox 0x9366f788 SendEventToEventTargetWithOptions + 75
15 com.apple.HIToolbox 0x9383eea0 SendMenuPopulate(MenuData*, OpaqueEventTargetRef*, unsigned long, double, unsigned long, OpaqueEventRef*, unsigned char*) + 370
16 com.apple.HIToolbox 0x9385d753 _ZL12PopulateMenuP8MenuDataP20OpaqueEventTargetRef P13CheckMenuDatamd + 102
17 com.apple.HIToolbox 0x9369fcbe _ZL21Check1MenuForKeyEventP8MenuDataP13CheckMenuDa ta + 308
18 com.apple.HIToolbox 0x9369f49e _ZL21CheckMenusForKeyEventP8MenuDataP13CheckMenuDa ta + 1062
19 com.apple.HIToolbox 0x9385e793 _IsMenuKeyEvent(MenuData*, OpaqueEventRef*, unsigned long, MenuData**, unsigned short*) + 745
20 com.apple.HIToolbox 0x9369f04a IsMenuKeyEvent + 106
21 com.apple.AppKit 0x9465a19e -[NSCarbonMenuImpl _menuItemWithKeyEquivalentMatchingEventRef:] + 308
22 com.apple.AppKit 0x94659ee9 _NSFindMenuItemMatchingCommandKeyEvent + 293
23 com.apple.AppKit 0x94557e9f _NSHandleCarbonMenuEvent + 529
24 com.apple.AppKit 0x944e86c6 _DPSNextEvent + 2196
25 com.apple.AppKit 0x944e7942 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 113
26 com.apple.AppKit 0x944e3cb1 -[NSApplication run] + 911
27 com.apple.AppKit 0x94774bd9 NSApplicationMain + 1054
28 com.cockos.reaper 0x00002fa2 _start + 216
29 com.cockos.reaper 0x00002ec9 start + 41

Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x979d490a kevent + 10
1 libdispatch.dylib 0x9a78de10 _dispatch_mgr_invoke + 969
2 libdispatch.dylib 0x9a78c85f _dispatch_mgr_thread + 53

Thread 2:
0 libsystem_kernel.dylib 0x979d1c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x979d11f6 mach_msg + 70
2 com.apple.audio.midi.CoreMIDI 0x0088cfcb XServerMachPort::ReceiveMessage(int&, void*, int&) + 101
3 com.apple.audio.midi.CoreMIDI 0x008aff8b MIDIProcess::RunMIDIInThread() + 259
4 com.apple.audio.midi.CoreMIDI 0x008b0912 MIDIProcess::MIDIInPortThread::Run() + 24
5 com.apple.audio.midi.CoreMIDI 0x0088e59f XThread::RunHelper(void*) + 17
6 com.apple.audio.midi.CoreMIDI 0x0088df69 CAPThread::Entry(CAPThread*) + 123
7 libsystem_c.dylib 0x97947ed9 _pthread_start + 335
8 libsystem_c.dylib 0x9794b6de thread_start + 34

Thread 3:
0 libsystem_kernel.dylib 0x979d1d36 mach_wait_until + 10
1 libsystem_c.dylib 0x978f5439 nanosleep + 388
2 libsystem_c.dylib 0x978f3cba usleep + 60
3 com.cockos.reaper 0x003c1522 Sleep(int) + 34
4 reaper_video.dylib 0x075c406f videoDecodeThread(void*) + 815

Thread 4:
0 libsystem_kernel.dylib 0x979d3b7a __sem_wait_nocancel + 10
1 com.digidesign.digidesign.DigiCoreAudioPlugIn 0x09eb8aa2 NewDigiCoreAudioPlugIn + 15035
2 com.digidesign.digidesign.DigiCoreAudioPlugIn 0x09eb8acf NewDigiCoreAudioPlugIn + 15080
3 com.digidesign.digidesign.DigiCoreAudioPlugIn 0x09eba382 NewDigiCoreAudioPlugIn + 21403
4 libsystem_c.dylib 0x97947ed9 _pthread_start + 335
5 libsystem_c.dylib 0x9794b6de thread_start + 34

Thread 5:
0 libsystem_kernel.dylib 0x979d3bb2 __semwait_signal + 10
1 libsystem_c.dylib 0x978fc7b9 nanosleep$UNIX2003 + 187
2 libsystem_c.dylib 0x978fc558 usleep$UNIX2003 + 60
3 com.WavesAudio.WaveShell-VST.9.1.0 0x0a5e7862 wvWavesV9_1::wvThread::sleep_milliseconds(unsigned int) + 21
4 com.WavesAudio.WaveShell-VST.9.1.0 0x0a60bd14 wvWavesV9_1::wvThread::WCIdleCommandDispatcher::th readMain(void*) + 32
5 com.WavesAudio.WaveShell-VST.9.1.0 0x0a5e72f4 _ZN11wvWavesV9_18wvThreadL13ThreadWrapperEPv + 29
6 libsystem_c.dylib 0x97947ed9 _pthread_start + 335
7 libsystem_c.dylib 0x9794b6de thread_start + 34

Thread 6:
0 libsystem_kernel.dylib 0x979d383e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9794be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x978f37f5 pthread_cond_timedwait + 47
3 com.cytomic.theglue 0x0ee0ac9e juce::WaitableEvent::wait(int) const + 190
4 com.cytomic.theglue 0x0f00f688 juce::InternalTimerThread::run() + 552
5 com.cytomic.theglue 0x0eeead1f juce::Thread::threadEntryPoint(juce::Thread*) + 239
6 com.cytomic.theglue 0x0eeeaf16 juce::threadEntryProc(void*) + 70
7 libsystem_c.dylib 0x97947ed9 _pthread_start + 335
8 libsystem_c.dylib 0x9794b6de thread_start + 34

Thread 7:
0 libsystem_kernel.dylib 0x979d1c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x979d11f6 mach_msg + 70
2 com.izotope.audioplugins.VST.Trash2 0x1150319a 0x1149e000 + 414106
3 libsystem_c.dylib 0x97947ed9 _pthread_start + 335
4 libsystem_c.dylib 0x9794b6de thread_start + 34

Thread 8:
0 libsystem_kernel.dylib 0x979d1d36 mach_wait_until + 10
1 libsystem_c.dylib 0x978f5439 nanosleep + 388
2 libsystem_c.dylib 0x978f3cba usleep + 60
3 com.cockos.reaper 0x003c1522 Sleep(int) + 34
4 com.cockos.reaper 0x00574a9d shmThreadProc(void*) + 221
5 com.cockos.reaper 0x003c120f __threadproc(void*) + 31
6 libsystem_c.dylib 0x97947ed9 _pthread_start + 335
7 libsystem_c.dylib 0x9794b6de thread_start + 34

Thread 9:
0 libsystem_kernel.dylib 0x979d3876 __psynch_mutexwait + 10
1 libsystem_c.dylib 0x979466af pthread_mutex_lock + 633
2 com.cockos.reaper 0x000ef70a WorkerThreadInst::threadProc(void*) + 154
3 com.cockos.reaper 0x003c120f __threadproc(void*) + 31
4 libsystem_c.dylib 0x97947ed9 _pthread_start + 335
5 libsystem_c.dylib 0x9794b6de thread_start + 34

Thread 10:
0 libsystem_kernel.dylib 0x979d3876 __psynch_mutexwait + 10
1 libsystem_c.dylib 0x979466af pthread_mutex_lock + 633
2 com.cockos.reaper 0x000ef7f1 WorkerThreadInst::threadProc(void*) + 385
3 com.cockos.reaper 0x003c120f __threadproc(void*) + 31
4 libsystem_c.dylib 0x97947ed9 _pthread_start + 335
5 libsystem_c.dylib 0x9794b6de thread_start + 34

Thread 11:
0 libsystem_kernel.dylib 0x979d3876 __psynch_mutexwait + 10
1 libsystem_c.dylib 0x979466af pthread_mutex_lock + 633
2 com.cockos.reaper 0x000ef70a WorkerThreadInst::threadProc(void*) + 154
3 com.cockos.reaper 0x003c120f __threadproc(void*) + 31
4 libsystem_c.dylib 0x97947ed9 _pthread_start + 335
5 libsystem_c.dylib 0x9794b6de thread_start + 34

Thread 12:
0 libsystem_kernel.dylib 0x979d402e __workq_kernreturn + 10
1 libsystem_c.dylib 0x97949ccf _pthread_wqthread + 773
2 libsystem_c.dylib 0x9794b6fe start_wqthread + 30




THANKS
amoretam is offline   Reply With Quote
Old 09-09-2013, 11:33 AM   #17
serr
Human being with feelings
 
Join Date: Sep 2010
Posts: 7,440
Default

Quote:
Originally Posted by amoretam View Post
imagine me trying to finish a mixing project, what do you want me to do, ? to offline all plugins and slowly making them online and wait until reaper crash?? that is crazyyyy...
Not slowly. I never said that. Crazy? You'd be done by now. This post has been here for days. This should take an hour.

Sorry if this sounds flippant. I don't mean to dismiss your troubles. But, truly, my experience with Reaper and OSX says to go through the plugins.

There are some 'big guns' that have bugs.
The AU version of Waves REQ and the UAD Precision Multiband comp to name two. Bad crash inducing bugs even! I have a workaround for the UAD because it's important to me to use.

Do a save as and add "test" to the project name or something. Then decide which is quicker - deleting one by one or adding one by one. By "one" I mean every different plugin, not every instance of the same one.

Last edited by serr; 09-09-2013 at 11:41 AM.
serr is online now   Reply With Quote
Old 09-09-2013, 11:33 AM   #18
amoretam
Human being with feelings
 
Join Date: Oct 2011
Posts: 485
Default

helllo people, what Can i do?
amoretam is offline   Reply With Quote
Old 09-09-2013, 11:35 AM   #19
amoretam
Human being with feelings
 
Join Date: Oct 2011
Posts: 485
Default

Quote:
Originally Posted by serr View Post
Not slowly. I never said that. Crazy? You'd be done by now. This post has been here for days. This should take an hour.
what I mean is wait for Reaper to crash,,, this is totally random and unexpected
amoretam is offline   Reply With Quote
Old 09-09-2013, 11:38 AM   #20
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 9,693
Default

Is it possible you are simply out of available memory on the machine when it crashes? Open Applications/Utilities/Activity Monitor and watch the free system memory.
schwa is offline   Reply With Quote
Old 09-09-2013, 11:50 AM   #21
amoretam
Human being with feelings
 
Join Date: Oct 2011
Posts: 485
Default

Quote:
Originally Posted by schwa View Post
Is it possible you are simply out of available memory on the machine when it crashes? Open Applications/Utilities/Activity Monitor and watch the free system memory.
i know this things ... thanks... not out of memory.... and most of the time I am freezing plugs, cause of this issue
amoretam is offline   Reply With Quote
Old 09-09-2013, 12:06 PM   #22
serr
Human being with feelings
 
Join Date: Sep 2010
Posts: 7,440
Default

Quote:
Originally Posted by amoretam View Post
what I mean is wait for Reaper to crash,,, this is totally random and unexpected
Are you are saying that sometimes the project runs error free at times (and even for lengths of time) but then at random times, going through the exact same motions will result in a crash?

As opposed to: Every time I do "X" Reaper crashes?

If that's the case, it sounds like a hardware issue. Swap the firewire cable on your interface first (or USB if it's that).

Wiggle the cables to maybe help force the issue if it happens to be that.

You could throw some music files in a track and hit play during some R&R time. (ie. use Reaper as a media player) This would exercise the system and give it time to crash if it's a hardware problem. And rule out anything complex relating to your project or plugin compliment.


I'm just trying to suggest methodical things you can try instead of just waiting for someone to read your crash logs while you sit there frustrated.
serr is online now   Reply With Quote
Old 09-09-2013, 12:20 PM   #23
amoretam
Human being with feelings
 
Join Date: Oct 2011
Posts: 485
Default

Quote:
Originally Posted by serr View Post
Are you are saying that sometimes the project runs error free at times (and even for lengths of time) but then at random times, going through the exact same motions will result in a crash?

As opposed to: Every time I do "X" Reaper crashes?

If that's the case, it sounds like a hardware issue. Swap the firewire cable on your interface first (or USB if it's that).

Wiggle the cables to maybe help force the issue if it happens to be that.

You could throw some music files in a track and hit play during some R&R time. (ie. use Reaper as a media player) This would exercise the system and give it time to crash if it's a hardware problem. And rule out anything complex relating to your project or plugin compliment.


I'm just trying to suggest methodical things you can try instead of just waiting for someone to read your crash logs while you sit there frustrated.
It happens in a 88kz 24 bit project with 56 tracks and some plugins.. this project with no plugins has like 20% cpu usage..... dont know why!

Crashes happens mostly when muting, soloing or saving.... I use cmacros for soloing/muting tracks/.. if that can help//////.... but when I press that solo/mute key (in playback) it makes this short buzzing and then it crashes....

EDIT: that is sometimes, not always.... but it happens a lot.. I am tire of that/// , most of my plusins are frozen because of me trying to unload resources on cpu
amoretam is offline   Reply With Quote
Old 09-09-2013, 12:33 PM   #24
ned
Human being with feelings
 
Join Date: Mar 2012
Posts: 331
Default

What's your buffer value in reaper's audio device settings?
ned is offline   Reply With Quote
Old 09-09-2013, 02:01 PM   #25
amoretam
Human being with feelings
 
Join Date: Oct 2011
Posts: 485
Default

Quote:
Originally Posted by ned View Post
What's your buffer value in reaper's audio device settings?
it can be whaever, 1024 or 512 or 256, it is all the same,,,, please I am not a newbie.... I know all this stuff
amoretam is offline   Reply With Quote
Old 09-09-2013, 02:30 PM   #26
amoretam
Human being with feelings
 
Join Date: Oct 2011
Posts: 485
Default

can anybody help me put here, I am totally stuck, PLeaseee

THANKS and thanks again
amoretam is offline   Reply With Quote
Old 09-09-2013, 03:03 PM   #27
amoretam
Human being with feelings
 
Join Date: Oct 2011
Posts: 485
Default

Quote:
Originally Posted by serr View Post
Not slowly. I never said that. Crazy? You'd be done by now. This post has been here for days. This should take an hour.

Sorry if this sounds flippant. I don't mean to dismiss your troubles. But, truly, my experience with Reaper and OSX says to go through the plugins.

There are some 'big guns' that have bugs.
The AU version of Waves REQ and the UAD Precision Multiband comp to name two. Bad crash inducing bugs even! I have a workaround for the UAD because it's important to me to use.

Do a save as and add "test" to the project name or something. Then decide which is quicker - deleting one by one or adding one by one. By "one" I mean every different plugin, not every instance of the same one.
I will do this right now

Thanks
amoretam is offline   Reply With Quote
Old 09-09-2013, 03:36 PM   #28
amoretam
Human being with feelings
 
Join Date: Oct 2011
Posts: 485
Default

Quote:
Originally Posted by serr View Post
Not slowly. I never said that. Crazy? You'd be done by now. This post has been here for days. This should take an hour.

Sorry if this sounds flippant. I don't mean to dismiss your troubles. But, truly, my experience with Reaper and OSX says to go through the plugins.

There are some 'big guns' that have bugs.
The AU version of Waves REQ and the UAD Precision Multiband comp to name two. Bad crash inducing bugs even! I have a workaround for the UAD because it's important to me to use.

Do a save as and add "test" to the project name or something. Then decide which is quicker - deleting one by one or adding one by one. By "one" I mean every different plugin, not every instance of the same one.
with every fx offline I have 27% Cpu consumption ....56 tracks.. hackintosh sandy bridge i5 and 8 gb ram...

what do you think??

thanks

EDIT: Also , muting otems takes like 600 mlseconds to mute.... it is not instant...

Last edited by amoretam; 09-09-2013 at 03:52 PM.
amoretam is offline   Reply With Quote
Old 09-09-2013, 04:05 PM   #29
amoretam
Human being with feelings
 
Join Date: Oct 2011
Posts: 485
Default

oh gosh this takes so long, because, the crashes happen so randomly.... I never know when I am finish with a plugin testing...
I mean.. I could be done with a plugin, but, the crash HANS'T really happen because of that plugin..
amoretam is offline   Reply With Quote
Old 09-09-2013, 04:23 PM   #30
ned
Human being with feelings
 
Join Date: Mar 2012
Posts: 331
Default

Man, if this is a mission critical mix then for god's sake downgrade to last version of reaper that wasn't crashing on you. You're just going to keep getting more frustrated spinning your wheels trying to trouble shoot in the middle of a project.
ned is offline   Reply With Quote
Old 09-09-2013, 04:25 PM   #31
amoretam
Human being with feelings
 
Join Date: Oct 2011
Posts: 485
Default REAPER please let me finish

Please I have had too much bad luck with reaper and my hacktosh i5 sandy bridge...8gb ram..

My computer run so smooth I can hardly believe it....compared to when I used windows before,..

Please help me put, Reaper is not working for me, I love Reaper, But it is too hard to diagnose what is going on...
I have a thread on too much CPU being use with apparent no reason..(before this one I think)...

I have used Reaper before for shorter sessions. But this one is giving me problems.. The plugin test is just too random or time consuming for me to know.... it crashed with no plugins for example...yes, IT CRASHED all plugins offline..... what is going on, here?


Why me
amoretam is offline   Reply With Quote
Old 09-09-2013, 04:43 PM   #32
karbomusic
Human being with feelings
 
karbomusic's Avatar
 
Join Date: May 2009
Posts: 22,630
Default

Quote:
Originally Posted by amoretam View Post
It happens in a 88kz 24 bit project with 56 tracks and some plugins.. this project with no plugins has like 20% cpu usage..... dont know why!
As Schwa said, please explicitly make it a point keep an eye on how much memory the Reaper process is using even if you don't think it is memory. Report exactly how much is being used here. Based on the fact it appears totally random would completely explain memory fragmentation and allocations that fail. AKA it'll look like you aren't out of memory but the allocation being made is larger than the largest free block of memory.

In other words you could have 200MB of memory left but if the largest free block is only 2MB and you need an allocation that requires 4MB, its going to crash anyway. The crash dump looks like 32 bit addresses so memory limitations are certainly possible.

When the above is the case it will appear somewhat random and only crash when some random event is unlucky enough to be the one that hits that ceiling and when that happens, Reaper (or any other application in that situation) will crash then and there with no explanation.

Can you reproduce with 10 tracks?
karbomusic is online now   Reply With Quote
Old 09-09-2013, 05:38 PM   #33
amoretam
Human being with feelings
 
Join Date: Oct 2011
Posts: 485
Default

Quote:
Originally Posted by karbomusic View Post
As Schwa said, please explicitly make it a point keep an eye on how much memory the Reaper process is using even if you don't think it is memory. Report exactly how much is being used here. Based on the fact it appears totally random would completely explain memory fragmentation and allocations that fail. AKA it'll look like you aren't out of memory but the allocation being made is larger than the largest free block of memory.

In other words you could have 200MB of memory left but if the largest free block is only 2MB and you need an allocation that requires 4MB, its going to crash anyway. The crash dump looks like 32 bit addresses so memory limitations are certainly possible.

When the above is the case it will appear somewhat random and only crash when some random event is unlucky enough to be the one that hits that ceiling and when that happens, Reaper (or any other application in that situation) will crash then and there with no explanation.

Can you reproduce with 10 tracks?
shit man.... what are you talking about, I just wanna make music.... I am not using no RAM intensive plugins at all. I have 8gb...
I use PT in same computer flawlessly with very intensive plugins while recording!!.
but now I am in Reaper with this project./.
I check activity monitor all the time... please telll how to reproduce, I have no idea what you talking about,...
You know I am trying to be in the creative side of brain right now.... it is hard to keep up with all this stuff!

Thanks a lot mang
amoretam is offline   Reply With Quote
Old 09-09-2013, 06:51 PM   #34
karbomusic
Human being with feelings
 
karbomusic's Avatar
 
Join Date: May 2009
Posts: 22,630
Default

Quote:
Originally Posted by amoretam View Post
shit man.... what are you talking about, I just wanna make music....
Who doesn't?

Quote:
I am not using no RAM intensive plugins at all. I have 8gb...
I use PT in same computer flawlessly with very intensive plugins while recording!!.
but now I am in Reaper with this project./.
I check activity monitor all the time... please telll how to reproduce, I have no idea what you talking about,...
You know I am trying to be in the creative side of brain right now.... it is hard to keep up with all this stuff!

Thanks a lot mang
We still don't know how much memory this project is using in general; the one with 56 tracks that is. No repro needed to do that
karbomusic is online now   Reply With Quote
Old 09-09-2013, 07:19 PM   #35
amoretam
Human being with feelings
 
Join Date: Oct 2011
Posts: 485
Default

Quote:
Originally Posted by karbomusic View Post
Who doesn't?



We still don't know how much memory this project is using in general; the one with 56 tracks that is. No repro needed to do that
there is like 4gb free
amoretam is offline   Reply With Quote
Old 09-09-2013, 07:36 PM   #36
ned
Human being with feelings
 
Join Date: Mar 2012
Posts: 331
Default

Quote:
Originally Posted by amoretam View Post
there is like 4gb free
Which isn't going to make spit of difference using the 32bit version of reaper. The os will only address so much ram to a 32bit application (3 or 4 GB I think). You are probably maxing out the ram that's been allocated to reaper.

http://en.wikipedia.org/wiki/RAM_lim..._x86_RAM_limit

Try running the cpu intensive plugins as a separate process, which will allow the os to allocate ram just for those plugins.

http://reaperblog.net/2012/02/run-pl...cated-process/
ned is offline   Reply With Quote
Old 09-09-2013, 07:47 PM   #37
karbomusic
Human being with feelings
 
karbomusic's Avatar
 
Join Date: May 2009
Posts: 22,630
Default

Quote:
Originally Posted by amoretam View Post
there is like 4gb free
How much is it actually using? Don't assume the available memory automagically means no memory issue. I mean its a specific irritating issue, shot gunning it isn't going to help so we really do need to be 100% specific no matter how much it hurts. Which reaper are you running 64bit or 32? Looking at the crash details it looks like the machine is 64 bit but I can't tell if the actual reaper process is 32 or 64; since I'm not a Mac guy I can't tell for sure.

Last edited by karbomusic; 09-09-2013 at 07:53 PM.
karbomusic is online now   Reply With Quote
Old 09-09-2013, 08:49 PM   #38
amoretam
Human being with feelings
 
Join Date: Oct 2011
Posts: 485
Default

Quote:
Originally Posted by karbomusic View Post
How much is it actually using? Don't assume the available memory automagically means no memory issue. I mean its a specific irritating issue, shot gunning it isn't going to help so we really do need to be 100% specific no matter how much it hurts. Which reaper are you running 64bit or 32? Looking at the crash details it looks like the machine is 64 bit but I can't tell if the actual reaper process is 32 or 64; since I'm not a Mac guy I can't tell for sure.
I am using x32 Reaper all the time... it does not matter if it is the x64 reaper version... it is same poor performence, I have not checked if crashes happen in x64 yet... Cause I use the x32 Reaper..

I am not using any ram consuming plugins at all, I am just mixing.. Eq plugins, compressors and stuff like that... all my ram or cpu consuming plugins are frozen (unfortunately because of paranoia).... I have to keep doing frozen stuff because my session is abnormally consuming too much CPU with no apparent reason (I have recent threads on that)..
I am a really persistent human being... I have had trouble with Reaper since I started using professionally..
I used PT for 8 years before with an excellent performance, ... but I prefer a lot better to work in Reaper because I just love it..
so, please I would really appreciate that you know that I am not newbie, .. I know what RAM consumption is, my problem is not RAM related stuff, I run other programs (PT for example) and Reaper is always giving me issues)...

I have read lots of threads talking about Reaper not being optimized for OSx... Lots of it!! and I am starting to believe I am one more of those.....
I really believe that a 88kz/56 track project consumes 25% of cpu with no plugins at all just because I am in OSX Lion 10.7.4...
There is threads by me which are totally unresolved .... if you want to look at

Thanks a lot people//// I am very irritated
amoretam is offline   Reply With Quote
Old 09-09-2013, 08:58 PM   #39
karbomusic
Human being with feelings
 
karbomusic's Avatar
 
Join Date: May 2009
Posts: 22,630
Default

Quote:
I know what RAM consumption is, my problem is not RAM related stuff,
If you refuse to tell me how much RAM the 32 bit version or Reaper is consuming (for that project) no matter how many times I ask, I respectfully give up.
karbomusic is online now   Reply With Quote
Old 09-09-2013, 09:16 PM   #40
amoretam
Human being with feelings
 
Join Date: Oct 2011
Posts: 485
Default

Quote:
Originally Posted by karbomusic View Post
As Schwa said, please explicitly make it a point keep an eye on how much memory the Reaper process is using even if you don't think it is memory. Report exactly how much is being used here. Based on the fact it appears totally random would completely explain memory fragmentation and allocations that fail. AKA it'll look like you aren't out of memory but the allocation being made is larger than the largest free block of memory.

In other words you could have 200MB of memory left but if the largest free block is only 2MB and you need an allocation that requires 4MB, its going to crash anyway. The crash dump looks like 32 bit addresses so memory limitations are certainly possible.

When the above is the case it will appear somewhat random and only crash when some random event is unlucky enough to be the one that hits that ceiling and when that happens, Reaper (or any other application in that situation) will crash then and there with no explanation.

Can you reproduce with 10 tracks?
OK I am very sorry I did not pay attention to this reply... ... Hope you are back

Real Memory = 291.5 MB

%CPU = 115.6 (changing constantly)

Threads = 13

what else should I reveal,,,,, thanks a lot
amoretam is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 11:54 AM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2018, vBulletin Solutions Inc.