June 3 2008 - PREVIEW NEARING BETA -- 2.301/0.98

[Justin]

http://reaper.fm/files/osx_early/reaper2301_098.dmg

Requires OSX 10.4 or 10.5. Intel macs are strongly encouraged but PPC macs should work as well, though slowly.

Post bug reports etc here.

Known plug-in compatability issues:
Addictive Drums demo does weird things if you resize its UI at all
Camel Audio Cameleon5000 fails miserably in VST form.
Probably more, too.

[Tallisman]

this is great news!
I should have the new studio up and going for the beta release!

:D
.t

[Bevosss]

Sounds about time I started testing it... :)


What's the installation process now? Drop it in the application folder? Is that it?

Cheers for any help here.

[rpantoja]

First of all, Justin: congratulations! This mac version is already looking VERY nice, worth moving back to REAPER instead of keep on w/ my change to Logic due to platform migration... The only little problem I see is that the IK plugs are still w/ a slight UI problem... it is necessary to click the UI for it to show up everytime I attempt to visualize the plug. That is all I can see so far, besides what you already know, of course. Best regards and EXCELLENT work.

Rafael

[Tallisman]

Sounds about time I started testing it... :)


What's the installation process now? Drop it in the application folder? Is that it?

Cheers for any help here.

Yes Bevosss
just drop it where you want it.

:D

.t

[Jeronimo]

Justin!!!!
Didn't spend a lot of time with 0.98 yet, but so far things seems GREAT!
ReaInsert is working great with my Audiofire12 under 10.4.10.
I'll be buying my license next month...
Thanks a lot man!

[kerryg]

BFD now works better in REAPER than it does in Logic 8 - you seem to have sorted it out more elegantly than they managed to. Similarly Rob "Papen's Albino" and G-Force's "Mini-Monsta". CPU useage is a bit high but I guess that's why you're recommending the Intels over my dual G5.

Nice work. Congrats!

[Jeronimo]

Ok,

Just tried recording 12 tracks 44.1/24 with Reaper, Digital Performer 5.12 and Logic 8.01.

Reaper needed the buffer set to 256 to be able to record without clicks.
Logic needed 128
DP could make it with 64.

I opened an old mixing session that was maxing out my Macbook with the old Reaper versions... now, it works without a hiccup!

[neural_rust]

this is some seriously good news..
thou i have been using last few versions without any problem at all..
maybe it's time for me to buy the full licence.
Thank you you Team Cockos,
*it's getting better all the time* etc..
browser is still missing, but that's no big deal to me right now..
was it in the last preview that gave us the option when saving the project, it gives you an option to move or copy all files to project folder..??
that was the most annoying thing for me, but since it's now there
i have actually nothing to bitch about.. :)
So thanks again and keep up the most awesome job..

-Neural_Rust

[Tom Drinkwater]

cool!

are PPC macs MORE discouraged now than for the earlier builds?

is changing to reaper as my main DAW now and trying to get another 12-18 months out of my G5 dual 1.8 just stupid? (i know the answer is probably "depends")

is there a thread on PPC performance specifically?

I certainly understand that spending time on optimising for PPC is wasted effort at this point, but I'd love some guidance about the best way forward for us G5 users..

[Justin]

cool!

are PPC macs MORE discouraged now than for the earlier builds?

is changing to reaper as my main DAW now and trying to get another 12-18 months out of my G5 dual 1.8 just stupid? (i know the answer is probably "depends")

is there a thread on PPC performance specifically?

I certainly understand that spending time on optimising for PPC is wasted effort at this point, but I'd love some guidance about the best way forward for us G5 users..

It's no worse than it was in previous builds, the note is simply because people (including us) have been seeing poor performance on PPCs.. So, you may wish to test and evaluate the performance for your own needs. We do not have any G5 macs here to test, just G4, so perhaps G5s will do well...

-Justin

[kerryg]

We do not have any G5 macs here to test, just G4, so perhaps G5s will do well...

-Justin

We gotta get you a G5.

But before that, I want to send you another prezzie - a much stranger one :D

[Tom Drinkwater]

well if anyone wants to devise or suggest a standard performance test, I'm more than happy to try it on my G5 and post the results

[juanito]

Justin,

It's-ah-smokin' on the 8 core amigo!!!!


It's got some serious PIP!!

[axel_ef]

It works good on my 10.4.9, but with Toontrack EZDrummer (AUi) I have no sound from the drums.

[Tallisman]

Hack bug...
I never discovered this but I did confirm it:

[shift] does not work as a mouse wheel modifier.
it seems to work on real Macs

[mahasandi]

Justin~
best yet great work thank you.
when in a say save as dialog , the mousewheel still modifies reaper , though it is in the background, is this a setting or....?

[bennals]

Brilliant Justin. All the AUinstruments that were failing in the previous build now seem to be fine, with the one small exception being that G-Media's Minimonsta GUI drawing seems to be out. To turn a knob or parameter you need to click somewhere above where the knob actually is on your screen.

So thats Zebra 2, Filterscape VA and Imposcar all working perfectly. Kjaerhus MPL-1 Pro now works fine as well. Great to have that one back.

Oh, I forgot, Togu Audio Line's Bassline still doesn't output sound.

Cheers.

Bill.

[Bevosss]

Well it was all going swimmingly, until I started setting up screensets...

1. Adjust docked mixer to a larger height
2. Save as a windows screenset X
3. Load screenset X...mixer/docker shrinks to previous size, instead of the saved set X.
4. Continue trying to load screenset X...
5. Reaper goes 'poof!'...(closed/crashed)

On an Intel iMac 2.0 G, 2G RAM, 10.4.6

[Bevosss]

Can anyone tell me where the application data that's in the PC version is in OSX?

ie Reaper.ini, screensets.ini, etc

My Reaper folder is in Applications...are there any other folders involved in OSX?

cheers :)

[GIlJanus]

In Mac terms, it is in ~/Library/Application Support/REAPER/

~ == your home directory/folder.

If it doesn't exist, it will be created when Reaper runs the first time. Also the saved *.ini files are written there, and folders for the FX Chains and Templates are created.

And when Reaper runs the next time, it uses these assets.

[Bevosss]

In Mac terms, it is in ~/Library/Application Support/REAPER/

~ == your home directory/folder.

If it doesn't exist, it will be created when Reaper runs the first time. Also the saved *.ini files are written there, and folders for the FX Chains and Templates are created.

And when Reaper runs the next time, it uses these assets.

Thanks, much appreciated! :)

[kungpostyle]

I bought an Alesis IO 26 on Thursday. Spent many hours on Friday trying to get Cubase AI 4 and LE 1 to accept audio from it. Failed.

Luckily, I've been following Reaper for at least a year now. I had even loaded a very early version (.36 or something) and messed around with it. I decided that I had spent enough time with the good people from Steinberg. It took me most of an hour just to register their free software. I had had earlier battles with cubase le 1 and a Tascam US-224. That one I eventually got working.

Anyway, I loaded this most recent version of reaper and was recording audio in about 5-7 minutes from the time I clicked download. Looks like Reaper is my new DAW, thanks Justine. I'll buy a license when the first beta hits. This may be the best 50 bucks I ever spend.

Kung

[mrelwood]

when in a say save as dialog , the mousewheel still modifies reaper , though it is in the background

Confirmed. The same goes for copy/paste shortcuts ( C,  V). I'm used to copy/paste directory or file names, now the only way to do it is through right clicking.

Other than that, I'm ditching my Bootcamp. :)

[bennals]

Not sure if this has been noted elsewhere, but saving plugin presets in the host format doesn't seem to work for AUs in the .98 build. The preset gets saved, but then recalling it doesn't seem to have any effect on the plugin parameters. Works fine for JS and VST plugins.

Bill.

[Justin]

Not sure if this has been noted elsewhere, but saving plugin presets in the host format doesn't seem to work for AUs in the .98 build. The preset gets saved, but then recalling it doesn't seem to have any effect on the plugin parameters. Works fine for JS and VST plugins.

Bill.

Got it, thx! :)

[hourglass]

Got it, thx! :)

now that's service! :D

[bennals]

Got it, thx! :)

No worries:)

[The Spark]

I was trying the latest version of DDMF IIEQ and it works fine in Reaper other than the mousewheel doesnt adjust the Q. Someone on KVR confirmed it works in another Mac host. Is this mousewheel issue something that hasnt been implemented for external plugs yet, or is it possibly a bug?

Thanks!

[Tallisman]

I was trying the latest version of DDMF IIEQ and it works fine in Reaper other than the mousewheel doesnt adjust the Q. Someone on KVR confirmed it works in another Mac host. Is this mousewheel issue something that hasnt been implemented for external plugs yet, or is it possibly a bug?

Thanks!

confirmed. great eq BTW especially since it costs what you are willing to pay. I have bought both flavours now... Mac&PC.

http://www.ddmf.eu/

.t

[EnzoPolotso]

Looks like I'm almost able to ditch Windows!
I'm having a problem with Drumagog though, when I select it as an effect, I just get a blank white window in the fx box.
Hmm...

[griz lee]

hello everyone mac

i fired it up and had a small problem with the routing matrix undocked. If you undock it then go have youself a serious routing party, the click boxes don't work. They regain perfect functionality again once docked. [g5]

supernice though.

[yan]

Most plugins and effects were gone, but using ktrace I found that Reaper tries to open the directories with a different case than they are in the filesystem.

If I create the following symbolic links, the plugins and effects are found:
---
cd /Applications/REAPER
ln -s Data data
ln -s Effects effects
ln -s Plugins plugins
cd Plugins
ln -s FX fx

cd ~/Library/Audio
ln -s Plug-Ins Plug-ins

cd /Library/Audio
ln -s Plug-Ins Plug-ins
---

