Hi patriciadaley and welcome to the forum!
You didn't complete the editing on the events (sections). So for example, you edited an event by detecting transients. You edited some parts but moved on to other events to edit those. You never finalized the event. To finalize an edit such as an audio event, right click on it and select to bounce the selection. Then the track or event color will return.

Welcome to the forum!

Lokeyfly is right, you're in "Show Bend Markers" mode, that's why the audio events are black. However, Bounce is not the solution (there's no need to bounce and create redundant new audio files, and with bouncing you will loose the original event).

You can just right-click the event and uncheck "Bend Markers". This will return to the "normal" mode with your regular colors...

Thanks! It's the first time I've used the bend tool. I don't think I could have figured that out. Much appreciated!

jazzundso wroteWelcome to the forum!

Lokeyfly is right, you're in "Show Bend Markers" mode, that's why the audio events are black. However, Bounce is not the solution (there's no need to bounce and create redundant new audio files, and with bouncing you will loose the original event).

You can just right-click the event and uncheck "Bend Markers". This will return to the "normal" mode with your regular colors...

Ah, I didn't realize or I just forgot to uncheck bend marker, probably thinking the event didn't hold.
Thx.

As to bouncing though, one won't lose the original event ever, really. The event is a clip still in the audio pool. I'm never worried about too many clips as it's so easy to eventually remove all unused audio clips. That's a rather defining moment to be aware of, but I Save As to a new song, so there's never any old clip issue.

Thank you for the uncheck reminder though!

Lokeyfly wroteAs to bouncing though, one won't lose the original event ever, really. The event is a clip still in the audio pool.

The event is not the clip. Sure, you won't lose the clip (audio file). But in case you have applied any editing to the event (such as fades, volume change, EventFX) this will be baked in when bouncing so you lose these edits as parameter changes and can't modify these changes anymore (unless you start from scratch). That's what I meant when I said you lose the original event.

jazzundso wrote

Lokeyfly wroteAs to bouncing though, one won't lose the original event ever, really. The event is a clip still in the audio pool.

The event is not the clip. Sure, you won't lose the clip (audio file). But in case you have applied any editing to the event (such as fades, volume change, EventFX) this will be baked in when bouncing so you lose these edits as parameter changes and can't modify these changes anymore (unless you start from scratch). That's what I meant when I said you lose the original event.

I never said the event is the clip. I said the event is a clip. Meaning coming from or changing to more clips. The point is a history of finalized edits is accessible.

Audio events at some point don't sit there with edits not printed (baked as you say). Sure, they can if that was someone's intent is not to do anything with the final result, such as stem, or solidify the resultant edit. Perhaps you work with a dozen or so partially edited audio events. I think its fair to say many if not more, dont, particularly with audio. With audio, many often tend to poop or get off the pot. (If I'm paraphrasing).

I think your point is in-process edits, and that's probably fair to say. Though editing audio typically requires not having them sit and lay around half edited. They inevitably do get printed (bounced).

To extend an olive branch. Sure, I probably should have said an event is from a clip. My bad.

Yea my definition of destructive editing is from the cubase days where you processed a fade in off line and you changed the original file.

When comping and you have a track with many pieces you need to bounce that to take it to melodyne but you could save a copy of all your edits if you think the editing has to be revisited. So Save a copy and bounce a copy.

That's the only destructive part of bouncing is loosing your edits. I quit doing that because I never revisited any editing.

Bouncing consolidates and replaces long files with relevant content. After bouncing to go into melodyne I bounce to get rid of the melodyne edits. I see an overhead with leaving them in the song as far as boot up time. I use it to print fx and use different patches from an instrument on one track.

I do not think of bouncing as destructive myself.