Jump to content

2019.07 Feedback


Jesse Jost

Recommended Posts

One small bug observed on my windows 10 1803 machine:

After the existing project is loaded, transport section in the control bar is not properly rendered until I select any track.

Other than that:

Really glad to have the bug fixed that was causing a project crash when opening it before closing the previous one!

Also like the selection highlighted on the timeline. Haven't tried how this works together with the loop markers over the same region though - that case was not handled nicely in previous versions.

Edited by Helene Kolpakova
  • Thanks 1
Link to comment
Share on other sites

Thanks Noel for elaborating on your thinking.

It's necessary to stop and restart playback in order to get Melodyned clips to play back at the right time. Resetting the audio engine is also usually a good idea when there are stability questions, as for example when using plugins with a lot of latency. As a result, it's rare that I would want to click somewhere during playback and have the time jump there. In the use case described, I generally prefer to stop playback using the space bar, set the now time before the peak in question, then restart playback while looking at the relevant meters or other screen elements.

I think ctrl-clicking as a way to change the now time during playback seems like it might occasionally be useful for me, and it would solve the use case you described, without creating the possibility of accidentally changing the playback position, so that seems like a good solution to all of the concerns people have mentioned.

Also, I'm not sure that this behavior was noted in the release notes. I think that the surprise and mystification I felt after updating and having the playback position jump around unexpectedly would have been significantly ameliorated by a big boldface notice of what is a fairly important change in the behavior of the software.

Link to comment
Share on other sites

Hey all--

Just updated last night (after creating a Windows restore point). Had a couple issues--both seemed to resolve after a reboot.

The Bandlab Assistant stayed all whited-out for a long time, before it finally settled down and let me install the update. I was surprised the update was so quick since there were some many "updates" and bug fixes, etc.

Then, when I opened CW, it hung for a long time before it finally opened. Then, when I went to open a medium sized project (small for me) it hung too. I had to wait for a long time before it opened and was seeing a Cakewalk not responding up in the top of the window.

Before I was going to do a system restore, I rebooted my computer and then CW and the same project opened fine--so of course I didn't need to do a system restore. I haven't tested the Bandlab Assistant yet--but I rarely use that. I just use it to check for updates.

That's my report.

  • Thanks 1
Link to comment
Share on other sites

5 hours ago, Helene Kolpakova said:

One small bug observed on my windows 10 1803 machine:

After the existing project is loaded, transport section in the control bar is not properly rendered until I select any track.

@Helene Kolpakova If reproducible, could you please post a screenshot of the issue?

Thanks for reporting!

  • Like 1
Link to comment
Share on other sites

1 hour ago, Jesse Jost said:

@Helene Kolpakova If reproducible, could you please post a screenshot of the issue?

Thanks for reporting!

Yes, sorry wasn't at my workstation to post the screenshot with my original post.

Here's the screenshot:

image.png.77973323befee2889babc8f47fb2585b.png

Here's the reproduction:

  1. Start CbB - it loads the Normal.cwt
  2. Open an existing project from the Start Screen (in this particular example, the project was created in 2019.05 but I think it doesn't matter)
  • Like 1
  • Thanks 1
Link to comment
Share on other sites

2 hours ago, Keni said:

New difficulty has popped up...

 

Since installing build 70 I continually get lockups between loading projects.

Each time it locks while toast is showing "Loading Clips and..."

 

Fix coming up for that Keni. Its related to having the option on for only opening a single project at a time.

  • Thanks 4
Link to comment
Share on other sites

And here's another which I finally caught. It's not unique to 2019.07, but annoyed me for years now. Would love to see this fixed.

Short Description: some VSTs get all MIDI ports selected on the corresponding MIDI/Instrument track as a MIDI In port after the track is armed for recording.

Reproduction steps:

  1. Insert one of the problematic VST synths in a new project.
  2. Create a corresponding MIDI/Instrument track if not created automatically.
  3. Notice that by default the MIDI In on that track is set to None (Omni).
  4. Arm the track for Recording.

Expected:

Typically, the MIDI In port of the track is then switched to "All Inputs - MIDI Omni"

Observed:

For some synths several MIDI ports are selected at the same time which looks like this

image.png.c1ae677e5f3a311aead6c6d97a1dbce0.png

Known VSTs affected: 

  • All NI synths (Komplete Kontrol and Maschine 2 are especially hurting in that regard)
  • Adam Szabo's JP6K and Viper
  • TAL U-no-LX-V2
  • chipsounds (but chipspeech is fine)
  • AudioRealism ABL3, ADM (but ReDominator is fine)
  • Novation V-Station
  • Cakewalk z3ta+

VST known to work fine:

  • LennarDigital Sylenth
  • Reveal Audio Spire
  • U-he Diva, Repro-1, Repro-5
  • AAS synths
  • Xfer Serum
  • Cableguys Curve 2
  • Cakewalk Z3TA+2

This behaviour is consistent on my machine, i.e. it survives reboots, CbB restarts, is independent of the project and project template.

Also while testing, I noticed that SonicProjects OP-X PRO II crashes CbB on insert - it's working totally fine in Komplete Kontrol though. But KK is affected by the weird MIDI Input ports issue.

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

Thanks for the great feedback and reports all.

We now have an early access hotfix build available that fixes known reported problems so far. If you are affected by any of the issues listed go ahead and install the build. Its identical to the 07 release with just these changes.
We plan to release the final hotfix a little later after we address a few more issues.

Please continue to give us feedback on this release in this thread.

New  option to enable/disable setting the now time during playback via Track View Options > Click Behavior > Set During Playback

@Walter Treppler and @btbrock this new option should allow you to switch back to your workflow.

 

  • Like 1
  • Thanks 5
  • Great Idea 1
Link to comment
Share on other sites

1 hour ago, Noel Borthwick said:

Thanks for the great feedback and reports all.

We now have an early access hotfix build available that fixes known reported problems so far. If you are affected by any of the issues listed go ahead and install the build. Its identical to the 07 release with just these changes.
We plan to release the final hotfix a little later after we address a few more issues.

Please continue to give us feedback on this release in this thread.

New  option to enable/disable setting the now time during playback via Track View Options > Click Behavior > Set During Playback

@Walter Treppler and @btbrock this new option should allow you to switch back to your workflow.

 

I love this hot fix!  Cakewalk has kept its promise to those of us who bought the lifetime updates back in the day.  There's not many companies that's as responsive to their users as CW.  Thanks, Noel to you and all the gang that have stayed with us throughout the years.

 

  • Like 2
Link to comment
Share on other sites

Clip Selection Bug

Short Description: if a track contains multiple clip,the last one is unselectable

https://youtu.be/XVBxFmtMCVM

when this happened,I have to close and reopen CbB,everything will be back to normal.

It seems appear randomly,I haven't figure out how to reproduce this bug. 

 

PS:Is it possible to make the transform tool avaliable for tempo map?

it will make tempo adjustment much much easier.:D

 

Edited by Blacksymphony
Link to comment
Share on other sites

12 hours ago, Noel Borthwick said:

Thanks for the great feedback and reports all.

We now have an early access hotfix build available that fixes known reported problems so far. If you are affected by any of the issues listed go ahead and install the build. Its identical to the 07 release with just these changes.
We plan to release the final hotfix a little later after we address a few more issues.

Please continue to give us feedback on this release in this thread.

New  option to enable/disable setting the now time during playback via Track View Options > Click Behavior > Set During Playback

@Walter Treppler and @btbrock this new option should allow you to switch back to your workflow.

 

I'm so glad Bandlab got you on board Sir!

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...