-
Notifications
You must be signed in to change notification settings - Fork 144
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
not enough buffer for parse video stream #563
Comments
@wolflopnew we need the mkv to reproduce the bug and be able to debug. Please see whether you can post a link. |
the MKV file to be processed is 73 GB in size. I cannot upload this size. |
You can cut the source video into smaller parts using HxD on Windows or the |
I have smal sample.iso of the file 7GB Size. Where can send the link? |
7GB is still pretty large - is there any way to cut it down further or compress it? If it isn't possible you would have to try uploading the sample to a site that allows files that large - you can check the list from here: https://multiup.org/en/upload/from-computer |
@wolflopnew if you are on Windows just use your OneDrive. |
Hello here is the google drive link
https://drive.google.com/file/d/1adrTWeVeJx3rXXnrwYtdOL_bCAw8Vp0b/view?usp=sharing
wolflop
Meet Google Drive – One place for all your files<https://drive.google.com/file/d/1adrTWeVeJx3rXXnrwYtdOL_bCAw8Vp0b/view?usp=sharing>
Google Drive is a free way to keep your files backed up and easy to reach from any phone, tablet, or computer. Start with 15GB of Google storage – free.
drive.google.com
…________________________________
Von: jcdr428 ***@***.***>
Gesendet: Donnerstag, 7. April 2022 07:25
An: justdan96/tsMuxer ***@***.***>
Cc: wolflopnew ***@***.***>; Mention ***@***.***>
Betreff: Re: [justdan96/tsMuxer] not enough buffer for parse video stream (Issue #563)
@wolflopnew<https://github.com/wolflopnew> if you use Windows just use your OneDrive.
—
Reply to this email directly, view it on GitHub<#563 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AYHVSPVLLRQ3S73RXB7GZ6DVDZ5VHANCNFSM5RC6JXLQ>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
@wolflopnew you should have received an email from OneDrive to give me access. |
Did you found something. Have the same problem with another movie. No muxxable parse error. If found a solution may be is it the Audio file (aac) i removed when i still had it in the mux there is no parse error but an othe info "m2ts may be not playable" |
@wolflopnew please resend a link, the previous link is not working anymore. |
Same problem with the next movie |
Further information: The original file is an mp4 with AAC sound. When I just create an iso with AAC I get an error saying it might not be playable, but it runs. But if I add the sound files (DTS:X sound and PCm sound, the parse message comes up... Hope that helps with the misfinding. I attach the small film file with AAC sound. |
Here´s the file |
By the way. Had often the problem that movies start in the player at 0.00 Min. it starts at 1. Min. Where is the bug? |
Still the same problem. Next movie Not enough buffer for parse video stream. Current frame num 0 |
I can't download 1fichiercom as it requests registration, and the OneDrive dile has disappeared. Please repost aOneDrive link, thanks. |
heres is another link |
@wolflopnew I downloaded the full 2GB file and the m2ts muxes fine in tsMuxer ?? |
It's not synonymous the complete film only 2GB. |
i have testet it with smal iso of the film. Its working... With the whole film - error at the end 99,4 %. The last 30 seconds of the movie are missing ... Whats the problem? |
With UHD movies, the max frame size can get much bigger. Increasing the buffer size should avoid errors such as issue #563.
You should have posted the faulty part, no point posting a working part... |
Thank you jcdr428. The problem is solved. Great!! |
Good. Closing ! |
Here is the message txmuxer gives me
[](https://abload.de/img/screenshot2022-03-15229ks9.jpg)
Hope you can fix this or give me a help to solve the problem...
wolflop
The text was updated successfully, but these errors were encountered: