Steinber nuendo software#

Another override (in this case is overriding the effects of the cut I just made and its own creation of an individual event) Schermata alle 21.38.27 1630×1184 75.8 KBīut since but since vertical range rules over this knowledge and they’re adjacent (but they’re technically separated tho’) it creates 1 single file. Nuendo states Event Start - Event Ends, which tells me that Nuendo perfectly knows it’s a single event Or this another example of confusing behavior: It is always best practice to bounce all consecutive audio events which use effects in order to consolidate all effects tailsĪgree with the practice but here’s what happens. A it’s obvs not a design choice otherwise why spending time coding, implementing, testing,debugging both if one nulls the other? If the range exceeds then it nulls the “separated events function” and blends multiple events.Īnd now you don’t get the declared “separated events” anymore and this option is overridden without notice. (at least in game dev)īased on my reverse engineering check, I’m pretty sure that CB/Nuendo’s rendering/exporting function - while it offers many settings - is range based only.īut both rendering/exporting function is also equipped with the tail function.īased on my guess, the tail function is a slave of the range. Otherwise, in my world, is half done work. If you add a function you need to make sure that doesn’t create conflicts with the existing functions. In a well designed multi function tool there should be no complications.

In this way any complications with tails will be avoided But this wasn’t related to this matter but to the fact, I suspect, that Nuendo is not familiar with APFS formatted drives. and this is already a sign of some voids in the code. So much that I made Nuendo crash 4 times in like 30 mins. So I actually spent around 3 hours on this feature alone performing and repeating actions. Obvs I’m not a regular user and being a game dev and tools designer, when I see these kind of stuff, the first things that pops into my head is to try to reverse engineer it and see if I can get a clue of how it’s designed. In case you’re interested for the love of conversation, for the other issue, I still think it’s not an optimized design. I invested in Nuendo and happy to change my workflow Yeah, similar in Nuendo, just more clunky but doable and that’s what matters. Before commencing, it is always best practice to export all consecutive audio events which use effects in order to consolidate all effects tails - in this way any complications with tails will be avoided when exporting as separate audio files. ‘Export Selected Events’ was designed specifically for users who want to export audio events as separate files with no regard for the timeline, such as those working with game audio, who may need to export a large number of individual audio events as seperate audio files. To achieve what you originally wanted… do the following:ġ - if using real-time reverb or delay on consecutive events on the same track, consolidate all events first to include all tails from effects associated with each event (this is best practice when exporting consecutive events as seperate audio files).Ģ - make sure the tracks on which the events are located are not mutedģ - select all the events you wish to exportĤ - select File / Export / Selected Eventsĥ - select ‘As Separate Events’ as the mode in the Export Selected Events dialogueĦ - select your processing choice in the Export Selected Events dialogueħ - if exporting consecutive events with effects which have a tail and you did not consolidate as outlined in step 1, set the tail in the Export Selected Events dialogue to 1ms less than the shortest gap between the events you are exporting.Ĩ - select a file location in the Export Selected Events dialogue and set up an appropriate naming scheme

If you want to export audio events as seperate events in Nuendo it’s really quite simple. You don’t need cycle markers at all in order to do the task you outlined in your first post above.

Steinber nuendo software#

Nuendo is certainly not perfect but before making such a statement it might be best to really get to know the software first. As a long time audio tools designer, my strong bet is that Nuendo’s rendering architecture has been fitted with many functionalities but it’s only range-based and, again my personal opinion, is a pretty limited design that creates - and that’s a legit fact - conflicts and inconsistencies with other rendering features like the example You are of course entitled to your opinion but your statement perhaps shows some misunderstandings of the design.