Jump to content

Recommended Posts

Posted (edited)

I seem to recall seeing this issue (or a similar one).  I might be misremembering, though.  What version (including build) are you using? I will look for the post I am remembering.**  

Edit: **Still looking. Maybe this is what I was remembering? I didn't find any public follow-up discussion on this. Not sure if the cause hasn't been pinpointed yet, or if there has been a solution. Others might know.  

Edited by User 905133
update

Share this post


Link to post
Share on other sites
Posted (edited)

SET MEASURE/BEAT AT NOW is broken?
Did I miss something in how the new Tempo Track works?

I lock Measure 1 at say 120BPM, I then set up a count in at Measure 9 and lock it at 120bpm.
Hit record and count the tune in and start playing. Then I go back and start start counting beats
find a "1" and SET MEASURE/BEAT AT NOW. This has always put that beat at the "1" .
Today (build 175) jumped back and changed the tempo at measure 1 (not to measure 9 as it always has)
and my beat that should be on the "1" is now late.
What gives? Is this expected behavior?

t

UPDATE:

If I set Measure 1 at 120.01, then the tempo at measure 9 is set properly.
Evidently the Tempo Track ignores subsequent "anchors" that are the same value?

hope I'm making my "issue" clear...

Edited by DeeringAmps

Share this post


Link to post
Share on other sites
19 hours ago, DeeringAmps said:

SET MEASURE/BEAT AT NOW is broken?
Did I miss something in how the new Tempo Track works?

I lock Measure 1 at say 120BPM, I then set up a count in at Measure 9 and lock it at 120bpm.
Hit record and count the tune in and start playing. Then I go back and start start counting beats
find a "1" and SET MEASURE/BEAT AT NOW. This has always put that beat at the "1" .
Today (build 175) jumped back and changed the tempo at measure 1 (not to measure 9 as it always has)
and my beat that should be on the "1" is now late.
What gives? Is this expected behavior?

t

UPDATE:

If I set Measure 1 at 120.01, then the tempo at measure 9 is set properly.
Evidently the Tempo Track ignores subsequent "anchors" that are the same value?

hope I'm making my "issue" clear...

As long as you're doing uninterrupted multiple Set Measure/Beat At Now operations, it will behave as it did before the tempo track was introduced.

If you manipulate the tempo track between Set Measure/Beat At Now operations however, it will remove tempo "anchor" points, as duplicate tempo entries in the tempo map are removed when converting from the envelope.

There may be a way to improve this for the next release, but in the meantime make sure you don't alter the tempo track between Set Measure/Beat at Now operations.

 

  • Thanks 1

Share this post


Link to post
Share on other sites
Posted (edited)
3 hours ago, msmcleod said:

it will behave as it did before the tempo track was introduced

Yes, after I had changed the measure 1 Tempo to 120.01 (9 was set to 120.00) 9 (instead of 1) changed to the
new tempo (in this case 100.ish) and subsequent changes all worked as it always has.

What I think though, is that if a series of the same tempo are placed (say every 2 measures) then Set Beat
will jump back to the first instance in that series, Not the last. Of course this is conjecture.
I'll fuss with it and report back with my findings...
Again I hope I've made myself clear.

t

created this to illustrate what I'm seeing
185614563_setbeat.thumb.jpg.ed428ee5831f0c331e630ec5fa3bba46.jpg

On the left I dropped a bunch of Tempo Changes, the audio starts at measure 4.
Then at measure 10 the audio increases in speed and I'm about to hit Set Beat 13:1.
On the right you can see that the Tempo Change jumped back to measure 1, not to measure 10
where the last Change occurred and that last beat is not "spot on" at 13:1.

Not at all what one would expect. There's a work around, if that last 120 at measure 10 is set to 120.01
it all comes out exactly on the n^!s, well it comes out right.
If this is how it has to work, for the tempo track to work, I'm all good with it; just got to tell CbB that a "change is coming"

Edited by DeeringAmps
added clarity

Share this post


Link to post
Share on other sites

I waited to install this update until after I finished a project I was on--just in case.

I haven't fully explored all the changes but have a couple of initial impressions I'd like to share.

I like the waveform outline. Looks like Wavelab and I like the definition.

I like the vst2 and vst3 indications for plugins.

I'm not a fan of the menu fly outs being gone. I might not be naming the feature correctly, but when I used to want to insert a soft synth, if I hovered my cursor over soft synth, the choices of my soft synths would automagically fly out without me having to click. Small thing, but I'm being honest.

Everything works, and that's most important!

Thanks!

Share this post


Link to post
Share on other sites
On 5/31/2021 at 3:04 AM, razor7music said:

I waited to install this update until after I finished a project I was on--just in case.

I haven't fully explored all the changes but have a couple of initial impressions I'd like to share.

