Jump to content

Tez

Members
  • Posts

    224
  • Joined

  • Last visited

Posts posted by Tez

  1. With the CbB current 2023.09 installed many times it is launched for the 1st time after booting up Windows it pops up a toast that says it is "Not Activated” contrary to which I believe it should be, I then have to immediately shut CbB down & relaunch, which then pops up the activated notice and is good for the rest of the windows session...

    The “Not Activated" toast doesn't occur on every reboot, but despite that, on a subsequent launch of CbB I'll see on occasion the now activated notice even though I was fully able to save projects?

     On 10/3/2023 at 1:15 PM, Noel Borthwick said: “Pretty unlikely. Once the app is activated it doesn't retry until the lease expires which is quite long. Check whether you have some backup script or something that is restoring some state when you reboot. If so, that might explain why Cakewalk is not activated again after a boot.”

    I don't have a backup script I'm aware of, or know what could restore state on a reboot? If either existed, wouldn't it have affected the previous version?  

    The odd thing is when the toast popped up that says it is "Not Activated” I checked Help, and it shows that I'm signed into BandLab so I'm at a loss as to what's going on. 

    It doesn't stop me from using CbB, but it is a bit annoying, and I hope nothing is else out of whack...

    If it's not a bug,  any suggestions as to what’s going on would be helpful, thanks

    • Thanks 1
  2. @msmcleod  Thanks, that totally makes sense, explains why inserting 1st worked for me ? Since I use it as a substitute for the GS Wavetable percussion, last night I found an alternative,  SF2s found at this link:  https://musical-artifacts.com/artifacts/1549 and used "sfZed09" sfz format editor at this link: http://steveholt.drealm.info/sfZed.html, to convert the SF2 percussion to an SFZ then loaded it into Rapture Pro, which eliminates TTS-1 issues & my ol' SF player's not reliable, All the other instruments are there in the SF2 and can be extracted as individual SFZ's!  I'm sure a lot of folks here are already familiar with this, but thought I'd list the info just in case it helps someone... 

    • Like 1
    • Great Idea 1
  3. I'm not using TTS-1 from scratch mainly if importing or opening some midi that uses the Microsoft GS Wavetable percussion, which once known can get substituted, and also it shows somewhat the original intent;  non-percussion instruments  just get substituted.  TTS-1's a geriatric DXi & I looked for an alternative,  didn't see anything appealing, any suggestions?  

  4. I have a template with 1 instrument all outputs mono, and a slew of aux tracks & FXs, using optional sends for FX signal paths & various configurations for 5.1 hard out targets, and NO busses...

    After adding TTS-1 (1st Stereo out) set to channel 10 for percussion, on playing any TTS-1 note CB crashes with no dump.

    If first, I delete the 1 instrument, then add the TTS-1 as before followed by adding back the 1 instrument configured as before deletion, it all works as expected, no crash, and a template created from this working configuration also has no problems...

    Also starting with a blank project adding the 1 instrument first followed by theTTS-1, both defaulting to a hard out, again no problems...

    Any reason for the crash??

  5. What I do to set a section of a midi to a different tempo from the rest of the project is to use the Tempo track mark the midi section start and end set the the temp at the start and set the project tempo at the end. After that, go to the now time and position to the end marker copy the time (I use H.M.S.F format), then delete the tempo changes in the tempo track. After that, select the marked section of the MIDI track then select "Process>Fit to Time..."  from the control bar menu select Event time option, paste the copied time in the "New Thru" box & press OK... Voila, the clip is set to the desired tempo differing from the project tempo...

    Hope this helps...

    • Like 1
  6. UPDATE: The crash as described below only seems to occur for "Paste Special" and "Paste into Existing Clips" is selected and the now time cursor is outside of any clip in a blank portion of the track. Further, this can also, if not  consistently, cause the crash if the paste is made in the same project as the copy, and once again this does not occur with version 2021.11 (build 18, 64 bit).  I believe this is bug...

     

    This is a consistent CbB Crash after installing 2021.12 where a copy from one project followed by a paste into a second project results in the W10 active spinning blue wheel followed by an immediate closure of CbB, without a crash dialogue or a mini-dump. This can occur on a copy/paste as follows:

    1. Both the 1st project (source) opened in CbB and the 2nd project (target) opened in CbB.

    2. The 1st project (source) opened in CbB and the copy performed and closed within CbB, followed by the 2nd project (target) opened and the paste performed.

    The test projects used each consisted of only a single Midi track and no buses, and a single Midi clip was copied.

    After both scenarios CbB crashes following the paste and in both cases the Fault offset is the same where a typical “Error Event” is shown below. This should hopefully help resolve this issue.

    Last, I confirmed this does not occur with version 2021.11 (build 18, 64 bit), using the same projects tested in the above scenarios...

    Error Event:

    Faulting application name: Cakewalk.exe, version: 27.12.0.102, time stamp: 0x61bb7276

    Faulting module name: Cakewalk.exe, version: 27.12.0.102, time stamp: 0x61bb7276

    Exception code: 0xc0000005

    Fault offset: 0x0000000000de512e

    Faulting process id: 0x6ccc

    Faulting application start time: 0x01d7faa3817a46ed

    Faulting application path: C:\Program Files\Cakewalk\Cakewalk Core\Cakewalk.exe

    Faulting module path: C:\Program Files\Cakewalk\Cakewalk Core\Cakewalk.exe

    Report Id: ec43dc72-d8c5-4e7e-a60f-6c125533d500

    Faulting package full name:

    Faulting package-relative application ID:

  7. 1 hour ago, Will_Kaydo said:

    Again: you're confused by this.

    I am not confused, maybe I wasn't clear enough for you, as I said  before I set the plugin (TTS-1) to “Upsample on Render” which only works if the global "Plug-in Upsampling" is enabled, I thought it was clear that on the render that's what I did, enabled the global "Plug-in Upsampling". Ergo the sample rate was doubled for the TTS-1 on rendering  to a value of 88.2kHz, since the projects sample rate is 44.1KHz. I know how to use plugin upsampling, and as I said before at the doubled rate the TTS-1 worked fine, on render and  also playback if set to “Upsample on Playback” with "Plug-in Upsampling" enabled .  You can easily verify this with a 44.1KHz test project...

  8. 10 hours ago, Will_Kaydo said:

    There is a difference between upsampling and project sample rate

    Thanks for your extensive reply, but the point I was trying to make, if I understood correctly what CbB does for a plugin when set to “Upsample on Render” , namely lets you specify whether a VST or DirectX plug-in effect or instrument should be resampled at 2x the project sample rate when bouncing, which is exactly what I did for the TTS-1 in a project with 44.1KHz sample rate which implies for the render it was sampled at 88.2kHz sample rate and Mr Anderton said the TTS-1 won’t function at function at that rate, the purpose of doubling the sample rate is because "some plug-ins can produce unwanted artifacts when running at lower sample rates". What CbB does to achieve the higher rate weather it's to increase buffer sizes or "inserting zero-valued samples between original samples" I wouldn't know. Regardless of the mechanism the rate was doubled to a value of 88.2kHz and the TTS-1 worked just fine in this context.

  9. @Craig Anderton I read in your article on the TTS-1 synth, that it won’t function at function at 88.2kHz sample rates. I created a 44.1KHz project from a multi-track Midi file for the Microsoft GS Wavetable Synth, where I used all the non-percussion MIDI tracks in equivalent VSTis, but the percussion was simple enough to use the TTS-1s channel 10. I set all VSTs, VSTis and the TTS-1 in the project to “Upsample on Render” and bounced 2X to a track and the percussion came out fine, which implies that 88.2kHz sample rate works for the TTS-1 or CbB ignores upsampling for the TTS-1. So, I’m a tad confused. Would you kindly explain if I’ve got it wrong?  Thanks...

  10. Upsample On Render

    Setting a VSTi to Upsample On Render for better performance and the FX plugins used, I found these issues using Fast Bounce. With the VSTi and 1 FX plugin set, the render proceeded at the pace of geologic time and hence canceled the render, with more than 1 FX plugin set CbB crashed without a dump. Is this a bug? I found nothing in the documentation prohibiting Fast Bounce for Upsampling... Not using Fast Bounce works fine!

    PRV copy/paste

    Under Editing, “Use Paste Special Options on Paste” and Under Paste Special “Paste into Existing Clips” are both selected, but in a MIDI clip in the PRV, when a copy of a note sequence from one part of clip  is then pasted into different location using Ctrl + V,  it’s pasted as new clip the length of which is equal to the start of the sequence being copied to the end of the original clip. This forces the use of Paste Special to paste into the existing clip, is this a bug?

  11. 33 minutes ago, John Vere said:

    Under many set ups your whole VST instrument world will be a mess

    Agreed, if you don't know exactly what your doing, e.g. any midi tracks associated with a shifted synth have to have their outputs reassigned to the new position, similarly if it's a percussion midi track using a drum map, the map assignments have to be reassigned to reflect the position change. Regardless, shifting synths in the rack ain't something I'm inclined to do anyway, and if I really wanted too it would be done carefully...

  12. 10 hours ago, scook said:

    Launchpad

    Thanks again, I am aware of Launchpad, and appreciate your generosity in providing useful tools, it was the compatibility check that was a news update that I'm glad to know, and in general I've never rolled back, my interest is a comparison between current and previous for some feature at best, if at all ?

  13. 4 hours ago, scook said:

    Now, there is a check in place to prevent the program from running if it detects this condition.

    That's good to know, thank you, and I assume for automation you're referring to CW130Auto.dll, and of the 4 dlls that have gotten updated this release, that CW130auto is the pertinent dll as I think Splat also uses 3 of the updated dlls plus CW120Auto.dll.  The others in shared utilities appear to be no later than 2019.  So, going forward keeping a copy of the current CW130auto  along with the "Cakewalk Core" might be an idea if desperate to run a prior version of CbB, unless the compatibility check some how prevents it? 

  14. On 6/11/2021 at 1:33 PM, scook said:

    AFAIK, there is no way to have more than one completely operational version of the DAW installed at a time.

    This has to be so, because I assume by that, changes can occur to folders other than "Cakewalk Core" but FWIW I keep all versions of the "Core" backed up and I was able to run "Cakewalk.exe - 2021.01 bld 098 (Update 1)"  from a renamed "Core" folder,  and this version has the prior tempo features operable, maybe that's all  Sam Stalos requires?

    This time running a prior version to the latest currently installed, I saw that there was no notice that a newer version was available, and following that on a startup of the current CbB there was a refreshing activation notice?

×
×
  • Create New...