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.

 

Go Back   Doom9's Forum > Video Encoding > MPEG-4 Encoder GUIs

Reply
 
Thread Tools Search this Thread Display Modes
Old 20th October 2018, 19:58   #16241  |  Link
oldschooltech
Registered User
 
Join Date: Jun 2018
Posts: 16
Quote:
Originally Posted by burt123 View Post
Hi Atak, I decided to download that file from Filehost, and I got it without too much trouble.

I played it on my LG 4K TV, and it played rather well, especially knowing how old this would be.

No interlacing, just probably needs an MDegrain2 encode.

see for yourself:-

https://www.mediafire.com/file/26c7y...9-001.mkv/file
not sure if your tv fixes it or not, but I can say mine does not and TBH im not sure if plex will when serving them to my other devices. So my goal is to remove it encase of any issues.

Yea it looks good, but after ripbot gets done with it, it looks so much better.
oldschooltech is offline   Reply With Quote
Old 20th October 2018, 20:07   #16242  |  Link
oldschooltech
Registered User
 
Join Date: Jun 2018
Posts: 16
byteshare, if i was to mux in the time codes for all my encodes if they where constant or variable would it hurt anything. every so often there is a 1 or 2 dvd that are variable from a season, or even 1 or 2 episode from a dvd when the rest are constant.

This would save me from having to waste so much time checking every file to see if it needs muxing. I had a few slip by that only had audio issues come the last 10 mins of 30.

Its not to much work as well. thanks to your batch script. I had forgot all about batch. I never was much good at it, but brushed up on it. now I can click and rename the outputs too after moving the original encodes, so there is no file name conflicts.

Thanks for all the help.
oldschooltech is offline   Reply With Quote
Old 20th October 2018, 20:20   #16243  |  Link
oldschooltech
Registered User
 
Join Date: Jun 2018
Posts: 16
I have a few strong pc and a good handfull of laptops and older weak desktops. DE is very very nice, but I do end up with a problem with slow downs more often then not. As an encode gets near the final chunks if they get sent to a weaker pc the encode can sit 5-10 more minuets waiting for the slow pc to encode it while everything else is idle. I see 3 solutions:

1. I remove slower pc, but take a 50-60 FPS hit.
2. Some home add in a prioritize mode. If chunks are =< the number of encode severs, then refer to user inputted data on what sever should get the final chunks encodes. the flip, what severs should not be sent the final chunks to encode.
3. If ripbot see idle encode severs and || the remaining chunks are < the amount of encode severs Then start a new job with the Idle severs and make sure the others kick in on the new job when they finish up on the last one.

Just a thought, I maybe a special case. At any rate thanks for all your hard work.
oldschooltech is offline   Reply With Quote
Old 20th October 2018, 20:33   #16244  |  Link
GZZ
Registered User
 
Join Date: Jan 2002
Posts: 581
Quote:
Originally Posted by oldschooltech View Post
I have a few strong pc and a good handfull of laptops and older weak desktops. DE is very very nice, but I do end up with a problem with slow downs more often then not. As an encode gets near the final chunks if they get sent to a weaker pc the encode can sit 5-10 more minuets waiting for the slow pc to encode it while everything else is idle. I see 3 solutions:

1. I remove slower pc, but take a 50-60 FPS hit.
2. Some home add in a prioritize mode. If chunks are =< the number of encode severs, then refer to user inputted data on what sever should get the final chunks encodes. the flip, what severs should not be sent the final chunks to encode.
3. If ripbot see idle encode severs and || the remaining chunks are < the amount of encode severs Then start a new job with the Idle severs and make sure the others kick in on the new job when they finish up on the last one.

Just a thought, I maybe a special case. At any rate thanks for all your hard work.
You should set the chunk size to much less and have more chunks that will finish faster.
GZZ is offline   Reply With Quote
Old 20th October 2018, 21:30   #16245  |  Link
oldschooltech
Registered User
 
Join Date: Jun 2018
Posts: 16
Quote:
Originally Posted by GZZ View Post
You should set the chunk size to much less and have more chunks that will finish faster.
solution 4 overlooked.

4. Learn more about the app and its setting to set it up just right XD.

thank you I will play with it see what I can come up with.
oldschooltech is offline   Reply With Quote
Old 20th October 2018, 22:29   #16246  |  Link
byteshare
ByteShare
 
byteshare's Avatar
 
