MOTUnation.com

Posted: **Sun Mar 08, 2009 10:10 am**

I've had two more sudden quits when using Redline Monitor. I'm pretty sure they're related. I'm just hoping they go away, or that I learn how not to precipitate them.

Shoosh

Posted: **Sun Mar 08, 2009 10:49 am**

Is there anything specific that seems to cause these quits? Do they generate an error report with mention of Redline Monitor? I did check with DP6 and no problem here, but computers being what they are I can't rule out the possibility of a bug in RM causing this. If you can find a way to reproduce them and/or an error report I'd much appreciate it. Will try to make it occur here as well.

Thanks,

-- dj!

Posted: **Sun Mar 08, 2009 11:21 am**

I'll see what I can find. I'm one of those people who hasn't had any sudden quits in DP 6.01 or 6.02, so for this to happen all of a sudden, 3 times in a row, I think there must be a connection. I temporarily disabled the plugin without leaving DP, then still got one more quit -- as if there was some residual effect from its having been active, but after rebooting DP one more time, things seem to be going more smoothly. (crossing fingers and hoping this isn't a new trend in my system)

OK, I checked my system logs under Digital Performer Crashes, and found this:

Process: Digital Performer [420]
Path: /Applications/MOTU Digital Performer 6/Digital Performer 6.02.app/Contents/MacOS/Digital Performer
Identifier: com.motu.DigitalPerformer
Version: 6.02 (6.02)
Code Type: X86 (Native)
Parent Process: launchd [105]

Date/Time: 2009-03-08 12:34:39.154 -0500
OS Version: Mac OS X 10.5.6 (9G55)
Report Version: 6

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000006f69747d
Crashed Thread: 0

Thread 0 Crashed:
0 com.112dB.Redline.Monitor 0x4902319f 0x48f04000 + 1175967
1 com.112dB.Redline.Monitor 0x49024240 0x48f04000 + 1180224
2 com.112dB.Redline.Monitor 0x48fb3756 0x48f04000 + 718678
3 com.apple.CoreFoundation 0x9426cb25 CFRunLoopRunSpecific + 4469
4 com.apple.CoreFoundation 0x9426ccd8 CFRunLoopRunInMode + 88
5 com.apple.HIToolbox 0x957e92c0 RunCurrentEventLoopInMode + 283
6 com.apple.HIToolbox 0x957e90d9 ReceiveNextEventCommon + 374
7 com.apple.HIToolbox 0x95847c6e _AcquireNextEvent + 58
8 com.apple.HIToolbox 0x958463cb RunApplicationEventLoop + 207
9 com.motu.DigitalPerformer 0x005d6126 0x1000 + 6115622
10 com.motu.DigitalPerformer 0x00002aa6 0x1000 + 6822
11 com.motu.DigitalPerformer 0x000029cd 0x1000 + 6605

I think that pretty well implicates Redline Monitor. If you want the entire log, please send me a Personal Message with your email address, and I'll send it to you as soon as I receive your PM. I may be out of touch for most of the day, but I'll at least get it to you by tomorrow. Sorry to be the messenger of crashes, but perhaps it will help you to figure it out.

Thanks so much for taking a look!

Shooshie

Posted: **Sun Mar 08, 2009 11:30 am**

Here are the last few log entries on the other two crashes I had after installing Redline Monitor:

Process: Digital Performer [360]
Path: /Applications/MOTU Digital Performer 6/Digital Performer 6.02.app/Contents/MacOS/Digital Performer
Identifier: com.motu.DigitalPerformer
Version: 6.02 (6.02)
Code Type: X86 (Native)
Parent Process: launchd [105]

Date/Time: 2009-03-08 12:03:41.949 -0500
OS Version: Mac OS X 10.5.6 (9G55)
Report Version: 6

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000665f6865
Crashed Thread: 0

Thread 0 Crashed:
0 ??? 0x665f6865 0 + 1717528677
1 com.112dB.Redline.Monitor 0x4904c756 0x48f9d000 + 718678
2 com.apple.CoreFoundation 0x9426cb25 CFRunLoopRunSpecific + 4469
3 com.apple.CoreFoundation 0x9426ccd8 CFRunLoopRunInMode + 88
4 com.apple.HIToolbox 0x957e92c0 RunCurrentEventLoopInMode + 283
5 com.apple.HIToolbox 0x957e90d9 ReceiveNextEventCommon + 374
6 com.apple.HIToolbox 0x95847c6e _AcquireNextEvent + 58
7 com.apple.HIToolbox 0x958463cb RunApplicationEventLoop + 207
8 com.motu.DigitalPerformer 0x005d6126 0x1000 + 6115622
9 com.motu.DigitalPerformer 0x00002aa6 0x1000 + 6822
10 com.motu.DigitalPerformer 0x000029cd 0x1000 + 6605

