What is the current best practice to speed up FMOD and Perforce? It takes about 8 seconds to import one single .wav asset into an FMOD project. Windows 11, latest version of Perforce helix, and FMOD Studio FMOD 2.02.25. the machine has 32 gigs of ram and it’a all ssd and NVMe drives.
I have tried using legacy integration but I am having issues connecting to p4 when I switch.
Hi,
Thank you for the information.
In the 2.03.05 release there were significant improvements to Perforce operations: FMOD Studio | Detailed Revision History: 2.03.05. However, this is in a different major version.
How large is the project? Is it included in any cloud storage? How are you importing the files?
New project, quite empty, just started some testing, we are not even sure if we will stay on FMOD. The perforce integration is a deciding factor. DO I have to manage the assets from FMOD? Having multiple sound designers working on the project, what’s the risk of managing assets directly in perforce? I assume the usual with any other software running some type of repository, people could edit the metatadat of the assets
Thank you for the information.
Would it be possible to record a screen capture importing an assets with the delay? I am not too sure what you mean by managing assets, could you please elaborate on an example workflow with assets and the source control interface?