0 Items in Your cart
Shopping cart ![[]](/sites/all/modules/ecommerce/cart/images/cart_empty.png "View your cart items")
User login
Recent News
Poll
Recent comments
- Always select the folder as the source
20 hours 30 min ago - We have never supported Adaptec cards
20 hours 35 min ago - "Did the trick" = read/compare/verify success?
23 hours 35 min ago - Larry - Was there EVER a solution for this found?
23 hours 50 min ago - Intended workflow...
1 day 15 min ago - my priorities
1 day 11 hours ago - I would get an ATTO card
2 days 10 hours ago - Help decide the future of Blu Ray on the Mac OS
2 days 21 hours ago - I would get an ATTO card
3 days 4 hours ago - More on the subject
3 days 14 hours ago
Active forum topics
Resources
Syndicate
Replace VTS causes crashes
Wed, 2008-03-26 05:57 — geraint78
Hi,
I'm having a problem with continual crashes of DVDAE. What I want to do is replace one VTS with another one in which I have removed a logo. The thing is though, that whenever I select the command "Replace VTS" the software crashes. I have tried with different VIDEO_TS folders as well as on my MacBook.
I'll paste my latest crash report below.
Is there a way around this, or do I need to call my client and ask them to go somewhere else? (Sorry for the dramatics, but that's just the way it is)
I hope you are able to help me.
Kind regards,
David
Process: DVDAfterEdit [753]
Path: /Applications/DVDAfterEdit
Identifier: com.tfdvd.DVDAfterEdit
Version: DVDAfterEdit version 3.0.4 (3.0.4)
Code Type: PPC (Native)
Parent Process: launchd [145]
Date/Time: 2008-03-26 13:45:34.075 +0100
OS Version: Mac OS X 10.5.2 (9C7010)
Report Version: 6
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000008
Crashed Thread: 11
Thread 0:
0 libSystem.B.dylib 0x965c4978 mach_msg_trap + 8
1 libSystem.B.dylib 0x965cb89c mach_msg + 56
Thread 1:
0 libSystem.B.dylib 0x965c4978 mach_msg_trap + 8
1 libSystem.B.dylib 0x965cb89c mach_msg + 56
2 ...ple.CoreServices.CarbonCore 0x9270b5ec YieldToThread + 528
3 ...ple.CoreServices.CarbonCore 0x927109c8 SetThreadState + 168
4 ...ple.CoreServices.CarbonCore 0x927108f0 SetThreadStateEndCritical + 132
5 ??? 0x0038598c 0 + 3692940
6 ??? 0x003853f8 0 + 3691512
7 ??? 0x00386c0c 0 + 3697676
8 ??? 0x00387270 0 + 3699312
9 ...ple.CoreServices.CarbonCore 0x92710818 CooperativeThread + 344
10 libSystem.B.dylib 0x96606b98 _pthread_start + 316
Thread 2:
0 libSystem.B.dylib 0x965c4978 mach_msg_trap + 8
1 libSystem.B.dylib 0x965cb89c mach_msg + 56
2 ??? 0x00387270 0 + 3699312
3 ...ple.CoreServices.CarbonCore 0x92710818 CooperativeThread + 344
4 libSystem.B.dylib 0x96606b98 _pthread_start + 316
Thread 3:
0 libSystem.B.dylib 0x965c4978 mach_msg_trap + 8
1 libSystem.B.dylib 0x965cb89c mach_msg + 56
2 com.apple.CoreFoundation 0x96d0e618 CFRunLoopRunSpecific + 1828
3 com.apple.CoreFoundation 0x96d0eea8 CFRunLoopRun + 60
4 com.apple.DesktopServices 0x918d6cf0 TSystemNotificationTask::SystemNotificationTaskProc(void*) + 104
5 ...ple.CoreServices.CarbonCore 0x926dbfc4 PrivateMPEntryPoint + 76
6 libSystem.B.dylib 0x96606b98 _pthread_start + 316
Thread 4:
0 libSystem.B.dylib 0x965c4978 mach_msg_trap + 8
1 libSystem.B.dylib 0x965cb89c mach_msg + 56
2 com.apple.CoreFoundation 0x96d0e618 CFRunLoopRunSpecific + 1828
3 com.apple.CoreFoundation 0x96d0eea8 CFRunLoopRun + 60
4 com.apple.DesktopServices 0x918d6e6c TFSEventsNotificationTask::FSEventsNotificationTaskProc(void*) + 176
5 ...ple.CoreServices.CarbonCore 0x926dbfc4 PrivateMPEntryPoint + 76
6 libSystem.B.dylib 0x96606b98 _pthread_start + 316
Thread 5:
0 libSystem.B.dylib 0x965cb38c __semwait_signal + 12
1 libSystem.B.dylib 0x96607f40 _pthread_cond_wait + 1580
2 ...ple.CoreServices.CarbonCore 0x926de1d4 TSWaitOnCondition + 132
3 ...ple.CoreServices.CarbonCore 0x926bc5c0 TSWaitOnConditionTimedRelative + 204
4 ...ple.CoreServices.CarbonCore 0x926ddd90 MPWaitOnQueue + 272
5 com.apple.DesktopServices 0x918e28e8 TNodeSyncTask::SyncTaskProc(void*) + 88
6 ...ple.CoreServices.CarbonCore 0x926dbfc4 PrivateMPEntryPoint + 76
7 libSystem.B.dylib 0x96606b98 _pthread_start + 316
Thread 6:
0 libSystem.B.dylib 0x966063d8 kevent + 12
1 com.apple.CoreFoundation 0x96ce5ed4 __monitor_file_descriptor__ + 88
Thread 7:
0 libSystem.B.dylib 0x96629004 select$DARWIN_EXTSN + 12
1 com.apple.CoreFoundation 0x96d19a68 __CFSocketManager + 764
Thread 8:
0 libSystem.B.dylib 0x965c49f8 semaphore_timedwait_signal_trap + 8
1 libSystem.B.dylib 0x96607e3c _pthread_cond_wait + 1320
2 com.apple.Foundation 0x90a3d898 -[NSCondition waitUntilDate:] + 384
3 com.apple.Foundation 0x90a3d6c4 -[NSConditionLock lockWhenCondition:beforeDate:] + 268
4 com.apple.AppKit 0x90e26b80 -[NSUIHeartBeat _heartBeatThread:] + 664
5 com.apple.Foundation 0x90a004f4 __NSThread__main__ + 1004
6 libSystem.B.dylib 0x96606b98 _pthread_start + 316
Thread 9:
0 libSystem.B.dylib 0x965c49f8 semaphore_timedwait_signal_trap + 8
1 libSystem.B.dylib 0x96607e3c _pthread_cond_wait + 1320
2 ...ple.CoreServices.CarbonCore 0x926bc5e4 TSWaitOnConditionTimedRelative + 240
3 ...ple.CoreServices.CarbonCore 0x926bc3b8 TSWaitOnSemaphoreCommon + 428
4 ...ple.CoreServices.CarbonCore 0x926bc07c AsyncFileThread(void*) + 64
5 libSystem.B.dylib 0x96606b98 _pthread_start + 316
Thread 10:
0 libSystem.B.dylib 0x965c49f8 semaphore_timedwait_signal_trap + 8
1 libSystem.B.dylib 0x96607e3c _pthread_cond_wait + 1320
2 ...ple.CoreServices.CarbonCore 0x926bc5e4 TSWaitOnConditionTimedRelative + 240
3 ...ple.CoreServices.CarbonCore 0x926bc3b8 TSWaitOnSemaphoreCommon + 428
4 ...ple.CoreServices.CarbonCore 0x926ee458 TimerThread + 68
5 libSystem.B.dylib 0x96606b98 _pthread_start + 316
Thread 11 Crashed:
0 com.apple.HIToolbox 0x91a40fa0 GetDITLCount(_DialogRec*) + 0
1 com.apple.HIToolbox 0x91a48a60 CountDITL + 12
2 com.apple.AppKit 0x913c78f0 _NSNavCustomControl + 2352
3 com.apple.NavigationServices 0x91e87fc4 NavCustomControl + 76
4 ??? 0x0045b830 0 + 4569136
5 ??? 0x0045b214 0 + 4567572
6 ??? 0x0041fc0c 0 + 4324364
7 ??? 0x00420668 0 + 4327016
8 com.apple.AppKit 0x913c5290 SendStartEvent + 228
9 com.apple.AppKit 0x913c5424 -[NSNavSavePanel sendCBEvent:withData:] + 160
10 com.apple.AppKit 0x913c7d04 -[NSNavSavePanel willBecomeVisibleNotification:] + 100
11 com.apple.Foundation 0x909ffea4 _nsnote_callback + 372
12 com.apple.CoreFoundation 0x96cf095c _CFXNotificationPostNotification + 920
13 com.apple.Foundation 0x909fd6d8 -[NSNotificationCenter postNotificationName:object:userInfo:] + 88
14 com.apple.AppKit 0x90e75b58 -[NSWindow _reallyDoOrderWindow:relativeTo:findKey:forCounter:force:isModal:] + 768
15 com.apple.AppKit 0x913c2f74 -[NSNavSavePanel _reallyDoOrderWindow:relativeTo:findKey:forCounter:force:isModal:] + 432
16 com.apple.AppKit 0x90eb26b4 -[NSApplication _orderFrontModalWindow:relativeToWindow:] + 704
17 com.apple.AppKit 0x90eb21a4 -[NSApplication _commonBeginModalSessionForWindow:relativeToWindow:modalDelegate:didEndSelector:contextInfo:] + 836
18 com.apple.AppKit 0x90fc91f4 -[NSApplication runModalForWindow:] + 128
19 com.apple.AppKit 0x90fbacfc -[NSSavePanel(NSSavePanelRuntime) runModalForDirectory:file:types:] + 260
20 com.apple.AppKit 0x913c317c -[NSNavOpenPanel run] + 140
21 com.apple.AppKit 0x913c6d00 _NSNavDialogRun + 240
22 ??? 0x00420b1c 0 + 4328220
23 ??? 0x00455b74 0 + 4545396
24 ??? 0x004540e0 0 + 4538592
25 ??? 0x0037fa50 0 + 3668560
26 ??? 0x003855bc 0 + 3691964
27 ??? 0x00387270 0 + 3699312
28 ...ple.CoreServices.CarbonCore 0x92710818 CooperativeThread + 344
29 libSystem.B.dylib 0x96606b98 _pthread_start + 316
Thread 12:
0 libSystem.B.dylib 0x965c49f8 semaphore_timedwait_signal_trap + 8
1 libSystem.B.dylib 0x96607e3c _pthread_cond_wait + 1320
2 ...ple.CoreServices.CarbonCore 0x926bc5e4 TSWaitOnConditionTimedRelative + 240
3 ...ple.CoreServices.CarbonCore 0x926ddd90 MPWaitOnQueue + 272
4 com.apple.DesktopServices 0x918e9c84 TPropertyTask::PropertyTaskProc(void*) + 100
5 ...ple.CoreServices.CarbonCore 0x926dbfc4 PrivateMPEntryPoint + 76
6 libSystem.B.dylib 0x96606b98 _pthread_start + 316
Thread 13:
0 libSystem.B.dylib 0x965c49f8 semaphore_timedwait_signal_trap + 8
1 libSystem.B.dylib 0x96607e3c _pthread_cond_wait + 1320
2 ...ple.CoreServices.CarbonCore 0x926bc5e4 TSWaitOnConditionTimedRelative + 240
3 ...ple.CoreServices.CarbonCore 0x926ddd90 MPWaitOnQueue + 272
4 com.apple.DesktopServices 0x918e45a8 TFolderSizeTask::FolderSizeTaskProc(void*) + 88
5 ...ple.CoreServices.CarbonCore 0x926dbfc4 PrivateMPEntryPoint + 76
6 libSystem.B.dylib 0x96606b98 _pthread_start + 316
Thread 14:
0 libSystem.B.dylib 0x965c49f8 semaphore_timedwait_signal_trap + 8
1 libSystem.B.dylib 0x96607e3c _pthread_cond_wait + 1320
2 ...ple.CoreServices.CarbonCore 0x926bc5e4 TSWaitOnConditionTimedRelative + 240
3 ...ple.CoreServices.CarbonCore 0x926ddd90 MPWaitOnQueue + 272
4 com.apple.DesktopServices 0x918e9c84 TPropertyTask::PropertyTaskProc(void*) + 100
5 ...ple.CoreServices.CarbonCore 0x926dbfc4 PrivateMPEntryPoint + 76
6 libSystem.B.dylib 0x96606b98 _pthread_start + 316
Thread 11 crashed with PPC Thread State 32:
srr0: 0x91a40fa0 srr1: 0x0200f030 dar: 0x00000008 dsisr: 0x40000000
r0: 0x913c78f4 r1: 0xf03087b0 r2: 0x054be950 r3: 0x00000000
r4: 0xffffe989 r5: 0x64726566 r6: 0xf0308668 r7: 0x00000003
r8: 0x054be9a0 r9: 0x054be9a0 r10: 0xffffffff r11: 0xa0178358
r12: 0x91a48a54 r13: 0xa0cb3d5c r14: 0x001479e0 r15: 0xf0309ba8
r16: 0x00000000 r17: 0xa019853c r18: 0x00197cf4 r19: 0x0094aa00
r20: 0x00106150 r21: 0x43300000 r22: 0xa01b6fd0 r23: 0x05441aa0
r24: 0xf03088e0 r25: 0x00185340 r26: 0x054bc8b0 r27: 0x00000000
r28: 0xf0309358 r29: 0xf0308930 r30: 0x0094aa00 r31: 0x913c6fd0
cr: 0x24042438 xer: 0x00000000 lr: 0x91a48a64 ctr: 0x91a48a54
vrsave: 0x80000000
Leopard has broken some carbon dialog callbacks
I ran some additional tests on my G4 Powerbook under Leopard. Even though the debugger doesn't work, I tried commenting thing out to see what was crashing, and used other means to see how far it gets in the code.
The replace VOB code uses some complex filtering on the dialogs. Though it would be possible to eliminate some of them and force the user to make the right choices, I feel this will be a losing battle as Leopard evolves and leaves Carbon support further behind.
So for now, we must say that Tiger or Panther is required to support all features of DVDAfterEdit. Opening a VIDEO_TS folder and formatting to disc or DDP folder still appear to work fine.
Regards,
Larry
Thanks for the feedback
Thanks for the feedback guys, tonight I will try some testing around the Permissions theory:
Once we know the outcome of these I'll add a Known Issue to the Release Notes and also add a news post explaining the issue.
I guess an external firewire boot drive with Tiger installed is the workaround for now :-(
Ian
VTS Import crash under Leopard
I replaced VTS on PowerBook G4 under Tiger and brought the project back on Leopard machine to finish the re-authoring. Opened fine on Leopard G5 machine, and formatted without errors. Fingers crossed now for Eclipse verification. Hopefully, this is the end of story.
I think a list of known problems under Leopard should be added to the documentation. Good luck with BD product, can't wait for it.
Now I am seriously considering going back to Tiger.
Alex
Powerbook Leopard Crashes also
Tried it on my Powerbook with Leopard and it crashed just as you described, trying to put up the file dialog I suppose. Weird.
Unfortunately the CodeWarrior Debugger doesn't work under Leopard either. I have a call in to John Brisbin, but we may be at the end of the line with this. For the time being please stick with Tiger for mission-critical work.
Regards,
Larry
DVD AE crashes when replacing VTS
Guys, thank you for your replays and suggestions. My case however does not involve networked or external FireWire drives. All files reside on local drives. Here is the workflow of this particular case: Copying files under Mac OS 10.5.2 from non-CSS protected DVD onto local drive. DVD After (latest version of course) alerts that some files in Video_TS folder are not writable/locked. Leopard sees the original DVD as read-only for all users and groups and inherits the permissions on copied files. Changing permissions in Finder and opening VIDEO_TS folder. Replacing VTS (muxed on the same drive) immediately crashes the program. (I've sent Larry a copy of Appple's crash report).
By the way, the new VTS includes 4 audio DD streams and 12 subtitles streams. It took DVD SP 4.2.1 about 8 hours to mux.
I copied the files to the G4 Powerbook running Mac OS 10.4.11 and the job was done in minutes.
Alex
Sounds like a mysterious
Sounds like a mysterious network problem. DVDAE does not add spurious extensions to file names, everything it does is very vanilla. But we also have had reports of crashes that happen only with raid arrays on a network, so it is perplexing.
Regards,
Larry
Exposing file extensions is a Finder preference
If "Show all file extensions" is checked under Finder prefs, you should be able to see and remove the '.txt' extension from the file under OSX. Assuming that's the only problem (and that's a nasty one) all should be good afterwards. There's certainly no need to haul these large files around and muck with them on a Windoze machine. ;->
FWIW...
Michael
That's correct
Hi Alex,
Yes.
Even if you import/replace a VOB in DVDAfteredit on another machine running Tiger, and bring it over to a Leopard machine, the program will crash trying to load the adjusted VIDEO_TS folder.
The underlying problem seems (it's still somewhat of a mystery) to have something to do with how DVDAfterEdit is suffixing imported/replaced VOBs with an additional ".txt". So the imported/replaced VOB file will be named, for example: "VTS_01_1.VOB.txt". This is invisible to the naked eye on the Mac, but can be readily seen when you move an adjusted VIDEO_TS folder resident on a Fire wire drive over to a Windows machine. There, the VIDEO_TS folder won't play, and if you try to rename the VOB file back to some semblance of normalcy, removing the illegal '.txt' at the end of the file names, the Windows computer will go into a hard lock up (the file name change will stick, and be back to normal when you reboot).
Maybe Leopard is reporting these 'invisible" but still there out of spec .txt extensions to DVDAfterEdit causing the crashing, since these file names aren't 'expected'?
I've had some luck on my 8-core running Leopard importing and replacing VOBs if both source and target VIDEO_TS folders reside on internal drives; so maybe those .txt extensions aren't created, in that case, or might not cause a problem? Sending a VIDEO_TS folder resident on a local hard drive over to Windows machines on the network, does not exhibit the incorrectly extensioned imported/replaced VOB file names. So maybe it has something to do with just external drive usage, as you suggest?
Take care,
Trai
--
Trai Forrester
TFDVD Research Labs
DVDVerification.com
Replace VTS causes crashes under Leopard
Hi guys,
I too am having problems with Leopard (10.5.2) on both MacPro (Intel) and G5 (PPC). Replace VTS command causes DVD AE to crash on both machines, but on PowerBook G4 running Mac OS 10.4.11 things are fine. I also suspect that my DDP formatting problems that I reported in another thread are related to Leopard. Leopard new permissions scheme is a total mess, especially when dealing with volumes that were originally formatted and used with system software prior to 10.5. It does not really matter if Leopard is a clean install, or an upgrade install. It royally messes permissions on other volumes, and there is nothing Disc Utility can do.
Hi David, Sorry not to reply
Hi David,
Sorry not to reply sooner, I didn't see your post when I logged in yesterday, for some reason. We aren't aware of any Leopard-specific problems, however I'll take a look into this for you. One instant thought - I know some people have had problems with networked or very large external hard drives - it might be worth moving your project to the system drive, if it isn't already there. It might also be worth repairing permissions under Leopard.
Ian
Found solution in Tiger
I seem to have found a solution that will get me through this Job at least. I thought at some point to dig up a harddrive with an old Tiger installation and gave it a try. Under Tiger there were no problems, so it seems to me to be a an issue with Leopard. I don't know if I missed something somewhere, but I was unaware of the fact that there may be some issues with Leopard. I am interested in knowing whether or not this is a problem other people have .
Thanks again,
David Morgan
Post new comment