BOLT (again)
drdrbob
times) with 1.3.3g, both with and without .dvdmedia extension (2 times
each). Each time Ripit stalls at 18 or 19 seconds left and 99.2%
complete. The resulting files all say "incomplete movie," and DTOX
says its not a valid movie. Still hoping for a fix. Thanx. Bob Gale
Scott
I'm literally making a shopping list right now and thats at the top of
the list. I'm going to try and find it locally to get it quicker.
Once I have it in hand, I'll start debugging. It's likely another
custom trap thats leading RipIt into some bad sectors. As soon as I
finish it, I'll have a new beta pushed with it.
Kind regards,
Scott, TLAF
Brian Donovan
Scott
I couldn't find the exact same ISBN locally, and wound up getting ISBN
0-7888-9594-X, and it ripped, transcoded with Handbrake, and imaged
with DVD2one without error. I'll have to order the exact same one
that you're using. If you open the console, do you see any messages
like "read error" appearing (or other detail). And you're sure the
disc is clean? Can you play in OSX DVD Player and then scan forward
at 32X from start to finish on the main movie without seeing any read
errors overlay? Sorry to ask these question, just wanted to double
check. Are you on an Intel or PowerPC machine?
Hi Brian,
Studios can't do anything to a disc that would obviously mess up the
playback on DVD players, but there is quite a bit of room that allows
them to make copying more difficult. They commonly modify the file
system entries on the discs to create files that physically overlap
other files. So even through they can only store single digital GBs
of data, because the file system reuses sectors for multiple
overlapping files, the computer thinks there might be 60GB+ on a
single disc (which isn't possible). That protection results in really
big copies if you attempt to copy all the files on it. The more
complex and cumbersome is how bad sectors are intentionally placed on
the disc at strategic places. The programming is designed so that
normal play will never hit the sectors but hidden pathways that a
computer might find will lead to them ... causing bad reads of the
disc. They're in locations where a normal user is likely not to
stumble on, but a computer analyzing it will. For instance, the new
Transformers menu is designed in a way that you can do a certain
series of navigations in the menu and wind up going into a title set
that has bad sectors. Its all legitimate DVD programming, but you
have to code to attempt to avoid those "traps." I hope this vague
summary gives an idea of how some disc work.
Kind regards,
Scott, TLAF
Scott
If you are using a PowerPC based Mac, could you download and try this
version?
http://files.thelittleappfactory.com/ripit/RipIt-beta-ppc.zip
Just ignore that link if you're on an Intel based Mac.
Thanks,
Scott, TLAF
randian
wonky navigation. According to the original author, RipIt was designed
using a software model of a DVD player as its base. If that model is
compliant with the DVD spec, it should perfectly rip anything that
doesn't also cause failures on real DVD players. If RipIt fails, that
means it's out of compliance in some way. Preferably, that should be
fixed by writing to the spec rather than accumulating ad-hoc fixes for
DVDs that don't rip now.
Scott
Actually, a 100% compliant emulation model will trip on protections
such as ARccOS. Take the new Transformers disc for example. One of
the menus includes about 7 visible buttons, however the program has
over 20 buttons that overlap to only look like 7. These buttons
overlap so that you can navigate around like normal, however a certain
series of steps will take you to a button that leads to a title set
that is intentionally damaged with bad sectors. All of the
programming in the nav packs, and program chains are completely
compliant with the DVD specification, but the VOB files include bad
sectors manufacturer into the disc. A user is just unlikely to
navigate the specific series of steps on a DVD player to that bad
title set, while an emulation model traversing all the options would.
Conversely, if a software emulation model isn't used to locate and
extract only the desired content, schemes that use overlapping VOB
sets result in huge rips. If you were to include all the title sets
on the Transformers disc, you'd wind up with a rip well over 60GB in
size (the size shown by 'get info' on the video_ts folder).
Studios will continue to come out with different implementations of
these protection schemes, that will require some fixes. I do my best
to code fixes to protect against different strategies rather than a
single specific defensive measure.
Kind regards,
Scott, TLAF
Bob Gale
I'm using an early 2008 MacPro (Intel), 16gb RAM, OSX10.5.8 (Leopard).
The ISBN #0-7888-9208-8 may be different because there is a digital copy for iTunes along with the regular disc.
I just ran the regular disc (in the MacPro using DVD player) at 32x fast forward with no apparent problems. Also watched portions in regular time with no issues. Ditto on my Sony DVD player/TV.
Console messages from earlier today:
2/10/10 10:16:42 PM Disk Utility[3857] Unable to burn “BOLT.toast”. (Resource temporarily unavailable)
2/10/10 10:16:42 PM Disk Utility[3857]
I was trying yesterday to burn a Toast image that was made from an earlier rip with many extra gb, even though the saved image was the right size.
Today:
2/11/10 12:13:59 PM RipIt[4598] unlockFocus called too many time.
2/11/10 12:26:29 PM Software Update[4647] arguments=(null)
2/11/10 12:32:16 PM com.apple.launchd[146] (0x10e550.Locum[4682]) Exited: Terminated
2/11/10 12:46:01 PM com.apple.launchd[146] ([0x0-0x183183].com.thelittleappfactory.RipIt[4598]) Exited: Terminated
2/11/10 12:46:26 PM DVD2oneX2[4724] starting loop
2/11/10 12:46:36 PM DVD2oneX2[4724] Src to UTF8
There are also multiple notices in a "Hang Log" about Ripit. And comments (seemingly unfavorable) about my Sonnet Tempo eSATA card and VM Fusion, but I have no clue about this level of what I assume is UNIX functioning.
Unfortunately, I can't offer any help. Although I'm considered to be computer literate by my friends, its not at todays programming levels (out in the cold since my RealBasic days many years ago on a VideoBrain and then an Apple 2). Maybe in my next life.
Let me know if there is anything else I should try or look for.
Bob
On Thursday, February 11, 2010, at 07:02PM, "Scott" <sc...@tlaf.com> wrote:
>Hi Bob,
>
>I couldn't find the exact same ISBN locally, and wound up getting ISBN
>0-7888-9594-X, and it ripped, transcoded with Handbrake, and imaged
>with DVD2one without error. I'll have to order the exact same one
>that you're using. If you open the console, do you see any messages
>like "read error" appearing (or other detail). And you're sure the
>disc is clean? Can you play in OSX DVD Player and then scan forward
>at 32X from start to finish on the main movie without seeing any read
>errors overlay? Sorry to ask these question, just wanted to double
>check. Are you on an Intel or PowerPC machine?
>Kind regards,
>Scott, TLAF
On Thursday, February 11, 2010, at 07:02PM, "Scott" <sc...@tlaf.com> wrote:
>Hi Bob,
>
>I couldn't find the exact same ISBN locally, and wound up getting ISBN
>0-7888-9594-X, and it ripped, transcoded with Handbrake, and imaged
>with DVD2one without error. I'll have to order the exact same one
>that you're using. If you open the console, do you see any messages
>like "read error" appearing (or other detail). And you're sure the
>disc is clean? Can you play in OSX DVD Player and then scan forward
>at 32X from start to finish on the main movie without seeing any read
>errors overlay? Sorry to ask these question, just wanted to double
>check. Are you on an Intel or PowerPC machine?
>Kind regards,
>Scott, TLAF
>
>
Scott
Here's a shot in the dark. Do you have the animation enabled in
preferences? if so, try disabling the animation, exit & relaunch
RipIt, and then try ripping the disc.
Our machine configurations appear very similar, except I'm running on
10.6.2. I'll go through more testing on my 10.5 machine as well.
We'll also go ahead and get the same ISBN version ordered as well.
Kind regards,
Scott, TLAF
Brian Donovan
bad sectors that you can navigate to, but that for a normal user it'd
be nearly impossible to do.
If that's the case then you can't go just with the spec and expect it
to work properly. You'd probably need to develop some heuristics for
determining "not human-navigable".
-bd
Brian Donovan
was no longer relevant.
-bd
Bob Gale
I tried the "Shot in the Dark"...If only Elke Sommer were here to help...
Sadly, same outcome. Stalls at 18 seconds remaining, 99.2% completed, and requires a force quit.
From console:
2/12/10 11:51:22 AM RipIt[244] unlockFocus called too many time.
2/12/10 12:22:26 PM com.apple.launchd[149] ([0x0-0x20020].com.thelittleappfactory.RipIt[244]) Exited: Terminated
I think my Sonnet Tempo card is corrupted (drives external eSATA discs, but the BOLT rip is from the DVD). I'm replacing it later this afternoon with a recently released Firmtek card the drive containers are all Firmtek and I've had trouble with Sonnet in the past). I don't think this is related to Ripit but I'll try anyway and let you know if it works.
Bob
randian
> If that's the case then you can't go just with the spec and expect it
> to work properly. You'd probably need to develop some heuristics for
> determining "not human-navigable".
Sounds like you'd have to determine the on-screen location of
navigable menu items, see which overlap, and choose the one that is
displayed last. That's the one that will be on top and clickable.
Nasty.