(Cubase SX2 also searches the wrong-case directories. There I didn't get some of its own plugins to work, though...)

Huge THANKS to Justin for this beautiful recording program.
/Yan

(using PowerBook G4, 1.5GHz, 1.25GB, OSX 10.4.11 - Yes, it's getting slow...)

[mrelwood]

Per item FX seems not to work yet. I don't use it much, but it is the only thing I found missing from the Mac version!

[DGT]

Anyone having an issue when adding FX?

I select the plug and at first it doesn't appear in the list, close the fx window and re-open its there, but the fx bypass ticks aren't visible, they work if I click where they should be, they bypass ok, kinda wierd. Everything else seems cool.

[MarkFrancombe]

Hi, was wondering if there is any mac caperbilities for synching with Reason yet, like the PC version does most excellently..

[Tom Drinkwater]

when playing a software instrument reaper seems to lose some midi data from my usb keyboard, resulting in some notes not sounding and some getting stuck.

this happened with Schwa Olga AU and also with NI B4II VST, so its not specific to a particular plugin or even a particular plugin format.

both plugins work fine in my other hosts.

anything i can try changing to fix this?

[Tallisman]

Fresh install of OSX 10.5.2 after disastrous attempts to try 10.5.3...

Got a crash while shift selectign about 7 plugins in the FX bin.
here's the junk:
Process: REAPER [2455]
Path: /Applications/Audio/REAPER/REAPER.app/Contents/MacOS/REAPER
Identifier: com.cockos.reaper
Version: ??? (2.301/0.98 PREVIEW VERSION)
Code Type: X86 (Native)
Parent Process: launchd [124]

Date/Time: 2008-06-13 23:06:19.429 -0600
OS Version: Mac OS X 10.5.2 (9C7010)
Report Version: 6

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

Thread 0:
0 libSystem.B.dylib 0x917bb9e6 mach_msg_trap + 10
1 libSystem.B.dylib 0x917c31dc mach_msg + 72
2 com.apple.CoreFoundation 0x924040de CFRunLoopRunSpecific + 1806
3 com.apple.CoreFoundation 0x92404d18 CFRunLoopRunInMode + 88
4 com.apple.HIToolbox 0x914256a0 RunCurrentEventLoopInMode + 283
5 com.apple.HIToolbox 0x914254b9 ReceiveNextEventCommon + 374
6 com.apple.HIToolbox 0x9142532d BlockUntilNextEventMatchingListInMode + 106
7 com.apple.AppKit 0x9699b7d9 _DPSNextEvent + 657
8 com.apple.AppKit 0x9699b08e -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
9 com.apple.AppKit 0x969940c5 -[NSApplication run] + 795
10 com.apple.AppKit 0x9696130a NSApplicationMain + 574
11 com.cockos.reaper 0x0000200a start + 258
12 com.cockos.reaper 0x00001f31 start + 41

Thread 1:
0 libSystem.B.dylib 0x917bba46 semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x917eddaf _pthread_cond_wait + 1244
2 libSystem.B.dylib 0x917ef633 pthread_cond_timedwait_relative_np + 47
3 ...ple.CoreServices.CarbonCore 0x90d1b92a TSWaitOnConditionTimedRelative + 246
4 ...ple.CoreServices.CarbonCore 0x90d1b70a TSWaitOnSemaphoreCommon + 422
5 ...ickTimeComponents.component 0x946b9aa2 ReadSchedulerThreadEntryPoint + 4724
6 libSystem.B.dylib 0x917ecc55 _pthread_start + 321
7 libSystem.B.dylib 0x917ecb12 thread_start + 34

Thread 2:
0 libSystem.B.dylib 0x917bb9e6 mach_msg_trap + 10
1 libSystem.B.dylib 0x917c31dc mach_msg + 72
2 com.apple.audio.midi.CoreMIDI 0x00325f0f XServerMachPort::ReceiveMessage(int&, void*, int&) + 101
3 com.apple.audio.midi.CoreMIDI 0x00318477 MIDIInPortThread::Run() + 111
4 com.apple.audio.midi.CoreMIDI 0x0031c07d XThread::RunHelper(void*) + 17
5 com.apple.audio.midi.CoreMIDI 0x003269ee CAPThread::Entry(CAPThread*) + 96
6 libSystem.B.dylib 0x917ecc55 _pthread_start + 321
7 libSystem.B.dylib 0x917ecb12 thread_start + 34

Thread 3:
0 libSystem.B.dylib 0x917bb9e6 mach_msg_trap + 10
1 libSystem.B.dylib 0x917c31dc mach_msg + 72
2 com.apple.CoreFoundation 0x924040de CFRunLoopRunSpecific + 1806
3 com.apple.CoreFoundation 0x92404d18 CFRunLoopRunInMode + 88
4 com.apple.audio.CoreAudio 0x910cd464 HALRunLoop::OwnThread(void*) + 160
5 com.apple.audio.CoreAudio 0x910cd300 CAPThread::Entry(CAPThread*) + 96
6 libSystem.B.dylib 0x917ecc55 _pthread_start + 321
7 libSystem.B.dylib 0x917ecb12 thread_start + 34

Thread 4 Crashed:
0 com.mda-vst.mda BeatBox 0x2efcbe8c main_macho + 9430
1 com.cockos.reaper 0x000eea4e start + 969542
2 com.cockos.reaper 0x000fd894 start + 1030540
3 com.cockos.reaper 0x00107c8c start + 1072516
4 com.cockos.reaper 0x00045175 start + 275053
5 com.cockos.reaper 0x00046742 start + 280634
6 com.cockos.reaper 0x00043d2d start + 269861
7 com.cockos.reaper 0x000690a5 start + 422301
8 com.cockos.reaper 0x0008f3b7 start + 578735
9 com.cockos.reaper 0x0008f63b start + 579379
10 com.apple.audio.CoreAudio 0x910defdf HP_IOProc::Call(AudioTimeStamp const&, AudioTimeStamp const&, AudioBufferList const*, AudioTimeStamp const&, AudioBufferList*) + 319
11 com.apple.audio.CoreAudio 0x910decd0 IOA_Device::CallIOProcs(AudioTimeStamp const&, AudioTimeStamp const&, AudioTimeStamp const&) + 274
12 com.apple.audio.CoreAudio 0x910debac HP_IOThread::PerformIO(AudioTimeStamp const&) + 1246
13 com.apple.audio.CoreAudio 0x910dcf87 HP_IOThread::WorkLoop() + 1239
14 com.apple.audio.CoreAudio 0x910dcaab HP_IOThread::ThreadEntry(HP_IOThread*) + 17
15 com.apple.audio.CoreAudio 0x910cd300 CAPThread::Entry(CAPThread*) + 96
16 libSystem.B.dylib 0x917ecc55 _pthread_start + 321
17 libSystem.B.dylib 0x917ecb12 thread_start + 34

Thread 5:
0 libSystem.B.dylib 0x917bbb06 mach_wait_until + 10
1 libSystem.B.dylib 0x9183372f nanosleep + 314
2 libSystem.B.dylib 0x918335ef usleep + 61
3 com.cockos.reaper 0x0005cc92 start + 372106
4 com.cockos.reaper 0x0019eaf1 start + 1690601
5 libSystem.B.dylib 0x917ecc55 _pthread_start + 321
6 libSystem.B.dylib 0x917ecb12 thread_start + 34

Thread 6:
0 libSystem.B.dylib 0x917bbb06 mach_wait_until + 10
1 libSystem.B.dylib 0x9183372f nanosleep + 314
2 libSystem.B.dylib 0x918335ef usleep + 61
3 com.cockos.reaper 0x0005cc92 start + 372106
4 com.cockos.reaper 0x0019eaf1 start + 1690601
5 libSystem.B.dylib 0x917ecc55 _pthread_start + 321
6 libSystem.B.dylib 0x917ecb12 thread_start + 34

Thread 7:
0 libSystem.B.dylib 0x917bbb06 mach_wait_until + 10
1 libSystem.B.dylib 0x9183372f nanosleep + 314
2 libSystem.B.dylib 0x918335ef usleep + 61
3 com.cockos.reaper 0x0005cc92 start + 372106
4 com.cockos.reaper 0x0019eaf1 start + 1690601
5 libSystem.B.dylib 0x917ecc55 _pthread_start + 321
6 libSystem.B.dylib 0x917ecb12 thread_start + 34

Thread 8:
0 libSystem.B.dylib 0x917bbb06 mach_wait_until + 10
1 libSystem.B.dylib 0x9183372f nanosleep + 314
2 libSystem.B.dylib 0x918335ef usleep + 61
3 com.cockos.reaper 0x0005cc92 start + 372106
4 com.cockos.reaper 0x0019eaf1 start + 1690601
5 libSystem.B.dylib 0x917ecc55 _pthread_start + 321
6 libSystem.B.dylib 0x917ecb12 thread_start + 34

Thread 9:
0 libSystem.B.dylib 0x917bba46 semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x917eddaf _pthread_cond_wait + 1244
2 libSystem.B.dylib 0x917ef633 pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9601a4fc -[NSCondition waitUntilDate:] + 236
4 com.apple.Foundation 0x9601a310 -[NSConditionLock lockWhenCondition:beforeDate:] + 144
5 com.apple.Foundation 0x9601a275 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.AppKit 0x96a017f0 -[NSUIHeartBeat _heartBeatThread:] + 753
7 com.apple.Foundation 0x95fd45ad -[NSThread main] + 45
8 com.apple.Foundation 0x95fd4154 __NSThread__main__ + 308
9 libSystem.B.dylib 0x917ecc55 _pthread_start + 321
10 libSystem.B.dylib 0x917ecb12 thread_start + 34

Thread 10:
0 libSystem.B.dylib 0x917bb9e6 mach_msg_trap + 10
1 libSystem.B.dylib 0x917c31dc mach_msg + 72
2 com.apple.CoreFoundation 0x924040de CFRunLoopRunSpecific + 1806
3 com.apple.CoreFoundation 0x92404d74 CFRunLoopRun + 84
4 com.apple.DesktopServices 0x9198846f TSystemNotificationTask::SystemNotificationTaskPro c(void*) + 123
5 ...ple.CoreServices.CarbonCore 0x90d3abeb PrivateMPEntryPoint + 56
6 libSystem.B.dylib 0x917ecc55 _pthread_start + 321
7 libSystem.B.dylib 0x917ecb12 thread_start + 34

[Tallisman]

and...
Thread 11:
0 libSystem.B.dylib 0x917bb9e6 mach_msg_trap + 10
1 libSystem.B.dylib 0x917c31dc mach_msg + 72
2 com.apple.CoreFoundation 0x924040de CFRunLoopRunSpecific + 1806
3 com.apple.CoreFoundation 0x92404d74 CFRunLoopRun + 84
4 com.apple.DesktopServices 0x919885e8 TFSEventsNotificationTask::FSEventsNotificationTas kProc(void*) + 216
5 ...ple.CoreServices.CarbonCore 0x90d3abeb PrivateMPEntryPoint + 56
6 libSystem.B.dylib 0x917ecc55 _pthread_start + 321
7 libSystem.B.dylib 0x917ecb12 thread_start + 34

Thread 12:
0 libSystem.B.dylib 0x917c2bce __semwait_signal + 10
1 libSystem.B.dylib 0x917ed8cd pthread_cond_wait$UNIX2003 + 73
2 ...ple.CoreServices.CarbonCore 0x90d3c9d7 TSWaitOnCondition + 126
3 ...ple.CoreServices.CarbonCore 0x90d1b8fe TSWaitOnConditionTimedRelative + 202
4 ...ple.CoreServices.CarbonCore 0x90d3c654 MPWaitOnQueue + 208
5 com.apple.DesktopServices 0x91993a7a TNodeSyncTask::SyncTaskProc(void*) + 84
6 ...ple.CoreServices.CarbonCore 0x90d3abeb PrivateMPEntryPoint + 56
7 libSystem.B.dylib 0x917ecc55 _pthread_start + 321
8 libSystem.B.dylib 0x917ecb12 thread_start + 34

Thread 13:
0 libSystem.B.dylib 0x917ec4c6 kevent + 10
1 libSystem.B.dylib 0x917ecc55 _pthread_start + 321
2 libSystem.B.dylib 0x917ecb12 thread_start + 34

Thread 14:
0 libSystem.B.dylib 0x9180bb3a select$DARWIN_EXTSN + 10
1 libSystem.B.dylib 0x917ecc55 _pthread_start + 321
2 libSystem.B.dylib 0x917ecb12 thread_start + 34

Thread 15:
0 libSystem.B.dylib 0x917bba3a semaphore_timedwait_trap + 10
1 ...ple.CoreServices.CarbonCore 0x90d4df7b MPWaitOnSemaphore + 125
2 ??? 0x29d5bc95 0 + 701873301
3 ??? 0x29d5311d 0 + 701837597
4 ??? 0x29d95191 0 + 702108049
5 libSystem.B.dylib 0x917ecc55 _pthread_start + 321
6 libSystem.B.dylib 0x917ecb12 thread_start + 34

Thread 16:
0 libSystem.B.dylib 0x917bba3a semaphore_timedwait_trap + 10
1 ...ple.CoreServices.CarbonCore 0x90d4df7b MPWaitOnSemaphore + 125
2 ??? 0x29d5bc95 0 + 701873301
3 ??? 0x29d5311d 0 + 701837597
4 ??? 0x29d95191 0 + 702108049
5 libSystem.B.dylib 0x917ecc55 _pthread_start + 321
6 libSystem.B.dylib 0x917ecb12 thread_start + 34

Thread 17:
0 libSystem.B.dylib 0x917bba3a semaphore_timedwait_trap + 10
1 ...ple.CoreServices.CarbonCore 0x90d4df7b MPWaitOnSemaphore + 125
2 ??? 0x29d5bc95 0 + 701873301
3 ??? 0x29d5311d 0 + 701837597
4 ??? 0x29d95191 0 + 702108049
5 libSystem.B.dylib 0x917ecc55 _pthread_start + 321
6 libSystem.B.dylib 0x917ecb12 thread_start + 34

Thread 18:
0 libSystem.B.dylib 0x917bba46 semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x917eddaf _pthread_cond_wait + 1244
2 libSystem.B.dylib 0x917ef633 pthread_cond_timedwait_relative_np + 47
3 ...ple.CoreServices.CarbonCore 0x90d1b92a TSWaitOnConditionTimedRelative + 246
4 ...ple.CoreServices.CarbonCore 0x90d1b70a TSWaitOnSemaphoreCommon + 422
5 ...ple.CoreServices.CarbonCore 0x90d43d0c AIOFileThread(void*) + 1056
6 libSystem.B.dylib 0x917ecc55 _pthread_start + 321
7 libSystem.B.dylib 0x917ecb12 thread_start + 34

Thread 19:
0 libSystem.B.dylib 0x917c2bce __semwait_signal + 10
1 libSystem.B.dylib 0x917ed8cd pthread_cond_wait$UNIX2003 + 73
2 com.apple.ColorSync 0x905e1460 pthreadSemaphoreWait(t_pthreadSemaphore*) + 42
3 com.apple.ColorSync 0x905f3d92 CMMConvTask(void*) + 54
4 libSystem.B.dylib 0x917ecc55 _pthread_start + 321


5 libSystem.B.dylib 0x917ecb12 thread_start + 34

Thread 20:
0 libSystem.B.dylib 0x917c2bce __semwait_signal + 10
1 libSystem.B.dylib 0x917ed8cd pthread_cond_wait$UNIX2003 + 73
2 com.apple.ColorSync 0x905e1460 pthreadSemaphoreWait(t_pthreadSemaphore*) + 42
3 com.apple.ColorSync 0x905f3d92 CMMConvTask(void*) + 54
4 libSystem.B.dylib 0x917ecc55 _pthread_start + 321
5 libSystem.B.dylib 0x917ecb12 thread_start + 34

Thread 21:
0 libSystem.B.dylib 0x917c2bce __semwait_signal + 10
1 libSystem.B.dylib 0x917ed8cd pthread_cond_wait$UNIX2003 + 73
2 com.apple.ColorSync 0x905e1460 pthreadSemaphoreWait(t_pthreadSemaphore*) + 42
3 com.apple.ColorSync 0x905f3d92 CMMConvTask(void*) + 54
4 libSystem.B.dylib 0x917ecc55 _pthread_start + 321
5 libSystem.B.dylib 0x917ecb12 thread_start + 34

Thread 22:
0 libSystem.B.dylib 0x917bbb06 mach_wait_until + 10
1 ...ple.CoreServices.CarbonCore 0x90d533eb MPDelayUntil + 39
2 ...ple.CoreServices.CarbonCore 0x90d5327f Delay + 104
3 ...opellerheads.rewire.library 0x2e4eb7e8 RWPUnregisterDeviceImp + 21574
4 ...opellerheads.rewire.library 0x2e506a5c RWPUnregisterDeviceImp + 132794
5 libSystem.B.dylib 0x917ecc55 _pthread_start + 321
6 libSystem.B.dylib 0x917ecb12 thread_start + 34

Thread 23:
0 libSystem.B.dylib 0x917bba3a semaphore_timedwait_trap + 10
1 ...ple.CoreServices.CarbonCore 0x90d4df7b MPWaitOnSemaphore + 125
2 ...yvan.flux.BitterSweetII.vst 0x2f194c95 Flux::Notify::CSignal::Wait(unsigned long) + 27
3 ...yvan.flux.BitterSweetII.vst 0x2f18c11d Flux::Thread::CApcThread::ThreadProc() + 1111
4 ...yvan.flux.BitterSweetII.vst 0x2f1ce191 Flux::Thread::TBase<Flux::Thread::CApcThread>::InternalThreadProc(void*) + 41
5 libSystem.B.dylib 0x917ecc55 _pthread_start + 321
6 libSystem.B.dylib 0x917ecb12 thread_start + 34

Thread 24:
0 libSystem.B.dylib 0x917bba3a semaphore_timedwait_trap + 10
1 ...ple.CoreServices.CarbonCore 0x90d4df7b MPWaitOnSemaphore + 125
2 ...yvan.flux.BitterSweetII.vst 0x2f194c95 Flux::Notify::CSignal::Wait(unsigned long) + 27
3 ...yvan.flux.BitterSweetII.vst 0x2f18c11d Flux::Thread::CApcThread::ThreadProc() + 1111
4 ...yvan.flux.BitterSweetII.vst 0x2f1ce191 Flux::Thread::TBase<Flux::Thread::CApcThread>::InternalThreadProc(void*) + 41
5 libSystem.B.dylib 0x917ecc55 _pthread_start + 321
6 libSystem.B.dylib 0x917ecb12 thread_start + 34

and a wack more!


greetings
.t

[bennals]

Hi, was wondering if there is any mac caperbilities for synching with Reason yet, like the PC version does most excellently..

I've never tried Reaper on a PC but I had a session running with Reason rewired and working well the other night. At first glance it seems to be a more cumbersome method of setting it up than my experience with DP. In that app you just have all the rewire outputs available like a physical input on your interface and the different Reason devices show up as midi output destinations on MIDI tracks. Very straightforward.

In Reaper you have to set up a track to operate as a conduit for both midi and audio. Then you set up more tracks to accept audio coming from Reason, and more again to send MIDI to Reason and all of it gets routed through that original conduit track. Now I think about it, it's really just setting up the conduit track which is unnecessary in DP. Perhaps I'll find some advantages in the Reaper method as I get more experience with it.

It'd be nice if you could have MIDI for a particular Reason device sent from the same track that accepts the audio output of that device, like it happens with VST and AU instruments.

Perhaps to come Justin?

Bill.

[MarkFrancombe]

In Reaper you have to set up a track to operate as a conduit for both midi and audio. Then you set up more tracks to accept audio coming from Reason, and more again to send MIDI to Reason and all of it gets routed through that original conduit track.

Bill.

WAIT A GODDARNED MINUTE!!... Whta are you doing here.. you confabulated me... Now I am a long time Reaper user on the PC, but having switched to Mac have only just tried the X Version... but on the PC version, there was simply an effect (Rewire blah di blah) that you added to a track and lo and behold Reason would launch, and synch right to Reaper, with Reasons Stereo out being routed into this track on Reaper. Now.. what was it you did..?

Is this PC method gonna be implemented, or is it already another way that I cant see (am a computer dunderhead)

yours

Mark

[Justin]

WAIT A GODDARNED MINUTE!!... Whta are you doing here.. you confabulated me... Now I am a long time Reaper user on the PC, but having switched to Mac have only just tried the X Version... but on the PC version, there was simply an effect (Rewire blah di blah) that you added to a track and lo and behold Reason would launch, and synch right to Reaper, with Reasons Stereo out being routed into this track on Reaper. Now.. what was it you did..?

Is this PC method gonna be implemented, or is it already another way that I cant see (am a computer dunderhead)

yours

Mark

The same way should work on OS X as on Windows.. for me I see "Rewire: Reason" in my FX list..

[MarkFrancombe]

The same way should work on OS X as on Windows.. for me I see "Rewire: Reason" in my FX list..

Well I checked, double checked, and triple checked... no Rewire:Reason shows up in MY effects list!!!

Great News though! Hope you can figure it out..

[axel_ef]

It works good on my 10.4.9, but with Toontrack EZDrummer (AUi) I have no sound from the drums.

I tested it once more and find that it was only when playing grooves on the toontrack gui. Drag and drop to the track works, the sound is playing now.
But all that works only with the VSTi, loading as AUi crashes Reaper.

[Tom Drinkwater]

hmm, my MIDI dropped data problem went away when i plugged the keyboard in thru an actual MIDI cable rather than the usb connection, however the usb connection worked fine on other hosts

i don't know what to make of that, but at least i have a workaround.

[bennals]

WAIT A GODDARNED MINUTE!!... Whta are you doing here.. you confabulated me... Now I am a long time Reaper user on the PC, but having switched to Mac have only just tried the X Version... but on the PC version, there was simply an effect (Rewire blah di blah) that you added to a track and lo and behold Reason would launch, and synch right to Reaper, with Reasons Stereo out being routed into this track on Reaper. Now.. what was it you did..?


Sorry for the confusion. Yes, you still launch that plugin to set up a connection with Reason. I guess having it all go through one track (the one I called the conduit) in Reaper, then bussing the different outputs from Reason from that one conduit track to wherever you want it to go is different to the way I'm familiar with in DP.

Justin, do I understand it right that you cant instantiate more than one of the Reason:Rewire plugins in a single project?

Bill.

[Justin]

Sorry for the confusion. Yes, you still launch that plugin to set up a connection with Reason. I guess having it all go through one track (the one I called the conduit) in Reaper, then bussing the different outputs from Reason from that one conduit track to wherever you want it to go is different to the way I'm familiar with in DP.

Justin, do I understand it right that you cant instantiate more than one of the Reason:Rewire plugins in a single project?

Bill.

You should be able to instantiate different ReWire applications, but correct you cannot create 2 of one app.

If you want control over more of the I/O, then you can route the outputs to other tracks etc...

[MarkFrancombe]

Sorry for the confusion. Yes, you still launch that plugin to set up a connection with Reason.
Bill.

BUT.. Where IS that plugin... I promise... I just dont see it in my FX list!!! Aint there! Is it a inbuilt bit of Reaper Justin, or could I have neglected to do something else on my system, like a weird Reason installation?

[bennals]

BUT.. Where IS that plugin... I promise... I just dont see it in my FX list!!! Aint there! Is it a inbuilt bit of Reaper Justin, or could I have neglected to do something else on my system, like a weird Reason installation?

Do you see a Rewire subsection between 'Instruments' and 'AU' when you hit the 'Add' button in the FX chain window?

[rcane]

Anyone have the transport disappear when you choose View-Mixer? Not all the time--I'm not seeing a pattern.

If you uncheck View-Transport and then go back in and recheck, it comes back and stays if the mixer's open and you close and open the mixer.

MacBook Pro 2.16gh, 2 gigs Ram, Running 10.4.11

[davidamnesia]

Just setting up a new MBP 2.6ghz 4gb ram, 10.5.3

1) Reaper crash with another app (Traktor) open; launches fine after closing other app. will test more cases.

2) With demo project open, fails to open another .rpp by double-clicking on the second one, but will load from file menu.

[davidamnesia]

Yeah. That's about it. MBP 2.6g 4gb RAM 10.5.3

db: email me at open labs if you want the crash dump.

[MarkFrancombe]

Do you see a Rewire subsection between 'Instruments' and 'AU' when you hit the 'Add' button in the FX chain window?

No I dont.. !!! Is it something I should have installed with Reason?

[bennals]

No I dont.. !!! Is it something I should have installed with Reason?

It's not something you need to install separately from Reason. Try looking in this folder on your hard drive:

Hard drive/Library/Application Support

You should see a folder named 'Propellerhead Software'.

Inside that folder should be another folder named 'Rewire' and in that should be some files called 'Rewire', 'Rewire.bundle' and 'Reason Engine.plugin'.

If you have all those files you should be ok. I'd try a 'Reaper' reinstall if that is the case. If those files aren't there, I'd do a complete reinstall of Reason.

Bill.

[Tallisman]

I encountered a strange issue last night for the first time...
Probably Pilot error, but no matter what I did, the Arrange Window would not allow any other window on top/over it. No other Reaper window (ie. the midi editor would hid behind the arrange window), and no other Leopard window.

Last night's workaround was to send the arrange window to the dock to edit midi notes... or peek at this forum.

Interesting note: When the arrange window was in the dock and I changed screen sets, the arrange would stay in the dock, but restore to the correct position for the active screen-set. that was cool.

.t

[Justin]

Yeah, there's some wonkiness due to the hackery required to make REAPER windows stay above the main REAPER window.. I'll see if I can't improve it..

[Tallisman]

Yeah, there's some wonkiness due to the hackery required to make REAPER windows stay above the main REAPER window.. I'll see if I can't improve it..

you are awesome!
thanks!
.t

[Kainer]

got some weird behavoir of docking battery3. sometimes if it is docked, it appears in all dock-windows and cover the mixer, the midieditor..whatever there is next to the battery3-dock-window.

as I free the pluginwindow from the docker, everything seems normal, but from this time on I can´t change the drumkits in battery3. the scrollmenu doesn´t open anymore.

if there´s time...anyone of your script-professionels should check this. ;)

[turtles]

For those not sure if they want to take a dip with their old macs, I offer my personal experience:

1Ghz, 512mb, G4 powerbook, OSX10.5, firewire to Tascam 1804
Fired up this build of reaper last night, recorded a live session (18 inputs) at 24-bit without a single click or stutter.

With a bit of ingenious routing and sparing use of processor-hungry fx, a perfectly serviceable demo popped out the other end. (Remember, kids, offline track rendering for processor-heavy fx is an easy way of cutting the processor overhead)

Bottom line- don't bin your slower mac; look on it as a blast-proof (and cheaper) multitrack.

[Jeronimo]

For those not sure if they want to take a dip with their old macs, I offer my personal experience:

1Ghz, 512mb, G4 powerbook, OSX10.5, firewire to Tascam 1804
Fired up this build of reaper last night, recorded a live session (18 inputs) at 24-bit without a single click or stutter.

With a bit of ingenious routing and sparing use of processor-hungry fx, a perfectly serviceable demo popped out the other end. (Remember, kids, offline track rendering for processor-heavy fx is an easy way of cutting the processor overhead)

Bottom line- don't bin your slower mac; look on it as a blast-proof (and cheaper) multitrack.

What buffer size did you use?

[Per Lichtman]

While trying to put together an illustrated Reaper OS X installation manual for a friend of mine I ran into some issues. Most notably, I could not finish writing the manual because the system kept crashing.

Problem: The system frequently crashes in conjunction with Reaper. The crashes occur in two types.

Type 1: Reaper runs fine and closes properly. A short while later (usually less than 3-5 minutes) normal system operations (such as web browsing) cause the "gray restart screen" to appear.

Type 2: Running Reaper at the same time as other programs causes the "gray restart screen" to appear. This time the error happens while Reaper is still running. For instance, I have been unable to run "Grab" for very long while running Reaper and ditto for FireFox.

Note: The crashes only happen on boots where Reaper has been run. I've been spending the last couple hours testing reproducibility and have only been able to get crashes on boots where I run Reaper.

System: G5 Dual 2.5 GHz
OS: OS X 10.4.8 and 10.4.10 (different partitions)


Has anybody else encountered similar difficulties? Any idea what might be causing the problem?

I have already tried running Disk Warrior and Disk Utility; flushing the "Reaper" folder in "Applications"; hiding VSTs from Reaper; switching audio interfaces and running on the versions of OS X mentioned above.

[kerryg]

REAPER runs like a top over here.

What audio interface are you using? Have you tried just using internal audio to eliminate the audio drivers as a variable?

[Per Lichtman]

REAPER runs like a top over here.

What audio interface are you using? Have you tried just using internal audio to eliminate the audio drivers as a variable?

Yes, that was one of the first steps I took. Running with built-in audio did not change the results.

[Jeronimo]

The only real recording session I did with Reaper took something like 4 or 5 hours non stop without a glitch.
Also I mixed 2 songs for a friend, took a whole day without a glitch.
Macbook 10.4.8 at the time. I don´t remember Reaper version I was using...

[turtles]

What buffer size did you use?

Whatever Reaper's standard settings are... didn't change anything. Installed the tascam drivers, installed reaper, connected the two together, that was it.
Me Like.

[Jeronimo]

Whatever Reaper's standard settings are... didn't change anything. Installed the tascam drivers, installed reaper, connected the two together, that was it.
Me Like.

If you don´t mind taking a look at it...
I think it´s under preferences/audio

You didn´t do any overdubs right? Just regular live recording?

[turtles]

Reaper's buffer is set at 1200ms, Tascam driver native latency set at 2ms, sampling at 44100. Default disk read and write buffers.

I was just doing a straight multitrack record of a live stage. No overdubs.
Mixing down later, I got 4 EQs, 1 reverb set up as a send, 1 chorus as a single-track insert, and a multiband compressor over the master, before things started getting clicky in the audio playback. I used the bundled VST EQ and the Apple AU reverb and multiband comp. Usual use of level/fx/eq automation in there too.

Admittedly it's not going to cut it for heavy use of convolution reverbs or big chorus fx, but I'd probably process those offline first, I think.

The fact that Reaper can do this in a pre 1.0 build, on fairly aged PPC kit, is not far short of amazing.

[mrelwood]

When trying to render to mp3, I get the error message familiar from the windows side:

"Error: I need lame_enc.dll to encode MP3!"

Now, correct me if I'm wrong, but OS X doesn't use dll files. :)

[HobbyCore]

Excellent work!

[bennals]

Just noticed another quirk with Kjaerhus Audio's MPL-1 Pro SE. The settings don't seem to get saved with the project. Each time you re-open the project the settings revert to the default. It's the only plug I've seen that does it so far but I haven't really been checking that closely.

Also, the free AU transient shaper from Flux 'Bittersweet II' crashes Reaper consistently. It works fine in DP. Audio Damage's 'Reverence' doesn't pass audio either.

Cheers.

Bill.

[Albatorus]

REAPER will Kick steinberg s ass
they recently changed their prices from 899 to 599 e !!! (not dollars)
I think it s not enough
it s pathetic
I m keeping an eyes on reaper on mac AND pc cause I need a sequencer for BOTH platforms
So as soon as the mac osx version is stable and that I can work on pc AND mac I just change sequencer
And if it Worx from an USB key ?? EVEN better
You go to the recording studio or a band s place yopu can work with you own license
THAT is great !!!
No dongle no nothing
I will spread the word around me and BLOG about it I have a 54 000 visits and it s growin and growin
I give you a tip : Howie B produced me one single
:b :D :D

[bennals]

Hello everyone.

I mentioned this before in relation to what seemed to be a quirk running Reaper on a hackintosh but it seems it may not be limited to that.

Using the shift key as a scroll wheel modifier (to go left and right in the conventional manner) doesn't seem to work in conjunction with a USB mouse plugged into my fully legit MacBook either (1.83, 10.4.11). It does work with the trackpad built into the Macbook however. I've tried setting the trackpad to be ignored when a USB mouse is plugged in via System Preferences but it made no difference.

Can someone running Reaper on a Apple desktop machine (without a trackpad) please check whether the shift key works as a modifier for the scroll wheel?

If not, perhaps that could be looked at Justin.

Also, I would love it if using the scroll wheel (or navigating via the keyboard) could be made to operate more smoothly or with a finer degree. Sometimes when zoomed in, scrolling left or right results in such a large jump that I can lose where I am. It also seems that one scroll action down is equivalent to two scroll actions up (they're not symmetrical, if you know what I mean).

Cheers.

Bill.

[Tom Drinkwater]

with the mouse over the middle of the window the scroll wheel changes zoom, alt scroll modifies it to scroll left and right

vertical scroll on the right hand scroll bars appears symmetrical

shift and scroll wheel stops the wheel working

Mac G5 dual 1.8ghz osx 10.4.11

[bennals]

Thanks Tom. That would seem to confirm my findings on the shift key. Clicking on the scroll buttons is symmetrical here as well, but it's the scroll messages sent by the scroll wheel and keyboard command that appear asymmetrical.

Any chance of a look at this one Justin? I use other apps where shift to scroll left and right are used all the time and I'm getting confused when I come back to Reaper.

Cheers.

Bill.

[steveoath]

I shall be a willing tester :-)

[labyrinth]

Latest release (2.4)

DOWNLOAD (http://www.landoleet.org/reaper24_098.dmg)

[bennals]

Yes, I was waiting for this thread to be updated by Justin before mentioning that there seems to be some glitchy graphics happening on the main page (after vertical scrolling) with this build (not present in 2.31 build). But, now that the cats out of the bag...

Bill.

[kerryg]

Or I should say graphics. I get around it by switching to another theme and back, but it's a bit tiresome.

[bennals]

Yes, even calling up the mixer then closing it seems to reset the graphics correctly (I don't have the mixer docked).

[semiquaver]

Using the Plogue Bidule VSTi you get all kinds of wierdness - gui disappears when clicked - can reappear behind and above the fx window - clicking the GUI button in the fx window closes the fx window - bits of the gui can persist when the fx window is closed etc etc.

this is the 2.4 @ LandOLeet G5 os 10.4.9

[labyrinth]

Latest Pre-Release... DOWNLOAD (http://www.landoleet.org/reaper241_098.dmg) (vs. 2.41pre/.98pre)

They're always here http://www.landoleet.org/ the ones with the .dmg not the .exe suffix.

[mio*star]

http://reaper.fm/files/osx_early/reaper2301_098.dmg

Requires OSX 10.4 or 10.5. Intel macs are strongly encouraged but PPC macs should work as well, though slowly.

Post bug reports etc here.

Known plug-in compatability issues:
Addictive Drums demo does weird things if you resize its UI at all
Camel Audio Cameleon5000 fails miserably in VST form.
Probably more, too.


Hi Justin !

Feature-wise, how does the Mac version compare to the Windows one ?
Is the Mac version updated right after the Win one ?

I am really enthusiastic about Reaper (using Bootcamp) and wish it could be full-blown on my Mac !!

thanx and congrats for your GREAT job !

mio*

[bennals]

Latest Pre-Release... DOWNLOAD (http://www.landoleet.org/reaper241_098.dmg) (vs. 2.41pre/.98pre)

Glitchy graphics on the main arrange page are still there, just like the previous build.

I'd really love to get Command-W for closing windows back. It works on a few (fx window for example) but midi editor and i/o windows can only be closed with the red button. Still, I'm finding the 2.031/.98 build extremely robust. Not a crash in ages.

Bill.

[semiquaver]

use escape to close fx and i/o windows !

[bennals]

use escape to close fx and i/o windows !

Aha! Thanks semiquaver. Unconventional for a Mac, but it'll do.

Cheers.

Bill.

[audioguy_on_ca]

Reaper's buffer is set at 1200ms, Tascam driver native latency set at 2ms, sampling at 44100. Default disk read and write buffers.

I was just doing a straight multitrack record of a live stage. No overdubs.
Mixing down later, I got 4 EQs, 1 reverb set up as a send, 1 chorus as a single-track insert, and a multiband compressor over the master, before things started getting clicky in the audio playback. I used the bundled VST EQ and the Apple AU reverb and multiband comp. Usual use of level/fx/eq automation in there too.

Admittedly it's not going to cut it for heavy use of convolution reverbs or big chorus fx, but I'd probably process those offline first, I think.

The fact that Reaper can do this in a pre 1.0 build, on fairly aged PPC kit, is not far short of amazing.

Then there's hope for me and my 1.67 G4 PB w/ 2GB to get 24 tracks in a similar situation. I just have to upgrade from Panther now, which has been in the cards for a while...
Thanks turtle and justin!