iXML metadata is lost when using "Split Multi-Channel to Mono"

Nuendo
1

Hi Steinberg team and users,

I noticed this issue depending on the method used to import audio from a field recorder.

Test results are as follows:

Environment:

  • Application: Nuendo
  • Version: 14.0.41
  • OS: Windows 11 25H2

Source:

  • Multichannel WAV recorded on Sound Devices field recorders
  • 32-bit float and 24-bit WAV files
  • Files contain BWF metadata (including timecode) and iXML metadata

Results:

  1. Normal Audio Import
  • Importing the multichannel WAV file normally
  • BWF metadata (including timecode) and iXML metadata are preserved
  1. “Split Multi-Channel to Mono”
  • Using “Split Multi-Channel to Mono” during import
  • Only BWF timecode (Time Reference / Origination Time) is preserved
  • All other BWF metadata and iXML / channel-related metadata are lost

This behavior is fully reproducible.
The audio itself is correct, but metadata is removed only when using
“Split Multi-Channel to Mono”.

This suggests that the metadata loss is not caused by the source file itself,
but by the split process.

For post-production workflows—especially location sound recorded on Sound Devices
and other professional field recorders—metadata preservation is critical,
so this behavior is problematic.

Could you please clarify:

  • Is this expected behavior?
  • A known limitation?
  • Or a bug that could be addressed in future versions?

Thank you.

2

No ! haha. this is terrible for post and I think has been mentioned before. I use other apps to work around this but Nuendo should never touch metadata on these kind of actions.

1 Like
3

Thanks for confirming. Good to know this is not considered expected behavior. Hopefully this can be addressed, as this is a critical issue for real-world post-production workflows.

4

Please either mark this thread “issue” or find the thread(s) klfnk referenced and bump them if they are marked “issue”…… then “pray” if you’re religious I guess. Or just “hope” or whatever. I have little faith in several critical issues for real-world post-production workflows getting solved. You’re basically yelling into a void.

1 Like