Thread 1:
0 libSystem.B.dylib 0x94bf02e6 mach_wait_until + 10
1 libSystem.B.dylib 0x94c673ad nanosleep + 314
2 libSystem.B.dylib 0x94c6726d usleep + 61
3 PerfMSL.dylib 0x021eddf2 PerfAssert::SetEnableDebugMsgs(bool) + 5142
4 PerfMSL.dylib 0x021edb1b PerfAssert::SetEnableDebugMsgs(bool) + 4415
5 libSystem.B.dylib 0x94c21095 _pthread_start + 321
6 libSystem.B.dylib 0x94c20f52 thread_start + 34

Thread 2:
0 libSystem.B.dylib 0x94bf01c6 mach_msg_trap + 10
1 libSystem.B.dylib 0x94bf79bc mach_msg + 72
2 libSystem.B.dylib 0x94c651e7 mach_msg_server + 675
3 PerfMSL.dylib 0x021ebc03 catch_exception_raise_state + 527
4 libSystem.B.dylib 0x94c21095 _pthread_start + 321
5 libSystem.B.dylib 0x94c20f52 thread_start + 34

Thread 3:
0 libSystem.B.dylib 0x94bf01c6 mach_msg_trap + 10
1 libSystem.B.dylib 0x94bf79bc mach_msg + 72
2 PerfFoundation.dylib 0x0206e61b PerfWorkerThread::GetThread() + 831
3 PerfFoundation.dylib 0x0206e719 PerfWorkerThread::GetThread() + 1085
4 libSystem.B.dylib 0x94c21095 _pthread_start + 321
5 libSystem.B.dylib 0x94c20f52 thread_start + 34

Thread 4:
0 libSystem.B.dylib 0x94bf021a semaphore_timedwait_trap + 10
1 AllUtilities.dylib 0x00f1c79b PerfSemaphore::timed_wait(long) + 115
2 PerfEngine.dylib 0x01b5cb18 PerfAudioCache::RunJobs(std::vector<workq_ele_t*, std::allocator<workq_ele_t*> >&) + 662
3 PerfEngine.dylib 0x01b5cb43 PerfAudioCache::RunJobs(std::vector<workq_ele_t*, std::allocator<workq_ele_t*> >&) + 705
4 libSystem.B.dylib 0x94c21095 _pthread_start + 321
5 libSystem.B.dylib 0x94c20f52 thread_start + 34

And this one was actually the first one:

Process: Digital Performer [309]
Path: /Applications/MOTU Digital Performer 6/Digital Performer 6.02.app/Contents/MacOS/Digital Performer
Identifier: com.motu.DigitalPerformer
Version: 6.02 (6.02)
Code Type: X86 (Native)
Parent Process: launchd [105]

Date/Time: 2009-03-08 10:32:49.652 -0500
OS Version: Mac OS X 10.5.6 (9G55)
Report Version: 6

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: 0x000000000000000d, 0x0000000000000000
Crashed Thread: 0

Thread 0 Crashed:
0 ??? 0x025035f5 0 + 38811125
1 com.112dB.Redline.Monitor 0x4900a756 0x48f5b000 + 718678
2 com.apple.CoreFoundation 0x9426cb25 CFRunLoopRunSpecific + 4469
3 com.apple.CoreFoundation 0x9426ccd8 CFRunLoopRunInMode + 88
4 com.apple.HIToolbox 0x957e92c0 RunCurrentEventLoopInMode + 283
5 com.apple.HIToolbox 0x957e90d9 ReceiveNextEventCommon + 374
6 com.apple.HIToolbox 0x95847c6e _AcquireNextEvent + 58
7 com.apple.HIToolbox 0x958463cb RunApplicationEventLoop + 207
8 com.motu.DigitalPerformer 0x005d6126 0x1000 + 6115622
9 com.motu.DigitalPerformer 0x00002aa6 0x1000 + 6822
10 com.motu.DigitalPerformer 0x000029cd 0x1000 + 6605

Thread 1:
0 libSystem.B.dylib 0x94bf02e6 mach_wait_until + 10
1 libSystem.B.dylib 0x94c673ad nanosleep + 314
2 libSystem.B.dylib 0x94c6726d usleep + 61
3 PerfMSL.dylib 0x021eddf2 PerfAssert::SetEnableDebugMsgs(bool) + 5142
4 PerfMSL.dylib 0x021edb1b PerfAssert::SetEnableDebugMsgs(bool) + 4415
5 libSystem.B.dylib 0x94c21095 _pthread_start + 321
6 libSystem.B.dylib 0x94c20f52 thread_start + 34

Thread 2:
0 libSystem.B.dylib 0x94bf01c6 mach_msg_trap + 10
1 libSystem.B.dylib 0x94bf79bc mach_msg + 72
2 libSystem.B.dylib 0x94c651e7 mach_msg_server + 675
3 PerfMSL.dylib 0x021ebc03 catch_exception_raise_state + 527
4 libSystem.B.dylib 0x94c21095 _pthread_start + 321
5 libSystem.B.dylib 0x94c20f52 thread_start + 34

Thread 3:
0 libSystem.B.dylib 0x94bf01c6 mach_msg_trap + 10
1 libSystem.B.dylib 0x94bf79bc mach_msg + 72
2 PerfFoundation.dylib 0x0206e61b PerfWorkerThread::GetThread() + 831
3 PerfFoundation.dylib 0x0206e719 PerfWorkerThread::GetThread() + 1085
4 libSystem.B.dylib 0x94c21095 _pthread_start + 321
5 libSystem.B.dylib 0x94c20f52 thread_start + 34

Thread 4:
0 libSystem.B.dylib 0x94bf021a semaphore_timedwait_trap + 10
1 AllUtilities.dylib 0x00f1c79b PerfSemaphore::timed_wait(long) + 115
2 PerfEngine.dylib 0x01b5cb18 PerfAudioCache::RunJobs(std::vector<workq_ele_t*, std::allocator<workq_ele_t*> >&) + 662
3 PerfEngine.dylib 0x01b5cb43 PerfAudioCache::RunJobs(std::vector<workq_ele_t*, std::allocator<workq_ele_t*> >&) + 705
4 libSystem.B.dylib 0x94c21095 _pthread_start + 321
5 libSystem.B.dylib 0x94c20f52 thread_start + 34

And here is a little more detail on the 3rd crash (the one I reported in the previous post):

Process: Digital Performer [420]
Path: /Applications/MOTU Digital Performer 6/Digital Performer 6.02.app/Contents/MacOS/Digital Performer
Identifier: com.motu.DigitalPerformer
Version: 6.02 (6.02)
Code Type: X86 (Native)
Parent Process: launchd [105]

Date/Time: 2009-03-08 12:34:39.154 -0500
OS Version: Mac OS X 10.5.6 (9G55)
Report Version: 6

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000006f69747d
Crashed Thread: 0

Thread 0 Crashed:
0 com.112dB.Redline.Monitor 0x4902319f 0x48f04000 + 1175967
1 com.112dB.Redline.Monitor 0x49024240 0x48f04000 + 1180224
2 com.112dB.Redline.Monitor 0x48fb3756 0x48f04000 + 718678
3 com.apple.CoreFoundation 0x9426cb25 CFRunLoopRunSpecific + 4469
4 com.apple.CoreFoundation 0x9426ccd8 CFRunLoopRunInMode + 88
5 com.apple.HIToolbox 0x957e92c0 RunCurrentEventLoopInMode + 283
6 com.apple.HIToolbox 0x957e90d9 ReceiveNextEventCommon + 374
7 com.apple.HIToolbox 0x95847c6e _AcquireNextEvent + 58
8 com.apple.HIToolbox 0x958463cb RunApplicationEventLoop + 207
9 com.motu.DigitalPerformer 0x005d6126 0x1000 + 6115622
10 com.motu.DigitalPerformer 0x00002aa6 0x1000 + 6822
11 com.motu.DigitalPerformer 0x000029cd 0x1000 + 6605

Thread 1:
0 libSystem.B.dylib 0x94bf02e6 mach_wait_until + 10
1 libSystem.B.dylib 0x94c673ad nanosleep + 314
2 libSystem.B.dylib 0x94c6726d usleep + 61
3 PerfMSL.dylib 0x021eddf2 PerfAssert::SetEnableDebugMsgs(bool) + 5142
4 PerfMSL.dylib 0x021edb1b PerfAssert::SetEnableDebugMsgs(bool) + 4415
5 libSystem.B.dylib 0x94c21095 _pthread_start + 321
6 libSystem.B.dylib 0x94c20f52 thread_start + 34

Thread 2:
0 libSystem.B.dylib 0x94bf01c6 mach_msg_trap + 10
1 libSystem.B.dylib 0x94bf79bc mach_msg + 72
2 libSystem.B.dylib 0x94c651e7 mach_msg_server + 675
3 PerfMSL.dylib 0x021ebc03 catch_exception_raise_state + 527
4 libSystem.B.dylib 0x94c21095 _pthread_start + 321
5 libSystem.B.dylib 0x94c20f52 thread_start + 34

Thread 3:
0 libSystem.B.dylib 0x94bf01c6 mach_msg_trap + 10
1 libSystem.B.dylib 0x94bf79bc mach_msg + 72
2 PerfFoundation.dylib 0x0206e61b PerfWorkerThread::GetThread() + 831
3 PerfFoundation.dylib 0x0206e719 PerfWorkerThread::GetThread() + 1085
4 libSystem.B.dylib 0x94c21095 _pthread_start + 321
5 libSystem.B.dylib 0x94c20f52 thread_start + 34

Thread 4:
0 libSystem.B.dylib 0x94bf021a semaphore_timedwait_trap + 10
1 AllUtilities.dylib 0x00f1c79b PerfSemaphore::timed_wait(long) + 115
2 PerfEngine.dylib 0x01b5cb18 PerfAudioCache::RunJobs(std::vector<workq_ele_t*, std::allocator<workq_ele_t*> >&) + 662
3 PerfEngine.dylib 0x01b5cb43 PerfAudioCache::RunJobs(std::vector<workq_ele_t*, std::allocator<workq_ele_t*> >&) + 705
4 libSystem.B.dylib 0x94c21095 _pthread_start + 321
5 libSystem.B.dylib 0x94c20f52 thread_start + 34

Thread 5:
0 libSystem.B.dylib 0x94bf01c6 mach_msg_trap + 10
1 libSystem.B.dylib 0x94bf79bc mach_msg + 72
2 com.apple.audio.MIDI.CoreMIDI 0x00eeff0f XServerMachPort::ReceiveMessage(int&, void*, int&) + 101
3 com.apple.audio.MIDI.CoreMIDI 0x00ee2477 MIDIInPortThread::Run() + 111
4 com.apple.audio.MIDI.CoreMIDI 0x00ee607d XThread::RunHelper(void*) + 17
5 com.apple.audio.MIDI.CoreMIDI 0x00ef09ee CAPThread::Entry(CAPThread*) + 96
6 libSystem.B.dylib 0x94c21095 _pthread_start + 321
7 libSystem.B.dylib 0x94c20f52 thread_start + 34

Posted: **Sun Mar 08, 2009 12:10 pm**

So much for Redline ....

Posted: **Sun Mar 08, 2009 12:23 pm**

Meanwhile, this is the Canz interface:

I must admit that it sounds pretty good, but with all this going on, I really have no idea what's happening, and I'm not in the mood to study the manual to learn what every one of those controls does, and how to make it perfectly emulate speakers.

Given the choice, I'll play with Canz now and then to see if I can figure it out, but I'm going to bet on Redline getting fixed. I just have a feeling that it will, and I'll take three knobs any day over 26 faders with names like "Live ACH" and "Dead ACH." On the other hand, if I can get Canz to sound like my speakers, then all I have to do is leave it set and forget it. I just want headphone monitoring software; I don't care how it looks as long as I can make it work. I just don't have a lot of faith in 26 sliders for this one little task at the moment.

Shooshie

Posted: **Sun Mar 08, 2009 12:33 pm**

The HIToolbox is a GUI compatibility protocol issue-- probably too much carbon and not enough cocoa.

Posted: **Sun Mar 08, 2009 2:21 pm**

Three pages on a post that wasn't here when last I logged in, is a bit overwhelming, but I did at least skim the whole content.

It looks like there are some stability problems with this plug-in at the moment, so maybe I'll wait.

But just to be clear on the concept, is this plug-in meant to widen and deepen the stereo image on headphones (which are a binaural listening experience) so that you are more likely to make mixes that work properly on monitors/loudspeakers?

Or is it meant for CREATING a binaural-oriented mix?

I'm guessing the former, as that's a lot more useful.

Posted: **Sun Mar 08, 2009 2:40 pm**

mhschmieder wrote:Three pages on a post that wasn't here when last I logged in, is a bit overwhelming, but I did at least skim the whole content.

