Bill Phillips

1 hour ago, Noel Borthwick said:

In newer builds you can directly drop multiple wave files into take lanes and it will create new take lanes as necessary.

Thanks Noel. I stay current when I can. So I have 2019.11 build 63 with the patch. I'll try that. I'd remembered a lot take lane improvements were added in one of the recent updates. Thanks for that. Looks like all I will need to do is bounce to tracks take lanes containing multiple clips to get the clips properly aligned in the new mix project.

I'm seldom happy with a mix. So I end up doing lots of re-mixes and am always looking for easy ways to load the tracks from one mix into a clean mix template for another go at it

37 minutes ago, Gswitz said:

Each wave will get its own track. You can manually move the clips around once imported.

Thanks. I should be able to move the take clips into take lanes.

12 hours ago, Gswitz said:

If you select a single track and click file... import audio it will import them all on individual tracks.

It goes faster if the project sample rate matches that of the files.

Will this method import all takes for tracks with multiple takes?

11 minutes ago, scook said:

The pages are not indexed. It would be nice of they were. While waiting for the situation to change here is a post suggesting how to deal with the current situation

More often that not, I open the CbB help index and search it using the browser.

Could also search the pdf, if one does not want to deal with the web index problem

Thanks for the explanation and workarounds. I'd seen the workarounds post before but forgot them and couldn't find the post.

Why don't CbB documentation searches search the most recent version the CbB online documentation? When I click Help > Documentation at the top left of CbB and then type a search phrase into the search box I get results like those shown in this screenshot. What I want are results from the latest CbB documentation, but I only see results from older pre-Bandlab versions. I think I've seen this question answered before but I can't find the answer so can someone please answer it again or point me to a previous answer. Thanks.

1 hour ago, MediaGary said:

You should play around with an online calculator called IsThisRetina. [ https://www.designcompaniesranked.com/resources/is-this-retina/ ]

The major parameters of how you see your screen are your working distance, the pixels-per-inch density, and the screen size.  The "Retina" distance is an ergonomic figure of how the limits of normal human visual acuity will have the image look no better with additional resolution or pixels-per-inch.  

A backstory may be useful:

I migrated from 28" 1920x1200 used at a distance of 42-inches.  That's an ~81PPI screen that has a Retina Distance (RD) of 43 inches. That's why my aging eyes were happy with it. I was using it just inside the RD value. 

-When I replaced it with a 30" Apple Cinema 2560x1600 at ~100PPI, I struggled to use this screen at 100-percent because the fonts were too small, and I wound up using it at 125-percent, with the concomitant loss of information (quantity of tracks, busses, etc) on the screen.  The RD of that Cinema was 34 inches, and I was far outside of that number with my 42-inch working distance. 

I then got a 40" Samsung and ran it at UHD 3840x2160, and things got worse, because the RD was now 31-inches.  I finally got a 55-inch UHD screen and am happy again at 100-percent.  Guess what?  A 55-inch UHD 3840x2160 is ~80PPI, and an RD value of 42-inches,  just like when I started with the original 28" 1920x1200. 

The calculator says that the 34" 4K display has an RD of 27-inches.  If you work that close, you have a shot. 

Very helpful. Thanks. I never considered the retina distance. My viewing distance is ideally 30"-32" but I don't have room for a 40" display. Also, I've noticed that there don't seem to be any 4K displays in the range of 32"-40." I have about 34" between my monitor speakers. I do have an Ergotron articulated display mount that supports 20 lbs and could support the 32" monitor at 25" viewing distance, though a slightly larger 34" display would be better if there was one.

Without a way to audition the 34" 4K display, I have trouble visualizing the impact it would have. On my 1K display I notice that the Inspector and Console Module widths and heights don't vary. Does that mean that they'd be half as wide and high on a 4K display which has twice the number of horizontal and vertical pixels? I'm also worried about text size. Is there a good way to visualize the what CbB would look like on a 4K display?

I mostly work in Track View with the Console View docked below. I also bounce between full Track View and full Console View depending on what I'm working on. I also usually have several analysis plugins open in the final stages of mixing along with the plugin I'm adjusting.

I have a related question. Can I replace my 27" 1K (1920 x 1080) display with a larger single display (probably 34" max) 4K (3840 x 2160) and have room to display track view (not maximized) and plugin pop-ups around it?

I'm thinking that I don't need the full 27"  for track view because I also have CbB on my Surface Pro 3 which has a 12" diagonal display which is cramped for sure. But somewhere between 12" and 27" would probably work if I could read the text in track view and on the plugin pop-ups.

Is there any way to visualize what that would look like without actually buying the 4K display and trying it? Also, maybe something in between would be better; say 2560 x 1080.

Any suggestions appreciated.

30 minutes ago, Noel Borthwick said:

Holding down shift engaged the quick grouping feature which made it  extract timing from all selected clips. If you want to extract timing from a single clip don't hold down the shift key.

 

Thanks Noel. That exactly describes what happened. I need to review Quick Grouping.

