DOP processes multiplied and never end

[MattiasNYC]

I’m not sure what you’re asking me.

Based on how I work and how I see things there are two separate things to consider:

First is whether or not processing should be applied to all events that refer to the same clip your selected event(s) refer to. I can see the utility in both, and normally I just create new, i.e. I get processing applied only to what I have selected.

Second is whether or not we want “handles” outside of the current edit boundaries. The whole point of that seems to me to be that we’ll be able to adjust our edits after the fact. For dialog editing for example I can have a bunch of edit points between words and syllables, and if I select all of them and apply processing to them all I want to be able to adjust those edits later in case the timing feels off. Right now, in N13, for a lot of processes the 2000ms setting I have is not applied, which means shifting edit points sometimes gives me noise or clicks which I solve by selecting the processing, cutting it, and then pasting it back. I would of course not want the “handles” to be literally applied to the adjacent unselected event and be audible at the same time. Why? Because I didn’t select that event. Additionally I would have no control over where the processing begins in the adjacent event without adjusting the value manually (i.e. the amount of ms).

When I tried this today most often it did not look like what you see in the image, but I could get it to look like that maybe 10-15 times while testing. I just couldn’t figure out what the sequence of commands were that consistently would lead to that outcome.

Either way, it seems unpredictable to me, and therefore unusable.

[Tajika]

Inconsistency is of course never good — this shouldn’t happen.

My point is: if you choose to process the whole file, you don’t need the extended range, as the whole range is processed anyway. The extended range could be discarded if you choose to process the whole file. The extended range is useful if you process into a new file.

[MattiasNYC]

I understand what you mean now. In my example I chose “new” every time.

[Steinberg_ProAudio]

@Tajika

I still have a problem with DOP that has not been fixed in Nuendo 15.0.30:

I have a dialogue track that has been cut into multiple events. I want to denoise all events at once. I select one event and denoise it. When applying, I am asked whether I want to process only the selected event or all events of the file — here I choose “Continue” (= all events). I would now expect all events based on the selected file to be processed. In fact, the effect has been added, but it has not been applied.

Repro DOP Problem

1. Create an empty project
2. Import an audio file
3. Cut the audio file into multiple parts using the scissors tool
4. Select one of the resulting events, press F7 (to open DOP)
5. Insert an EQ with a high-pass filter at 1k
6. Click “Apply”
7. In the dialog that now pops up — asking whether you want to apply the changes only to the selected event or to all events using the same audio material — click “Continue”

→ All events should now be high-pass filtered. In fact, the correct EQ with a high-pass filter at 1k is also inserted in DOP on all events. However, the EQ is only applied/audible on the event where it was originally inserted. On all other events, the EQ with the high-pass filter is present but not applied. Even when clicking “Apply” on these events, the high-pass filter is not applied/audible.

The problem is documented in the video DOP1.

Can you reproduce the issue? I sent this issue to support 7 months ago and they were able to reproduce the issue. However, it’s still not fixed in 15.0.30.

OFFICIAL UPDATE

The issue has been reproduced and added to our list for future fixing.

Thank you Tajika for bringing it to our attention.

[Tajika]

That’s great news, thanks for taking care of that longstanding bug.

[MattiasNYC]

When you fix that new bug please pay close attention to “Extend Process Range”. In my post above you can see how in some cases the extended range applies across the event boundaries into the adjacent event. This behavior is not consistent. It sometimes happens, sometimes not.

Also intermittent is the opening of the dialog for selecting “New Version” or applying to all events sharing the same clip. Sometimes this open, sometimes not.