Reaper-Waapi-Transfer icon indicating copy to clipboard operation
Reaper-Waapi-Transfer copied to clipboard

Published 20 hours ago • verified publisher icon karltechno

Perforce 'Mark for Add' causing import error

Open undertheradar84 opened this issue 7 years ago • 5 comments

Hello,

I get an error cropping up due to Perforce insisting on 'Mark for Add' being okayed on new files. I get a pop up window on the Waapi saying 'some files could not be imported into Wwise. The associated render queue projects have been re-created'.

The files DO in fact get imported but the error is a bit misleading. I'm not sure if there is anyway around this?

Thanks

image

undertheradar84 avatar Jan 08 '18 17:01 undertheradar84

Same thing happens to me with SVN. The problem happens because WWISE asks me to confirm if I want new files to be added to SVN repo. If I manage to click YES quickly for every sound while rendering is active everything goes smoothly, like in gif below. while

But, if I fail to click confirmation dialog on time some sounds remain in BouncedSounds folder even though I uncheked "Copy Files to Wwise Originals" and they remain in my Render Queue inside REAPER. after

This is very annoying and it would be extremely eficient to override this dialog box inside WAAPI Transfer. I export a large number of files from REAPER everyday and I would like to have this solved, if possible. A simple YES TO ALL checkbox inside plugin would be nice.

nikolalkc avatar Feb 08 '18 14:02 nikolalkc

Hi @undertheradar84 and @nikolalkc - please try https://github.com/karltechno/Reaper-Waapi-Transfer/releases/tag/v0.1.8-beta and let me know if this fixes the issue, thanks.

karltechno avatar Feb 11 '18 12:02 karltechno

@karltechno Thank you for responding so quickly. This fix actually helps. Error message doesn't pop up anymore, but, I still have to click YES in wwise for every sound that is exported from REAPER. Is there a way to override this dialog so WAAPI Transfer automatically marks all new files for Add in source control?

nikolalkc avatar Feb 11 '18 16:02 nikolalkc

@nikolalkc From a cursory glance I can't see anything in the schema allowing me to do that: https://www.audiokinetic.com/library/edge/?source=SDK&id=ak__wwise__core__audio__import.html - additionally it seems as though source control operations aren't available to WAAPI currently: https://www.audiokinetic.com/qa/4347/how-to-create-a-new-workunit-using-waapi

karltechno avatar Feb 11 '18 18:02 karltechno

Oh well, we'll just have to wait for those options to be implemented. Thanks again.

nikolalkc avatar Feb 12 '18 09:02 nikolalkc