Jump to content

Promidi

Members
  • Posts

    3,006
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by Promidi

  1. 9 minutes ago, Greg said:

    Still is painfully slow to launch.  Not sure why it takes 3-4 minutes to launch. 

    7.5 seconds from shortcut click to product list appearing here (PC config as per sig). 

    NA 3.90

  2. Interlock?  Wasn't this a precursor to iLok?  I have never seen CbB needing any form of iLok or Interlock.

    Check in Control Panel,  "Programs and Features" (Start + run appwiz.cpl ) to see if you have any old plugin installed.  There must be something on your PC causing this that is outside of CbB’s control.

    Note: Windows 10 has a known incompatibility issue with really older iLok drivers.  They causes a blue screen (even in Windows safe mode.  Some older SONiVOX plugins were known to cause this. The only way out of that one (short of a full Windows clean install) is to boot from a CD Windows repair software and change “TKPD.sys” driver from “boot” to “disabled”. 

  3. Another thought I had is that a higher tier of Cakewalk might actually include Roland Canvas VA. 

    Of course, there would have to be some negotiations with Roland to allow this, and what the licence fee from each sale of Cakewalk Sonar to Roland would be.

  4. What audio interface are you using? 

    If you are using on board sound with ASIO4ALL, please do yourself a favour and get an audio interface that comes with native ASIO drivers.

    BTW rename your AUD.INI file rather than delete it.

    This file is found in the following folder:

    %appdata%\Cakewalk\Cakewalk Core

    • Great Idea 1
  5. What I would do is create a RechannelMIDI=1 entry under the [WinCake] section in the Cakewalk.ini file

    Then after you have opened the MIDI file in CbB, select all, then bounce tracks.  This combines all the MIDI clips on each given track to one clip per track.

    This will also rechannel all the MIDI events to match the MIDI channel if the MIDI tracks that those events are on.  The MIDI tracks will retain their track separation.

    Don’t use Omni. Make sure your MIDI tracks are set to specific channels.

  6. On 2/24/2024 at 4:12 AM, dsurkin said:

    Please forgive me if this is the wrong place for this question. Product Center 051 shows that I do not have Melodyne Essential 1.0.0.7 installed. However, over the years I've updated Melodyne to Essential version 5. If I select download on the Cakewalk Product Center, is this going to install an earlier version of Melodyne? Or is version 1.0.0.7 later than Essential version 5?

    If you have Melodyne 5 installed, then you would (should) have updated from Celemony themselves.

    I have Melodyne Studio 5.3.1.018 and this is the latest version.  I intend to ignore the version from Cakewalk Product Centre.

    Melodyne updates are done from the Melodyne GUI itself and are handled by Celemony..

    The Cakewalk Product Centre version would be for those who do not have any version of Melodyne installed and want to run the trial.

    • Like 1
    • Thanks 1
  7. 3 hours ago, Ronny.G said:

    Are you sure? For what I can see the sysxs  can already be sent to a VSTis if the output is a VSTi.

    Actually, come to think of it, I think you’re right.  If one has VSTis in a project, then those ports become available as destinations for Sysex banks in Sysex View.

    Unfortunately, The only VSTis that states it can receive Sysex data that I have is ShowMIDI.  This is a handy utility that can show MIDI data streams, including sysex.  I tried sending sysex data to ShowMIDI, using Banks. and this did not show any sysex as being received.

    Of course, Raw sysex Data events (not banks) will be sent to the first available port, which for many, will be a hardware port.

    Cakewalk probably needs a better way to handle Sysex data to VSTi, rather than using port numbers (which can change, depending on the number of VSTis in a project)

    But was are digressing, this topic is TTS end of life

  8. 7 minutes ago, Ronny.G said:

    The problem is with the auto sysx. Now when you open a midi file that have these data they are auto sended to TTS-1. But in future this could be a problem. You will have to "manual" send these auto sysx after you have open the midi and assigned its tracks to the sound canvas plugin. This is the point in where you sought the old TTS-1 where you don't have to worry about this passage.

    What we also need is the ability for Cakewalk to send Sysex data to VSTis.  Currently, Sysex can only be sent to physical hardware ports. Personally,  I use a lot of sysex for the SW1000XG (My clients to require this).

    For Roland GM/GS sound modules to be properly and more fully emulated, Sysex needs to be part of the equation (with Roland or Yamaha). This is because Sysex tends to be where most of the cool stuff happens.

    • Like 1
  9. 3 hours ago, T Boog said:

    Thanks. Forgive my ignorance but what is the advantage(s) to downloading the entire installer? And does it matter which download I choose as far as the TTS-1 goes?

    If you need to do a fresh install without the Cakewalk Product Centre.   Mind you the Cakewalk Product Centre will do the install for you  - that would probably be easier.

  10. 6 hours ago, T Boog said:

    I only have CbB. I havent done the new update yet. When I do, will I lose access to the TTS-1? (I have current projects that use the "piano 1" in the TTS-1). Thanks!

    If you have a fully functional TTS-1, then CbB 2024.02 build 98 will pick this up and be able to use is (I have tested this). 

    If you do a fresh install of CbB 2024.02 build 98, then you need to first install the latest version of Cakewalk you had that came with TTS-1

    I am fairly confident that the new Sonar Paid will also pick up any previous working version of TTS-1.  I suspect a fresh of install of the new Sonar Paid will also require that you first install the latest version of Cakewalk you had that came with TTS-1.

  11. 5 minutes ago, John Vere said:

    I just saw this posted in the announcement regarding the last release. 
    Quote: 

    “The TTS-1 synth is no longer installed by Cakewalk, by request from Roland. This product is no longer supported and has reached end of life. Older installed versions may continue to work but it is no longer a default for insert instrument.”

    Unquote 
     

    But I would imagine we will still have access to it if it was already installed.
    I guess it will not be installed with upcoming Sonar. 
    I wonder if  Sonar will include the same Generic boring instruments as Cakewalk Next? 
    I noticed in Next that GM midi files open with very few appropriate instruments assigned to the tracks. I think there’s only a few common instruments. 
    So GM midi files will end up with a lot of piano substitutes as tracks instead of wind instruments and what not. 

    I can see Roland requested the removal of the TTS-1 as they  are one of the few developers that make a GM player still. 

    We will all be fine until down the road when you rebuild a new system then you will be faced with life with out a free GM player. 


    If you had TTS-1 installed and you wish to do a fresh install, you should just need to install your previous version of Cakewalk, then install the latest Cakewalk By Bandlab.

    I am fairly confident that the New Sonar will also pick up a previously installed version of TTS-1.

    But, I share your concerns.   Queue the posts , “all my imported MIDI files won’t play”.

    Maybe Roland wants to steer users to their paid Roland Canvas VA (which, currently, costs $US69).

    Note: I use an external Yamaha SW1000XG card for this, which can emulate Roland GM/GS.  This is basically a Yamaha MU100 on a card.

  12. 3 hours ago, Ephraim Isaac said:

    I made this post a while back about CakeWalk crashing when using 2 specific vst's in a project.
    Using the Poise & UVI workstation vst crashes CakeWalk..Help!

    Will this be resolved in CakeWalk Sonar?
    Or maybe still with Bandlabs CakeWalk?

    Brutally honest answer, I highly doubt it.

    With Sonar, they will simply tell you to contact the makers of Poise as this is an issue with their plugin, not Cakewalk

    With CbB, definitely not - development as pretty much ceased.

    As good as Poise might be, I would simply give it the flick and find something more reliable.

  13. 6 minutes ago, T Boog said:

    Wow man, I didnt know that. Let me ask u this, All this time Ive been trying the universal control with my friend's audiobox iTwo. The new iTwo came in today at my daughter's house but I figured it'd be the same thing. Is there a chance that having the registered driver could make a diff?

    I am not sure if the driver for the iTwo is native ASIO or just an ASIO4ALL variant.

    The way to test is this.  

    In Cakewalk, select the iTwo’s driver mode in Cakewalk’s audio Preferences.  Play a project in Cakewalk. 

    While that project is playing, adjust the Windows volume using the volume control in the Windows taskbar.

    If the volume does NOT change, then you are using a native ASIO driver.  That is because true ASIO bypasses much of the Windows audio subsystem (including Windows level controls).   Think of true ASIO as a Batphone to your your audio interface. 

    • Like 1
  14. 8 minutes ago, T Boog said:

    Well I looked at the 2i2 first but it has no midi. I gotta have midi.

    Then the Focusrite 4i4. - that has MIDI ports.

    I believe that the majority of your issues will evaporate if your get an audio interface that comes with native ASIO drivers, and that had 5 pin MIDI ports.

    15 minutes ago, T Boog said:

    Oh, about my last question... Is there anything special I need to do to switch over besides following the uninstall directions?

    Make sure you select the right device in Preferences - Audio - Devices

    I believe when you select the umc204 in CbB, you might get a message, Asio4all  “is known to be incompatible with Cakewalk”

    If you do stay with the umc204, then consider using WASAPI driver mode. 

    Most folks on here will stay away from anything to do with ASIO4ALL. 

    • Like 1
  15. 13 minutes ago, T Boog said:

    Btw, I took ur advice and also ordered a diff brand interface. The Behringer umc204. All reviews said the preamps are low noise and John mentioned it uses asio4all. Im hoping that helps.

    Personally I would have got a Focusrite 2i2 as it comes with true ASIO drivers.  ASIO4ALL are not true ASIO drivers but are only a wrapper.

    Is it too late to cancel the order?

    • Like 1
  16. 23 minutes ago, T Boog said:

    Thanks a lot guys. Well I may have found a problem. When following the Audiobox uninstall directions, under "program files" > "Universal Control" file, there's both old and new presonus & Univ-Control files that wont let me delete them. When I try to delete them it says... "File in use, The action can't be completed because the file is open in Universal Control, close the file and try again".

     Could someone please tell me how to do this? How do I close the file yet delete what's inside of it?

     

    Looks like the Universal Control is still running . 

    Personally, I would not be deleting files in c:\program files.

    What I would do go Start run > "appwiz.cpl" and see if there is an older version there that you can remove

    I am assuming that you have headed to the manufacturer's website and downloaded the latest drivers already so that you can reinstall them.

    • Like 1
×
×
  • Create New...