Jump to content

Tez

Members
  • Posts

    214
  • Joined

  • Last visited

Posts posted by Tez

  1. When you bounce to track what wav files are produced in addition to the typically named "bounce file" and for the bounced file exactly what is its format as seems like its a wrapper for a dated wav file and if possible please explain this! Thank you verrry much 😁...

  2. 1. I bounced to tracks on a project I closed the project and did not save, in the Audio folder the bounced tracks disappeared but there were some additional wav files that get produced that don't get deleted, the same thing happens if the bounced track gets deleted  and the project gets saved. These files have to then be manually deleted.

    2.  Shifting to another workspace and then trying to shift back to  basic CS becomes unresponsive and has to be canceled.

  3. I had a problem with iZotope  plugins including Ozone all of which were  OS authorized not iLok, that only got resolved when I installed iLok in order to establish the service running in background,  since despite  local authorization iZotope 1st  checks for the iLok service & with no iLok  it's a problem .  This may not be relevant to your issue but I thought it was worth a mention 🥴 ...

    • Like 1
  4. Same here for CbB guess it's a server error a 502 bad gateway... For the latest  CbB and I guess the the Nu Sonar they started using new servers,  and I believe  the endless activation-reactivation  issues  folks have been having,  in my case daily,  might be due to these servers. With any luck maybe they're fixing it!!

    UPDATE:

    Should be working now...  Yippee yo ki yay !

    • Like 1
  5. On 4/27/2024 at 10:50 AM, steve@baselines.com said:

    Every once in a while I get that ugly red 'activation needed' box pop up when opening Cakewalk.  I think it is in error as I seem to be up to date and already activated.  Have you had this problem, or is it a valid activation needed notice?  

    Thanks

    Every day  after booting up windows, the 1st CbB launch  gives me the RED Popup,  I immediately  shutdown CbB and relaunch and Voilà it's activated!!  Noel Borthwick claims it not an error, but a failure to complete a browser handshake ergo a local system problem!   Well, a load of us seem to run into this and it wasn't  happening to versions prior to the final versions, So, go figure ?...

    • Like 1
    • Sad 1
  6. 18 hours ago, Noel Borthwick said:

    Sign in is complex because it relies on the browser handshake.

    Thanks Noel,  but I'm not sure I understand what the "the browser handshake"  is? Something internal to CbB or is it related to the default system browser in my case Firefox as CbB shows I'm signed it? Thanks again ?...  

    UPDATE:

    I signed in to Bandlab using Firefox (my default system browser) and stayed signed in. Rebooted my system,  performed sundry activities, following which I launched CbB and had no activation issues, or related activation notifications.  Hopefully, in my case, this fixed the issue, we'll see going forward ? 

    UPDATE2:

    Well,  the above was short lived and it's back to the the activation issue  today (3/14/2024)... Ho hum ☹️.

  7. 22 hours ago, Noel Borthwick said:

    Logging in to bandlab.com is irrelevant. You have to sign in from within CbB. When the Web browser opens sign in there with your bandlab credentials. That's all there is to it.

    If it fails then something on the system is blocking it. You can attempt offline with using a different PC if so.

    I documented my experience, others have a similar issue and for me this did not occur to CbB versions prior to "2023.09". The question is how to track this down if it only occurs to some of us,  A windows task manager dump may not capture what's initially blocking  the handshake  which for me subsequently disappears on a relaunch with a now activated notice, incidentally when the Bandlab membership promo notice popped up there was no following activation issues and clicking check for updates shows the CbB version is up to date. Any suggestions?

  8. 4 hours ago, Promidi said:

    Here is what I would try.

    This is very thorough, and thank you BUT... The link I posted above refers to "2023.09" but it's equally applicable to "2024.02 Build 98"  and for my system none of your suggestions are necessary as all I have to do  when the toast pops up that says it is "Not Activated”  is close CbB and relaunch and viola it gets activated. I don't know if the OP can do this? I thought it might be the AV and excluded the "Cakewalk.exe" from real time scanning to no effect & I have no blocked connections!  This did not occur to CbB versions prior to "2023.09"!  It appears that I'm not unique so it seems that maybe, just maybe it's condition caused by these final versions released after "2022.11", at least, for some of us. It's a largely a worrying annoyance, but I wish support would look into it ?... 

  9. 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
  10. @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
  11. 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?  

  12. 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??

  13. 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
×
×
  • Create New...