Anyone using the Field Recorder Import feature?

[nabw]

When splitting files using WaveAgent, the track names I’ve carefully assigned get replaced with generic numbering like “_1.wav,” which is quite unfortunate.

In that regard, I personally prefer Nuendo’s standard import method, since it preserves the original track names when generating files.

Also, as you demonstrated, it is possible to reference split files directly — but even in that case, the Original Time metadata still gets lost, which remains a key issue for me.

If the Field Recorder Import (FRI) feature supported reference-based import rather than always creating copied files, it could help avoid unnecessary duplication and — ideally — preserve the Original Time metadata as well. That would make a big difference in workflows like mine.

[Fredo]

@nabw

he track names I’ve carefully assigned get replaced with generic numbering like “_1.wav,”

You must be doing something wrong.
The name of the file is preserved, and the _x suffix is added.
Which is normal, due the fact that you split a x-number of tracks from a Multichannel file in individual files.

@nabw

I personally prefer Nuendo’s standard import method, since it preserves the original track names when generating files.

Hmmmm. Nuendo also adds a suffix to the original filename.
I don’t see a difference except the fact that Nuendo offers you a choice of possible suffixes.

@nabw

it is possible to reference split files directly — but even in that case, the Original Time metadata still gets lost, which remains a key issue for me.

Just tested this in every way I can, and I can not confirm.
Origin time and metadata is preserved.

@nabw

If the Field Recorder Import (FRI) feature supported reference-based import rather than always creating copied files,

Well, extracting a single track from a Multichannel file is per definition a process that creates a new file.

@nabw

it could help avoid unnecessary duplication

Again, splitting an 8 channel file into separate tracks will result in 8 new files.

@nabw

and — ideally — preserve the Original Time metadata as well

That is correct. As said, I have reported that issue.

Best regards
Fredo

[nabw]

Dear Fredo,

Thank you again for taking the time to engage so thoughtfully with this discussion.

I realize now that I may have moved too far ahead with my own assumptions and didn’t provide enough background, so please accept my apologies for any confusion.

To be honest, I’m not very experienced with WaveAgent.

I used it briefly about 10 years ago when I was working with a Sound Devices 788, but I haven’t used it much since.

On the other hand, I find Nuendo’s standard import process to be very helpful — especially the ability to select suffix formats when splitting interleaved files.

It’s particularly useful that the track names set in the recorder are reflected in the resulting filenames, which fits nicely with my workflow.

The reason I brought up my previous comment was that I saw your workflow and thought,

“If I adapt this approach, maybe I can integrate it into my own workflow more efficiently.”

For example, if I use Nuendo’s standard import function to split interleaved files within the session,

and specify the recorder’s track name as the suffix, the files retain their Original Time (recorded timestamp) —

in this step, the metadata remains intact.

Then, if I could perform conforming via the Field Recorder Import feature,

while referencing the files already present in the session’s Audio folder —

a new feature like “reference mode” would allow me to avoid unnecessary file duplication,

preserve the Original Time, and make file management much more efficient.

Through this ongoing conversation, I’ve come to feel that we likely work in very similar fields.

I truly appreciate your technical insight and your professional approach, and I want to express my sincere respect.