I like the waveform outline. Looks like Wavelab and I like the definition.

I like the vst2 and vst3 indications for plugins.

Everything works, and that's most important!

Thanks!

Well    @razor7music ^This^ is the info I've been waiting for before I too go down the upgrade path...  Do I need to read through the 18 pages - or is there an update summary? 

As always - Thanks to the Bakers and all the Cakewalk team for continuing the development of this DAW.   

 

  • Like 1

Share this post


Link to post
Share on other sites

About fonts in the new plugin menu.
I noticed that some symbol characters are not displayed.
Is this the correct specification?
The symbol character currently confirmed is "&".

font.gif.53b754ea63da095cf821c85adf8eb4d7.gif

Share this post


Link to post
Share on other sites
8 hours ago, icu81b4 said:

Do I need to read through the 18 pages

Who reads a manual or update notes? 🙃

But on a serious note, download the "rollback", that way if something is amiss; ya just roll 'er back.
I'm speaking from experience here; been there, done that...

t

  • Like 1

Share this post


Link to post
Share on other sites
1 hour ago, DeeringAmps said:

Who reads a manual or update notes? 🙃

But on a serious note, download the "rollback", that way if something is amiss; ya just roll 'er back.
I'm speaking from experience here; been there, done that...

t

I read the update notes like it's Christmas.

 

  • Like 2

Share this post


Link to post
Share on other sites

I really like the upgraded Bandlab integration, but I'm having a hard time make it work properly. Very ofter only some of the tracks have content and the rest are empty and when I try try to upload again it's ok. This happens both ways. Especially when you try to upload buses to get over the limitation of number of tracks. I only get one bus and master no matter how many times I try.

Share this post


Link to post
Share on other sites

Everything feels really really good with this update, it's a lot easier on the eye. Enjoying the GUI enhancements a lot. 

Only issues I'm encountering are the clip gain issue (which I know has been addressed) and problems with certain plugins which I think are GUI related. 

Soothe2, Oxford Drum Gate and Neural DSP Archetype Cory Wong all play up. Displays are laggy, jumpy and eventually stop displaying at all and turn into white boxes. Opening them sometimes crashes the program. This issue doesn't happen in Sonar Platinum, and plugins work fine there. 

Share this post


Link to post
Share on other sites

So - I've updated and now none of my plug-ins are working - They scan and load ok, but don't do anything.  - The insert appears slightly 'dimmed' in the channel. 

This applies to ALL plug-ins - (Cakewalk - ProChannel, Waves, Soundtoys, Unversal Audio etc ... ) 

 

Any ideas ? 

 

  • Sad 1

Share this post


Link to post
Share on other sites
Posted (edited)
On 5/25/2021 at 2:09 PM, Noel Borthwick said:

@Will Zégal Its very unlikely that the latest release caused any of these issues but have you tried rolling back to the prior release to verify?  A link to the rollback installer is always listed at the top of the new release thread. Very often issues are being attributed to the latest release when they are preexisting or externally caused issues so its important to roll back and verify if you have a reprodicble issue.

Is the problem reproducible every time or intermittent? Which version of Kontakt are you using?

Sorry for the late reply. Much work to do.

I use the up to date version Kontak (6.5.3)

I've done the rollback and the problems are gone, even if I sometimes still have some menus issues when a plugin is open on my secondary screen.

I have another problem with Kontakt (and often with Reaktor).

For instance, I try to use 8Dio Glass Marimba instrument.

Here is the state of the plugin when I open the project

_tmp.jpg.f9950e885a7aa3d05e4f280082e254e9.jpg

and each time I stop the playing

 

_tmp2.jpg.69f8f6e5f28b4643b39610220e81fd0c.jpg

 

there is nothing else than some notes on the MIDI track that is the default one created by the insertion of the instrument in the synth rack. No controller, no sysex or RPN nor anythin of that kind. And the project is almost empty with just another audio track with a audio clip imported on it.

I've tried this instrument in Maschine and do not encounter this problem.

