2015/07/09 17:43:56
Jon Sasor [Cakewalk]
With the 2.0.2 update the logging location has changed to be within Cakewalk Content\Rapture Pro\Logs. This allows RP to write the log file to any customized Cakewalk Content location.
2015/07/09 17:50:22
Doktor Avalanche
Jon Sasor [Cakewalk]
With the 2.0.2 update the logging location has changed to be within Cakewalk Content\Rapture Pro\Logs. This allows RP to write the log file to any customized Cakewalk Content location.



OK that's cool, can that be added to release notes?
I'll edit my post :).
Any other responses?
 
Thanks...
 
2015/07/09 18:02:18
BobF
Hey Jon - Tell the team "Good Release" & "Thanks"
 
I got RP updated (no CCC) with no problems and have been running it thru its paces.  Useability is up a bazillion percent or so; snappy load, quick single-click program changes, etc.
 
I don't expect their work to ever be completely finished, but they have advanced in a big way with this release.
 
Tell 'em Noel owes them cocktails -
2015/07/09 18:30:41
dmbaer

Compatibility Improvements

  1. Fully compatible with all hosts, especially Cubase 8, Studio One 3, Ableton Live 9, FL Studio, Plogue Bidule, Bitwig Studio and Reaper 4
Sadly not so.  Keyboard tracking still does not work in Cubase 7.5 (or maybe 8 - I forgot which one I just tested with).  This bug was reported approx. four weeks ago.
2015/07/09 18:31:32
critter0107
Very good.  This update solves my Galbanum Pisces issue.  Thank you!
2015/07/09 18:51:08
Doktor Avalanche
dmbaer

Compatibility Improvements

  1. Fully compatible with all hosts, especially Cubase 8, Studio One 3, Ableton Live 9, FL Studio, Plogue Bidule, Bitwig Studio and Reaper 4
Sadly not so.  Keyboard tracking still does not work in Cubase 7.5 (or maybe 8 - I forgot which one I just tested with).  This bug was reported approx. four weeks ago.




Confirm RP states 2.00.2.541. Thanks.
2015/07/09 20:01:10
Lynn
This works for me.  I've been using it all day and have found no glitches, yet.  Way to go CW!
2015/07/09 23:19:07
Kamikaze
Stand alone still not fixed for Roland Soundcard users. Is this on the agenda, or is the finger pointed at Roland?
2015/07/09 23:21:25
Doktor Avalanche
Kamikaze
Stand alone still not fixed for Roland Soundcard users. Is this on the agenda, or is the finger pointed at Roland?


I can't see how RP code could effect a specific audio interface. Is there a thread you can point to with the full details?
2015/07/09 23:23:30
jih64
Sadly too late . . . 2 months too late :(
© 2024 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account