DOP processes multiplied and never end

Nuendo
21

We will have a dev meeting tomorrow, let me come back to you then with further information.

22

I can confirm that .

23

Hello,
the current analysis shows that this bug occurs as soon as iZotope RX is involved. The way to solve this issue is different compared to “normal” plug-ins and might also require further information from iZotope. Given the current situation at NI, we hope that we will get dev support in case necessary. However, we’ll try to do it on our own first. Realistically, this will probably take 2-3 more months to be solved, but it is definitely now on the fixlist.

Thanks,

Timo

24

Thanks for the information and confirmation that this is indeed an RX only issue.

It seems Izotope are not willing or able to fix issues for longer than one point release.

Given the current situation this should be reason enough for Nuendo users to look for alternatives. Acon Digital is a good one, Spectralayers is another one, any other alternatives for spectral editing in the DOP?

25

Thanks.

I hate to say it, but judging from the behavior and history of iZotope I have very little confidence in them helping out. I agree with the previous poster that finding alternatives are the better option. In fact, I might even say that IF RX is truly the only problem then you might as well leave that crap behind and focus on more important matters, for example expanding features for DOP (see here: Plugins, DOP, other processing - Features Request )…. IF that is the case.

I’ll investigate on my end what other plugins can take the place of the RX ones I use for DOP.

26

Timo,

I forgot to add: there is still the problem with DOP processes not processing in the “extended range” outside of the edit boundaries. Is that also failing because an RX process is present? Because I’ve seen that with Acon Digital processing for example.

It seems to be a differeng bug / issue.

27

This bug happens to me even without using any RX plugins on the DOP chain.

28

Well, let us hope then that this gets solved in Nuendo v15.

I have little hope these days.

29

I’m hoping since N8.

N7 is the last stable and almost bug free version.

30

Yep. Those were the days.

31

Can we get an update on this please?

The problems with DOP are not limited to iZotope RX, and it’s now been 3 months since our last communication, 9 months since I started this thread, and I don’t know how long since v14 or since these problems started and were first detected.

32

Hi Matthias,

this issue was fixed in the latest 15.0.30 maintenance. In case you could also confirm, that would be much appreciated.

Thanks,

Timo

33

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.

34

"Oh! Right, same bug. Although I must say I always have the ‘create new version’ option enabled. Even if it means losing free space. And I’m in the habit of manually selecting all the events to be processed offline.

It happens in Nuendo 14 too. Maybe the process actually should disappear from the DOP in subsequent regions. Sorry, Events XD"

35

You’re right, it’s an old bug. Up to now, working on multiple events was a mess and “create new version” in my experience was the only work around. In the latest update they fixed the bug when working on multiple events would multiply the processes in DOP.

Now there’s only the bug above left.

36

I started looking at DOP again today, and before I checked what I reported in the first post I tried the bug you guys are talking about with events that are split and reference the same audio clip.

Immediately I ran into this when applying one process to one event (after split):

image
image1774×541 41.8 KB

As you can see the processing applied to the second event (Low-cut) is applied to the last section of the first event as well.

I also ran into another problem regarding “Open Options Dialog” “On Processing Shared Clips”, which is appears inconsistently.

I’m too busy to troubleshoot this right now so I’ll have to revisit it later, but sufficed to say I don’t really think you can fully trust DOP in N15.

37

Back to Nuendo 13 for now.

38

This is because you set “extend processing range” to 2000ms. With this set, DOP extends the processed range 2000ms before and after the selected event.

Thanks for confirming the issue.

39

I can do the exact same thing and sometimes it shows like that and sometimes it doesn’t. It’s inconsistent. I certainly want the processing to take place, but not to the adjacent event. It should apply to the “unseen” portion of the selected event, so that if I want to adjust the boundaries of the edit at a later point I don’t have to do the edit first, cut the processing chain, and then re-apply it (like I do now in N13).

40

But does it make sense to extend the processing range if you process the whole file anyway? I think that would be useful if you create a new version for that event.

It’s still strange, that it turns up in the neigbouring event.