It looks like there are some stability problems with this plug-in at the moment, so maybe I'll wait.

But just to be clear on the concept, is this plug-in meant to widen and deepen the stereo image on headphones (which are a binaural listening experience) so that you are more likely to make mixes that work properly on monitors/loudspeakers?

Or is it meant for CREATING a binaural-oriented mix?

I'm guessing the former, as that's a lot more useful.

It would seem to me that if the data is printed to audio that one could create an audio track exclusive for headphone listening... ? I know that the intent is not to print this plugin to audio in general, but maybe there are some potentially useful extended techniques possible.

Posted: **Sun Mar 08, 2009 3:09 pm**

It's for monitoring with headphones. That's really all it's for. Headphones alone do not present a true stereo image, but instead present something like a binaural image. Everything is either left or right. You don't get the same thing as you get in speakers, where both ears hear both speakers more or less equally, just slightly delayed in timing by the speed of sound as it travels the difference of the distance from one ear as to the other.

I've used headphone monitors before, and they are great. While nothing can replace speakers (unless you're mixing for iPod), headphone monitors send both images to both ears, with the requisite delay. This gives a truer center channel. In the end, you bypass or remove the headphone monitor and listen through speakers, doing any final tweaks at that point. But if you've calibrated them well, there should be little difference in panning and balances, and the center channel should be pretty much as you heard it in the headphones.

Posted: **Sun Mar 08, 2009 3:16 pm**

Frodo wrote:It would seem to me that if the data is printed to audio that one could create an audio track exclusive for headphone listening... ?

I would think that if your intent is to mix for headphones, i.e., the iPod, then you'd just use headphones without the monitor software. In other words, just route your main outs straight to your headphones and mix. Of course, then there are all those fancy kinds of headphones and microphones that reside in a head-shaped stand... I think all that is another subject entirely.

Posted: **Sun Mar 08, 2009 6:36 pm**

Shooshie wrote:
Frodo wrote:It would seem to me that if the data is printed to audio that one could create an audio track exclusive for headphone listening... ?

I would think that if your intent is to mix for headphones, i.e., the iPod, then you'd just use headphones without the monitor software. In other words, just route your main outs straight to your headphones and mix. Of course, then there are all those fancy kinds of headphones and microphones that reside in a head-shaped stand... I think all that is another subject entirely.

You know what would really be cool??? if RME and DP allowed a plugin in the outboard phone section of the mixer like in Total mix fireface mixer.

That would be the real ticket for sure!!!!

Posted: **Sun Mar 08, 2009 11:17 pm**

Shooshie, thanks for clearing that up; your explanation makes perfect sense, and is what I was hoping to be the case.

I definitely need this plug-in then, as I mix almost exclusively on headphones due to the hours I operate, and only use monitors for final tweaking and sanity checks.

Of course most of what I do is mono, so it's not an issue in most cases. The majority of my projects these days are not designated for CD and so are best left in mono due to there being no valid assumptions about computer listening.

Posted: **Mon Mar 09, 2009 3:36 am**

Shooshie wrote:Here are the last few log entries on the other two crashes I had after installing Redline Monitor:

Thanks much for going to the trouble of retrieving and posting those, it's definitely Redline Monitor that's at fault.

The logs do tell me what goes wrong though I'm not sure *why* it does--this seems DP specific, at least I didn't receive any reports of a similar nature with other hosts. Anyway I'll check into this and hope to have a fix in a few days at most. Will report back here.

Take care,

-- dj!

Posted: **Mon Mar 09, 2009 11:52 am**

Thanks much, dj. If you can get it stable on DP, I think it would be popular here. Not sure, but I know that I liked it a lot up to the point that it crashed DP. Minor annoyance.

I look forward to trying it with the fix.

Shoosh

MOTUnation.com

Plug-In for Mixing in Headphones

Re: Plug-In for Mixing in Headphones

Re: Plug-In for Mixing in Headphones

Re: Plug-In for Mixing in Headphones

Re: Plug-In for Mixing in Headphones

Re: Plug-In for Mixing in Headphones

Re: Plug-In for Mixing in Headphones

Re: Plug-In for Mixing in Headphones

Re: Plug-In for Mixing in Headphones

Re: Plug-In for Mixing in Headphones

Re: Plug-In for Mixing in Headphones

Re: Plug-In for Mixing in Headphones

Re: Plug-In for Mixing in Headphones

Re: Plug-In for Mixing in Headphones

Re: Plug-In for Mixing in Headphones

Re: Plug-In for Mixing in Headphones