WAV files not seen upon return to PMX

[Julian Gough]

Yes, I did this a few versions ago as well for the solution, but this time it is not seeing it.
Also, this works fine for "complete" files, but when you do a bunch of snippets for manual noise removal, and then it doesn't see them - NIGHTMARE.

Indeed a nightmare, I'm at a bit of loss too.

I do a lot of manual noise removal and work through the render command to export then import the clips. Apart from the sheer number of files it generates, it works quite well for me.

Earlier in this thread, DJS made the valid comment that Merging are a small company with limited resources. This might be the case but every year I pay a significant amount for my ASM, and that is per key. As a professional in the sound business, I don't begrudge paying this. I see it as maintaining the tools of my trade. I don't think it is unreasonable to expect a return on my investment, not only having new features but also keeping old ones working.

A few months ago my dealer in the UK sent round an email asking PMX users what they would like to see in future versions. I expect some of you received something similar. I couldn't think of anything at the time but if I was to make a suggestion, I would request that EVERY current feature worked as it should do. If that was to happen, I would be a happy bunny.

Best,

slightly grumpy bunny.

[mpdonahue]

Hello,
Yes. Save to different folder. Save to different drive. Make another copy. The file just doesn't get recognized by PMX and the original file remains upon reopen.

What was the RX problem - same with PMX to RX and back in or just working in RX?

Save a stereo file as a BWAV (without unique ID number), import it into RX, after working on it, save it with a different filename and PMX would not see the new file. Save it into a different folder (with different filename) and PMX finds it. This was several versions ago, of both PMX and RX.

Julian

I suspect that Izotope is not modifying the RIFF INFO_List or BEXT chunk of the BWF header. Even if you change the file name, PMX looks into the BWF metadata for information. Try regular WAV or AIFF and see if it has the same problems.

All the best,
-mark

[ljudatervinning]

I have found I need to un-tick "preserve non-audio data" when exporting Pyramix rendered waves via RX6, to avoid problems.
I also tick "BWF", as I prefer Broadcast wave files.

[mpdonahue]

I have found I need to un-tick "preserve non-audio data" when exporting Pyramix rendered waves via RX6, to avoid problems.
I also tick "BWF", as I prefer Broadcast wave files.

Just wondering out loud....Once you've deleted all the non audio data from a BWF, don't you have a WAV file?
All the best,
-mark

[ljudatervinning]

*LOL*
Probably!
I expected any new meta data created in iZotope is saved, but I have not checked.

[draudio2u]

So I have to thank Jordi and David at Merging for helping fix this issue. Here are the required protocols:
- In the Mounting rules window, activate both "Ignore BWF Chunk..." and "Ignore iXML chunk.." in the Special rules for Wave files containing BWF or iXML chunks section. This solves part of the problem in my current project but I assume if I start with this engaged, it will be enough.
- Make sure Wavelab generates a new ID for the processed file (the ID is called Originator Reference). (Wavelab is where I run my Cube-Tec restoration tools as it understands VPI).
Edit the Originator Reference in the BEXT chunk so that no 2 files have the same exact reference. This can be done from within Pyramix's Metadata editor tab or with a third party utility that allows to edit these metadata. If you decide to do it like this , you should probably limit yourself to editing no more than the very last three digits as other digits are used for specifying timestamp and number of channels in the file.

(And final thought from David):
-You can also use the Project > Reconform > Relink to new media feature to relink the files.
Put the processed files in a subfolder (to also have the mounting rules applied), then relink "using current Media Name" / "Matching Media Name" / "Match exactly" or "Match only minimum common available characters". Make sure you tick the "Ignore TimeCodes" option, and in the "Search in" field, select the subfolder containing the processed files.

To avoid such trouble in the future, you can also export the required files from Pyramix to "standard" wav files rather than BWF.
Wav files do not contain such embedded UID, so renaming the processed file in Wavelab would be sufficient.
Unfortunately wav files do not contain Timecode, so you won't be able to use the file timestamp to reimport it in Pyramix.

I plan on changing my file creation to follow this last step in my next project when I need to render. If creating just snippets I will see if not having BWF will still auto insert, but when I have complete file renders, I will use suggestion above.

Thank you all for you support.

[Perfect Record]

I've had similar problems- that is if I'm interpreting your issue correctly.

I've passed files out to iZotope RX, amended their file names, then returned them to the project in Pyramix, only to find that Pyramix opened the original files, despite the file name change.

My simple solution is to use standard WAV files, instead of BWAV. Haven't had the problem since.