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. |
28th September 2017, 13:08 | #15181 | Link |
Registered User
Join Date: Jan 2012
Posts: 104
|
Coexist?
I tried and there is a source of problems. When I create a job with version 1.21 then it will also show in job queue of 1.20.
So you have a source of error and must be very careful not to start a given job in the wrong version. Thats because there exists one single working directory for all version. Maybe in a future version this could be adapted. |
28th September 2017, 14:23 | #15184 | Link |
Registered User
Join Date: Feb 2008
Location: Brazil
Posts: 753
|
Exactly, unfortunately we can not create two temporary folders on the same partition, the folder is created automatically when we define a partition.
RipBot264 defines the location for temporary files by partition, not by folders. |
28th September 2017, 14:28 | #15185 | Link |
RipBot264 author
Join Date: May 2006
Location: Poland
Posts: 7,815
|
You can always use TEMP option (system temp folder. Usually in x:\Users\[user_name]\AppData\Local\Temp)
__________________
Windows 7 Image Updater - SkyLake\KabyLake\CoffeLake\Ryzen Threadripper |
28th September 2017, 15:09 | #15186 | Link |
Registered User
Join Date: Feb 2008
Location: Brazil
Posts: 753
|
But to speed up the process(demux) I use disk E as temporary and destination and D as source.
And C is an SSD that prevents overwriting, including the path of the temp folder has been changed to disk D. Changing the temp folder to disk D, my only alternative, would not speed up the process. |
28th September 2017, 15:21 | #15187 | Link | |||
Registered User
Join Date: Jan 2012
Posts: 104
|
Quote:
Quote:
Quote:
|
|||
28th September 2017, 18:25 | #15188 | Link | ||
ByteShare
Join Date: Sep 2014
Location: On the Internet
Posts: 560
|
Figured it out...almost.
Quote:
I ran the same problem videos on a different RipBot computer and I do not get the msuper error, the difference was 1 computer is on core build 2017.09.21 (works) and the other is on 2017.09.27 (does not work). I happened to close and open and got updated to 2017.09.25 and that version also had the msuper issue. I backed up my build on the working computer, updated to 2017.09.27 and I'm getting the same error. Will PM sample. Update: Sent PM with link to a file for testing Update Update: Either you're really fast or I missed an update, but I'm now on 2017.09.28 and it is working again Last edited by byteshare; 28th September 2017 at 19:53. Reason: Working |
||
28th September 2017, 19:54 | #15189 | Link | |
ByteShare
Join Date: Sep 2014
Location: On the Internet
Posts: 560
|
I think I got too excited. I'm not having issues while in the Preview but when I try to actually start an encode I'm getting:
Quote:
|
|
28th September 2017, 20:16 | #15190 | Link |
RipBot264 author
Join Date: May 2006
Location: Poland
Posts: 7,815
|
Update: nevermind. Thanks to your sample I see what is wrong.
__________________
Windows 7 Image Updater - SkyLake\KabyLake\CoffeLake\Ryzen Threadripper |
28th September 2017, 21:03 | #15191 | Link | |
ByteShare
Join Date: Sep 2014
Location: On the Internet
Posts: 560
|
Quote:
I changed my Code:
LastCheck= Reran the tests and the preview and the actual encoding process is working now. Not getting the info.txt issue. Didn't have to even re-add the jobs or anything |
|
1st October 2017, 20:27 | #15194 | Link |
Registered User
Join Date: Jan 2012
Posts: 104
|
Processing 16bit clip generated by avs only gives garbage
My AVISYNTH+ generates a 16bit clip YUV444P. I can add it as job to RipBot264 (newest 64bit version), and it will also encode.
However the resulting clip is complete garbage. (OK, audio is correct) It would be nice to have an error message when adding job. It would be even nicer if RipBot would support it. |
2nd October 2017, 05:41 | #15196 | Link |
Registered User
Join Date: May 2016
Location: Earth - Sol System, Milky Way, Virgo Cluster
Posts: 3
|
I'm also having Avisynth issues with 1.21, preventing me from using both RipBot and the encoding server.
When I try to prepare a job in RipBot, it fails to a blank "Decode Error" screen. When I try to push a job to the encoding server, it fails immediately on start, saying it couldn't load avisynth.dll. I've tried nuking my Avisynth installation and letting RipBot install it fresh but it hasn't helped. I've also tried manually reinstalling AviSynth to no avail. Encoding Server reports that I have Avisynth+ 0.1 (r2508, MT, x86-64). Here's an example error message from Encoding Server. Code:
Encoding started... ""\\{source machine}\Ripbot264temp\tools\avs2yuv\avs2yuv.exe" -seek 169 "\\{source machine}\RipBot264temp\job1\Chunks\36.avs" -o - | "\\{source machine}\Ripbot264temp\tools\x265\x265_x64.exe" --crf 19 --fps 24000/1001 --min-keyint 24 --keyint 240 --frames 1411 --sar 1:1 --rd 4 --psy-rd 1.5 --psy-rdoq 2.5 --aq-strength 1.5 --y4m --output "\\{source machine}\RipBot264temp\job1\Chunks\36.265" -" error: failed to load avisynth.dll x265 [error]: unable to open input file <-> Encoding terminated. Connection Closed Gracefully. |
2nd October 2017, 13:48 | #15197 | Link |
RipBot264 author
Join Date: May 2006
Location: Poland
Posts: 7,815
|
@BabyPuncher
https://support.microsoft.com/en-us/...al-c-downloads If I remember correctly you need version 2015 x64 Here is my compilation containing all version since 2010. http://www.mediafire.com/file/v8cwed...g/vc_redist.7z @Soneca I do not speak portuguese.
__________________
Windows 7 Image Updater - SkyLake\KabyLake\CoffeLake\Ryzen Threadripper Last edited by Atak_Snajpera; 2nd October 2017 at 13:59. |
2nd October 2017, 18:42 | #15198 | Link | |
Registered User
Join Date: Feb 2008
Location: Brazil
Posts: 753
|
Quote:
Message says that an invalid media type was specified. How do I set a color space in version 1.21.0? |
|
3rd October 2017, 02:37 | #15199 | Link | |
Registered User
Join Date: May 2016
Location: Earth - Sol System, Milky Way, Virgo Cluster
Posts: 3
|
Quote:
Thanks that did the trick |
|
5th October 2017, 21:50 | #15200 | Link |
ByteShare
Join Date: Sep 2014
Location: On the Internet
Posts: 560
|
AVS2YUV.exe
It might just be me but since the switch to 64bit AVISynth I feel that the AVS2YUV.exe has been crashing more. It also happened in the past but much less so.
https://imgur.com/a/sF2ty Code:
Problem signature: Problem Event Name: APPCRASH Application Name: avs2yuv.exe Application Version: 0.0.0.0 Application Timestamp: 4e78e879 Fault Module Name: ntdll.dll Fault Module Version: 6.1.7601.23889 Fault Module Timestamp: 598d5074 Exception Code: c0000026 Exception Offset: 00000000000c8078 OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 1033 Additional Information 1: e2d5 Additional Information 2: e2d5003a216db1cab2c94354ea6fa1f8 Additional Information 3: 16a0 Additional Information 4: 16a02affa9044e7398158527105fddca Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt I think this isn't a RipBot issue per say, since it is the AVS2YUV.exe, but it also doesn't seem to be a consistent issue, meaning I could encode the same chunk more than once and it won't always happen, and I don't believe I've seen it happen where AVS2YUV.exe crashes and I stop the server, close the error, and start the server again and then AVS2YUV.exe crashes again, so maybe it is a memory issue? Last edited by byteshare; 5th October 2017 at 22:50. |
Tags |
264, 265, appletv, avchd, bluray, gui, iphone, ipod, ps3, psp, ripbot264, x264 2-pass, x264 gui, x264_64, x265, xbox360 |
|
|