Join Date: Sep 2014
Location: On the Internet
Posts: 560
Quote:
Originally Posted by oldschooltech View Post
byteshare, if i was to mux in the time codes for all my encodes if they where constant or variable would it hurt anything. every so often there is a 1 or 2 dvd that are variable from a season, or even 1 or 2 episode from a dvd when the rest are constant.

This would save me from having to waste so much time checking every file to see if it needs muxing. I had a few slip by that only had audio issues come the last 10 mins of 30.

Its not to much work as well. thanks to your batch script. I had forgot all about batch. I never was much good at it, but brushed up on it. now I can click and rename the outputs too after moving the original encodes, so there is no file name conflicts.

Thanks for all the help.
The only case I know of it being an issue is when there is video corruption, but then again you have video corruption. I can't say with 100% certainty but I can say I can't think of a case really it would hurt to auto mux back the timecodes, nor can I say I've experienced an issue with muxing back timecodes for variable or constant FPS files that didn't already have an issue with the source.
byteshare is offline   Reply With Quote
Old 21st October 2018, 03:28   #16247  |  Link
mdchaser
Registered User
 
Join Date: Aug 2005
Posts: 36
Quote:
Originally Posted by Atak_Snajpera View Post
Run manually D:\Temp\RipBot264temp\job1\job1_EncodeAudio1.cmd and see what error message you get.
I ran it manually and sure enough it created the file so I'm not sure whats going on. Here is the output:

Output #0, ac3, to 'D:\Temp\RipBot264temp\job1\Encoded_Audio_1.ac3':
Metadata:
encoder : Lavf58.17.103
Stream #0:0: Audio: ac3, 48000 Hz, 5.1, fltp, 640 kb/s
Metadata:
encoder : Lavc58.24.101 ac3
size= 3400194kB time=01:40:44.79 bitrate=4608.0kbits/s speed= 159x
video:0kB audio:3400194kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.000003%
size= 472250kB time=01:40:44.79 bitrate= 640.0kbits/s speed= 159x
video:0kB audio:472250kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.000000%
mdchaser is offline   Reply With Quote
Old 21st October 2018, 11:52   #16248  |  Link
Atak_Snajpera
RipBot264 author
 
Atak_Snajpera's Avatar
 
Join Date: May 2006
Location: Poland
Posts: 7,806
Quote:
Originally Posted by oldschooltech View Post
solution 4 overlooked.

4. Learn more about the app and its setting to set it up just right XD.

thank you I will play with it see what I can come up with.
Default chunk size is 1 minute. You must have change that to something larger.
Atak_Snajpera is offline   Reply With Quote
Old 22nd October 2018, 01:34   #16249  |  Link
mdchaser
Registered User
 
Join Date: Aug 2005
Posts: 36
Quote:
Originally Posted by mdchaser View Post
I ran it manually and sure enough it created the file so I'm not sure whats going on. Here is the output:

Output #0, ac3, to 'D:\Temp\RipBot264temp\job1\Encoded_Audio_1.ac3':
Metadata:
encoder : Lavf58.17.103
Stream #0:0: Audio: ac3, 48000 Hz, 5.1, fltp, 640 kb/s
Metadata:
encoder : Lavc58.24.101 ac3
size= 3400194kB time=01:40:44.79 bitrate=4608.0kbits/s speed= 159x
video:0kB audio:3400194kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.000003%
size= 472250kB time=01:40:44.79 bitrate= 640.0kbits/s speed= 159x
video:0kB audio:472250kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.000000%
A quick update. I encoded a movie, got the failure. Encoded it again and ran job1_EncodeAudio1.cmd while it was in the middle of encoding and the encode finished properly! It looks as if the audio encoding scripts aren't being called.
mdchaser is offline   Reply With Quote
Old 23rd October 2018, 09:22   #16250  |  Link
Wishbringer
Silent Reader
 
Wishbringer's Avatar
 
Join Date: Dec 2003
Location: Germany
Posts: 295
@Atak_Snajpera:
Could you add a "Core" option for demuxing/decoding E-AC3 Bluray-audio?
For DTS there is a "Core" option, but not for E-AC3.

There is a old bug/missing feature in eac3to when extracting some eac3 streams:
http://bugs.madshi.net/view.php?id=450
Happened in some new BluRay movies.
Quote:
[a01] Extracting audio track number 1...
[a01] Removing AC3 dialog normalization...
[a01] Applying (E-)AC3 delay failed. <ERROR>
Aborted at file position 1048576. <ERROR>
"Core" would be a workaround till madshi fixes eac3to demuxing/decoding.
Wishbringer is offline   Reply With Quote
Old 24th October 2018, 19:52   #16251  |  Link
FuzzyNutz
Registered User
 
