Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
18th November 2019, 17:15 | #17802 | Link | |
ByteShare
Join Date: Sep 2014
Location: On the Internet
Posts: 560
|
Holding on to my butt
Quote:
My camera uses MP4 and .ts files so I haven't used mxf files before, but I haven't needed to use time codes for those files (yet). |
|
19th November 2019, 02:14 | #17805 | Link |
Grumpy Old Man.
Join Date: Jul 2019
Location: Out There....
Posts: 692
|
Let's give it up for Atak....he's a Bloody Legend !!!
Well done, as we knew it would be, when you say "I give up" we don't really believe it. It was a community effort of some of the RB users out there. I'd just like to say that some things were said, that should have been a lot more tactful, but some of us express themselves differently to others. I'll take note of the critisicm against me, and the comments I made, however I was also surprised with the support of some, for some suggestions I made, so it's not all bad. We're all here to help with the ongoing improvement of this awesome free app, and I know that I won't stop using it, I have spent a lot of time & money setting up a range of systems so as to get the best benefit & performance out of RB, that I can, so I guess I was frustrated by the sudden unexpected DE problems, as DE, IS the awesome function of RB. So hopefully we can move forward..... So again Atak, thank you very much.......... PS:- I just wanted to add, that I just tested RB, (pre this latest fix), by changing my LAN's IP address from 192.168.0.5, to 192.168.1.5, and it worked, but now it's been fixed, that isn't an issue anymore.
__________________
Not poorly done, just doin' it my way !!! Live every day like it's your last, because one day, it will be !! (M$B) Last edited by Pauly Dunne; 19th November 2019 at 02:42. |
19th November 2019, 07:38 | #17807 | Link |
Registered User
Join Date: Feb 2019
Posts: 4
|
Thanks for the update Atak! Also, not sure if anyone else has reported it yet but RipBot is still prompting for the pinterf branch rather than the official Avisynth+ repo that merged his changes and is now on 3.4.0. Not a big thing just a small quality of life change for a future update
|
19th November 2019, 16:19 | #17808 | Link |
RipBot264 author
Join Date: May 2006
Location: Poland
Posts: 7,816
|
Auto-update core 2019.11.19
Code:
Added: support for mxf files (Material Exchange Format)
__________________
Windows 7 Image Updater - SkyLake\KabyLake\CoffeLake\Ryzen Threadripper |
20th November 2019, 20:13 | #17809 | Link |
Registered User
Join Date: Nov 2010
Posts: 124
|
What about AviSynth v3.4?
https://github.com/AviSynth/AviSynthPlus/ When I starting RipBot I've a message like this: AviSynth+ MT x64 not installed! |
21st November 2019, 16:07 | #17810 | Link |
Registered User
Join Date: Mar 2011
Posts: 433
|
Slow Chunk Starting
I'm not sure if it's just me or not. I've tried to trouble shoot this and I have not found anything that changes it's behavior.
I had to move back to spinning platters (six SAS 10K 2.5" drives, in a ZFS raidz2 with a 10GB SSD SLOG Write Cache) as the SSDs I had would not trim running behind LSI HBA. I'm waiting for Western Digital's new SA500 NAS SSDs to become available to purchase and I'll try that again. Essentially it's taking 20-30 minutes of Starting.... before a chunk begins to encode, for each chunk. So after it finishes a chunk, another 20-30 minutes has to go by for it to do the next one. I have three encoding servers running. There seems to be a lot of disk access on the drive containing the ripbot264temp folder. I'm encoding 4K rips from discs. I've tried installing a fresh version of RipBot264 and let it perform all it's updates and there does not seem to be any difference. I've tried pulling in fresh jobs and there is no difference. I've run disk benchmarks of the VM running RipBot264 and for spinning platters, it's not too bad and this is while the system was a little busy: I've added a 8 core 16 thread E5-2650 V2 chip, so I shoudn't be CPU bound anymore. Is there anything else I can provide? I'm at a loss right now. |
21st November 2019, 16:35 | #17811 | Link |
RipBot264 author
Join Date: May 2006
Location: Poland
Posts: 7,816
|
1) Abort your encoding
2) Double click on IndexStreams_RunAll.cmd for each job causing this problem 3) Restart encoding It is a side effect of (good) changes in lsmash index structure. (2x size reduction). What you see is a reindexing process caused by incorrect (old) index file version (15 vs 16) stored in job folder.
__________________
Windows 7 Image Updater - SkyLake\KabyLake\CoffeLake\Ryzen Threadripper Last edited by Atak_Snajpera; 21st November 2019 at 16:45. |
22nd November 2019, 01:08 | #17812 | Link |
Grumpy Old Man.
Join Date: Jul 2019
Location: Out There....
Posts: 692
|
Another "sneaky" auto-update..
Updated Core (20-11-19), & ES (v1.16.1), Avisynth 3.4 & ffmpeg.
__________________
Not poorly done, just doin' it my way !!! Live every day like it's your last, because one day, it will be !! (M$B) |
22nd November 2019, 14:11 | #17813 | Link |
Registered User
Join Date: Mar 2011
Posts: 433
|
Couple of things.
Just had a machine update and when an encoding server starts it complains about "AviSynth+ MT x64 not installed!". Running as administrator, I ran Tools\Avisynth\install.cmd and it does not seem to make a difference. I tried Tools\Avisynth\Avisynth+\uninstall.cmd and installed again and that did not make a difference, it still complains. I'll dig into this a bit later. I tried the IndexStreams_RunAll.cmd and it did not make any difference. Though, I did discover something interesting. When the very long slow "Starting...." of chunks, or the 10-20 minutes of "Gathering Information" to pick a second audio stream or leaving the Avisynth Menu. It only occurs if RipBot264 demuxes from a ripped 4K disc. If I use MakeMKV to make a mkv of the 4K source, and then pull that into RipBot264, everything behaves normally and takes seconds to complete. Only extra bit is for the EncodingClient to copy the large mkv before starting. So at least that is a workaround for now. |
22nd November 2019, 14:51 | #17814 | Link | |
RipBot264 author
Join Date: May 2006
Location: Poland
Posts: 7,816
|
Quote:
__________________
Windows 7 Image Updater - SkyLake\KabyLake\CoffeLake\Ryzen Threadripper |
|
22nd November 2019, 16:08 | #17815 | Link | |
Registered User
Join Date: Mar 2011
Posts: 433
|
Quote:
|
|
23rd November 2019, 11:56 | #17816 | Link |
Registered User
Join Date: Mar 2016
Location: Austria
Posts: 32
|
FFVideoSource: No video track found
Hello
I've a mkv-file which has 1 video, 2 audio and 37 subtitle tracks. After demuxing i get an Error: Code:
FFVideoSource: No video track found (D:\Temp\RipBot264temp\job2\getinfo.avs, line 2) |
23rd November 2019, 12:09 | #17817 | Link | |
Grumpy Old Man.
Join Date: Jul 2019
Location: Out There....
Posts: 692
|
Quote:
__________________
Not poorly done, just doin' it my way !!! Live every day like it's your last, because one day, it will be !! (M$B) |
|
23rd November 2019, 13:48 | #17819 | Link |
RipBot264 author
Join Date: May 2006
Location: Poland
Posts: 7,816
|
Forget about buggy ffvideosource. Use lsmash.
__________________
Windows 7 Image Updater - SkyLake\KabyLake\CoffeLake\Ryzen Threadripper |
Tags |
264, 265, appletv, avchd, bluray, gui, iphone, ipod, ps3, psp, ripbot264, x264 2-pass, x264 gui, x264_64, x265, xbox360 |
|
|