In episodic series you are doing 3 to 4 episodes simultaneously, often you would be dubbing in hotel rooms and patching it with location dialogue. Its a high stress environment and hardly any time to breathe. So clean dialogue is extracted minus the hotel rumblings, AC and other room echo and noise. Several RX tools are used to achieve it not just dialogue isolate. ProTools is the go to DAW here. Time Management is the glue here.
Same. These became two of my main complaints when I tried Cu 13 days ago. Now they’re in Nuendo 13.
Voice Separator is just another tool at your disposal.
Any dialogue editor working in Post will have all the above mentioned and is using whatever it takes to achieve a good ,result.
Voice Separator was never meant to blow the competition out of the water, just like audio-alignment was not build to be better than AutoAlignPro. And that serves the userbase working in commercials, podcasts, online content extremely well.
Fredo
Speaking of which: I noticed in the live video yesterday that the menus on the Mac all match the rest of the design (dark charcoal). On our Windows computers, the menus are light grey.
So I was right in my assumption. Your answer just matched my quote too well. ![]()
Perhaps with the next update, or the one after that, Steinberg will listen to our pleas to reverse this change. ![]()
But if that were the case, there’s nothing wrong with it.
It would save me money, because I wouldn’t have to keep extra plug-ins that all do (more or less) the same thing.
I may have worded this wrong in the frenzy of discussion yesterday.
What’s going on with VoiceSeparator wasn’t as much a case of tool A is worse than tool B, and therefore I hate tool A. What I did in my test more or less mirrored exactly what was done in the live stream and also demonstrated in the separate Nuendo DX feature highlight, except my results were different.
So it felt more like a bug, not a feature that behaves differently. Bugs are not uncommon in major releases, and it was just disappointing that I couldn’t replace my other tool in place with this new tool, when following exactly what the release demo suggested should work.
After further testing it’s become clear that this may indeed be a ‘bug’. The problem only occurs in the first few frames when there are no handles. It appears the tool needs a few frames of tuning time before it works properly. That’s not something the other tools require, and was not evident in the demo as there they also lowered the slider to or near infinity, but they did so while playback was already going on, not at the start of an event.
It seems like this should be looked at as a bug or improvement, so people cutting this in too close to an event start may find it frustrating. And by all appearance the degradation may exist at lower strength settings too, just not be as apparent and may be missed, which would still make it a problem for discerning operators.
The fix most likely may involve some sort of look ahead to allow the algorithms learning/adaptive logic to see what’s coming when it’s processing the very first frames of an event. That may require an unfortunate latency but that is the nature of these algorithms.
And yes, I have all these other tools, which is why I was able to compare. And as we all know some of these tools work better with some material than others, so I was excited to have one more at my disposal, and somewhat disappointed that a headline feature appears to have a bug in it.
Not sure about anyone else, but I’d really love a customized view for the renderer. When you are so used to working with Dolby’s standalone look that you could position any way you want, being stuck to an overhead view in Nuendo is kind of a bummer.
Noted. But the design, including the drawing itself, remains inconsistent on both platforms.
I’m getting old.
I don’t find a place to download Goyo anywhere. Could you share a link, please?
Right, it was called GoYo during the beta test phase, but the released product is called Clear.
You could say that about exactly every single functionality and plugin in every DAW though as long as it wasn’t as good as alternative X by a third party, right?
Take Pro Tools for example. It has a compressor. Why doesn’t it have one that sounds like a Fairchild 670 or Neve 33609? Does Reaper’s plugins that saturate do the job as well as UA’s Studer?
Yeah, of course if it was better then great, but the question is how far any given DAW maker can reasonably go on any given plugin before it becomes a problem. We users ask for all sorts of things and certainly basic tools are among that. Basic restoration tools have great value as long as the production audio we’re working isn’t too bad.
I think we ended up talking about this specific tool because someone else said it was literally “unusable”. It clearly doesn’t seem to be unusable.
Nobody wins by using hyperbole.
Most definitely. Once the dust settles in a few days, I think we will hopefully return to normal professional discourse.
I suggested some time ago that the view of the Dolby render should be made a little nicer. ![]()
Speaking of Supertone Clear (formerly Goyo), is it working for anyone in DOP? As soon as I put it in DOP, Nuendo crashes. Goyo was working fine - it’s just Clear. I sent support an email last week, haven’t heard back.
Yes, the released version seems to have a bug. Works as insert, not in DOP. For me I can preview it, but when I select ‘Apply’ it jumps back to defaults and becomes a no-op, but doesn’t crash. Need to file a bug report on that.
Same here.
ST-Clear in DOP crashing Nu12 and Nu13 as well.
Last version of Goyo crashed Nu12 too in DOP…
Also I have crashes with Uberloud in DOP.
In general, DOP is the main crash problem for me for the last years, I think they need to look into its code more carefully and make some crash protection for it. If it make sense =)
It doesn’t crash N13 for me, but it stretched the audio around pretty weirdly. A section was pulled forward, another section wasnt. Not by much, just enough to have a slight delay from the other mic.
Yeah, Supertone is clearly broken. GoYo worked fine though.
Fredo
Well, it’s Ai.
The plugin “learns” and fixes.
The plugin needs at least a little bit of time to learn.
Alternative is including a “learn” function (like many others have) before you can apply.
Fredo
Understood. That’s where it would be nice to see some dev effort.
When you use RxConnect and the tools in RX, it’s easy to include handles for RX to work on before you re-apply. When using VoiceIsolate as an insert, having those handles is not always feasible.
In my test I had an event with no handles on a timeline (and no way of extending it to the left) which I had GoYo on it during the original mix. I duplicated the track, took GoYo off and added VoiceIsolate. That didn’t work. Until I cloned some silent section of the event to the left and rendered in place to create a handle.
So yes, AI tools can work in those scenarios. VoiceIsolate seems to have a blind spot in this specific situation at the moment. Again, I’m not saying it’s a bad or unusable tool. But in this discussion here it seems very hard to cut through the noise, that this would be just a good thing for the SB devs to revisit and see if it can be improved. Everybody just responds with ‘well, that’s how it is’, or ‘well, that’s a BS comparison’. So what does it take to have the devs take a look and see if this can be improved? File a ticket? I’m not sure that’s a thing on SB if I remember.
I have spent decades developing software in a previous career, I’m in multiple beta testing programs for other apps. I’m not making this stuff up just because, I like platforms and tools to get better. And I wouldn’t mind Nuendo and it’s plugins to get better, if I can make a contribution to it by pointing out something that could be improved. And as developer, I would appreciate trouble reports with specific details and repeatable test cases, especially on a new module which may not have seen all real-world use cases.
Of course I can keep using GoYo and other tools. And I can use other DAWs. I do favor Nuendo in general and am invested in it. But some of this gets old. End of rant and I’ll leave it at that for VoiceIsolate.
Totally agree! ![]()
regards