RipBot264 v1.18.3 - Simple and easy to use GUI -> IPOD . PSP . CONSOLES . BLURAY

[jerky33]

Originally Posted by Atak_Snajpera

jerky33
find ripbot264_update_2012-02-12.7z

page538

This is great, I like that you shrunk the size of the chunks this should greatly improve efficiency as I have 1 slower machine on my network that was bogging down encoding jobs, especially when it was the last to finish up.

Thanks for directing me to the update, and keep up the good work.

[73ChargerFan]

Requests:
1) In New Job, Properties dialog where you can change deinterlacing, cropping, etc, if no changes were made, then exiting the dialog should be instant, no gathering of information
2) As part of job control, after audio is encoded once, note the time stamp. If the job is re-run and the audio settings, track, audio rip, etc haven't change, then don't encode audio again.
3) In "Encoding Settings" add quickie field to encode 10 second segment. An enable button & beginning time would be required.

Thanks Atak as always.

[jerky33]

I understand that the folks on this forum are not responsible for the x264 project directly, but was wondering if anybody knew if the x264 project had plans to take advantage of GPU based hardware for their encoding application?

[Atak_Snajpera]

no plans. too much work.

[Slitheen]

Latest release seems a bit buggy. Shutdown when finished doesn't work. I had to go into task manager to close the application and the temp folder is not emptying by itself.

[BosDvD]

How can i use this program in internet , not network ? (disturbed encoding)

Can i do it hamachi or something like that..?

[Wishbringer]

For distributed encoding computing clients need to have access to source material (e.g. Bluray-rips).
So for example, if you have a 40GB Source, and a local computing client and a remote computing client with nearly same performance,
you would have to transfer 20GB to your remote client.
Do you really want that?!
Additional remote client has to transfer computed result (smalller than that 20GB) back to source for muxing.

Maybe you have a synchron 100MBit Internet access, then it is possible (short transfer time),
but if you have an asynchron DSL connection (16.000/1000 kbit/sek).... good luck.... upload sucks... in both ways... upload from source to client and upload results from clients back to source.

[archaeo]

Originally Posted by Slitheen

Latest release seems a bit buggy. Shutdown when finished doesn't work. I had to go into task manager to close the application and the temp folder is not emptying by itself.

Found the same issues here...

[soneca]

Originally Posted by Slitheen

Latest release seems a bit buggy. Shutdown when finished doesn't work. I had to go into task manager to close the application and the temp folder is not emptying by itself.

It has been repaired a long time.
This is the latest update.

[BosDvD]

Yep, i know. I have 4 server ,1gbit duplex conn. so it's not problem Teamviewer VPN app. is failed :/

[Slitheen]

Originally Posted by soneca

It has been repaired a long time.
This is the latest update.

This thread is 546 pages long. That update should be on page one with latest version. Let's have some initiative.

[Selur]

@Atak_Snajpera: got a question regarding fhg aac encoder: Did you check if WinAmps license allows the redistribution of the .dlls ?
(I was wondering since I added support for fhgaacenc but I'm not sure if it's okay to bundle the dlls with the Hybrid installer,..)

[Shrekage]

Originally Posted by BosDvD

Yep, i know. I have 4 server ,1gbit duplex conn. so it's not problem Teamviewer VPN app. is failed :/

first thing you have to do is make sure you have SMB access (can access \\server\ripbot264temp from each client PC.
second then you have to make sure your firewall allows the server app access.

I have successfully used the distributed encoding over a routed network without issue

[JimmyK814]

Originally Posted by Shrekage

first thing you have to do is make sure you have SMB access (can access \\server\ripbot264temp from each client PC.
second then you have to make sure your firewall allows the server app access.

I have successfully used the distributed encoding over a routed network without issue

Shrekage, what type of setup do you have? Are you using a HomeGroup? I have a domain setup, and after a month or more of trying, I can't get it to work.

[Shrekage]

Originally Posted by JimmyK814

Shrekage, what type of setup do you have? Are you using a HomeGroup? I have a domain setup, and after a month or more of trying, I can't get it to work.

I have a Windows 2008 R2 server that I use for media streaming. it is a Dell Poweredge 1950 with 2 Dell powervault MD1000's attached. I have a specific volume of striped drives that I use for temp space for encoding. It has a drive letter of A. the drive is administratively shared as a$. Also, I have the a:\temp\ripbot264temp shared as \\server\ripbot264temp with "Domain Users" having full control. I also set the folder permissions giving domain users full control.

Each encoding server PC has the a: drive mapped to \\server\a$.

That drive has the following folders

a:\source (all source material goes there)
a:\temp\ripbot264temp (temporary space for ripbot264)
a:\ripbotoutput (all output from ripbot is directed there

On each machine ripbot is run on, I placed the ripbot files in c:\program files (x86)\RipBot, and made shortcuts in the startmenu.

in each encoding server, I started up the server and verified that it created an exception in the firewall. on the client, I fired up the encoding client by itself and verified that I can connect to the encoding servers. once that was done, I started some testing with various source files...

I actually found that on some files the encodign cliend did not copy the file to the shared folder, but instead referred it to it's location on the server (a:\source\folder\file) so mapping the drive to the same letter on the encoding server solved that problem

[Atak_Snajpera]

I actually found that on some files the encodign cliend did not copy the file to the shared folder, but instead referred it to it's location on the server (a:\source\folder\file) so mapping the drive to the same letter on the encoding server solved that problem

what files? extensions? .avi , .mp4 .mkv...

On each machine ripbot is run on, I placed the ripbot files in c:\program files (x86)\RipBot, and made shortcuts in the startmenu.

Frankly you just need EncodingServer.exe. You can copy that file to Autostart folder.

[Shrekage]

Originally Posted by Atak_Snajpera

what files? extensions? .avi , .mp4 .mkv...

after it happened on a .mpg file I mapped the drive and have not had any more issues. I have planned to unmap it and test with other file types to get a list but have not had time to do it yet. to be clear on what happened there, Ripbot created a job#.d2v file that points to the .mpg in the drive source. I can zip up the job file and attach if you want to see it...



I should also add that it does not seem to want to start the distributed encoding for .TS or .VOB files either. is this expected as I found that if I go in and trick ripbot it will distribute the encoding for these file types...

[Atak_Snajpera]

after it happened on a .mpg file I mapped the drive and have not had any more issues. I have planned to unmap it and test with other file types to get a list but have not had time to do it yet

for now only .vob (from DVD structure!) .mp4 and .mkv are copied. .TS is not well supported by FFMS2 decoder (Interlaced stream for example) so I can add it to DE mode yet.

[Shrekage]

Originally Posted by Atak_Snajpera

for now only .vob .mp4 and .mkv are copied. I can add .mpg as well.

I would say that should be done even though I found a workaround for my situation.

as for the .TS files... I have had these for a very long time. and I dont have that many so it's not a big proglem...

Thanks!

[Atak_Snajpera]

for .mpg you can trick ripbot by remuxing all your mpg collection to .mkv