Join Date: Jun 2016
Location: Canada
Posts: 131
video encoding error: unknown option -- ctu

Since an auto-update yesterday, RipBot stopped encoding video. The setting " --ctu 32" or " --ctu 16", inside the jobXX_EncodeVideoPass1.cmd file, inside the X:\Temp\RipBot264temp\jobXX folder, is causing the error "unknown option -- ctu". Manually deleting this setting returns RB to a functioning state.

Last edited by FuzzyNutz; 25th October 2018 at 20:32.
FuzzyNutz is offline   Reply With Quote
Old 25th October 2018, 06:36   #16252  |  Link
burt123
Registered User
 
burt123's Avatar
 
Join Date: Jun 2010
Location: NSW, Australia.
Posts: 366
Quote:
Originally Posted by FuzzyNutz View Post
Since an auto-update yesterday, RipBot stopped encoding video. Seems the setting, "--ctu 32" or "--ctu 16", inside the "jobXX_EncodeVideoPass1" file is causing the error "unknown option -- ctu". Manually deleting this setting returns RB to a functioning state.
Hey Fuzzy,

I concur, I am now getting the exact same error, the Job just keeps trying to start, and doesn't progress from there

What do you need to delete ???

Here's the info from the Encoding Client Window:-

Encoding started...
""\\BIG-XEON\Ripbot264temp\Tools\ffmpeg\bin\ffmpeg.exe" -loglevel panic -i "\\BIG-XEON\RipBot264temp\job17\Chunks\2.avs" -strict -1 -f yuv4mpegpipe - | "\\BIG-XEON\Ripbot264temp\tools\x264\x264_x64.exe" --seek 21 --colorprim bt709 --transfer bt709 --colormatrix bt709 --opencl --opencl-device 0 --opencl-clbin "C:\Users\Burt123\AppData\Local\Temp\x264_lookahead_2.clbin" --crf 20 --fps 24000/1001 --force-cfr --min-keyint 24 --keyint 240 --frames 1440 --sar 1:1 --level 4.0 --aud --nal-hrd vbr --vbv-bufsize 25000 --vbv-maxrate 25000 --b-pyramid none --ctu 32 --stdin y4m --output "\\BIG-XEON\RipBot264temp\job17\Chunks\2.264" -"
\\BIG-XEON\Ripbot264temp\tools\x264\x264_x64.exe: unknown option -- ctu

Atak, please fix this ASAP, as it renders the program totally useless


And as the last auto update was fairly substantial, I would have expected a change to the build version, like 1.23.2 (just to make it a little easier to keep track of)

Last edited by burt123; 25th October 2018 at 09:50.
burt123 is offline   Reply With Quote
Old 25th October 2018, 09:49   #16253  |  Link
Wishbringer
Silent Reader
 
Wishbringer's Avatar
 
Join Date: Dec 2003
Location: Germany
Posts: 295
Seems some x265 options were in the RB pregeneration of x264 scripts
--ctu 32 is good for FullHD-Movies to distribute encoding on more threads (otherwise x265 only uses around 50% on Ryzen 2700x)
Wishbringer is offline   Reply With Quote
Old 25th October 2018, 17:07   #16254  |  Link
byteshare
ByteShare
 
byteshare's Avatar
 
Join Date: Sep 2014
Location: On the Internet
Posts: 560
I don't use
Code:
--ctu
Since the update (not sure all of the changes such as the scripts) I've no issues. I did need to change the restart time on my encoding servers from 2 to 4 because I found 5 segments that were taking longer than any of my other encodes. More an FYI for other users that use a lower threshold.

Last edited by byteshare; 26th October 2018 at 14:00.
byteshare is offline   Reply With Quote
Old 25th October 2018, 17:08   #16255  |  Link
FuzzyNutz
Registered User
 
Join Date: Jun 2016
Location: Canada
Posts: 131
Quote:
Originally Posted by burt123 View Post
What do you need to delete ???
Delete --ctu 32, including the single space before it, from the applicable jobXX_EncodeVideoPass1 file in the applicable X:\Temp\RipBot264temp\jobXX folder.

