Andres Medina

Thanks!

I did some additional tests, and found out a way to work it out, with some limitations. Not sure how melodyne is applied in Cubase to composite tracks, so here is a way to use inside Cakewalk:

When applying melodyne to take lanes:

• All takes must be active before applying melodyne. Otherwise, Melodyne renders the muted clips as silence. 
• Each lane must be selected independently to select and apply the melodyne region (otherwise melodyne renders the whole comp track to one single melodyne composite take)
• Once this is done, you can select and edit the comp takes as always, and melodyne reflects your selection in its own screen (the selection must be done in the cakewalk lane, not inside melodyne). 
• For been able to see the different selected clips independently inside melodyne, I think you need the studio version, which provides multitrack editing, otherwise all the clips that has melodyne applied inside the comp track are displayed together in a single window, and this makes pointless the use of this comp+melodyne tool.

So, I guess that to really use the comp track with melodyne, you need to have the studio version.

Hi - I'm struggling to make it work too. - I'm using latest Cakewalk (2021.04 build 175) and Melodyne Assistant version (no multitrack editor, no polyphonic capabilities) 

Here are my findings:

1. If I apply Melodyne to the whole track (comp lanes inside), Melodyne renders whatever clips are active into a single clip, losing the ability to work the individual clips again.
2. If I apply Melodyne one by one on the individual takes of the comp track, I can work and hear the edits made on the comp tracks, but Melodyne displays all the blops of the clips stuck together - not useful at all.

Not sure if this is a limitation on my Melodyne version, or a malfunction on the integration of Melodyne with Cakewalk ...

I wonder if any of you are using Melodyne Studio+Cakewalk to check?