I often problems like that. For instance, I often can't change the master volume in Kontakt. Everytime I hit "play", it returns to it's default -6dB state. (notice that it's not the case this time : only the filter state changes.

[Edit : I've found the cause : the filter is controlled by the modulation wheel. There's no modulation wheel information one the track no modulation line, but when I hit stop, the mod wheel in Kontakt returns to zero even if I have tuned it]

I encounter some similar problems in Reaktor : with many Reaktor instruments, hitting play make some changes in them. Often I can't tell which ones because there are not audible, but Reaktor adds the star to the name of my saved preset that indicate it has been changed.

Edited by Will Zégal

Share this post


Link to post
Share on other sites
59 minutes ago, Will Zégal said:

Sorry for the late reply. Much work to do.

I use the up to date version Kontak (6.5.3)

I've done the rollback and the problems are gone, even if I sometimes still have some menus issues when a plugin is open on my secondary screen.

I have another problem with Kontakt (and often with Reaktor).

For instance, I try to use 8Dio Glass Marimba instrument.

Here is the state of the plugin when I open the project

_tmp.jpg.f9950e885a7aa3d05e4f280082e254e9.jpg

and each time I stop the playing

 

_tmp2.jpg.69f8f6e5f28b4643b39610220e81fd0c.jpg

 

there is nothing else than some notes on the MIDI track that is the default one created by the insertion of the instrument in the synth rack. No controller, no sysex or RPN nor anythin of that kind. And the project is almost empty with just another audio track with a audio clip imported on it.

I've tried this instrument in Maschine and do not encounter this problem.

I often problems like that. For instance, I often can't change the master volume in Kontakt. Everytime I hit "play", it returns to it's default -6dB state. (notice that it's not the case this time : only the filter state changes.

[Edit : I've found the cause : the filter is controlled by the modulation wheel. There's no modulation wheel information one the track no modulation line, but when I hit stop, the mod wheel in Kontakt returns to zero even if I have tuned it]

I encounter some similar problems in Reaktor : with many Reaktor instruments, hitting play make some changes in them. Often I can't tell which ones because there are not audible, but Reaktor adds the star to the name of my saved preset that indicate it has been changed.

This looks very much like the Filter control is bound to the Modulation Wheel control (CC #0), and you have "Zero Controllers When Play Stops" checked within Preferences->Project->MIDI.

The default value for CC#0 is zero, so when the controllers are reset, this is set to zero.

Share this post


Link to post
Share on other sites
4 hours ago, Will Zégal said:

Sorry for the late reply. Much work to do.

I use the up to date version Kontak (6.5.3)

I've done the rollback and the problems are gone, even if I sometimes still have some menus issues when a plugin is open on my secondary screen.

I have another problem with Kontakt (and often with Reaktor).

For instance, I try to use 8Dio Glass Marimba instrument.

Here is the state of the plugin when I open the project

_tmp.jpg.f9950e885a7aa3d05e4f280082e254e9.jpg

and each time I stop the playing

 

_tmp2.jpg.69f8f6e5f28b4643b39610220e81fd0c.jpg

 

there is nothing else than some notes on the MIDI track that is the default one created by the insertion of the instrument in the synth rack. No controller, no sysex or RPN nor anythin of that kind. And the project is almost empty with just another audio track with a audio clip imported on it.

I've tried this instrument in Maschine and do not encounter this problem.

I often problems like that. For instance, I often can't change the master volume in Kontakt. Everytime I hit "play", it returns to it's default -6dB state. (notice that it's not the case this time : only the filter state changes.

[Edit : I've found the cause : the filter is controlled by the modulation wheel. There's no modulation wheel information one the track no modulation line, but when I hit stop, the mod wheel in Kontakt returns to zero even if I have tuned it]

I encounter some similar problems in Reaktor : with many Reaktor instruments, hitting play make some changes in them. Often I can't tell which ones because there are not audible, but Reaktor adds the star to the name of my saved preset that indicate it has been changed.

VST2 plugins have no way to distinguish between reset CC data sent when playback is stopped. CbB resets certain CC’s on playback stop such as CC 0, CC 64. Generally you should not use such CC’s to control plugin parameters for this reason.

Share this post


Link to post
Share on other sites
3 minutes ago, rescareguy said:

FET compressor in Pro Channel crashes Cakewalk

It is not a CbB 2021.04 issue.

It is a bug in the Softube code from April 2020.

There is no reason to cross-post in this thread

 

 

  • Like 1

Share this post


Link to post
Share on other sites
Posted (edited)

Hello

 

I asked in Q&A but I will ask this here too because I tried different things and seems like it's somehow related to 2021.04 update.

 

 Yesterday I installed CbB 2021.01 on my laptop to check out what's going on (I had only the latest Platinum on my laptop until now and don't have this problem).

If  Non desctrutive MIDI editing is enabled the MIDI clip always stays intact, if Non desctrutive MIDI editing is disabled the MIDI clip always cut to the last note in the clip.

Then I updated CbB to the latest version 27.04.0.175 (2021-04).

When Non desctrutive MIDI editing is enabled, if I move a MIDI clip (drag with left mouse click) the length of the clip will be cut to the end of the last MIDI note. If I CTRL+C and CTRL+V or CTRL+left mouse click and drag to  duplicate, the lenght won't change.

When Non desctrutive MIDI editing is disabled (unchecked) the length of the clip will be cut to the end of the last MIDI note in all 3 cases.

 

It looks like, it has something to do with this update but i don't see anyone else to mention this problem. 

 

Edited by Ferenc Hegedus

Share this post


Link to post
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...