Colin Nicholls

I confess I come here every day to check the Early Access Program forum for bold text.

Interesting. Thanks for researching. I've updated the link in the top post.

FLAC ? Not as compact as mp3 but TANSTAAFL My music archive used to be 320kbps mp3 but I've recently been ripping all my CDs using FLAC.

I've just checked it and it is working for me, in chrome and firefox. I also tried the URL with https:// just in case it made a differences. Give it another shot? It may have been a temporary glitch with our web host?

Release 2.e. @MarianoGF asked a question about knob indicative color and I realized that a selected track in the Console View made this color almost invisible. Resolved by using a tinted color strip behind the knobs. I really like the result. MIL-SPEC-ALPHA-R2 is now my preferred theme, but I've retained Release 1 in the ZIP archive for those who might prefer it.

Hi @MarianoGF, you can totally change this indicative color but it is baked into the knob strip images, and isn't a separate color value that you can just change. With a good image editor you can edit the image and adjust the hue, saturation, etc to suit your needs. It's not ideal but it can be done.

Yes you can but before you enable groove clip looping, the clip should be an exact multiple of quarter note beats.

Make the groove clip a multiple of quarter notes. Repeat the loop twice within the clip if you have to, or ad a variant to taste. You can totally do it.

Select the clip. Show the Inspector, Clip Properties. Set the Time Format to H:M:S:F (for display) Set the Time Base = ABSOLUTE. Note the Start and Length values Changing the Time Base of the clip should mean that it will start at the same clock time even if you change the temp (bpm) of the project. We know that the duration/length of the clip will change because MIDI clips follow the measure/beat. HOWEVER: You can go into the Inspector Clip Properties and change the LENGTH of the clip after the bpm change, and put it back to the original length (minutes, secs, etc). Now the midi note events in the clip should occur at the original SMPTE time prior to the project bpm change. CAVEAT: I'm not sure how this would work for continual bpm changes throughout the length of the MIDI clip - some experimentation might be needed, or you might need to break the clip up into independent sections. (EDIT: I see you've said you've tried changing clip properties so perhaps this process isn't suitable. If so, I apologize. But I learned something during the research so, thanks for that.)

When I use the Mercury or Tungsten themes, and select "Volume" in the Edit Filter (so as to view the volume automation data without expanding the separate lanes) I see a "dark color" waveform on a grey clip background (with a bright green envelope). It's quite easy to see all the information by default, but it does make a difference what track color you're using. It is possible to choose a custom track color that is close to the background grey. Best avoided. You can definitely change the default clip foreground colors. There are themes that use black waveforms and colored backgrounds, and they also seem quite easy to read when editing automation lanes. >> I can't find a way to edit them in the Theme Editor or in Preferences>Colors. Does anyone know where to find and how to change those color defaults? @William W. Saunders, Jr., In the theme editor they are under Track view / Clips Pane / Clips See the Foreground / Background colors for tracks 1-10, etc.

Document version 2021.03.21 uploaded and available at URL in First Post. I added a Case Study on Read Automation status display and there are some other minor updates that I can't recall. FYI, the changes in this version arose mostly from my recent development work on MIL-SPEC-ALPHA Release 2, available from its own thread on Themes.

It is smart enough to download the full installer if the difference in versions is greater than 1.

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.

More information on what "stopped working" means, please. All my plugins and third-party stuff continued to work and be available when I re-install CbB. Especially AD2.

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