(in the meanwhile I think I'll try the 30 day test drive for Melodyne Editor  or Studio to  see how it behaves)

On 5/12/2021 at 2:07 PM, Larry Jones said:

Thank you. Yes, I saw that readme. It just says "If you're using already one of the named interfaces without any trouble, there is no need to install this driver." Since the OP was setting up a new computer, I assume he did not have any driver installed, so the logical one to use would be the newest one, right?

Note to @Tom Ham: Did the 4.59 driver work for you?

Yes, you are right - it's not suggesting to use 4.59 instead of 5.0 - my mistake.

Anyway, I did a few tests, and here are the results: 

Driver 5.0 working just fine.

I did uninstall completely both drivers: 4.59 driver and ASIO4ALL - Restart PC - Install 5.0 driver - Restart PC

So far, everything is working just fine.

15 hours ago, Larry Jones said:

The only documentation I found on the Behringer website is a PDF "Quick Start" guide, and in there I can't find where the manufacturer makes this recommendation. May I ask where you found it?

Sure: it's in the ReadMe file when you download the 5.0 driver. 

Enclosed a copy if it helps.

UMC-Series_DriverV5-ReadMe_2021-02-25.pdf

5 minutes ago, John Vere said:

Did you install the ASIO driver from the Behringer's support page under downloads? 

https://www.behringer.com/downloads.html

 

And make sure you install the right one for your system.

I have the UMC 404HD model and  works perfectly well  with the 4.59 version.

The 5.0 version didn't work at all, and the manufacturer recommends installing this one only if the other doesn't work.

See screenshot.

Yes, sometimes it happens to me too, but not all the times.

There is a workaround: open Task Manager - find the cakewalk icon - select it - select End Task .

It should release the driver, so you don´t need to restart your PC.

Hi Noel.

I switched to Guitar Rig 6 instead of Amplitube, as the later was compromised on the crashes I'm getting.

Unfortunately, got a crash again: this time, after disengaging the solo option within the plugin (Guitar Rig).

Enclosed the minump and the crash window.

Thanks!

test guit rig 6_04252021_174950.zip

New crash...

I reverted to 2021.01

Enclosed the crash window and the minidump.

I wonder why I'm getting so many crashes... 

TyC 0206 Dragonzorro Ok6 b test new drums_04212021_170536.zip

I've got another crash.

I'm already working on the 2021.04 Early Access version.

The crash occurred inside takes lanes, when selecting clips while the audio was running.

Enclosed the minidump.

TyC 0206 Dragonzorro Remoto 3_04202021_085100.dmp

5 hours ago, Noel Borthwick said:

Its in the bus compressor. Is this reproducible? If so please PM me the project file and steps.

No luck. I tried to reproduce it without success. The crash occurred just once, and the project is kind of complex, with lots of audio and midi clips, and several Virtual Instruments...

I had inserted multiple PC4k compressors in several buses. One of them was sidechained (the reason I use this particular compressor), the others not.

I'll keep you posted.

Thanks -

Noel, I've got another crash.

This time it seems to be something with Prochannel.

I've got today a mail response from Sean, regarding tha last crash:

"Hello,

Thanks for writing in. The crashes are caused by the PC4K Bus compressor. Could you try replacing that plugin in your project and let us know if this helps?

Thanks,
Sean
 "

May this crash from today has something to do with the compressor again.

Enclosed the crash window and the minidump.

Thanks!

TyC 0205 Patiamigos v3 4-1 All Voices_04142021_121321.zip

49 minutes ago, Noel Borthwick said:

Let me know if it happens again in the next release. I’ve prevented the actual crash from happening.

Got it -

11 hours ago, Noel Borthwick said:

@Andres Medina I tried to look for cases where this issue would occur and was not successful. Does this crash only occur with the Listento receiver and is it a reproducible problem? Also I see you are running a behringer audio interface. Did you notice any particularly odd behavior when loading templates with this plugin? We also tired making a template with the plugin and it does not crash.
I've added code to prevent the crash itself but the cause is a mystery.

Nop... I tried several times, using different templates and inserting the plugin directly on the project and from a track template, and was unable to reproduce the crash. Ugh... 

It's easier when is reproducible, right?

Besides the crash, I have no trouble using the plugin at all.

I'll keep an eye on this, and send a dump if it happens again.

Thanks Noel -

8 hours ago, Noel Borthwick said:

@Andres Medina Its a crash in our code where its doing something unexpected when loading a track template.
I'll fix it for the new release. Thanks for sending this dump since it allows us to find and fix issues we would not know about otherwise.
Although it happens when loading the Listento receiver the crash is not a plugin fault from what I can see.

Ok, I understand. Thanks!

Glad to help!

Noel, I continue to have crashes, but this time is not Amplitube related.

I'm starting to use remote recording plugins, as Connection Open and Audiomovers.

This time the crash happened when trying to insert a track template with Audiomovers Listento plugin inserted.

Enclosed the screenshot and the dump file.

Thanks!

TyC Patiamigos 1-2 Conn Open_04092021_191910.dmp

15 hours ago, Noel Borthwick said:

Please double check that this file is the correct version.
C:\Program Files\Cakewalk\Shared Utilities\CW130Auto.dll

If you check the file properties it should be 27.1.0.98 - i.e the same version as Cakewalk. If not the file was not updated properly and you should rerun the Cakewalk installer.

Thanks! I did check and the file is correct.

Enclosed the image.

Thanks Noel! Very helpful.

I'll redirect the Amplitube issue to IK Multimedia then.

---

"The second file is a crash in the prochannel bus compressor on one of your buses. I'd like to investigate this further, so if you can reproduce this please let me know. 
Its hard to say what caused the crash just by looking at the dump file but the plugin's internal state is corrupted so its possible that heap corruption caused the issue. 

Unhandled exception at 0x00000000471E5CB7 (PCS-BusCM.dll) in TyC 0205 Patiamigos v3 1-6_04052021_171612.dmp: 0xC0000005: Access violation reading location 0xFFFFFFFE47227160."

Ok, I´ll try to reproduce it. If successful, I'll send you the dump file.

--- 

"All your other dump files in the public.zip are caused by you running with an old automation dll. Are you using an old version of @scook utilities to load the application? Perhaps you have already fixed this since your other dump file doesnt have this issue. If not reinstall Cakewalk since you have a wrong dll there which is going to cause crashes. The dump shows that you have a different version of cw130Auto.dll."

Nop, I'm not using scook utilities. My Cakewalk version is the latest: 2021.01 build 098, 64 bit

--- 

Thanks a lot!

11 hours ago, Noel Borthwick said:

@Andres Medina its working as expected, source category tracks today only captures the output of tracks. To capture the destination it would have to do the tracks one by one and capture the output bus. Some others have also requested this behavior so we’ll consider it as a future option.

Got it. I was misled because the "Mix Enables Option" has the select bus options available. Now I understand.

Looking forward for this option to be implemented.

Thanks Noel

Hi,

I'm trying to export several stereo tracks at once, using the Track Source Category in the export dialog window.

All tracks are routed to a Bus containing  the Adaptive Limiter plugin.

The thing is that the exported  audio is not going thru the limiter, therefore the audio is not properly exported.

I have checked all the boxes in the Mix Enables options to make sure that the audio is being processed all the way thru the bus (see picture)

If I export track by track using the Entire Mix Source Category, the audio is exported right.

May be I'm missing something? I tried to find a Signal Flow Chart to double check the signal flow, but apparently is missing in the online help (https://www.cakewalk.com/Documentation?product=Cakewalk&language=4&help=Mixing.07.html) 

Thanks!

1 hour ago, reginaldStjohn said:

If it is Amplitube then you need to submit a report to IK Multimedia.  You can also submit a crash dump to support@cakewalk.com to see if there is anything Cakewalk is doing that could help.

 

Thanks a lot - I'll do that.

Hi,

I've been having a lot of crashes in a project, and the crash window refers to a problem with Amplitube plugin, an Amp simulation plugin.

Enclosed the minidump file.

I'll appreciate any help.

Thanks!!

Andres

TyC 0205 Patiamigos v3 1-6_04052021_171612.zip

20 minutes ago, Andres Medina said:

Great - Thanks! I'll give it a try.

Got it: at first I just copy-paste the 4 new modules, and of course it didn´t work, so I did copy-paste all the modules of the Select Tool Tungsten Theme into my edited theme and voilá. Got it - Thanks a lot.

14 hours ago, scook said:

Photoshop is fine for modifying images but I doubt you really want to resize images using any editor.

 

The easiest way to update the background image (or any image) depends on whether the user theme is based on Mercury or Tungsten.

If it is based on Mercury, deleting the existing image will automatically pick up the new Mercury image.

If it is based on Tungsten, open Tungsten in another instance of the Theme Editor, copy and paste the Tungsten image into the new theme.

Delete, Copy and Paste are on the context menu shown when right-clicking an image.

This will insure the size of the image is exactly what CbB expects.

 

Then modify the texture or color as desired in Photoshop.

The Theme Edit lets you add an image editor using the Setup Wizard in the Tools tab.

Great - Thanks! I'll give it a try.

On 1/15/2021 at 7:47 PM, Colin Nicholls said:

This is not official; just my comment:

It seems that the minimal change we need to make to have our custom themes be compatible with 2021.01 is to increase the width of one Theme Element:

Control Bar / Modules / Select / Background (large)

Increasing the width from 131px to 204px will allow the four new buttons to be visible in the UI. Otherwise, they are not shown except for a thin sliver on the right edge of the Select Module.

(It is not essential to customize the new buttons themselves, but they will of course look like they do in Mercury, if you make no other changes.)

This change is semi-backward compatible with 2020.11 in that the only side-effect is that the Select module is wider than previous, with "empty space" on the right side. Interesting... I wonder if we can make the other module backgrounds wider than they are currently without detriment?

Hi! Haven´t find the way to change the width of the Select module... I go as far as to find the Control Bar /Modules / Select / Background (large) within the Theme Editor, and get stuck. Should I edit it in Photoshop? - thanks!

2 hours ago, Andres Medina said:

I work a lot in projects involving video and syncing music to it.

No problems at all, providing that:

1. the video is encoded with mp4 codec and you have your windows codecs up to date.

2. You add a blank space at the beginning of the video to provide room for any pre roll you need for your music.

3. The exported video is not too heavy (for your computer configuration).

4. The other thing, for accurate frame syncing is to reexport your video file with as little as 1 frame in the Keyframe distance option of your video editing.

This ensure that when advancing your video frame by frame (in the video window of Cakewalk) , the video doesn´t jump several frames. 

Once you get the video right, just import it, and it should play smoothly,  using little resources.

If you get it right once, to get it right for ever.

For the music composition task, I find useful this:

1. Lock completely  the audio track imported along the video, to ensure that it doesn't  change position when you change your tempo.

2. Mark your video syncing spots using the markers feature and lock them, for the same reason.

Sure, it would be nice if someday this wonderful DAW could just move the video in the timeline and lock it...! 

Hope this helps!

 

... and a snapshot of the export video configurations that always works for me. H.264 codec is the best I came across.

Using this configurations I manage to work really smoothly with video inside Blb.