Is Fielder Audio as good and complete as Dolby’s Renderer or Nuendo’s in-house Renderer?
I believe Fiedler is very similar look/workflow and full-featured. Of course, a bit more cumbersome to set up as you have to insert the plugin in on every track. That’s one reason I like Cubendo (native Atmos renderer) But here is a great video about it:
Although I find the concept of the Atmos Composer interesting and exciting, I prefer the Atmos Renderer integrated into Nuendo. I like simple solutions. Using the Atmos Composer reminds me a bit of setting up the external Dolby Atmos renderer. And I always start crying and shaking when I think about setting up the external Atmos renderer…
REAPER is a DAW with excellent value for money and a great community. But the Steinberg community is just as great. Also, the lack of Atmos is a deal breaker for us. Furthermore, many of the “3D plug-ins” we use are not officially and/or fully supported by REAPER. But if you’re looking for a lot of features for little money, REAPER is a good choice.
Yes, but you can read in C12/N12 compatibility specs: " The following features/functions are not yet available when running in native Apple silicon mode:
- MPEX Time-stretch and Pitch-shift algorithms are not available!"
The word is YET, so I supposed that it will come back on apple silicon some day, isn’t?
Each track or each group? Because with 250 tracks…
I know what you mean. I have a Dante network here and a separate PC with an AIC card but can’t bring myself to implement the external renderer (even though only $99) because of the hassle. Was hoping N13 would have the .mp4 rendering capabilities but then what would we need the external renderer for? If N13 had ripple edit I could live with all its other shortcomings.
Well I think you could place one for your bed but any object would need its own plugin.
Looks like each track. To me it looks more cumbersome to use than it would be to just learn a different DAW. Great that people are able to extend into Atmos, but not very elegant. And it might be more reasonable to use with music which tends to be far more static than scripted fiction for example.
I think there are advantages for the B-chain, for example grouping speakers/channels together as well as delays/EQ etc.
I have the external renderer and it’s useful for exporting to MP4, once the ADM file has been created. You import the ADM into the standalone Dolby renderer and export your MP4.
Not interesting from a CPU usage point of view.
I meant then we would have less of a reason to purchase the external renderer from Dolby if the internal one was more full featured. But you are right about the advantages. Anyway, if I need an MP4 I will just send my .adm to cmbourget.
We also do (UHD) Blu-ray authoring. Luckily we have the Dolby Media Encoder and the Encoding Engine. That’s why we only use the external renderer on the computer with PT. But it would be nice if Nuendo could export an MP4 file. However, this would mean implementing the E-AC-3 codec in Nuendo. This would probably involve licensing costs. Maybe Steinberg should go the same way with E-AC-3 as they did with the video decoder for Avid DNxHD!? (If Dolby ever wants to make this possible.)
Can be. However, as I am not a Steinberg employee and do not have a crystal ball, I do not know.
I get the feeling that Dolby does NOT allow this. I can’t confirm it, because Steinberg won’t say (I suspect they are under NDA) and Dolby themselves are very cagey but given that the encoder included in DAWs seems to be the same features in all the DAWs that include it, and the fact that Dolby won’t answer the question, I suspect it is the case. I suspect that they have only one version they license and it has the features they are willing to give. They’ve increased those with time (like adding 9.1.6) but they don’t let companies just license other features.
I don’t know that Dolby will ever stop being jerks about it, they seem to like the idea that we should pay yearly to use their stuff. I’m hoping that ffmpeg may get Atmos support, it can do E-AC3 encoding already, and I think it knows how to decode Atmos from TrueHD sources, so I’m hopeful they’ll keep working on it and it’ll get full Atmos encoding support at some point.
We’re in the Nuendo 13 thread, so let me make a general comment.
I’m going to need to upgrade from 7.1.4 to 9.1.4. So I was looking at N13 despite my strong misgivings about the interface and the lack of certain workflow improvements, as I’ve explained many times before. But then I read on this forum about the huge number of bugs and problems encountered by new N13 users. My God, it makes me want to leave N12 even less. I wonder if SB will have time to fix all this in the promised (soon to be released) version where the major interface problems will be corrected. I have a feeling it’ll take several updates. And that I’ll have to wait for 9.1.4…
Update (2023-11-21): the list of bugs is growing.
For this reason, I would like to see MPEG-H become more popular. The fact that Steinberg has integrated MPEG-H into Nuendo 13 is perhaps a first step towards making MPEG-H more known and popular. Pro Tools has also integrated MPEG-H since July this year. Admittedly, I don’t have much hope. Dolby’s market power is simply too great, especially in the US. But I’m not giving up hope.
9.1.4 or 9.1.6? The internal Atmos renderer only supports 9.1.6.
Could you please let us know what bugs you’re talking about? I’m sure there are several people that haven’t yet started on v13 yet that would like to know.
My guess is that, unfortunately, Dolby wins out mostly because of their name and because they were first. I think for music, the immersive fad will pass, just like surround did, and we’ll only see a bit actually made for Atmos, and some other stuff just quickly plugin-upsampled. I think music will largely continue to be stereo, as that’s just how people listen to it.
For film it seems like it’ll probably stick around, but that is where Dolby just has a stranglehold. Maybe theaters will hop over to MPEG-H but to the extent any of them are doing it, it seems to be Atmos. All the receivers out there support Atmos, most support DTS-X, only a couple support MPEG-H.
I mean I hope I’m wrong, but I’ve noticed that once a format gets its claws in, everything seems to stick with that, even if there’s a better solution that comes later.