This is done by right-clicking the jobXX_EncodeVideoPass1 file, selecting "edit", manually deleting " --ctu 32" and saving the now-modified file.
FuzzyNutz is offline   Reply With Quote
Old 25th October 2018, 19:58   #16256  |  Link
slalom
Registered User
 
slalom's Avatar
 
Join Date: Jan 2010
Posts: 456
Quote:
Originally Posted by FuzzyNutz View Post
Since an auto-update yesterday, RipBot stopped encoding video. Seems the setting, "--ctu 32" or "--ctu 16", inside the "jobXX_EncodeVideoPass1" file is causing the error "unknown option -- ctu". Manually deleting this setting returns RB to a functioning state.
Same problem here. All servers starting and stopping on a loop

EDIT
Oh, and I noticed an error appearing when there are too many subs in the file, in the last one there were 31 subs

Code:
File: H:\***
FFVideoSource: No video track found
(E:\Temp\RipBot264temp\job392\getinfo.avs, line 2)
If I remove the subs, the file loads successfully
Is there a limit in the number of subs?
__________________
E5 2697 v2 @ 3.0GHz on P9X79 Deluxe 24GB
Xeon E5-2680 v2 @ 3.1GHz 16GB
Sony Vaio VPC-F13Z1E/B

Last edited by slalom; 25th October 2018 at 20:38.
slalom is offline   Reply With Quote
Old 25th October 2018, 20:39   #16257  |  Link
FuzzyNutz
Registered User
 
Join Date: Jun 2016
Location: Canada
Posts: 131
--ctu error issue resolved

Quote:
Originally Posted by FuzzyNutz View Post
Since an auto-update yesterday, RipBot stopped encoding video. The setting " --ctu 32" or " --ctu 16", inside the jobXX_EncodeVideoPass1.cmd file, inside the X:\Temp\RipBot264temp\jobXX folder, is causing the error "unknown option -- ctu". Manually deleting this setting returns RB to a functioning state.
An auto-update today fixed RB. The --ctu setting is no longer being created.
FuzzyNutz is offline   Reply With Quote
Old 26th October 2018, 18:51   #16258  |  Link
ejone
Registered User
 
Join Date: Sep 2018
Posts: 2
Quote:
Originally Posted by ejone View Post
I think this is a very annoying issue with Ripbot that should be fixed.

https://youtu.be/uxCkIvUdo0M

Evidently, if you are converting TV shows, even if you select a particular M2TS file, Ripbot will not default to the playlist you specifically picked (should be assumed from the file name - select the one with the matching name by default).

Super annoying. Had to redo everything. Would it be possible to select the correct default if you pick the file manually as shown in the video?
Quote:
Originally Posted by Atak_Snajpera View Post
Because .m2ts files are in blu-ray structure. Move those files outside this folder and you will get "correct" behaviour. You can also rename BDMV folder to something else.
I still think it would be much better to default to the file that was actually selected in the dropdown (which can still be changed manually... default behavior should be to keep it as simple as possible, so select the one I specifically opened by default). Seems like it should be extremely easy to implement.

It would avoid all the wasted time and power I spent on encoding the same things over and over again.
ejone is offline   Reply With Quote
Old 27th October 2018, 14:33   #16259  |  Link
byteshare
ByteShare
 
byteshare's Avatar
 
Join Date: Sep 2014
Location: On the Internet
Posts: 560
Quote:
I don't know what 'YV12' means.
Getting this on a lot of files when trying to import via batch.
Getting this on files that I've already encoded before.
I have the most recent version of RipBot.

If I retry them individually (add rather than batch) sometimes I get the error and sometimes not. Sometimes If I retry adding several times it works.

Last edited by byteshare; 27th October 2018 at 16:31.
byteshare is offline   Reply With Quote
Old 27th October 2018, 15:13   #16260  |  Link
Atak_Snajpera
RipBot264 author
 
Atak_Snajpera's Avatar
 
Join Date: May 2006
Location: Poland
Posts: 7,806
Quote:
Originally Posted by byteshare View Post
Getting this on a lot of files when trying to import via batch.
Getting this on files that I've already encoded before.
I have the most recent version of RipBot.
You need to find pattern. What file type is causing this? What setting do you use in batch mode? Do you use custom script and so on.
Atak_Snajpera is offline   Reply With Quote
Reply

Tags
264, 265, appletv, avchd, bluray, gui, iphone, ipod, ps3, psp, ripbot264, x264 2-pass, x264 gui, x264_64, x265, xbox360

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 09:58.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.