ClunkClunk

kapperz, I haven't tested it at all, but this should work (newest trunk release): http://www.clunkclunk.com/HandBrakeCLI-svn3282-unraid.tgz Please report back with success or fail.

I've compiled the most recent snapshot, svn3154 for unRAID as it's better with Foreign Audio Search than 0.9.4 (and some other minor improvements). Follow instructions in prior posts. http://www.clunkclunk.com/HandBrakeCLI-svn3154-unraid.tgz

My workflow is a bit more complicated to set up, but overall I'm pleased with how easy it is to use once I got it running. I rip a lot of movies and TV DVDs, so I needed a solution that would be somewhat flexible for both. • In my go script I install HandBrakeCLI 0.9.4, perl 5.10.0, screen 4.0.3, and copy two scripts to /usr/bin (optional - it's just so I don't have to type their path out each time). • I rip my DVDs to VIDEO_TS folders on my local computer, then transfer to my unRAID server. I separate TV and movie rips, as they get treated slightly differently. For my own organization, movies go in to /mnt/user/HandBrake/Movies/Ripped and TV goes in to TV/Ripped. Any folder structure works. • I then set up a quick screen session, then execute the relevant script (TV or movies). It runs continuously until it's done encoding every VIDEO_TS rip in the folder its been pointed to. The scripts are just very slightly modified versions of handbraker.pl. Long story short, this script traverses the folder you point it at, finds all the VIDEO_TS folders, HandBrake encodes every title in each VIDEO_TS folder that's more than 10 minutes long, using your settings. I like it over HandBrake's default setting of looking for the single longest title as it's more useful for getting extras, documentaries, and other bonus content from movie DVDs, and with a simple tweak, it's great for TV DVD encoding. I use the stock script, though I replaced all the quality settings with my own set of settings, and I made the time limit so it only encodes 20 minute+ titles, for movie encodes. For TV encodes, I added a little bit of logic that checks to see if the title is more than 20 minutes long, but less than 55 minutes long (so it grabs all titles that are TV episode length), then encodes them. As for quality settings - x264 all the way, but that's a discussion for another day, and another forum. My unRAID server is on a 2.5GHz Core 2 Duo, so encoding speeds are pretty rapid. With my fairly high quality settings, I see 25 to 30fps regularly, and even 40fps on some content. It's hard to compare apples to apples though, unless you're using identical settings with identical sources, as encoding speeds can vary with HandBrake a ton. I'll attach my modified versions of the handbraker.pl scripts in case anyone wants to see them. Let me know if you'd like help setting them up.

HandBrake 0.9.4 is out. Here's an unraid package, follow instructions in previous posts: http://www.clunkclunk.com/HandBrakeCLI-0.9.4-unraid.tgz

Thanks for the how-to aaronjb! I managed to compile the newest HandBrake snapshot, which is going down the path towards 0.9.4. I've been using it on my Macs for a few weeks now and it's been solid for my needs. If you want to use it, just use aaronjb's instructions, and substitute my package for his, and adjust your go script accordingly. http://www.mediafire.com/download.php?m50mncmnj3t

Something's not working correctly. It worked fine in both Firefox and Safari previously, and now clicking the calculate button doesn't do anything in either...

Thanks for the explanation, Joe :-)

Seagate 1.5TB 7200rpm: =========================================================================== = unRAID server Pre-Clear disk /dev/sdh = cycle 1 of 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Testing if the clear has been successful. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 35C, Elapsed Time: 18:41:55 ============================================================================ == == Disk /dev/sdh has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 54c54 < 1 Raw_Read_Error_Rate 0x000f 111 099 006 Pre-fail Always - 30858950 --- > 1 Raw_Read_Error_Rate 0x000f 119 099 006 Pre-fail Always - 206230051 58c58 < 7 Seek_Error_Rate 0x000f 070 060 030 Pre-fail Always - 12579753 --- > 7 Seek_Error_Rate 0x000f 071 060 030 Pre-fail Always - 12656194 64,66c64,66 < 189 High_Fly_Writes 0x003a 087 087 000 Old_age Always - 13 < 190 Airflow_Temperature_Cel 0x0022 064 046 045 Old_age Always - 36 (Lifetime Min/Max 35/36) < 195 Hardware_ECC_Recovered 0x001a 059 031 000 Old_age Always --- > 189 High_Fly_Writes 0x003a 080 080 000 Old_age Always - 20 > 190 Airflow_Temperature_Cel 0x0022 065 046 045 Old_age Always - 35 (Lifetime Min/Max 35/38) > 195 Hardware_ECC_Recovered 0x001a 056 031 000 Old_age Always 70,72c70,72 < 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 11016591118409 < 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 1999204935 < 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 1405887411 --- > 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 183124520603740 > 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 635175937 > 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 1250497505 ============================================================================ root@Tower:/boot# I'm looking for some interpretations on this data. I believe the firmware of this Seagate 1.5tb is not the one that was causing issues (it's a later one). Head flying hours concerns me, as that's nearly 1,200 millenia. Thanks!

I think a little checkbox next to a drive marking it as the cache drive would be effective.