-
Notifications
You must be signed in to change notification settings - Fork 136
Recorded video quality. after patch 6.2 #236
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
Comments
How come you want to get or4? it is lower quality right? However in the future I will implement the option to select the quality of live |
or4 doesn't mean the original?
I'll test it again and see the video format. |
I tested _uhd.flv and _or4.flv, both of which had the same codec and resolution, but _or4.flv had twice the bitrate of _uhd.flv. I think or4 is much higher. |
uhd":{"main":{"flv":"https://pull-f5-sg01.tiktokcdn.com/stage/stream-~~~~~~~~~_uhd.flv? origin":{"main":{"flv":"https://pull-f5-sg01.tiktokcdn.com/stage/stream-~~~~~~~~_or4.flv? or4 seems to be the original. |
As a workaround, you can replace lines 135 through 157 in '\core\tiktok_api.py' with the following to get or4. From
To (this is from 'tiktokbot.py' in v5.8)
|
I provided an additional option in pull request in #241 |
Sorry, I wrote it through a translator.
Thank you for your program.
I previously made a fix through this link and got or4.flv.
→ #210
recording test after the patch, but it was recorded as uhd.flv.
Is there a separate option to get or4?
And can I request an additional option to change the -mode automatic time from 5 minutes to 1 minute? plz
ex)
This is the program I installed while checking for other bugs, and this is where I recorded or4.flv.
→ https://github.com/roju/tiktok-live-recorder
Thank you in advance for your wonderful update.
The picture tlr1.png below is your program,

Play : main.py -user UserName -mode automatic -output OutputFolder
and tlr2.png is roju's program.

Play : ttlr.py -user UserName -mode auto -out_dir OutputFolder -ffmpeg -combine
The text was updated successfully, but these errors were encountered: