Jump to content

gmp

Members
  • Content Count

    114
  • Joined

  • Last visited

Community Reputation

31 Excellent

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. You say "if I delete some of the instruments". Do you mean you delete all the soft synths or some? Or delete other TS-1's? What exactly are you deleting?
  2. Hey abacab thanks for the old Cakewalk account link. I assumed after 2 years of CbB, it would not work anymore. I know Noel said we'd have access to that for a while but couldn't say how long. I hope it's permanent. Although it's doubtful I'd need it since I have downloaded the files on a regular basis over the years and still have all my CD's and DVD's, since 1992. It's still very good for all the users in case they need something. With my initial problems with TTS-1, I was wondering if I needed to download something, but I've got it working fine now. My suspicion is since the crash was happening as soon as you'd hit a midi note on your keyboard that it had something to do with the settings on the midi track, most likely the midi input.
  3. Thanks for the detailed post. I checked plugin manager to see what DLL I was using and the only one that's in the 64 bit shared DXi folder is the latest one 2018 like you have. I then loaded the default normal template from 2017 and TTS-1 works fine with that. Then I tried again the song I wanted the TTS-1 on and this time it worked - no crash. This is surprising after 2 crashes in a row and all the other posts of the same crash problem. So it appears there's something a little quirky about this plugin. For my future reference I documented the steps I took to get it to work. Possibly this will help someone else in the future. Some of this is unique to my setup like the MOTU midi interface and the Ivory output OPEN TTS-1 IN SYNTH RACK CHOOSE DEFAULTS GO TO AUDIO TRACK AND CHOOSE IVORY OUTPUT GO TO MIDI TRACK AND CHOOSE MOTU MIDI AND CHANNEL - 1-TTS 1 OPEN TTS-1 WINDOW CHOOSE PRESET PUT ACTIVE TRACK ON MIDI TRACK - PLAY So Craig Anderton, I don't need the DX wrapper. maybe it's already being used by CbB. I've rarely used this plugin, but after that endorsement by Craig, I'll definitely check it out more.
  4. I'm not sure what you mean by "only send it through one or two audio FX plug-ins and one or two spectrum analysis plug-ins" What I've tried is to open the Synth rack and hit the + button and add the TTS-1. I can then change the preset, but as soon as I hit a note on my keyboard it crashes. Others have reported the exact same thing in this thread with no solution. If you can outline what steps you take to make this work I'd appreciate it
  5. Craig, after looking at this long thread, it seems you are the only one who has a solution and are successfully using it with CbB. Can you tell us how to use the DX wrapper so we can use the TTS-1? I have a project that needs Steel Drums and after opening TTS-1 several times and choosing the Steel Drums and then having it instantly crash when I hit a midi note on my keyboard. I went ahead and tried the last Sonar Platinum and it works fine there and actually is an excellent Steel Drum sound. I have almost every version of CbB and tried this on the very first one April 2018 and got the same crash. I do have the 64 bit and 32 bit versions installed, so I'd love to try the DX wrapper, so I can use it. Please help.
  6. This bug has been going on since the first CbB version. All Sonar Platinum versions worked correctly without this bug. I have always had Splat and CbB open with my custom template. In the past I could just start working on the new song after opening Splat. And then save the song specifying the CWP folder and the audio folder. Since I record tons of songs, I prefer to keep all my CWP files together in 1 folder on my E drive and each one has it's own wav file folder stored on my D drive. This works fine when choosing File/New, but doesn't work when I open CbB to my template and hit save as. I tried in vain to get this fixed using email support. I wish we'd hear from Cakewalk about this long standing issue.
  7. Thanks for putting some light back on this issue. I'm not sure if Noel or any of the other main guys are even aware of this. Email support was worthless on this issue
  8. T his all makes sense now, except I'm still curious how older Platinum versions can work without Launchpad. Do they use W130auto.dll? I also have Sonar 8.5, is hta tok too?
  9. I understand why I should use Launchpad with 2019.09 and any later versions, because of CW130auto.dll. And I see only 2 CW130auto.dll in the "sub" folder. So how is Launchpad handling 2019.07 and all earlier versions of CbB? It seems like it would need all those versions of CW130auto.dll in the sub folder also.
  10. So just for clarity. From now on I can use the desktop icons and not Launchpad for opening all old Platinum and all CbB from 2019.07 and earlier. For all CbB from 2019.09 I should use Launchpad to open them. And before installing each new CbB version I should use "quick copy" to save the current version and then install the newest version. Is this all correct?
  11. I copied it and now CbB 2019-09 works in Launchpad - thanks for the great tip. So currently that's the only file change? Yet there may be other different file changes in the future?
  12. I found cw130Auto.dll dated 10/11/19 on my backup HD. It resides in C:\Program Files\Cakewalk\Shared Utilities. Is that the only file that causes the problem? If so I'd assume I can temporarily move the current cw130Auto.dll to a temp folder and then move the 10/11/19 cw130Auto.dll in it's place in that folder and then 2019.09 would run just fine. Right?
  13. Very impressive work on Launchpad, Steve. I'm sure in your situation in this Forum you find the multiple features very helpful. IN my situation I would assume I can just use the very basic features. I quite often need to open 32 bit Platinum 2016.08 to revisit old projects that use 32 bit plugins that won't load in 64 bit CbB. As far me opening older versions of CbB, I only do that if I have a problem with the current version and suspect a bug, like I did in the post your responded to. So in moving forward I'm wondering what my best approach is. Should I always open 32 bit Platinum from within Launchpad? AS you suggested I checked "Restore CW130auto.dll on exit". If I didn't open it within Launchpad, what kind of problems would I run into? Maybe not being able to load a plugin because of changes in the Shared Plugins folder? When I installed 2019.11 Friday night, I wasn't aware of Launchpad or any of this, but I do still have the Shared Plugins folder intact from before Friday's install. Should I save that permanently? I tried opening 2019.09 from Launchpad and got the error message "no usable CW130auto.dll for this version. Or since this is so new should I not worry about 2019.09 and just open it using my desktop icon? Next time I update to a new CbB, I'll use "quick copy" to make a copy of the Cakewalk Core folder and then proceed with the new update. And when I want to open a CbB that is later 2019.11, I assume I need to do it from Launchpad. Whereas any version from 2019.07 and earlier I can just click on my desktop shortcut and not worry with Launchpad. Is that right? For Launchpad to work in my situation with future CbB updates, is this all I need to do?
  14. scook, you said "If you start using Launchpad to save versions, it should always be used to run CbB. This way the version is set up properly." Once I set it up can I double click a CWP file to open CbB like I currently do? Or can I double click a desktop icon and open CbB to my template?
×
×
  • Create New...