Alignment files Bug

[BrassNucks]

I will check it too later. What OS and what Graphiccard do you have?

I run conversions and extractions on 64-bit Windows 10 machines, they range in capabilities from GTX 1050Ti to 4060 Ti, but all exhibit the same behavior.

For example, try these files with a simple Preview and you'll see this:

Code: Select all

Loading...
Setting Faceswap backend to NVIDIA
04/26/2024 11:48:10 INFO     Log level set to: INFO
04/26/2024 11:48:13 INFO     Input Video: \\B450M\face_vidslib\alba\ja_ok_20150611.mkv

04/26/2024 11:48:14 INFO     Reading alignments from: '\\B450M\face_vidslib\alba\ja_ok_20150611_alignments.fsa'
04/26/2024 11:48:14 INFO     Updating alignments file to version 2.4
04/26/2024 11:48:14 INFO     Writing alignments to: '\\B450M\face_vidslib\alba\ja_ok_20150611_alignments.fsa'
04/26/2024 11:48:14 INFO     Updating alignments file to version 2.4
04/26/2024 11:48:14 INFO     Writing alignments to: '\\B450M\face_vidslib\alba\ja_ok_20150611_alignments.fsa'
04/26/2024 11:48:14 ERROR    No faces were found in any of the frames passed in. Make sure you are passing in a frames source rather than extracted faces, and that you have provided the correct alignments file.

Process exited.

Manual Tool works fine with them.

manual_tool.jpg (684.58 KiB) Viewed 14305 times

[torzdf]

Here's one I had in the archives, it's from 2022 and loads just fine into the Manual tool. You can save the alignments after making changes to them, and it will still exhibit all the problems we're describing.

https://filebin.net/3j5vk9bc1x3xrcq3

I can confirm replication with this file. I will see about getting a fix issued today.

[torzdf]

Here's one I had in the archives, it's from 2022 and loads just fine into the Manual tool. You can save the alignments after making changes to them, and it will still exhibit all the problems we're describing.

https://filebin.net/3j5vk9bc1x3xrcq3

I can confirm replication with this file. I will see about getting a fix issued today.

[torzdf]

Well, I said it would be trivial. Issue was with files with multiple underscores (_) in the name.

Please update. Should be fixed.

[BrassNucks]

Haha I don't believe it, it worked. Here I was thinking underscores are the perfect way to visualize spaces without violating popular naming practices, and it turned out to be my downfall

Good job getting that sorted out quickly, hopefully the end of that problem for so many people.

[JDBAU]

Can confirm it's working for me again now.

Thanks for all your hard work.

[Jacksonjunge]

I trust that a solution is coming.

Not unless someone actually makes the effort to provide me with some data, it's not.

And my trust was not compromised.

Great work! Thank you!

[wongca]

After the latest update. It works again!!!

Thank you!!!!