Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Errno 22] Application provided invalid, non monotonically increasing dts to muxer in stream 1 #9

Closed
3 tasks done
Poggerslads opened this issue Jan 8, 2024 · 4 comments · Fixed by #10
Closed
3 tasks done
Assignees
Labels
bug Something isn't working

Comments

@Poggerslads
Copy link

Bug Description

Error message not found on bugs for downloading a video file in a timeline of a fansly content creator using the executable of the downloader.

Expected behavior

Downloading of the video

Actual behavior

Got the following error message displayed :

Application provided invalid, non monotonically increasing dts to muxer in stream 1: 9216 >= 8192

[43]ERROR | 20:48 || Unexpected error during Timeline download:
Traceback (most recent call last):
File "download\common.py", line 144, in process_download_accessible_media
File "download\media.py", line 162, in download_media
File "download\m3u8.py", line 152, in download_m3u8
File "av\container\output.pyx", line 211, in av.container.output.OutputContainer.mux
File "av\container\output.pyx", line 232, in av.container.output.OutputContainer.mux_one
File "av\container\core.pyx", line 285, in av.container.core.Container.err_check
File "av\error.pyx", line 336, in av.error.err_check
av.error.ValueError: [Errno 22] Invalid argument: 'C:\Users\XXXX\Downloads\Fansly_Downloader_NG-Windows-v0.7.10\XXXXXX\Timeline\Videos\2023-12-26_at_01-07_id_595820358733410305.mp4'; last error log: [mp4] Application provided invalid, non monotonically increasing dts to muxer in stream 1: 9216 >= 8192

Environment Information

  • Operating System: Windows
  • Fansly Downloader Version: v0.7.10
  • Fansly Downloader Type: Executable
  • Specific creators name: prefer not to disclose

User Research

I have done the following:

Additional context

This is an echo of this bug I also opened on Avnsx github, the issue still happens, I don't know what to do, you can PM me for more details if needed

@prof79
Copy link
Owner

prof79 commented Jan 19, 2024

Hi, I've been quite busy, sorry. I'll plan to rewrite the video download code as it is also very memory-inefficient (#8). I hope to have something soon. I do fear, however, that this might break existing downloads/de-duplication so videos might download all over again. Parsing and re-muxing the video manually was a hazardous move by Avnsx. I also hope my pyffmpeg will package properly.

@prof79 prof79 self-assigned this Jan 19, 2024
@prof79 prof79 added the bug Something isn't working label Jan 19, 2024
@Poggerslads
Copy link
Author

Best of luck to you then, no issue for the "delay" you do only what you can do in time you have :)

@prof79
Copy link
Owner

prof79 commented Jan 20, 2024

Hi, you might try this version but note the warning - try with a different folder or backup your existing creator(s). Though I have some ideas I do not yet have a solution for the de-duplication thing as the files essentially become different files when ffmpeg merges them proper.

Be interesting to know whether the pyffmpeg approach fixes that DTS problem. I still see a potential Linux issue but that shouldn't hurt you on Windows.

https://github.com/prof79/fansly-downloader-ng/releases/tag/ondemand

@Poggerslads
Copy link
Author

Hello :)
So, I downloaded it, and just pasted my folders and my ini file where the exe was, and as a result the dedup worked, and the file it would not be able to download previously got downloaded properly :) so all good for me :)
Thank you very much

@prof79 prof79 linked a pull request Jan 27, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants