Sailor55

I'm not a great singer, yet good enough to make a demo that gives a real singer a concise idea of what I'm after. I don't like take lanes either. I sing vocals one line at a time. Take after take. I usually know when I've done a keeper. Of course, that's almost never. Thus, I save a ton of time by not bothering to listen to a dozen takes that I know are weak (i.e. most of them). After enough takes (followed by ctrl-Z), my vocal delivery improves to the point where I have something that's worth examining in Melodyne. If the Melodyne tweaking is not too extensive, I'll do the necessary editing, then render, then move on to the next line. After I've finished the whole tune I'll take a serious listen to entire vocal in context of the entire song. Invariably, I find there's always a few few lines that could have been better. I will correct these by the same method detailed above. And yes, it take ages. Did I mention I'm not a great singer?. Why bother if I plan to hire a pro anyway? Well, I don't necessarily hire a pro for everything and I don't want any of my demos to be cringe-worthy. A good singer would find the above to be pure madness. But I am a pragmatist. I tend to work with what I've got. But I'm always alone when doing thirty takes of the same line. Nobody wants to hear that. The trick for me is to be ruthless. If I know I've flatted (or, more likely, wavered) on the last word of an otherwise reasonably good take, I'll delete it and keep trying. The worst thing about comping is the process of deciding what is "best" from dozens of takes. I prefer to decide that on the fly.

A complete remix & rearrangement of something I posted a few years ago. I had some fun with this. - Daniel https://www.taggerband.com/Music/DBH/BillyAndDiva.html

I'd be happy to. But I've never done it before. How much do you need? Just the .cwp file? What about the audio, effects and synths? Where do I send it? Edit: Actually, I've tried it. The .cwp file alone exhibits these problems without audio, effects etc. It is only 644K in size. I could email it. - D

I downloaded 2021.12 build 93. I have a small project that happens to have a single folder (no nesting) containing two tracks. It is now completely broken. The two tracks in the folder still play but are not visible. The tracks are disconnected (spatially) from the actual folder. The folder can not be moved, expanded of contracted. You can not remove the tracks out of the folder either by dragging or any other command. Manipulating some other tracks eventually results in a crash. The file was saved under build 93. I rolled back to build 79. Still broken. I rolled back to build 18. Still broken. The project now seems to be corrupt. I can't go forward, I can't go back. Fortunately this was not a particularly important project. But I think it is now lost. - D

I found two things confusing: Why does the extra 0.6 dB only occur in the right channel? And why does "render in real time" fix it? As I said, I've tried it both ways many times and the results are perfectly consistent. I can think of only two possibilities: This is a problem specific only to my DAW and only under specific circumstances, or... This is a bug. If it is a bug, it's fortunately one that very rarely manifests itself. I've never noticed it in dozens of other projects. I usually only bounce entire mixes to a track at the end of a project, but in future, I will be doing it in real time when I must be confident of the result. Perhaps someone could shed light on why the "real time render" option exists in the first place. Anyway, thanks to everyone who commented. I hesitate to update this thread to "solved". But there does seem to be a usable workaround. - Dan

John Vere, I appreciate your suggestions regarding snare compression but this simple fact remains: What is happening on the master bus does not get duplicated when bouncing the "entire mix" to a track. That should not happen. I have completely cured the problem by checking the "render in real time" box. Then there is no extra 0.6 dB in the right channel. Granted, it takes longer to mix down, but it actually work correctly. This observation is completely consistent over many tries. I'm about ready to declare this a bug.

Thanks for the replies. I tried muting the master bus, but there seems to be nothing bypassing it. I had originally 5 tracks. Rhythm Guitar, Lead Guitar, Bass (midi), Drums(midi) and a Vocal. I've narrowed the problem down the drum track (Addictive Drums 2). With all effects in the project disabled, and all other tracks muted, the drum track peaks at -7.9 dB in both of the stereo channels. That is can be seen on both the drum track and on the master bus. But... after "bouncing to track" (entire mix) the resultant track (which is now only drums) peaks at -7.9 in the left channel, but -7.3 in the right channel. It is happening on snare shots. Actually, on the very first one and every one thereafter. It seems the mix down is adding 0.6 dB of volume to the right channel whenever it encounters a snare shot. Very odd.

I'm having a weird problem where the output from my project's master bus is not what I get when I bounce the "entire mix" to a track . Both channels are hard limited (as shown) on the master bus meter but only the left channel is limited in the mix. Never seen this before. I've tried many things but the result is always consistent. Running 2021.11. Any ideas?

