Fairlight markers can't be placed precisely

Markers are heavily crippled in Fairlight because they reject precise positioning. This is not appropriate or acceptable on audio tracks in an audio editor. Here's a screen grab of the behavior in an audio-only project; this audio comes from audio-only files, not associated with any video.

I believe markers are tied to video frames, not audio samples.

Thanks for the reply. That's a problem that needs to be fixed. It's incredible that they integrated a whole DAW into the product and it's crippled to uselessness.

It is a DAW meant for FILM production.

But...we can request new features at the link below.

viewforum.php?f=33

Best practice is to search first, to see if someone already asked. If not, post one idea per thread with a very brief description of the idea in the thread's title.

It is a DAW meant for FILM production.

And? This doesn't eliminate the necessity for precise editing. Sometimes, for example, you need to cut audio in the middle of word to save a shot or a recording.

It is a DAW meant for FILM production.

And? This doesn't eliminate the necessity for precise editing. Sometimes, for example, you need to cut audio in the middle of word to save a shot or a recording.

Couple things .. Markers not being sample based certainly doesn’t make fairlight “unusable”, nor unable to do precision editing ..

In and out points work perfectly fine at sub frame levels, and so does the blade tool. Is fairlight perfect? No far from it, but at the same time I’ve never ran into an edit I could not accomplish.

Worst case link to an external sample editor if you want a different workflow ..

This doesn't eliminate the necessity for precise editing.

Markers and editing are two different things. We CAN edit and mix at the sample level. We just can't add a Marker there.

We CAN edit and mix at the sample level. We just can't add a Marker there.

Then that's a broken marker system. You can even set the time display to show the time in samples.

Then that's a broken marker system.

I think it works for a film production environment. The video player wouldn't get you anywhere but to a frame anyway.

I just provided an example of why it does not work in a film-production environment. There's no reason to cripple it this way. The video player is irrelevant; we're on a DAW page.

Well, I'm not saying Resolve has to work this way, or even that it should work this way. Only that I understand why it works this way. To me, it makes sense.

But if you post up your idea in the Feature Request section, others who want it can join in, and maybe one day it'll get done. (I've had quite a few of my request turn up over the years.)

Thanks. I consider this a bug, therefore posted it here.

Thanks. I consider this a bug, therefore posted it here.

Yes I get what you are saying, it's always been like this in Fairlight, so not a 19 Beta bug but still, I also think it's a pain in the butt. Its a very unnatural way of working for audio people as you can't use snap to markers because they are mostly in the wrong position.

I am glad you brought this up as its something that needs a solution. Even if markers are not changed, how about instead introducing an Audio Marker tool/menu in addition to the normal markers on the Fairlight page?

Is this able to be move to the DaVinci Resolve Feature Requests part of the forum?

There are many reasons to have the possibility to place a marker precisely placed on a clip.
I often have to struggle when I want to align precisely a song cut in two clips, put in different tracks.
Or if I'm syncing a SFX or if I want to put markers precisely on the beats of a song...
It can be done, everything can be done the way Fairlight is now, but it would be done way faster if we could place a marker at a sample level position.
Just look at how ProTools manage this, nothing so complicated.
Hope this will be fixed soon.

Thanks for the reply, Daz.

Feel free to dupe it over there and link to this one if you like. I reject the current behavior as defective; so while it may not have been introduced in version 19, we can't really be expected to know when a bug was introduced. Therefore I think this forum is fair game for any problem that exists in the latest build.