Problem solved. Before dragging the acoustic guitar DI track to the timeline, select all tracks with the Clip Inspector open, hold down the CTRL key and change the Time Base to Absolute. Also, don't hold down SHIFT key when dragging the clip to the timeline. Holding the SHIFT key down seems to trigger some bizarre mixdown behavior in Melodyne.

I'm getting what appears to be unexpected and possibly erroneous results when using the "Copy Melodyne Clip Tempo Map to Cakewalk's Tempo Map" capability explained on page 978 of the 2019.09 PDF Reference Guide and need some help in using the tool.

I'm accustomed to using the "drag a clip to the timeline" method of adjusting the Cakewalk tempo map to the clip tempo. This has worked well for me until now. The band I record doesn't use a click track so the tempo wonders around a little which is fine. I usually drag the acoustic guitar DI track to the timeline to set the project tempo and get the results I want, a project timeline that follows the acoustic guitar DI tempo. But the results I get now seem erroneous to me.

My understanding of what should happen is that the CbB project beats per minute tempo map will be adjusted to match the acoustic guitar without affecting the absolute time position and length of any clip.  All clips should remain exactly where they are with respect to milliseconds and samples rulers. But that doesn't appear to be what's happening for the project I'm working on shown here before the tempo is adjusted. If I hold down the SHIFT key and drag the acoustic guitar DI clip to the timeline Melodyne appears to go through every track and create a region effect and mix it down which to me is not only not necessary but also possibly changing the audio of each track.

When Melodyne is done the tempo map is correct, but I don't know why most tracks were mixed down by Melodyne and the tracks with clips that don't start at the beginning are time shifted which seems to confirm my suspensions that other tracks were stretched.

I've read through the 2019.09 PDF documentation page 978 and I think I'm following the instructions. The instructions don't mention the shift key, but I worry about moving the clip left or right as I drag it.

I also tried another method of creating a Melodyne RX for the acoustic guitar DI track and adjusting the project tempo to match the clip in Melodyne and then closing the region effect. The results appear to be the same because the clips that didn't start at the beginning are still time shifted. This shouldn't happen. What am I doing wrong?

For clarity some of the tracks (including the acoustic guitar DI track) have four to six take lanes which don't show up in the screenshots and it's possible that take lanes are adversely affecting the tempo map change process.

Dare, reading through your comments, it appears that you've abandoned CbB for now and are investigating other DAWs. That seems to be a good idea and will give you another point of reference. So my responses to your questions and explanations below probably won't be much use to you now.  But should you revisit CbB in the future, hopefully some of my responses will be useful then.

On 10/29/2019 at 11:04 AM, Dare Rihter said:

Did You personally made clean install Win10 Creator to get working system?

Yes, as you noted, clean installs are not as important now as they were in the past and they are time consuming, but I still like to start that way. I suggested it to you because the problems you were reporting seemed to be very unlikely which made me think there might be serious problems with your OS or other applications.

On 10/29/2019 at 11:04 AM, Dare Rihter said:

On that machine i have a lot of worthwhile software that must run for business purposes and that's not really easy decision for me.

This other software could be contributing significantly to your problem. You might want to check that out.

On 10/29/2019 at 11:04 AM, Dare Rihter said:

BTW, do You use take lanes for recording? My latest problem on take lanes (multiple on one track) was dissapearing recorded audio materials and total mess up with recorded audio (weird clip splits, putting everything on last lane, some clips simply dissapeared, also from disk (!) etc). 

I am trying to learn to use take lanes. So far they are a challenge. I've learned that doing things in the right order is really important, but I still have problems. One thing that I believe is recommended by documentation is turn of the Comp Smart Tool and then find the Mute tool which took me a while. The Mute tool can quickly undo selection mistakes. Take lanes seem to automatically split take clips that are longer than others which can also cause problems with things like drag moves that tend to leave the automatically generated clips behind or cover them up. I've still got a lot to learn here.

5 hours ago, Jan said:

Could you elaborate a bit more about the "changing buffer size while CbB is open"? What exactly is the issue and what are the workarounds? Thanks!

Yes. I'm still using the 4.63.24 which I think is the latest version available for my 1st gen 18i8 and I thought it was working perfectly until I popped a project open to make this screenshot for this post. The first time I clicked the ASIO Panel button on the Driver Settings Preferences page,  the Scarllet Settings dialog box opened on top as it should. But on subsequent times the Scarllet Settings dialog box did not open on top. It opened behind the CbB window, So the workaround I use to find it and make a buffer size change, I close the Preferences dialog, reduce the size of the CbB window and drag the CbB window to the left to uncover the Scarllet Settings dialog box. So it works fine, you just have to find it to use it. Again, I actually thought this was fixed but it's not and I'm not sure who should fix it. I've assumed that should be Focusrite, but I'm not sure.  Let me know it the workaround is still not clear.

Is there a way to change muted clip colors in take lanes?  I use the Tungsten Theme where muted clips in take lanes are about the same color of gray as the background. I'd like to use a different color but haven't found a color option under preferences and it appears that the clip color options under Clip Properties don't appear to have any affect over clips in take lanes.