I've had a similar problem. Maybe this will help...

I have also experienced the soloing problem in the early release [123] . It happened on only on two occasions. Once, I restarted Cakewalk and the problem disappeared. On the other occasion, I just started soloing and un-soloing random tracks (and the master solo too) then after a while normal operation resumed.

Today I was recording a vocal track. Nothing special. Just some typical clips in an ordinary audio track. When I tried to create a Melodyne region effect on one of the clips, Cakewalk (2020.11) crashed in an odd way. Suddenly, it froze and the entire Cakewalk window greyed out. Usually, at this point Win 10 recognizes a non-responding application and offers to close it (and send a report to Microsoft etc.). But that didn't happen. Instead, Cakewalk began stitching between a greyed-out window and a normal window every few seconds while still remaining completely frozen. The only thing I could do was terminate Cakewalk with the task manager. Naturally, I assumed it was some Cakewalk + Melodyne issue. I re-opened the project and this time I didn't try creating a Melodyne region effect. I just tried to bounce to clips into one single clip. Same problem. I was able to repeat th crash scenario consistently that way. And, I could also do it by making a Melodyne region effect on that track. I'm running the very latest Melodyne version 5.1.1.003. Here's how I fixed it: I created a fresh audio track, dragged the clips into it, then deleted the original one. All problems gone. Melodyne works fine. Bouncing to clips works fine. So, can a track become corrupt such that it's simply broken and needs to be deleted? Seems like this has happened to me before in the distant past.

I know what it means to 'normalize' a track, but I'm not sure what you mean by normalizing tracks ' to each other'. A normalized track is one where the loudest peak is moved to exactly 0 dB (or some other specified value) and the rest of the signal is scaled according to that. Thus, if you normalized every track to the same value I suppose you could say they were normalized to each other. Somehow, I don't think that's what you mean. If you want each track to have the same loudness then you'd need to use a loudness meter (say like the Waves WLM Plus meter) to help you adjust the loudness to some LUFS (Loudness Units Full Scale) value. I usually target my full mixes to -14 LUFS.

Glenn Stanton had the right idea in the beginning, I think. The monitor is really two monitors in one. (Hence the fat price). Therefore, twice the data must be sent through it in a given time frame. Formerly, that data was shared between two ports and two cables. Now, it all travels through only one port and one cable. If a cable is at all marginal (as my original one probably was) then it makes sense the throughput just couldn't quite be maintained. Running Cakewalk in full screen mode on a high resolution monitor with a 32x10 aspect ratio is probably a big ask. One would imagine Asus has tested their cables extensively. Anyway, I can report there have been no problems whatsoever since I started using the cable packed with the monitor. And there's the lesson. Cheers... - Dan

I may have a resolution. When I installed my monitor there were already two displayport cables being used for my two Dells. Rather than unpack the new cable that came with the Asus monitor, I just used one of the ones I already had. And that almost worked. That is, every application except Cakewalk worked fine (and Cakewalk only had problems intermittently). This morning I replaced the old cable with the new one from the box. Since then, I haven't any issues with Cakewalk or anything else. The old cable was about 8 ft and about 3/8" thick. The new cable is 6 ft and 1/4" thick. Or maybe it was just a slightly flaky connection. I know that doesn't seem likely but..., Or maybe it's all just black magic. Anyway, I'm really hoping this is a fix. Note to self: If you get new cables, then use them. BTW, I highly recommended the Asus XG43VQ for anyone who prefers a 16x10 over a 16x9 aspect ratio and wants to replace a dual monitor system. It's designed for gamers, but since I'm not a gamer, I just ignore those extra features. It can be had for about $750 AM (or $999 CD, which is what I paid). Thanks again everyone. I'll bump this post if I have any further problems. - Dan

First, let me thank everyone who responded for the great help and suggestions. All I really wanted to do was get rid of the bezel gap between my two Dell monitors (although, having a curved 32 x 10 display is pretty nice too). My PC has a Small Form Factor and so if I wanted a video card to replace the onboard video I'd be hunting for a half-height card which might limit my options. My thought is now this: my PC has only two DisplayPort outputs which formerly ran two 16x10 monitors quite nicely. My new Asus XG43VQ monitor has only one DisplayPort input, but it has two HDMI port inputs. This allows the monitor to support a 16x10 display on either side. In other words, I'd be back to the way it was before except there would be no bezel gap. It'll cost me two DisplayPort to HDMI converter cables to find out if this would work. I'll probably give it a try. I hope I don't burn $100 to find out that won't work either.