RBH

I'm moving from a 2006 new construction house. The electrical is very nice in this house, 200 amp, everything grounded, the line in is buried. Next week I'm moving to a 1966 house - everything 2 wire , no grounds. One item on my future agenda is to run new electric everywhere I can access it. I'm getting too old for this stuff anymore. Luckily or not - my studio space is in the basement and running new lines there should be easier.

also - a very quick method is to zoom out until the entire track length is visible in PRV. Go to the extreme right hand side and right click and drag your mouse left to capture only the velocity range you wish to edit. It should select only those notes defined by the window height that grabs the velocities. - hit delete. It becomes very quick and intuitive to select velocities ranges this way for other kinds of edits.

One way to quickly que playback a few bars before recording is that I assign a keybind ( ctrl < to move back 1 measure and I set ctrl > to forward 1 measure. It becomes second nature and allows quick short movements. For other ques I use markers and set them a few bars ahead of basic punch points ( verses, chorus, bridge etc.

Make sure when selecting Punch that you click the selection button just beneath it.

Craig - superb Demo ! This is an excellent primer for someone starting out and needing clear concise examples.

I think it may look strange to you because you're looking at the Clip Audio Transients view in the Before view and looking at the Clips view in the After view. It looks like the Audio Transients view markers are covering the initial transient of the wave. This would be normal. Maybe try viewing it in Clips view both Before and After. I would hope they look the same, that's how it appears in my CbB. Edit - Maybe I'm mis-understanding : is the issue that the scaling of the wave form is different ? Is it possible that you have increased the value of the automation lane? I seem to do that and not catch it until the waveform re-draws.

I like the amp. I think it's horn loaded.

Reminds me a little of PFM. The moog is the best part Bit, IMO. Is that a CP 70 for piano ?

I sold a Taurus 1 a few years back after resuscitating it back from near dead. I bought it in a package deal about 25 years ago and lent it to my brother who let mice nest in it. ( nice ) so I was running out of room - and sold it to someone who said they've been wanting one forever and couldn't find them anymore. I got decent buck out of it - and was glad to let it go to some one who REALLY REALLY wanted one. The guy marked it up 800.00 bucks and sold it 3 weeks later. There is no lesson to be learned.

Me and 3 of my friends all had mid 70's Pinto's, back in the late 70's . We used to go ice racing in them.... what a blast. Figuratively speaking.

I get this occasionally as well. I believe that I've just run the I-lock license manager and it refreshes the license. I don't know for sure but I think there is a time out on the Lexicon licensing that requires a refresh. I assume that it's an anti pirating measure from the plug vendor.

The install on Windows 7 operates perfectly on my ( quite - quaint ) old set-up.

If you have a known time computed for one track - you can set-up the nudge feature to offset the additional tracks you wish to move. Quick and easy way to move multiple tracks accurately. Also - you can select all the tracks you want to move Right click on one of the track headers and make a " Selection group " Then when selecting one of those tracks you will automatically select all of them.

In the export window there is button to select Project or Selection. Try using ( Selection ) for just exporting a selected clip.

There is a utility called Audio finder. It may take a while to go through your drives - but it may pay off if you have not permanently deleted your files. Utilities > CWAF Tool The Utilities > CWAF Tool command opens the Cakewalk Audio Finder Tool, which lets you locate audio files that are used in your Cakewalk projects. For more information about Cakewalk Audio Finder Tool, see the Cakewalk Audio Finder Tool online Help.

Yea - They're top notch. Wish I could afford to get all of their plugs.

Thanks Steve.

Is there any view in an open project that shows the full drive path ? It would be very useful to have that at a glance - or not too deeply hidden. The Start screen( recent projects ) has an icon that shows project information. That would be a great place to show the full drive path for the project opening. I'm wondering if I'm just not seeing it with the open project.

How about providing a status of your installation of the Apollo. 1. Do you have playback of any track through the Apollo to your monitors? - if not - set the track output to the Apollo's main or monitor out. 2. Do you have instrument inputs into the Apollo and are seeing meters light up - on the Apollo ? if so : Select a track and set it's input to whatever Apollo's input corresponds to your instrument in. Set the input echo to on. Place the track in record mode. Hit (R) and Record away. It will automatically select monitoring status whether you are in record or playback mode. There are several recording modes. Sound on Sound - Over write mode - Comping mode with looping etc. This is basic info for any interface though. You can get deeper into the Apollo's capabilities for unison processing on the way in.

Looks like an introductory discount . Demo sounds very good. https://www.orangetreesamples.com/products/the-famous-e-electric-piano

It takes time to load VSTI's samples that might be required for real time play back. Loading audio regions ( i guess means just that - Time taken to read audio files from disk and get them aligned and ready for playback. I've noticed some projects take longer to load than others - it's usually a resource hungry VST instrument or 2 on my system. Some VST's take a long time to load on their own as well - I know that Scuffham amps S-gear can take awhile to load on my system. It has it's internal list and Ir's to load until it's ready/.

NOTE * be cautious when deleting and removing associated tracks. You should use the " replace synth " dialogue when testing instruments. If those instruments are associated ( assigned ) from a midi track you wish to save or archive - you will lose those midi tracks. I have complained about this in the past, as I think there should never be an instance where you can accidentally erase raw data tracks ( at least without a redundant warning ). This can happen even with careful culling through track assignments. I think it can even hit hidden tracks. The first time I came across the " remove associated tracks " I assumed it would just remove the Audio tracks assigned to the instrument being removed. No - it also removes any MIDI track assigned to the instrument as well. Imagine having 15-20 or so separate midi drum tracks assigned to multiple drum instruments. It can be easy to over look where those tracks are assigned if deleting one of the instruments.

I've stopped updates to all other DAWS except CbB. When I re-build and go for a clean new set-up. It will be a pure CbB daw. It still amazes me to open a 25 + year old project - and do a little updating to current plugs or VSTi - and bada bing..... 1989 ... I plug in a guitar and I'm playing new agey puke jazz all over again. wow - maybe that's not a good thing.

It sounds like you're " merging " clips instead of tracks. Make sure you are in sound on sound mode. Do you see the notes in the piano roll view after the drag ? I would check that - in the sections you are not hearing - make sure there notes there. ....... .bounce to clip after the moves.

I purchased Sonar Pro just a few months before the Gibson " thing " . That was an upgrade from Sonar 5 ! But - I made it a clean install at the time. I do wish I could at least upgrade to the original Splat version to get the added pro channels modules. I didn't want to take on all the added content at the time because I thought the loops and stuff were not worth it. I do wish CbB would make Cake updated to at least Splat version for plug-in content. That would put all new installations at a common starting point and we could then share pre-sets etc now that Pro Modules can save presets. What say Ye CbB ?