10 hours ago, Dare Rihter said:

Welcome to further debate about my rare and highly specific troubles. Or better kick a** somebody in CW dev team. Suppose, nobody else has troubles like me? Or end users accept testing just because software is free (until it's tested enough, that can be selled to the same users?).

Best wishes for success with political excuses for bad software

Dare, really; who are you debating?

I'm sorry that you are experiencing so many "rare and highly specific showstopper" problems. I'm assuming that you are able to reproduce those problems, describe them in detail in your bug reports, and hopefully can send dump files are even example projects to the support folks. If not, support staff will probably have problems understanding and fixing the bugs you are seeing.

My problem is that I've been a on-again, off-again SONAR and now CbB user for 15 years and somehow I've always been able to use the SONAR/CbB to record and mix audio. I suppose I did experience "showstoppers" from time to time, but they must of been rare, because I don't remember any of them.

So I'm wondering if the problems you're seeing are more related to your DAW hardware, other applications and Windows 10 64x configuration than they are to CbB. Since, you are apparently unable to accomplish anything worthwhile, maybe now would be a good time to clean up, all of your resource/project harddrives, and clean install Windows 10 Creator Edition and CbB along with any other applications on your DAW.

Anyone using Microsoft's OneDrive for DAW files?  To me it looks like a good option because I have a Microsoft Office 365 subscription which includes 1TB OneDrive space for each of six users. I'm assuming that I can have access to all 6TBs which I think is plenty for my DAW and personal files.

My plan is to put all documents and resource/install files on OneDrive and mirrored in a local OneDrive folder. I'll keep project files on a local drive and manually drag them to a backup OneDrive folder that isn't mirrored on a local OneDrive folder. Does this seem like a reasonable plan?

On 10/19/2019 at 10:54 PM, User 905133 said:

 Thank's to scook's very handy VST Inventory program

Where can I find the scook very handy VST Inventory program?  Thanks.

That appears to have worked.

Thanks scook.

Bingo! Thanks scook. NIMBUS was not in the VST3 excluded list. So I tried the VST3 Reset from preferences with "Scan in Sandbox" and "Generate Scan Log" enabled. NIMBUS VST3 is now available. I did get "Wrong computer id" notifications for Additive Keys and Drums during the Reset scan that I will review, but I think Additive Keys and Drums are working fine.

Thanks again! No regedits required. Yea!

21 hours ago, Blindeddie said:

I have had this issue before,  all were activated prior to scanning, but did not show up until I ran as Admin...whether its required or not is besides the point, that is what worked for me...doing it has worked for me many times and usually solves my problems when it comes to plugins. Its the first thing I do when I have issues.

Peace,

Blindeddie

Thanks Blindeddie. I tried running as Admin and rescanning. It didn't help this time.

22 hours ago, scook said:

As a class, iLok authorized plug-ins do not require DAWs to run as administrator. It is a good idea to activate iLoked plug-ins using the iLok License Manager before scanning though. Failing to activate plug-ins before scanning can result in the plug-in landing in the excluded list. There are remedies for plug-ins that get excluded often times it is as simple as activating then re-scanning failed plug-ins.

I use the License Manager.  Here's a screenshot showing NIMBUS authorization as active. the VST2 version works, but I prefer using VST3. I've already tried uninstalling and re-installing NIMBUS. That didn't help. I just did a rescan which also didn't help. Thanks.

23 hours ago, scook said:

I would be surprised if running as administrator makes a difference but it is an easy test and if it works, it would save a lot of typing. So, try that first. Don't have the plug-in to test but have several ideas if this suggestion does not solve the problem.

It didn't. Interested in your other suggestions. Thanks.

23 hours ago, Blindeddie said:

Try running CbB as Administrator.  right click the CbB icon and select Run as Administrator then do a rescan.  I had a similar issue and that worked for me.

Peace,

Blindeddie

Thanks. Just tried that running CbB as Administrator and rescanning VSTS. NIMBUS VST3 still missing from browser and Plugin Manager and track FX bin Insert audio plugins dropdown. Izotope says they can't help.

I just installed a reverb plugin NIMBUS along with another reverb plugin R4. The R4 VST3 shows up in the browser, plugin manager and in track FX dropdowns but NIMBUS does not. See browser, plugin manager  screenshots. I've also included a VST3 Folder screenshot showing that NIMBUS VST3 is available. The browser screenshot shows search results for NIMBUS which only turned up the VST2 version under uncharacterized.

I've uninstalled and reinstalled NIMBUS, restarted CbB several times and restarted my PC.

Any suggestions on how to fix this appreciated.

14 hours ago, Colin Nicholls said:

Yeah, I did that. I'm offered the download for Focusrite Control 3.4.4. I'm sure that if I installed it, it would install the actual driver with the updated version number.

Available drivers vary based on your hardware & firmware. In the notes for the 4.63.24.564 driver I think it listed the 1st & 2nd gen devices that can use it.