Closed Chad90b closed 2 years ago
This is an issue with windows file naming. I slowly getting around to it. There are other issues open with this, I think #1 or #2.
@nadermx i apologize for not noticing those. thank you for the feedback. we can probably just close this issue then - right?
Ill close it when i or someone fixes the issue
El lun, 11 de abr. de 2022 15:49, Chad90b @.***> escribió:
@nadermx https://github.com/nadermx i apologize for not noticing those. thank you for the feedback. we can probably just close this issue then - right?
— Reply to this email directly, view it on GitHub https://github.com/nadermx/backgroundremover/issues/33#issuecomment-1095552567, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABYACXBLHS4MTVZMXXY4YSTVESF7JANCNFSM5TBMBY2A . You are receiving this because you were mentioned.Message ID: @.***>
Any chance this will get fixed? Or is there a workaround?
Join the question, I'm curious if somebody fixed it? I'm getting a 0 Byte sized file named: "output.mov"
I tried doing it on linux but the dependencies changes so much now have syntax errors. I'm guessing this project isn't being maintained anymore
I should have a commit today for this I hope. Windows uses different folder structure than linux, so have to add a exception
El sáb, 30 de jul. de 2022 10:21, happyguyhere @.***> escribió:
I tried doing it on linux but the dependencies changes so much now have syntax errors. I'm guessing this project isn't being maintained anymore
— Reply to this email directly, view it on GitHub https://github.com/nadermx/backgroundremover/issues/33#issuecomment-1200224696, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABYACXASIV22TMSDWFCBOMLVWVB5ZANCNFSM5TBMBY2A . You are receiving this because you were mentioned.Message ID: @.***>
I am working on this now, as it should close, https://github.com/nadermx/backgroundremover/issues/8 as well. Once I get something live I will ask one of you with windows to try.
Could some one on windows try installing the most recent version of this repo and letting me know if it works now?
pip install git+https://github.com/nadermx/backgroundremover.git@2a7421970591a12f57f275079e54febe9dd3c287
As I do not have a windows system to try.
Could some one on windows try installing the most recent version of this repo and letting me know if it works now?
pip install git+https://github.com/nadermx/backgroundremover.git@2a7421970591a12f57f275079e54febe9dd3c287
As I do not have a windows system to try.
I just tried it, unfortunately it still creates an "output.mov" which is 0 Byte size.
Let me know if you want to test again, I'll be happy to test whenever I see your message :)
I'm working on as many issues as I can this month and will commit by the 30thish.
El jue, 7 de jul. de 2022 15:00, happyguyhere @.***> escribió:
Any chance this will get fixed? Or is there a workaround?
— Reply to this email directly, view it on GitHub https://github.com/nadermx/backgroundremover/issues/33#issuecomment-1178158098, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABYACXAHE5AGAPCCQZXXYADVS4ZNDANCNFSM5TBMBY2A . You are receiving this because you were mentioned.Message ID: @.***>
I'm having the same issue, the video output for -tv is empty
This is my command:
backgroundremover -i "30fps.mp4" -m "u2net_human_seg" -fr 30 -tv -o "output2.mov"
Windows?
El mié, 3 de may de 2023 13:06, g5fighter @.***> escribió:
I'm having the same issue, the video output for -tv is empty
This is my command:
backgroundremover -i "30fps.mp4" -m "u2net_human_seg" -fr 30 -tv -o "output2.mov"
— Reply to this email directly, view it on GitHub https://github.com/nadermx/backgroundremover/issues/33#issuecomment-1533402341, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABYACXEIUJHQ76LTI4BPIMDXEKF7TANCNFSM5TBMBY2A . You are receiving this because you modified the open/close state.Message ID: @.***>
Yes
FINISHED ALL FRAMES (135)! Starting alphamerge after call
on windows after completing all frames and about to merge nothing happens. temp dir is cleaned. no error occurs but the user is thrown out of the program from the terminal and the output file remains empty at 0 bytes. its like the program forgot to actually write the data to the output location before ending