Colin Nicholls

Uh... what is a "flatbed" in this context?

Well he's not wrong but opinions are free on the Internet. Including mine ? Some reading material: Mixing for Vinyl: https://resoundsound.com/mixing-for-vinyl-dont-fall-for-these-traps/ Ozone Imager 2 (Free) VST: https://www.izotope.com/en/products/downloads/ozone_imager2.html I recommend using a stereo imaging tool like the Ozone one. Learn about what the graphs mean. Now compare your mixdown with other commercial releases and see how the graphs compare. My impression is that you've followed the "100% Left or Right" rule a little too hard, and your mix is unbalanced, and fatiguing to listen to. It might sound fine mixed to mono or it might have strange empty spaces in the freq.spectrum. I hope that helps.

I think it means that you have stuff either hard right or hard left (which is, indeed, what it sounds like) which can work but can also be a problem. Bass frequencies would be better served to be center/mono.

Nice track. I reviewed it with Voxengo SPAN. (if you don't have this tool, you need it.) The phase correlation meter is fluctuating widely but this doesn't necessarily mean there's a problem. You've got quite a wide stereo field here, instruments panned 100% left and right. I used Channel Tools to flip the phase on each channel, and also to reduce to mono, to see if I could hear any obvious problems and, frankly, I didn't. So I suggest put an instance of Voxengo SPAN on your Master bus. Play the track, solo the busses, instruments, and watch the phase correlation meter and see if you can find an obvious problem. Here's an anecdote for you: I had a track with a lovely stereo string pad played on my Korg M1 and I didn't understand why it sounded so whimpy. I SOLO'd it and checked its phase correlation, and sure enough, the "Stereo Ensemble" effect was generating a lot of out-of-phase movement between the two channels. Experimenting with the chorus parameters fixed the problem, and I was in business with a weighty string pad track that I had to reduce in volume in the mix. Sounded great.

I would say, No, it's not possible. Melodyne probably has the technology ready to release in the next upgrade /joking

@Robert Johnston, try reviewing these posts and see if any of the advice there helps you out:

We'd like to help but you're not giving us much to work with. Try this: Go to this url and download the assistant installer: https://www.bandlab.com/download/assistant/windows Run the installer (you shouldn't need to "Run as Administrator" but keep that idea in your pocket). Post details of the first error you encounter, or a screen shot of the first place you find yourself unable to proceed as expected.

ProChannel comes first by default. Verified experimentally with Channel tools in the PC FX Chain, and Sonitus Delay on the track FX bin. The PC context menu flips this sequence, as pointed out by @scook.

Release 2. ZIP file now contains previous version plus MIL-SPEC-ALPHA_R2 with revised Transport buttons. See top post for deets

I'll play. I'm 55. I used MOscillator in Cakewalk to generate tones. My ears tell me that anything above 13kHz might as well not be there. That's depressing, but not news to me.

I use a venerable ECHO Layla3G PCI card in my DAW. The ASIO drivers are version 8.6, released for Windows 7 "back in the day", but work fine in my Windows 10 system. Related to PCI cards, is the description of how I managed to install it into a new computer with only smaller PCIe slots.

Clear that "Show Strip Colors" checkbox under Preferences > Colors

I have my vertical zoom so far out that I didn't even realize that Notes are colored with a gradient

I tried the demo VST3 version and encountered this problem, but the demo VST2 version worked as advertised. Did you initially try VST3? That might explain it. Nice if it is fixed.

I've updated the zip file with a new version, and edited the Update History on the top post with details. (A very minor change, but it was bugging me.)

I use key bindings to bind [F2] to [Rename Clip] in the Track View. Works great.

I use multiple tracks and then delete the parts from the guide track that aren't necessary.

You're referring specifically to this part? I don't know the answer to why Cakewalk, Cubase, Logic Pro, and Studio One do not have this ability, while Ableton, FLStudio, ProTools, and Reaper do. I don't know if this achieves the same result, but in Cakewalk you could SEND the audio track to two separate aux tracks or busses, and put an instance of PEEL on each, and invert the filtering on one of the PEEL instances. (FYI, I couldn't get the VST3 version of PEEL to work at all, but the VST2 one did.)

I highly recommend this: https://www.resonantdsp.com/swankyamp/

On reflection I do see the problem if we have multiple drum tracks with their own Drum Map.. I mean, you don't want the drum-mapped tracks to overlay in the Drum Pane, so maybe keeping it exclusive as it is now is the best idea. Some workarounds: Opening two PRV windows, undocking, and locking the contents to see different types of track in each: https://discuss.cakewalk.com/index.php?/topic/12153-piano-roll-per-track/ Inline PRV in Track View: https://bandlab.github.io/cakewalk/docs/Cakewalk Reference Guide.pdf#G16.1083508 Not perfect but pretty good:

With my beloved Echo Layla3G PCI/ASIO at the heart of my system, I suspect I'm not upgrading past 1803 until the hardware dies. Thank goodness for Winaero Tweaker.

I feel like I'm missing something here. I want to see the drum notes when editing the other tracks, but they keep vanishing: Does anyone have any insight? I can't think of any reason why - from a user experience point of view - this should be the case. EDIT: I've submitted this as a bug report because it is driving me crazy.

I don't believe these are customizable, as yet.

From @Pete Brown's article: This gives me some hope I can upgrade from 1803 at some point.

I think @GreenLight meant to reply to this thread: