Skip to main content
Participant
October 24, 2024

Can't make new ingest preset for the new 2025 version

  • October 24, 2024
  • 5 replies
  • 250 views

Hoping someone can help.

 

I have updated to the latest version of Adobe ME 2025. It has however presented me with new bugs whilst using my Ingest Preset. I have to tick both boxes in the settings window to Transfer and copy files to the destination otherwise it won't work, see attached pic. This also copies the sources files to the same destination which is kind doubling up creating more HDD space than needed

 

I also can't create a new one properly. The window looks like the encoding preset window

 

hope there's a solution to this

 

Thanks

 

Cameron 

 

5 replies

GSPFilmworks
Known Participant
November 5, 2024

OK, now things are getting worse. The Ingest presets aren't saving correctly. I'm using a facebook preset, h264, in the Ingest preset. After I hit "OK", it reverts to AAC and no preset. Now after a couple of runs, inexplicably, there are folders labelled "Export" in the destination folder of this ingest preset, something I did not create nor are there settings for such an option. 

 

Now that I look closer, the "Export" folder must be from clicking the "Copy files to Destination" option being checked, which is required to use the "Transcode files to Destination" option.

 

Oh, and when the Ingest preset is applied to the Queue, the name doesn't show, only "Custom". Too many wires are crossed.

GSPFilmworks
Known Participant
November 5, 2024

OK, after some quick testing, it looks like "Copy files to Destination" is required to be checked in order to use "Transcode files to Destination" checkbox. That has changed. Previously I had only "Transcode files to Destination" checked and it worked. Someone needs to go through the code and remove the dependancy.

 

Also, I still sometimes get the Encoding preset creation dialog when I go to make an Ingest preset. This was fixed in v23.3 and has found it's way back in. Shouldn't be copying/pasting old code when updating.

GSPFilmworks
Known Participant
November 5, 2024

I get the same thing (AME 25 Build 54). Additionally, it doesn't add the suffix I've created. In short, this is completely broken and unusable.

Participant
October 24, 2024

It still randomly  stores the MP4 file in the source folder and also creates a source file folder with the MXF in the destination target folder

 

Not sure how to fix?

EckiAME
Community Manager
Community Manager
October 24, 2024

It did work for me when I added a path for the transcode.