Layer Break Won't Change-- Corrupt File
I'm trying to change my layer break marker and no matter what I do it won't change. I even tried automatic and it doesn't change. Not only that, but the marker that it seems to be stuck on being the break point doesn't show up as such and when I change another marker to the break point, it doesn't change. When I try to delete that track, it won't delete. Sounds to me like a corrupt file. Anyone agree? Disagree? Help? Please? Thanks!
http://www.dvdstepbystep.com/markers.mov
Not a full project (I can do a more detailed one if you need it) shows what I am speaking about about adding markers into the timeline, you willl first Build then go to Format as shown. The pulldown should have a chapter markker that is black. You may need to hunt and peck to add markers in the proper place.
You can also use the VTS view to get some sense of where the 1/2 point may be
http://www.dvdstepbystep.com/vts.php
Let me know if that helps or I will do another example
Similar Messages
-
Encore CS3 Error: Disc requires a layer break
Hi,
So I'm trying to build a DVD with DVD Video and ROM content (3.92GB for DVD video and 4.61GB for ROM content) on a dual layer DVD. When preparing the disc layout encore stops and comes up with a warning: DualLayer - This disc requires a layer break.
I've set Encore to make the layer break automatically, and changing it to manual doesn't make any difference... can you help?? I've tried exporting the project to disc, image and folder but it makes no difference!!!
TimYou have a mixture of problems at play here, and whilst this may seem like a pain in the rear, there is a way out for you.
Problem #1 is that Encore cannot set a layer break in the ROM content, as it cannot hook into it and therefore has no way of knowing what it contains.
Problem #2 is that when creating DVD9 discs, there are 2 ways to master them - OTP (Opposite Track Path) and PTP (Parallel Track Path).
All DVD Writers are incapable of writing in PTP mode. This has caused me problems on more occasions than you can possibly know. It's a real PITA.
You can however
i replicate
to PTP mode.
Why is this the case? Well, because DVD is usually used for DVD-Video, and the Layer Break needs to be as unobtrusive as possible - so the disc mastering uses OTP so that for Layer 0, the laser starts at the middle of the disc, travels to the outside, refocusses to Layer 1 and then travels back towards the middle again. The idea is to minimize the time taken to refocus, giving if anything just a small pause at worst, should the break point need to be placed in the middle of a film (Do not confuse this with "Seamless" layer break in apps like IMGBurn, as that ONLY applies to Multiple Angle discs. NEVER add a "seamless" flag on a single angle film)
Trouble with OTP is that you cannot have more information on Layer 1 than on Layer 0 - for obvious reasons.
The solution is PTP - and this has to be done in a PreMastering application. GEAR Pro Mastering Edition is one for PC, and DVD AfterEdit is one for Mac. The masters cannot be burned. They need to be written to DLT tapes.
One possible workaround is to tell Encore to create a Folder with just your DVD-Video material. Do not - at this point - add the ROM content.
Launch IMGBurn (freeware/Donationware, www.imgburn.com)
Go into BUILD mode.
Make sure it is set to "Calculate Optimal" for Layer Breaks.
Add your Video_TS folder.
Add your ROM folder.
Hit "Write" - it will tell you it cannot find a suitable location for a Layer Break to spec, and ask you if you want to proceed anyway.
Tell it "YES" and it will make your disc.
Where the layer break will be is anybody's guess, but it will load your Video_TS and try to split the data equally between the layers. It should put it between files.
It's your only shot at getting a written disc - this will not be suitable for replication unless you master it in PTP mode though.
Good Luck. -
White Wall - Photoshop CS6 corrupted files won't zoom
So my Photoshop CS6 is slowly corrupting files. I open psds to find nothing but a giant whit wall. I zoom out and the white disappears but then I can't zoom in any further than 50%. My rulers however, show that I'm zooming in. Then when I select another layer... it snaps to % I should be looking at. (Also... this particular file won't give me a preview in the icon on my desktop. Related?) This is not happening with all my files. Just the ones surrounding this particular project. Please. Help. Me.
Welcome to the forum.
With display issues, the first thing that I recommend is to check the installed video driver, and if it is not the latest, update that from the mfgr's Web site.
What OS are you running?
What video card (make & model) is installed?
What is the video driver version?
Is that the latest on the AMD/ATI, or nVidia Web site?
Good luck, and if that does not help, at least we will have gotten that out of the way early.
Hunt -
Corrupt File Won't Let Me Start FCPX.. PLEASE HELP!
I've been working on this big production with Final Cut Pro X for a Tv company here in Panama. Suddenly after I finished my edit one day and went back the next day to check if everything was good to turn in, FCPX wouldn't start or work at all. I've been doing research for the past few days. So I downloaded "Pro Maintenance Tools", which helped me found what the error was by reading the crash report FCPX gave me. It appear that the problem is related to a series of corrupt files related to Audio, Plugin, and Effects Rendering. So I scanned the whole Project and Event folders with the "Corrupt Clip Finder" tool from the ''Pro Maintenance Tools'' Application, but it couldn't find a thing.
Ps: The program only works whenever I move the project folder out of the movie carpet, and won't when putted back in again. So the problem is definetly within the project folder somewhere.
I'm attaching a copy of my error report so you guys can help me!
CRASH THREAD ONLY:
0 libsystem_kernel.dylib 0x00007fff8fba9ce2 __pthread_kill + 10
1 libsystem_c.dylib 0x00007fff8bbac7d2 pthread_kill + 95
2 libsystem_c.dylib 0x00007fff8bb9da7a abort + 143
3 libsystem_c.dylib 0x00007fff8bbfc84c free + 389
4 com.apple.proapps.flexo.AudioEffects 0x00000001260ef47e LoudnessMeterUnitEntry + 61054
5 com.apple.proapps.flexo.AudioEffects 0x00000001260ee75a LoudnessMeterUnitEntry + 57690
6 com.apple.proapps.flexo.AudioEffects 0x00000001260e9ad8 LoudnessMeterUnitEntry + 38104
7 com.apple.proapps.flexo.AudioEffects 0x00000001260df217 NoiseReductionEntry + 3399
8 com.apple.proapps.flexo.AudioEffects 0x00000001260d5593 0x1260d0000 + 21907
9 com.apple.proapps.flexo.AudioEffects 0x00000001260e5864 LoudnessMeterUnitEntry + 21092
10 com.apple.proapps.flexo.AudioEffects 0x00000001260de4f7 NoiseReductionEntry + 39
11 com.apple.audio.toolbox.AudioToolbox 0x00007fff9345a9a3 _AT_AudioUnitSetProperty + 183
12 com.apple.Flexo 0x00000001007ba961 -[FFAudioUnitEffect cachedAudioUnit] + 401
13 com.apple.Flexo 0x00000001007c15b4 -[FFAudioUnitEffect(ParameterSupport) createChannelsInFolder:] + 36
14 com.apple.Flexo 0x000000010079860e -[FFEffect channelFolder] + 366
15 com.apple.Flexo 0x0000000100b96d56 -[FFEffectStack insertObject:inEffectsAtIndex:postNotification:] + 230
16 com.apple.CoreFoundation 0x00007fff951cd20c __invoking___ + 140
17 com.apple.CoreFoundation 0x00007fff95266772 -[NSInvocation invokeUsingIMP:] + 114
18 com.apple.CoreFoundation 0x00007fff951c82b4 ___forwarding___ + 756
19 com.apple.CoreFoundation 0x00007fff951c7f48 _CF_forwarding_prep_0 + 232
20 com.apple.Flexo 0x0000000100b9a9f0 -[FFEffectStack initWithCoder:] + 720
21 com.apple.DeepSkyLite 0x0000000101cdfbf2 -[DSSyncContext load:persistentObject:] + 125
22 com.apple.DeepSkyLite 0x0000000101ce2c5b -[DSObject DSObjectInitWithInvocation:] + 260
23 com.apple.CoreFoundation 0x00007fff951c82b4 ___forwarding___ + 756
24 com.apple.CoreFoundation 0x00007fff951c7f48 _CF_forwarding_prep_0 + 232
25 com.apple.Flexo 0x0000000100b2198a -[FFAnchoredTransition initWithCoder:] + 218
26 com.apple.DeepSkyLite 0x0000000101cdfbf2 -[DSSyncContext load:persistentObject:] + 125
27 com.apple.DeepSkyLite 0x0000000101ce16b3 _ZL12SyncObjects_P11objc_objectP12DSCollectionP14DSPropertyDescP13DSSyncContext a + 656
28 com.apple.DeepSkyLite 0x0000000101ce273c _ZL11CreateMany_P12DSCollectionP14DSPropertyDescP13DSSyncContextaa + 460
29 com.apple.DeepSkyLite 0x0000000101ce2899 -[DSSyncContext decodeObjectForKey:] + 324
30 com.apple.Flexo 0x0000000100b37411 -[FFAnchoredCollection initWithCoder:] + 385
31 com.apple.DeepSkyLite 0x0000000101cdfbf2 -[DSSyncContext load:persistentObject:] + 125
32 com.apple.DeepSkyLite 0x0000000101ce16b3 _ZL12SyncObjects_P11objc_objectP12DSCollectionP14DSPropertyDescP13DSSyncContext a + 656
33 com.apple.DeepSkyLite 0x0000000101ce273c _ZL11CreateMany_P12DSCollectionP14DSPropertyDescP13DSSyncContextaa + 460
34 com.apple.DeepSkyLite 0x0000000101ce2826 -[DSSyncContext decodeObjectForKey:] + 209
35 com.apple.Flexo 0x0000000100a3f495 -[FFAnchoredSequence initWithCoder:] + 453
36 com.apple.DeepSkyLite 0x0000000101cdfbf2 -[DSSyncContext load:persistentObject:] + 125
37 com.apple.DeepSkyLite 0x0000000101cdec2a -[DSBridge objectWithID:store:] + 163
38 com.apple.Flexo 0x00000001007c77a7 -[FFCatalogStore objectWithID:] + 39
39 com.apple.Flexo 0x0000000100c24227 __-[FFSequenceInfo sequence]_block_invoke_1 + 183
40 libdispatch.dylib 0x00007fff90ed38ba _dispatch_call_block_and_release + 18
41 libdispatch.dylib 0x00007fff90ed4799 _dispatch_worker_thread2 + 255
42 libsystem_c.dylib 0x00007fff8bbac3da _pthread_wqthread + 316
43 libsystem_c.dylib 0x00007fff8bbadb85 start_wqthread + 13
CRASH ANALYZER:
4 com.apple.proapps.flexo.AudioEffects 0x00000001260ef47e LoudnessMeterUnitEntry + 61054BTW- Here is my crash report:
Thanks so much if you can help. I will be indebted to you... Right now I am beside myself from this loss.
Process: Final Cut Pro [52174]
Path: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
Identifier: com.apple.FinalCut
Version: 10.0 (179114)
Build Info: ProEditor-179110400~1
App Item ID: 403961173
App External ID: 3154134
Code Type: X86-64 (Native)
Parent Process: launchd [210]
Date/Time: 2012-03-11 13:26:06.822 -0400
OS Version: Mac OS X 10.7.3 (11D50b)
Report Version: 9
Interval Since Last Report: 60653 sec
Crashes Since Last Report: 21
Per-App Interval Since Last Report: 8522 sec
Per-App Crashes Since Last Report: 20
Anonymous UUID: 9F755C15-CF96-4A5E-96FB-147D4E82AAE4
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: 0x000000000000000d, 0x0000000000000000
VM Regions Near 0:
-->
__TEXT 0000000100000000-00000001000c2000 [ 776K] r-x/rwx SM=COW /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
Application Specific Information:
objc[52174]: garbage collection is OFF
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.apple.proapps.flexo.AudioEffects 0x000000016d75e19b LoudnessMeterUnitEntry + 60315
1 com.apple.proapps.flexo.AudioEffects 0x000000016d758aff LoudnessMeterUnitEntry + 38143
2 com.apple.proapps.flexo.AudioEffects 0x000000016d74e217 NoiseReductionEntry + 3383
3 com.apple.proapps.flexo.AudioEffects 0x000000016d7445a3 0x16d73f000 + 21923
4 com.apple.proapps.flexo.AudioEffects 0x000000016d754864 LoudnessMeterUnitEntry + 21092
5 com.apple.proapps.flexo.AudioEffects 0x000000016d74d507 NoiseReductionEntry + 39
6 com.apple.audio.toolbox.AudioToolbox 0x0000000107ce39d3 _AT_AudioUnitSetProperty + 183
7 com.apple.Flexo 0x00000001007c07a1 -[FFAudioUnitEffect cachedAudioUnit] + 401
8 com.apple.Flexo 0x00000001007c7d24 -[FFAudioUnitEffect(ParameterSupport) createChannelsInFolder:] + 36
9 com.apple.Flexo 0x000000010079f17e -[FFEffect channelFolder] + 366
10 com.apple.Flexo 0x0000000100b86d56 -[FFEffectStack insertObject:inEffectsAtIndex:postNotification:] + 230
11 com.apple.CoreFoundation 0x0000000101e46f4c __invoking___ + 140
12 com.apple.CoreFoundation 0x0000000101ee0552 -[NSInvocation invokeUsingIMP:] + 114
13 com.apple.CoreFoundation 0x0000000101e41ff4 ___forwarding___ + 756
14 com.apple.CoreFoundation 0x0000000101e41c88 _CF_forwarding_prep_0 + 232
15 com.apple.Flexo 0x0000000100b8a9f0 -[FFEffectStack initWithCoder:] + 720
16 com.apple.DeepSkyLite 0x000000010c9b0bf2 -[DSSyncContext load:persistentObject:] + 125
17 com.apple.DeepSkyLite 0x000000010c9b3c5b -[DSObject DSObjectInitWithInvocation:] + 260
18 com.apple.CoreFoundation 0x0000000101e41ff4 ___forwarding___ + 756
19 com.apple.CoreFoundation 0x0000000101e41c88 _CF_forwarding_prep_0 + 232
20 com.apple.Flexo 0x00000001009e480d -[FFAnchoredObject _addUserEffectsFromEffectStack:toArray:] + 45
21 com.apple.Flexo 0x00000001009e7219 -[FFAnchoredObject effects] + 377
22 com.apple.Flexo 0x00000001009e75be -[FFAnchoredObject assetRefsIncludingAnchored:] + 94
23 com.apple.Flexo 0x0000000100b9bdf5 -[FFSequenceProject assetReferences] + 149
24 com.apple.Flexo 0x00000001007da6db -[FFProject _updateOfflineReasonsForQuality:] + 267
25 com.apple.Flexo 0x00000001007db83f -[FFProject mediaAvailable] + 127
26 com.apple.Flexo 0x0000000100c0c583 -[FFProjectOrganizerModule updateCell:forNode:] + 435
27 com.apple.Flexo 0x0000000100c0997a -[FFProjectOrganizerModule _assetsChangedNotification:] + 506
28 com.apple.CoreFoundation 0x0000000101e4475d -[NSObject performSelector:withObject:] + 61
29 com.apple.Flexo 0x00000001006ee0af Observers::Notify((anonymous namespace)::Notification const&) + 303
30 com.apple.Flexo 0x00000001006eec07 +[FFNotificationCenter postNotification:] + 199
31 com.apple.Flexo 0x00000001006ecee3 +[FFNotificationCenter postNotificationName:object:userInfo:] + 67
32 com.apple.Flexo 0x00000001007d7f50 -[FFProject _deferredAssetChangedNotification] + 96
33 com.apple.Foundation 0x0000000102152d88 __NSFirePerformWithOrder + 382
34 com.apple.CoreFoundation 0x0000000101e14bd7 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23
35 com.apple.CoreFoundation 0x0000000101e14b36 __CFRunLoopDoObservers + 374
36 com.apple.CoreFoundation 0x0000000101de9ce9 __CFRunLoopRun + 825
37 com.apple.CoreFoundation 0x0000000101de9676 CFRunLoopRunSpecific + 230
38 com.apple.HIToolbox 0x000000010802b31f RunCurrentEventLoopInMode + 277
39 com.apple.HIToolbox 0x000000010803251b ReceiveNextEventCommon + 181
40 com.apple.HIToolbox 0x0000000108032456 BlockUntilNextEventMatchingListInMode + 62
41 com.apple.AppKit 0x00000001025d5f5d _DPSNextEvent + 659
42 com.apple.AppKit 0x00000001025d5861 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 135
43 com.apple.AppKit 0x00000001025d219d -[NSApplication run] + 470
44 com.apple.prokit 0x00000001002fc3a6 NSProApplicationMain + 387
45 com.apple.FinalCut 0x0000000100002138 start + 52
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x0000000103d4ee06 __select_nocancel + 10
1 libdispatch.dylib 0x0000000103b5831e _dispatch_mgr_invoke + 251
2 libdispatch.dylib 0x0000000103b5714e _dispatch_mgr_thread + 54
Thread 2:: Dispatch queue: com.apple.root.low-priority
0 libsystem_kernel.dylib 0x0000000103d4f7e6 kevent + 10
1 com.apple.Flexo 0x000000010099dcac __-[FFStorageManager _createKernelQueue]_block_invoke_1 + 28
2 libdispatch.dylib 0x0000000103b568ba _dispatch_call_block_and_release + 18
3 libdispatch.dylib 0x0000000103b57799 _dispatch_worker_thread2 + 255
4 libsystem_c.dylib 0x0000000103c0d3da _pthread_wqthread + 316
5 libsystem_c.dylib 0x0000000103c0eb85 start_wqthread + 13
Thread 3:
0 libsystem_kernel.dylib 0x0000000103d4f192 __workq_kernreturn + 10
1 libsystem_c.dylib 0x0000000103c0d594 _pthread_wqthread + 758
2 libsystem_c.dylib 0x0000000103c0eb85 start_wqthread + 13
Thread 4:
0 libsystem_kernel.dylib 0x0000000103d4ebca __psynch_cvwait + 10
1 libsystem_c.dylib 0x0000000103c0f274 _pthread_cond_wait + 840
2 com.apple.progl.framework 0x000000010d8f47ea (anonymous namespace)::threadFunc(void*) + 70
3 com.apple.procore.framework 0x00000001001594fc PCThread::startup(void*) + 18
4 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
5 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 5:
0 libsystem_kernel.dylib 0x0000000103d4f192 __workq_kernreturn + 10
1 libsystem_c.dylib 0x0000000103c0d594 _pthread_wqthread + 758
2 libsystem_c.dylib 0x0000000103c0eb85 start_wqthread + 13
Thread 6:: com.apple.flexo.throttled-scheduled-io
0 libsystem_kernel.dylib 0x0000000103d4ebca __psynch_cvwait + 10
1 libsystem_c.dylib 0x0000000103c0f274 _pthread_cond_wait + 840
2 com.apple.Flexo 0x0000000100860858 Synchronizable::Wait() + 56
3 com.apple.Fig.provider 0x000000011494e0a8 0x114921000 + 184488
4 com.apple.Flexo 0x000000010086965a Thread::RunHelper(void*) + 42
5 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
6 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 7:: CVDisplayLink
0 libsystem_kernel.dylib 0x0000000103d4ebca __psynch_cvwait + 10
1 libsystem_c.dylib 0x0000000103c0f2a6 _pthread_cond_wait + 890
2 com.apple.CoreVideo 0x000000010876763f CVDisplayLink::waitUntil(unsigned long long) + 279
3 com.apple.CoreVideo 0x0000000108766aa5 CVDisplayLink::runIOThread() + 559
4 com.apple.CoreVideo 0x000000010876685d _ZL13startIOThreadPv + 148
5 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
6 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 8:: MIO Mounting Thread
0 libsystem_kernel.dylib 0x0000000103d4ebca __psynch_cvwait + 10
1 libsystem_c.dylib 0x0000000103c0f2a6 _pthread_cond_wait + 890
2 com.apple.Foundation 0x000000010215ba80 -[NSCondition waitUntilDate:] + 371
3 com.apple.Foundation 0x0000000102125252 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4 com.apple.proapps.MIO 0x00000001015e689c -[PluginLockPair scanPaths] + 284
5 com.apple.Foundation 0x000000010212c74e -[NSThread main] + 68
6 com.apple.Foundation 0x000000010212c6c6 __NSThread__main__ + 1575
7 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
8 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 9:: MIO Mounting Thread
0 libsystem_kernel.dylib 0x0000000103d4ebca __psynch_cvwait + 10
1 libsystem_c.dylib 0x0000000103c0f2a6 _pthread_cond_wait + 890
2 com.apple.Foundation 0x000000010215ba80 -[NSCondition waitUntilDate:] + 371
3 com.apple.Foundation 0x0000000102125252 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4 com.apple.proapps.MIO 0x00000001015e689c -[PluginLockPair scanPaths] + 284
5 com.apple.Foundation 0x000000010212c74e -[NSThread main] + 68
6 com.apple.Foundation 0x000000010212c6c6 __NSThread__main__ + 1575
7 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
8 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 10:: MIO Mounting Thread
0 libsystem_kernel.dylib 0x0000000103d4ebca __psynch_cvwait + 10
1 libsystem_c.dylib 0x0000000103c0f2a6 _pthread_cond_wait + 890
2 com.apple.Foundation 0x000000010215ba80 -[NSCondition waitUntilDate:] + 371
3 com.apple.Foundation 0x0000000102125252 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4 com.apple.proapps.MIO 0x00000001015e689c -[PluginLockPair scanPaths] + 284
5 com.apple.Foundation 0x000000010212c74e -[NSThread main] + 68
6 com.apple.Foundation 0x000000010212c6c6 __NSThread__main__ + 1575
7 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
8 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 11:: MIO Mounting Thread
0 libsystem_kernel.dylib 0x0000000103d4ebca __psynch_cvwait + 10
1 libsystem_c.dylib 0x0000000103c0f2a6 _pthread_cond_wait + 890
2 com.apple.Foundation 0x000000010215ba80 -[NSCondition waitUntilDate:] + 371
3 com.apple.Foundation 0x0000000102125252 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4 com.apple.proapps.MIO 0x00000001015e689c -[PluginLockPair scanPaths] + 284
5 com.apple.Foundation 0x000000010212c74e -[NSThread main] + 68
6 com.apple.Foundation 0x000000010212c6c6 __NSThread__main__ + 1575
7 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
8 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 12:: MIO Mounting Thread
0 libsystem_kernel.dylib 0x0000000103d4ebca __psynch_cvwait + 10
1 libsystem_c.dylib 0x0000000103c0f2a6 _pthread_cond_wait + 890
2 com.apple.Foundation 0x000000010215ba80 -[NSCondition waitUntilDate:] + 371
3 com.apple.Foundation 0x0000000102125252 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4 com.apple.proapps.MIO 0x00000001015e689c -[PluginLockPair scanPaths] + 284
5 com.apple.Foundation 0x000000010212c74e -[NSThread main] + 68
6 com.apple.Foundation 0x000000010212c6c6 __NSThread__main__ + 1575
7 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
8 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 13:: com.apple.dvdplayback-DDPTask
0 libsystem_kernel.dylib 0x0000000103d4d6b6 semaphore_wait_trap + 10
1 com.apple.AVCHDPlugin 0x00000001402eceb7 semaphore_wait(viona_semaphore_t*) + 55
2 com.apple.AVCHDPlugin 0x00000001402fa460 WinPortServer::ProcessMessages() + 768
3 com.apple.AVCHDPlugin 0x000000014027e8a3 DDP_Init + 723
4 com.apple.AVCHDPlugin 0x00000001402ec6c0 ST20Thread::Run(PThreadRunParams*) + 32
5 libsystem_c.dylib 0x0000000103c0d768 _pthread_body + 59
Thread 14:: com.apple.flexo.player-render (playback)
0 libsystem_kernel.dylib 0x0000000103d4ebca __psynch_cvwait + 10
1 libsystem_c.dylib 0x0000000103c0f2a6 _pthread_cond_wait + 890
2 com.apple.Foundation 0x000000010215ba80 -[NSCondition waitUntilDate:] + 371
3 com.apple.Foundation 0x0000000102125252 -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4 com.apple.Flexo 0x00000001007170b5 -[FFPlayer _waitForAttention] + 37
5 com.apple.Flexo 0x00000001007198a4 -[FFPlayer playerRenderThreadMain:] + 324
6 com.apple.Foundation 0x000000010212c74e -[NSThread main] + 68
7 com.apple.Foundation 0x000000010212c6c6 __NSThread__main__ + 1575
8 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
9 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 15:: com.apple.flexo.time-rate-change-controller
0 libsystem_kernel.dylib 0x0000000103d4ebca __psynch_cvwait + 10
1 libsystem_c.dylib 0x0000000103c0f274 _pthread_cond_wait + 840
2 com.apple.Flexo 0x000000010072379b TimeRateChangeController::threadFunction() + 299
3 com.apple.Flexo 0x000000010072bf7d TimeRateChangeController::thread_routine(void*) + 61
4 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
5 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 16:: com.apple.audio.IOThread.client
0 libsystem_kernel.dylib 0x0000000103d4d67a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x0000000103d4cd71 mach_msg + 73
2 com.apple.audio.CoreAudio 0x000000010857eeb3 HALB_MachPort::SendMessageWithReply(unsigned int, unsigned int, unsigned int, unsigned int, mach_msg_header_t*, unsigned int) + 93
3 com.apple.audio.CoreAudio 0x000000010857ef05 HALB_MachPort::SendSimpleMessageWithSimpleReply(unsigned int, unsigned int, int, int&, unsigned int) + 37
4 com.apple.audio.CoreAudio 0x0000000108578568 HALC_ProxyIOContext::IOWorkLoop() + 888
5 com.apple.audio.CoreAudio 0x0000000108578151 HALC_ProxyIOContext::IOThreadEntry(void*) + 73
6 com.apple.audio.CoreAudio 0x000000010857800c HALB_IOThread::Entry(void*) + 78
7 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
8 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 17:: BGTask: MEBackgroundLoadManager Dispatch queue: com.apple.root.default-priority
0 com.apple.CoreFoundation 0x0000000101dedec1 CFArrayCreate + 1
1 com.apple.procore.framework 0x00000001001582b4 PCString::append(PCString const&) + 94
2 com.apple.prochannel.framework 0x000000010d3640fe OZChannelRef::OZChannelRef(OZChannelBase const*, OZChannelBase const*) + 292
3 Ozone 0x0000000115587675 OZNotificationManager::willModifyChannel(OZChannelBase const*, unsigned int) + 101
4 Ozone 0x00000001155830b5 OZDocument::willModifyChannel(OZChannelBase const*, unsigned int) + 69
5 com.apple.prochannel.framework 0x000000010d35a129 OZChannel::willBeModified(unsigned int) + 99
6 com.apple.prochannel.framework 0x000000010d359fc3 OZChannel::assign(OZChannelBase const*) + 47
7 com.apple.prochannel.framework 0x000000010d3792a2 OZChannelEnum::assign(OZChannelBase const*) + 18
8 com.apple.prochannel.framework 0x000000010d37c788 OZChannelFolder::assign(OZChannelBase const*) + 158
9 com.apple.prochannel.framework 0x000000010d37c788 OZChannelFolder::assign(OZChannelBase const*) + 158
10 com.apple.prochannel.framework 0x000000010d37c788 OZChannelFolder::assign(OZChannelBase const*) + 158
11 com.apple.prochannel.framework 0x000000010d388733 OZChannelObjectRootBase::assign(OZChannelBase const*) + 27
12 com.apple.prochannel.framework 0x000000010d37c788 OZChannelFolder::assign(OZChannelBase const*) + 158
13 Ozone 0x00000001155c0a5d OZSceneNode::operator=(OZSceneNode const&) + 557
14 Ozone 0x00000001157033c2 OZTransformNode::operator=(OZSceneNode const&) + 18
15 Ozone 0x00000001155cb476 OZElement::operator=(OZSceneNode const&) + 22
16 com.apple.motion.TextFramework 0x000000011682e39e TXTextLayout::operator=(OZSceneNode const&) + 46
17 com.apple.Motion.effect 0x00000001150ba0a9 -[FFMotionEffect initSceneNodesOrChannelsFromSavedEffectValues:scene:isInitSceneNode:] + 1044
18 com.apple.Motion.effect 0x00000001150c553f -[FFMotionEffect _makeLoadedDocReady] + 484
19 com.apple.Motion.effect 0x00000001150bf93a -[FFMotionEffect _backgroundLoadDocument:onTask:] + 139
20 com.apple.Motion.effect 0x00000001150e1942 -[MEBackgroundLoadManager _backgroundTask:onTask:] + 304
21 com.apple.CoreFoundation 0x0000000101e47591 -[NSObject performSelector:withObject:withObject:] + 65
22 com.apple.Flexo 0x0000000100827fdb -[FFBackgroundTask main] + 331
23 com.apple.Foundation 0x000000010211a6d8 -[__NSOperationInternal start] + 705
24 com.apple.Foundation 0x000000010212d936 ____NSOQSchedule_block_invoke_2 + 124
25 libdispatch.dylib 0x0000000103b568ba _dispatch_call_block_and_release + 18
26 libdispatch.dylib 0x0000000103b57799 _dispatch_worker_thread2 + 255
27 libsystem_c.dylib 0x0000000103c0d3da _pthread_wqthread + 316
28 libsystem_c.dylib 0x0000000103c0eb85 start_wqthread + 13
Thread 18:: com.apple.helium-unit
0 libsystem_kernel.dylib 0x0000000103d4ebf2 __psynch_mutexwait + 10
1 libsystem_c.dylib 0x0000000103c0a1a1 pthread_mutex_lock + 545
2 com.apple.Helium.HeliumRender 0x000000010e4e7e42 hg_pthread_loop(void*) + 98
3 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
4 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 19:: com.apple.helium-unit
0 libsystem_kernel.dylib 0x0000000103d4ebf2 __psynch_mutexwait + 10
1 libsystem_c.dylib 0x0000000103c0a1a1 pthread_mutex_lock + 545
2 com.apple.Helium.HeliumRender 0x000000010e4e7e42 hg_pthread_loop(void*) + 98
3 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
4 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 20:: com.apple.helium-texture-finish
0 libsystem_kernel.dylib 0x0000000103d4ebca __psynch_cvwait + 10
1 libsystem_c.dylib 0x0000000103c0f274 _pthread_cond_wait + 840
2 com.apple.Helium.HeliumRender 0x000000010e4ce7ca textureFinishThread(void*) + 186
3 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
4 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 21:: com.apple.helium-render-queue-exec-unit-gpu
0 libsystem_kernel.dylib 0x0000000103d4ebca __psynch_cvwait + 10
1 libsystem_c.dylib 0x0000000103c0f274 _pthread_cond_wait + 840
2 com.apple.Helium.HeliumRender 0x000000010e52fb8e HGSynchronizable::Wait() + 46
3 com.apple.Helium.HeliumRender 0x000000010e44f0cf HGRenderQueue::GetRenderJob(HGRenderExecUnit*, HGRenderJob**) + 207
4 com.apple.Helium.HeliumRender 0x000000010e44690e HGRenderExecUnit::RunLoop() + 110
5 com.apple.Helium.HeliumRender 0x000000010e446894 StartRenderExecUnitFunc(void*) + 20
6 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
7 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 22:: com.apple.helium-render-queue-pbo-readback-unit
0 libsystem_kernel.dylib 0x0000000103d4ebca __psynch_cvwait + 10
1 libsystem_c.dylib 0x0000000103c0f274 _pthread_cond_wait + 840
2 com.apple.Helium.HeliumRender 0x000000010e52fb8e HGSynchronizable::Wait() + 46
3 com.apple.Helium.HeliumRender 0x000000010e450860 HGRenderQueue::GetPBOReadbackJob(HGPBOReadbackExecUnit*, HGPBOReadbackJob**) + 80
4 com.apple.Helium.HeliumRender 0x000000010e445625 StartPBOExecUnitFunc(void*) + 85
5 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
6 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 23:: com.apple.helium-render-queue-pbo-readback-unit
0 libsystem_kernel.dylib 0x0000000103d4ebca __psynch_cvwait + 10
1 libsystem_c.dylib 0x0000000103c0f274 _pthread_cond_wait + 840
2 com.apple.Helium.HeliumRender 0x000000010e52fb8e HGSynchronizable::Wait() + 46
3 com.apple.Helium.HeliumRender 0x000000010e450860 HGRenderQueue::GetPBOReadbackJob(HGPBOReadbackExecUnit*, HGPBOReadbackJob**) + 80
4 com.apple.Helium.HeliumRender 0x000000010e445625 StartPBOExecUnitFunc(void*) + 85
5 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
6 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 24:: com.apple.helium-render-queue-exec-unit-gpu
0 libsystem_kernel.dylib 0x0000000103d4ebca __psynch_cvwait + 10
1 libsystem_c.dylib 0x0000000103c0f274 _pthread_cond_wait + 840
2 com.apple.Helium.HeliumRender 0x000000010e52fb8e HGSynchronizable::Wait() + 46
3 com.apple.Helium.HeliumRender 0x000000010e44f0cf HGRenderQueue::GetRenderJob(HGRenderExecUnit*, HGRenderJob**) + 207
4 com.apple.Helium.HeliumRender 0x000000010e44690e HGRenderExecUnit::RunLoop() + 110
5 com.apple.Helium.HeliumRender 0x000000010e446894 StartRenderExecUnitFunc(void*) + 20
6 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
7 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 25:: com.apple.helium-render-queue-pbo-readback-unit
0 libsystem_kernel.dylib 0x0000000103d4ebca __psynch_cvwait + 10
1 libsystem_c.dylib 0x0000000103c0f274 _pthread_cond_wait + 840
2 com.apple.Helium.HeliumRender 0x000000010e52fb8e HGSynchronizable::Wait() + 46
3 com.apple.Helium.HeliumRender 0x000000010e450860 HGRenderQueue::GetPBOReadbackJob(HGPBOReadbackExecUnit*, HGPBOReadbackJob**) + 80
4 com.apple.Helium.HeliumRender 0x000000010e445625 StartPBOExecUnitFunc(void*) + 85
5 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
6 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 26:: com.apple.helium-render-queue-pbo-readback-unit
0 libsystem_kernel.dylib 0x0000000103d4ebca __psynch_cvwait + 10
1 libsystem_c.dylib 0x0000000103c0f274 _pthread_cond_wait + 840
2 com.apple.Helium.HeliumRender 0x000000010e52fb8e HGSynchronizable::Wait() + 46
3 com.apple.Helium.HeliumRender 0x000000010e450860 HGRenderQueue::GetPBOReadbackJob(HGPBOReadbackExecUnit*, HGPBOReadbackJob**) + 80
4 com.apple.Helium.HeliumRender 0x000000010e445625 StartPBOExecUnitFunc(void*) + 85
5 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
6 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 27:: CAOpenGLLayer
0 libsystem_kernel.dylib 0x0000000103d4d67a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x0000000103d4cd71 mach_msg + 73
2 com.apple.CoreFoundation 0x0000000101de16fc __CFRunLoopServiceMachPort + 188
3 com.apple.CoreFoundation 0x0000000101de9e64 __CFRunLoopRun + 1204
4 com.apple.CoreFoundation 0x0000000101de9676 CFRunLoopRunSpecific + 230
5 com.apple.CoreFoundation 0x0000000101df938f CFRunLoopRun + 95
6 com.apple.QuartzCore 0x00000001018360a1 _ZL27CAOpenGLLayer_render_threadPv + 156
7 com.apple.QuartzCore 0x000000010171f509 thread_fun + 24
8 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
9 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 28:
0 libsystem_kernel.dylib 0x0000000103d4d67a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x0000000103d4cd71 mach_msg + 73
2 com.apple.CoreFoundation 0x0000000101de16fc __CFRunLoopServiceMachPort + 188
3 com.apple.CoreFoundation 0x0000000101de9e64 __CFRunLoopRun + 1204
4 com.apple.CoreFoundation 0x0000000101de9676 CFRunLoopRunSpecific + 230
5 com.apple.CoreFoundation 0x0000000101df938f CFRunLoopRun + 95
6 com.apple.qmaster.do 0x0000000131375439 swamp::CRAdReceiver2::ReceivingThread::runOnce() + 187
7 com.apple.AECore 0x0000000114cfeca5 aecore::CThread::runThread() + 35
8 com.apple.AECore 0x0000000114cfcc8a threadProc(void*) + 9
9 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
10 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 29:
0 libsystem_kernel.dylib 0x0000000103d4f192 __workq_kernreturn + 10
1 libsystem_c.dylib 0x0000000103c0d594 _pthread_wqthread + 758
2 libsystem_c.dylib 0x0000000103c0eb85 start_wqthread + 13
Thread 30:: com.apple.appkit-heartbeat
0 libsystem_kernel.dylib 0x0000000103d4ee42 __semwait_signal + 10
1 libsystem_c.dylib 0x0000000103bc1dea nanosleep + 164
2 libsystem_c.dylib 0x0000000103bc1bb5 usleep + 53
3 com.apple.AppKit 0x000000010280cc73 -[NSUIHeartBeat _heartBeatThread:] + 1727
4 com.apple.Foundation 0x000000010212c74e -[NSThread main] + 68
5 com.apple.Foundation 0x000000010212c6c6 __NSThread__main__ + 1575
6 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
7 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 31:: Dispatch queue: com.apple.root.default-priority
0 libsystem_kernel.dylib 0x0000000103d4ebca __psynch_cvwait + 10
1 libsystem_c.dylib 0x0000000103c0f274 _pthread_cond_wait + 840
2 com.apple.Foundation 0x000000010212e4e4 -[NSCondition wait] + 261
3 com.apple.Foundation 0x0000000102121878 -[NSObject(NSThreadPerformAdditions) performSelector:onThread:withObject:waitUntilDone:modes:] + 975
4 com.apple.Foundation 0x000000010212142b -[NSObject(NSThreadPerformAdditions) performSelectorOnMainThread:withObject:waitUntilDone:] + 135
5 com.apple.AppKit 0x0000000102812b14 ____NSAppKitFinalizeThreadData_block_invoke_2 + 79
6 com.apple.Foundation 0x0000000102153b05 -[NSBlockOperation main] + 116
7 com.apple.Foundation 0x000000010211a6d8 -[__NSOperationInternal start] + 705
8 com.apple.Foundation 0x000000010212d936 ____NSOQSchedule_block_invoke_2 + 124
9 libdispatch.dylib 0x0000000103b568ba _dispatch_call_block_and_release + 18
10 libdispatch.dylib 0x0000000103b57799 _dispatch_worker_thread2 + 255
11 libsystem_c.dylib 0x0000000103c0d3da _pthread_wqthread + 316
12 libsystem_c.dylib 0x0000000103c0eb85 start_wqthread + 13
Thread 32:: com.apple.coremedia.scheduledfileio
0 libsystem_kernel.dylib 0x0000000103d4ebca __psynch_cvwait + 10
1 libsystem_c.dylib 0x0000000103c0f274 _pthread_cond_wait + 840
2 com.apple.CoreMedia.ProAppsSupport 0x000000010028af39 WaitOnCondition + 14
3 com.apple.CoreMedia.ProAppsSupport 0x000000010028b105 FigSemaphoreWaitRelative + 167
4 com.apple.CoreMedia.ProAppsSupport 0x0000000100289212 FigScheduledFileIOThread + 5109
5 com.apple.CoreMedia.ProAppsSupport 0x000000010028c03a figThreadMain + 397
6 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
7 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 33:
0 libsystem_kernel.dylib 0x0000000103d4edf2 __select + 10
1 com.apple.AECore 0x0000000114cfecd2 aecore::CThread::runThread() + 80
2 com.apple.AECore 0x0000000114cfcc8a threadProc(void*) + 9
3 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
4 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 34:: com.apple.CFSocket.private
0 libsystem_kernel.dylib 0x0000000103d4edf2 __select + 10
1 com.apple.CoreFoundation 0x0000000101e32cdb __CFSocketManager + 1355
2 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
3 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 35:: com.apple.coremedia.JVTlib
0 libsystem_kernel.dylib 0x0000000103d4d6b6 semaphore_wait_trap + 10
1 com.apple.VideoToolbox.ProAppsSupport 0x000000010ca5a41b VTImageRotationSessionCreate + 77488
2 com.apple.VideoToolbox.ProAppsSupport 0x000000010ca59dc8 VTImageRotationSessionCreate + 75869
3 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
4 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 36:: com.apple.coremedia.JVTlib
0 libsystem_kernel.dylib 0x0000000103d4d6b6 semaphore_wait_trap + 10
1 com.apple.VideoToolbox.ProAppsSupport 0x000000010ca5a41b VTImageRotationSessionCreate + 77488
2 com.apple.VideoToolbox.ProAppsSupport 0x000000010ca59dc8 VTImageRotationSessionCreate + 75869
3 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
4 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 37:: com.apple.coremedia.JVTlib
0 libsystem_kernel.dylib 0x0000000103d4d6b6 semaphore_wait_trap + 10
1 com.apple.VideoToolbox.ProAppsSupport 0x000000010ca5a41b VTImageRotationSessionCreate + 77488
2 com.apple.VideoToolbox.ProAppsSupport 0x000000010ca59dc8 VTImageRotationSessionCreate + 75869
3 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
4 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 38:: com.apple.coremedia.JVTlib
0 libsystem_kernel.dylib 0x0000000103d4d6b6 semaphore_wait_trap + 10
1 com.apple.VideoToolbox.ProAppsSupport 0x000000010ca5a41b VTImageRotationSessionCreate + 77488
2 com.apple.VideoToolbox.ProAppsSupport 0x000000010cb17650 JVTLibDecoDispose + 479680
3 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
4 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 39:: com.apple.coremedia.JVTlib
0 libsystem_kernel.dylib 0x0000000103d4d6b6 semaphore_wait_trap + 10
1 com.apple.VideoToolbox.ProAppsSupport 0x000000010ca5a41b VTImageRotationSessionCreate + 77488
2 com.apple.VideoToolbox.ProAppsSupport 0x000000010ca59dc8 VTImageRotationSessionCreate + 75869
3 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
4 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 40:: com.apple.coremedia.JVTlib
0 libsystem_kernel.dylib 0x0000000103d4d6b6 semaphore_wait_trap + 10
1 com.apple.VideoToolbox.ProAppsSupport 0x000000010ca5a41b VTImageRotationSessionCreate + 77488
2 com.apple.VideoToolbox.ProAppsSupport 0x000000010ca59dc8 VTImageRotationSessionCreate + 75869
3 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
4 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 41:: com.apple.coremedia.JVTlib
0 libsystem_kernel.dylib 0x0000000103d4d6b6 semaphore_wait_trap + 10
1 com.apple.VideoToolbox.ProAppsSupport 0x000000010ca5a41b VTImageRotationSessionCreate + 77488
2 com.apple.VideoToolbox.ProAppsSupport 0x000000010ca59dc8 VTImageRotationSessionCreate + 75869
3 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
4 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 42:: com.apple.coremedia.JVTlib
0 libsystem_kernel.dylib 0x0000000103d4d6b6 semaphore_wait_trap + 10
1 com.apple.VideoToolbox.ProAppsSupport 0x000000010ca5a41b VTImageRotationSessionCreate + 77488
2 com.apple.VideoToolbox.ProAppsSupport 0x000000010cb17650 JVTLibDecoDispose + 479680
3 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
4 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 43:: com.apple.coremedia.JVTlib
0 libsystem_kernel.dylib 0x0000000103d4d6b6 semaphore_wait_trap + 10
1 com.apple.VideoToolbox.ProAppsSupport 0x000000010ca5a41b VTImageRotationSessionCreate + 77488
2 com.apple.VideoToolbox.ProAppsSupport 0x000000010ca9f8c6 VTImageRotationSessionCreate + 361307
3 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
4 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 44:: com.apple.coremedia.dvvideodecoder
0 libsystem_kernel.dylib 0x0000000103d4ebca __psynch_cvwait + 10
1 libsystem_c.dylib 0x0000000103c0f274 _pthread_cond_wait + 840
2 com.apple.CoreMedia.ProAppsSupport 0x000000010028af39 WaitOnCondition + 14
3 com.apple.CoreMedia.ProAppsSupport 0x000000010028b105 FigSemaphoreWaitRelative + 167
4 com.apple.VideoToolbox.ProAppsSupport 0x000000010ca11c8a H264VideoDecoder_CreateInstance + 114132
5 com.apple.CoreMedia.ProAppsSupport 0x000000010028c03a figThreadMain + 397
6 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
7 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 45:: com.apple.coremedia.dvvideodecoder
0 libsystem_kernel.dylib 0x0000000103d4ebca __psynch_cvwait + 10
1 libsystem_c.dylib 0x0000000103c0f274 _pthread_cond_wait + 840
2 com.apple.CoreMedia.ProAppsSupport 0x000000010028af39 WaitOnCondition + 14
3 com.apple.CoreMedia.ProAppsSupport 0x000000010028b105 FigSemaphoreWaitRelative + 167
4 com.apple.VideoToolbox.ProAppsSupport 0x000000010ca11c8a H264VideoDecoder_CreateInstance + 114132
5 com.apple.CoreMedia.ProAppsSupport 0x000000010028c03a figThreadMain + 397
6 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
7 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 46:: com.apple.coremedia.dvvideodecoder
0 libsystem_kernel.dylib 0x0000000103d4ebca __psynch_cvwait + 10
1 libsystem_c.dylib 0x0000000103c0f274 _pthread_cond_wait + 840
2 com.apple.CoreMedia.ProAppsSupport 0x000000010028af39 WaitOnCondition + 14
3 com.apple.CoreMedia.ProAppsSupport 0x000000010028b105 FigSemaphoreWaitRelative + 167
4 com.apple.VideoToolbox.ProAppsSupport 0x000000010ca11c8a H264VideoDecoder_CreateInstance + 114132
5 com.apple.CoreMedia.ProAppsSupport 0x000000010028c03a figThreadMain + 397
6 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
7 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 47:: com.apple.coremedia.dvvideodecoder
0 libsystem_kernel.dylib 0x0000000103d4ebca __psynch_cvwait + 10
1 libsystem_c.dylib 0x0000000103c0f274 _pthread_cond_wait + 840
2 com.apple.CoreMedia.ProAppsSupport 0x000000010028af39 WaitOnCondition + 14
3 com.apple.CoreMedia.ProAppsSupport 0x000000010028b105 FigSemaphoreWaitRelative + 167
4 com.apple.VideoToolbox.ProAppsSupport 0x000000010ca11c8a H264VideoDecoder_CreateInstance + 114132
5 com.apple.CoreMedia.ProAppsSupport 0x000000010028c03a figThreadMain + 397
6 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
7 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 48:: CVDisplayLink
0 libsystem_kernel.dylib 0x0000000103d4ebca __psynch_cvwait + 10
1 libsystem_c.dylib 0x0000000103c0f2a6 _pthread_cond_wait + 890
2 com.apple.CoreVideo 0x000000010876763f CVDisplayLink::waitUntil(unsigned long long) + 279
3 com.apple.CoreVideo 0x0000000108766aa5 CVDisplayLink::runIOThread() + 559
4 com.apple.CoreVideo 0x000000010876685d _ZL13startIOThreadPv + 148
5 libsystem_c.dylib 0x0000000103c0b8bf _pthread_start + 335
6 libsystem_c.dylib 0x0000000103c0eb75 thread_start + 13
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000103ca1fb0 rbx: 0x00000001cd5e02f0 rcx: 0x0000000135000000 rdx: 0x00000000007d0000
rdi: 0xbb2a0000bb3c0000 rsi: 0x000000010eedfe00 rbp: 0x00007fff5fbfd450 rsp: 0x00007fff5fbfd410
r8: 0x0000000135214c00 r9: 0x0000000000000002 r10: 0xc9985a24b6b9ed0b r11: 0x00000000bb4a0000
r12: 0x00000001cd5e02f0 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000
rip: 0x000000016d75e19b rfl: 0x0000000000010286 cr2: 0x00000001ce00d000
Logical CPU: 2
Binary Images:
0x100000000 - 0x1000c1fef com.apple.FinalCut (10.0 - 179114) <87A93BA7-2A69-1860-23E6-488F5B67F581> /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
0x100139000 - 0x100214ff7 com.apple.procore.framework (4.0.2 - 757) <AF641CD5-22F4-A3A3-8DA0-6DA454F9F936> /Applications/Final Cut Pro.app/Contents/Frameworks/ProCore.framework/Versions/A/ProCore
0x10026d000 - 0x1002b8fff com.apple.CoreMedia.ProAppsSupport (1.0 - 705.23) <0A55958C-289F-A22B-8D1D-B77FC78083A7> /Applications/Final Cut Pro.app/Contents/Frameworks/CoreMedia.framework/Versions/A/CoreMedia
0x1002da000 - 0x1002dafff com.apple.Cocoa (6.6 - ???) <7EC4D759-B2A6-3A99-AC75-809FED1500C6> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
0x1002dd000 - 0x100556fef com.apple.prokit (7.2.1 - 1710) <BE6E9380-FC68-307A-A23E-E06D3FC82811> /System/Library/PrivateFrameworks/ProKit.framework/Versions/A/ProKit
0x1006d8000 - 0x101166fe7 com.apple.Flexo (1.0.0 - 21) <91672C1C-5F24-7DA3-8F20-D947CEF87488> /Applications/Final Cut Pro.app/Contents/Frameworks/Flexo.framework/Versions/A/Flexo
0x101587000 - 0x1015a3fff com.apple.ScriptingBridge (1.2.1 - ???) <A4162BA5-2432-3BF3-8EBC-47AEF2BDD8DA> /System/Library/Frameworks/ScriptingBridge.framework/Versions/A/ScriptingBridge
0x1015b6000 - 0x10167bff7 com.apple.proapps.MIO (2.0 - 17882.8) <76C85FB2-8916-CA80-157C-DE1F58964A0B> /Applications/Final Cut Pro.app/Contents/Frameworks/MIO.framework/Versions/A/MIO
0x1016e0000 - 0x1016fefff com.apple.pro.sharedstudio (1.0 - 17882.8) <29B0D24A-8DD5-C3C7-259F-F6B5304279BC> /Applications/Final Cut Pro.app/Contents/Frameworks/StudioSharedResources.framework/Versions/A/StudioSh aredResources
0x10171d000 - 0x1018bcfff com.apple.QuartzCore (1.7 - 270.2) <F2CCDEFB-DE43-3E32-B242-A22C82617186> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x101964000 - 0x101a29ff7 com.apple.TLKit (1.0 - 17882.8) <D0728C96-1CB6-5DE7-CAAB-7FEB43CD3115> /Applications/Final Cut Pro.app/Contents/Frameworks/TLKit.framework/Versions/A/TLKit
0x101a84000 - 0x101a84fff com.apple.ApplicationServices (41 - 41) <89B6AD5B-5C75-3E83-8C2B-AA7F4C55E400> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Application Services
0x101a87000 - 0x101b2bfe7 com.apple.LunaKit (1.0 - 17882.8) <7FA08F09-5359-DEC3-000F-C0F8DC2867C7> /Applications/Final Cut Pro.app/Contents/Frameworks/LunaKit.framework/Versions/A/LunaKit
0x101ba3000 - 0x101ba3fff com.apple.audio.units.AudioUnit (1.7.2 - 1.7.2) <04C10813-CCE5-3333-8C72-E8E35E417B3B> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
0x101ba9000 - 0x101c1cfff libstdc++.6.dylib (52.0.0 - compatibility 7.0.0) <6BDD43E4-A4B1-379E-9ED5-8C713653DFF2> /usr/lib/libstdc++.6.dylib
0x101c7a000 - 0x101ca7fe7 libSystem.B.dylib (159.1.0 - compatibility 1.0.0) <7BEBB139-50BB-3112-947A-F4AA168F991C> /usr/lib/libSystem.B.dylib
0x101cb5000 - 0x101d99e5f libobjc.A.dylib (228.0.0 - compatibility 1.0.0) <871E688B-CF57-3BC7-80D6-F6476DFF109B> /usr/lib/libobjc.A.dylib
0x101db1000 - 0x101f85fff com.apple.CoreFoundation (6.7.1 - 635.19) <57B77925-9065-38C9-A05B-02F4F9ED007C> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x1020d2000 - 0x1023ebff7 com.apple.Foundation (6.7.1 - 833.24) <6D4E6F93-64EF-3D41-AE80-2BB10E2E6323> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x1025cd000 - 0x1031d1fff com.apple.AppKit (6.7.3 - 1138.32) <A9EB81C6-C519-3F29-89F1-42C3E8930281> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x103854000 - 0x103854fff com.apple.Accelerate (1.7 - Accelerate 1.7) <82DDF6F5-FBC3-323D-B71D-CF7ABC5CF568> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0x103857000 - 0x103867ff7 com.apple.opengl (1.7.6 - 1.7.6) <C168883D-9BC5-3C38-9937-42852D719718> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x10386f000 - 0x1038d9ff7 com.apple.framework.IOKit (2.0 - ???) <EEEB42FD-E3E1-3A94-A771-B1993B694F17> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x103904000 - 0x103904fff com.apple.CoreServices (53 - 53) <043C8026-8EDD-3241-B090-F589E24062EF> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x103907000 - 0x103907fff com.apple.quartzframework (1.5 - 1.5) <2C13AE76-C86B-3D48-A583-121689190F74> /System/Library/Frameworks/Quartz.framework/Versions/A/Quartz
0x10390a000 - 0x10390afff com.apple.vecLib (3.7 - vecLib 3.7) <9A58105C-B36E-35B5-812C-4ED693F2618F> /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
0x10390d000 - 0x103a43fff com.apple.vImage (5.1 - 5.1) <A08B7582-67BC-3EED-813A-4833645964A7> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.fr amework/Versions/A/vImage
0x103a61000 - 0x103a61fff com.apple.Accelerate.vecLib (3.7 - vecLib 3.7) <C06A140F-6114-3B8B-B080-E509303145B8> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/vecLib
0x103a64000 - -
Originals won't open in iPhoto, Preview, Photoshop; Corrupted files?
I am using the latest version of iPhoto 6 (6.0.5, I think).
I have 2 external Firewire hard drives. One is for backup. One is for my music and pictures.
Everytime I would start iPhoto I would get "rebuild thumbnail cache". Knowing this is not normal, I used the latest version of Backup, and backed up to an external hard drive.
Now the external hard drive with the music and photos has failed completely (I think the circuit board is fried, but that's another story).
I restored my iPhoto library from my backup, to my computer's main drive. I checked permissions, and none required fixing.
Now all of my pictures are corrupted. The thumbnails show, but neither the originals nor the modified picture files will open in iPhoto, Preview, or Photoshop. I get the infamous "unknown or invalid JPEG marker type" error.
And I have rebuilt the iPhoto database several times to no avail.
I have 13500 pictures in my library, including the birth of my daughter and 3 years of her growing up. There must be a way to fix this.
Please help!
20" iMac G5 2.0/MacBook 1.83/eMac 1.25 Mac OS X (10.4.8)Robert
Sorry to hear of your problems.
Right now I would concentrate on getting the pics back, and figure out the iPhoto part later.
Select one of the pics in the Finder and try change the file suffix: if it's pic.jpg, then try pic.JPG or .jpeg and see if that helps.
Try open the pics with Graphic Converter, which seems to be less fussy about things. You can download it here: http://www.lemkesoft.com/
BackUp (if this is the Apple App we're talking about) creates a pkg file. Can you see the one you restored from? Right click on it, and choose 'Show Package Files. Inside you'll find a .dmg file. This contains the actual files. Mount the dmg and see if you can find the files inside it. Can you view them in Preview?
Regards
TD -
i purchased a song thats a corrupted file and won't download - how do i get this song or get a refund as i have already benn charged ?
http://support.apple.com/kb/HT1933
Regards. -
IPhone won't completely delete songs in iTunes (corrupted files?)
Hey guys,
I've been working on this issue for nearly two days now, and I just have no idea of how to fix it. The issue: in iTunes, my iPhone says I have multiple albums/songs on the phone, despite me trying multiple times to delete them, and despite them not actually appearing on my phone. These are all songs that have been purchased, and are on the cloud. On my actual iPhone screen, the songs don't appear at all, since I deleted them. But when I plug my phone into my computer, in my iTunes, the songs remain - they're just dimmed, with dotted circles on the left of them. My goal is to have all of these songs deleted from the iPhone altogether, and have that appear both on the phone and in iTunes. It seems like these are corrupted files, but I have no idea how to get rid of them. This is how my iTunes and my iPhone look, right now.
I've done the following things:
--I've fooled around with redownloading them from the cloud on the iPhone separate from the computer, then plugging it into my computer to delete them in iTunes. But even after I delete them in iTunes, it constantly brings the files back after I sync.
-I checked and unchecked the items in iTunes, before syncing. It lets me delete them; but again, after I click Sync, the files return.
-I deleted all of the music from my iTunes library, and I turned off the Manually Manage Music option, so that the iPhone would sync with the iTunes and delete everything from the phone. The result was all the music on the iPhone being deleted...except these straggling files that I'm having this issue with.
Does anyone have any other tips? I don't want to reset to factory settings because I have a couple work apps on the phone that I can't find links to to redownload them. And the iPhone managing apps are not an option; I can't download apps on this computer. I've been troubleshooting online, but I'm not sure if I'm just doing some of these things incorrectly. Can anyone help me?I've reset it - erased all content and settings - and they're still there! Though I restored it from the Cloud. Not sure if that would influence it.
-
I have some corrupted files on my OS9.2. hard drive that won't delete.
My computer is in three sections, the OS X is fine, but both OS9.2 drives are causing me trouble. The additonal OS9.2 drive is purely for music, but originally my audiophile card 2496 was installed on both drives. I had a problem with the sound on the small drive so I uninstalled everything and then reinstalled it all. The music records alright now, but when I close Cubasis it freezes on the small drive . When uninstalling all the music I found I couldn't delete all the audiophile card files that were on the main hard drive - they were in an invisible file marked usr (that is the spelling used) and the rest of the path was greyed out. I tried to delete them straight from Sherlock but to no avail. I am wondering now whether to reinstall the OS9.2 system on both hard drives but need to ask a few basic questions. When I do this will this fix the 'corrupted files' that are already there or will this cause more trouble. Will I lose all the work that I have already done on these files or should I make sure and do a back-up onto DVD just in case. How does one reinstall the Operating System? I have the disc but just not sure what to do as I haven't done it before. Will these corrupted files do more damage to the computer if I just leave well alone - it is a nuisance restarting the computer every time I use Cubasis but I would sooner do that than get into more of a muddle than I am in at the present.
Hi, peckerpac -
If I deep-wipe the drive what exactly does that mean?
That means the drive is effectively stripped of all data, including the removal of the disk directories. A file (or folder) that refuses to be trashable indicates there is probably damage to the directory. DiskWarrior usually can fix that; apparently not in this case.
Once the drive has been stripped, the initialization process creates a new structure on the drive so that it is usable for data storage, including new directories.
When you say I can't deep-wipe a partition, do you mean that the whole Hard Drive OSX as well will be deep wiped, or does it mean that only the OS9 part that needs it will be wiped?
A hard drive that has been partitioned has had its disk subdivided into two or more volumes. For most things the Mac will treat each volume as if it were a separate hard drive - each volume will have its own icon on the desktop; files can be copied from one volume to another; if each has an OS, each will appear individually in Startup disk control panel and in Startup Manager; etc.
However, although the Mac treats each partition as if it were a separate drive, they aren't - they are still part of the same physical drive.
A single partiton can be erased, for example by using the Erase function in the Special menu in OS 9. Unfortunately all that an Erase does is to delete entries in the disk directory - none of the data is actually removed, including the directories themselves.
A deep-wipe of the drive is part of a broader initialization of the drive; this affects the entire drive, meaning all partitions of the drive will be wiped of all data.
Will I lose everything when I deep wipe the drive?
Everything that is on that drive, on all partitions of that particular drive, yes.
As Grant noted, the Big System Morsels error usually indicates a problem with the machine being able to read the CD properly. Often that can be fixed by cleaning the CD. A Mac's optical drive is far less tolerant of smudges (fingerprints, etc.) on a data disk (such as an install CD) than it is with such on an audio disk. -
Corrupt file error won't let me manage nano
I followed the 5 R's from the Apple website, but iTunes will not allow me to run the ipod updater and refuses even to show the ipod in its listing. It says "corrupt file /ipod-control/itunes run chkdsk". I actually ran a chkdsk from dos and that errors out saying the ipod_control/itunes is inaccessible. Is there an Apple program to just reformat the ipod withou having to "read" it, as the iTunes seems to? I did put on the latest iTunes (7.2).
dell Windows XP ProYou could try a format of the iPod in Windows. A full format does a check and remap of bad sectors on the iPod hard drive, and you would need to restore the iPod as normal (using the iPod updater) afterward. This can also work when the iPod is recognized by the computer, but not by the updater.
First, put the iPod into forced disk mode.
See: How to put the iPod into disk mode.
On your PC, go "my computer" and right click on the iPod, then choose "format". Ensure the settings are at "default" and that "quick format" is not checked. Now select "format". It will take a while, but when that's finished, restore the iPod using the updater.
Also, see if either of these help.
What to do if iTunes displays a corrupt file message.
Da Gopha's corrupt file info. -
It seems that as of yesterday 05/10/13, anything that is downloaded will not install. Tried updating to the latest version of firefox, but that give the error of corrupt files.
It is possible that anti-virus software is corrupting downloaded files or is otherwise interfering with downloading files.
Try to disable the real-time (live) scanning of files in your anti-virus software temporarily to see if that makes downloading work.
See:
*http://kb.mozillazine.org/Unable_to_save_or_download_files
*browser.download.manager.scanWhenDone
Boot the computer in Windows Safe Mode with network support (press F8 on the boot screen) as a test to see if that helps. -
Toshiba M45-s269 Windows won't start-missing or corrupt file
Toshiba M45-s269 Windows xp sp3
Recently got the message upon a restart that "Windows cannot start because a file is missing or corrupt" then names the file "<Windows root>\system32\ntoskrnl.exe."
Screen show options to restart windows normally, in last known good config, safe mode, safe mode with command prompt or with networking. All options only have the result of a 2-minute freeze-up and returning to the same screen after showing the Toshiba splash screen.
I was able to F12 at splash screen which gives the option of what to reboot from: Multiple discs, single disc, floppy or networked. Otherwise all options have same looped result notifying cannot start due to missing/corrupt file.....
Having the factory recovery disc, I was able to select the single disc option with F12 at splash and try running a recovery from D:/.
The disc, however, says it will reload Windows 98 (the computer came with XP Home) and wants to re-format which will blow out EVERYTHING I have on the hard drive which is NOT an option for me!
A while ago I was given a disc from a friend that has XP Professional. I have been trying to restore from that with less than expected results. Have gotten to a DOS promt and tried to COPY the file from XP Pro disc but being told cannot find the file. I'm most likely not doing something right. Don't know what destination to send it IF I'm able to copy the file anyway.
Tried to load XP Pro on hard drive but computer sees the Home version and gives the message that loading 2 OS's is not recommended. Was hoping that XP Pro would simply over-write Home.
Any help appreciated. Thanks in advance,
RobHi
Setup CD is not delivered with your notebook, just recovery CD and recovery CD does not offer repair option.
Try to obtain Microsoft Installations CD. Talk with your friends. I am pretty sure someone has this WXP installations CD. Check if you can do something using R option.
Check also what Microsoft wrote about this issue:
http://support.microsoft.com/?kbid=307545
http://support.microsoft.com/kb/269075/en-us
Good luck! -
My I phone 4 has put itself into recovery mode and I cannot now restore it. I have plugged it into I Tunes about 10 times and every time it starts to restore then comes up with the message Corrupted file start again. Please help.
Try restoring as a new device first.
-
Setting a Layer Break for GEAR Pro Mastering Edition with EncoreDVD & IFOEdit
Setting Layer Breaks Manually for Encore/GEAR Projects
Although we can write straight to a DVD+R DL disc directly out of EncoreDVD 2.0 and we can also create our Master DLT tapes directly out of EncoreDVD 2.0 also, there are times when these options simply are not sufficient.
For example - we wish to Verify the successful writing of a DLT Tape, or we wish to create a QC disc for our clients in DVD-R DL format.
Either way, the "option" of using a +R DL disc is often unacceptable.
Another very good reason for +R DL discs to be NFG is that they are NOT DVD-Video format, and as such tend to expect the layers 0 and 1 to be of equal size.
Yet another reason could simply be we are using EncoreDVD 1.01, which does not support direct writing of any DL discs at all.
The solution is to use GEAR Pro Mastering Edition to create your DLT or DVD-R DL disc directly from your Encore project instead.
And here's how you do it.
You are going to need copies of both GEAR Pro Mastering Edition, EncoreDVD (any version) and finally a copy of the freeware application IFOEdit http://www.ifoedit.com/. Additionally, we will also need the GEAR Layer Break Calcuulator, provided for free on their excellent support site at http://www.gearsoftware.com/support/documentation/layerbreakcalculator.xls
Now we are ready - lets look at how it is all done. Don't be put off by what looks like a lot of math here either - this gets easier every time you do it and all it takes is a little common sense and practise.
The best way to proceed is to use EncoreDVD to build your project to a folder. This will not make any Layer Break settings at all, and will allow us to create a new DL Project in GEAR and also allows GR+EAR to build the UDF/ISO structure for us.
So once we have written our tested and checked project to a folder, the next step is to close out of EncoreDVD and launch GPME. By the way - if you're not certain that you need the expense of GPME for a one-off project you can simply download their 30 day trial version and use this as it is 100% fully functional in every way - there are no limitations at all.
When GEAR loads, select to create a new DVD-Video project and be certain you tick the DVD9 box in this screen too. Another window will appear now asking you to locate the folder where the Video_TS files are stored. Point this at the Video_TS folder and GEAR will create a basic DVD9 project for you.
Next we need to load up the Excel Spreadsheet with the Layer Break Calculator we downloaded earlier. I always use a different machine for this as I don't have Office installed and any open source application that can read an XLS file will do the job. If you don't have one, I recommend either OpenOffice or Star Office to do this. There are a lot of helpful calculators in XLS mode, and you won't regret it. Just try to keep all this stuff well clear of your authoring system though. But I am rambling, and I'm sorry. Back to buiness.
Once we have loaded up our Layer Break Calculator, we need to enter in some numbers.
Back over in GPME, where we have our shiny new DVD9 project sat there waiting for instructions, there is a file structure on the lower left hand side of the project screen. Att the top of the list we should see something very much like "VOLUME (projectname) (DVD-Video ISO/UDF)"
Right-click on this, and select "Properties". A screen will appear with all sorts of numbers in it, and we ignore the lot of them except for the "Total Volume Size in Sectors" - which we need to write down, nip across the room to our spreadsheet, and type the number in right at the top where it says "Total Volume (project) Size"
Another set of (probably) meaningless numbers appears - and the 2 we are interested in here are the ones where it says "RULES" and specifically "Layer Break Point must be Greater than .....
And Less than.....
Write these 2 numbers down, and hop smartly back across to where we have our GEAR project open on our authoring machine. Or simply minimize the spreadsheet if we are doing all this on the same system.
We now need to click on the folder marked "Video_TS" in the bottom left of the GEAR screen, and on the lower right we need to click once on the bar in the middle above all the VOB files marked "start sector" to arrange all the files in the sequence they will be on the disc. This makes finding our VTS file so much easier.
Somewhere in that list there will be a file that has that range of numbers in it. If we are really lucky, there will be more than one, which means that one of these will soon become our Layer Break.
When we have identified the correct file, take a note of it's name - it will be VTS_01_4.VOB or something with a similar structure name wise.
Next, we need to write down and enter into the Layer Break Calculator the start sector number of the VTS_xx_1.VOB file that holds our values.
I will try to explain why. If our Sector range is to be found in the example we gave earlier, say VTS_01_4.VOB, we need to note the start sector of the file VTS_01_1.VOB. This is because all these VTS_xx_x.VOB files are all extensions of the same file. They are just in handy blocks so that the Computer can keep track of them without breaking any rules about file sizes. Anyway, we write down the Start Sector of the file VTS_xx_1.VOB where xx is the file where the Layer Break range is to be found.
Just to try & make the concept clear, if the range were found in the file VTS_05_5.VOB, our start sector we need to write down is VTS_05_1.VOB
Enter this into the Calculator/Spreadsheet in the place where it says "Chosen Video Object VTS_xx_1.VOB Start Sector.
Now this will tell us exactly where we need to look next, and tell us we now need to hunt for a cell start sector between a range of sectors.
It might be something like "1,148,678 and 2,051,052" sectors.
This is where IFOEdit comes in.
Launch IFOEdit - and you may as well go back to GEAR, and close the project - but not the application. Go to the "File" menu, and from the drop dow select "Delete GEAR Project" and delete the one we just created, as we will need to change it anyway. Why you will find out later on.
From IFOEdit, you will see 2 halves of a screen. Down the bottom left there is an "Open" button. Click on this and locate the Video_TS folder, and specifically the file VTS_xx_1.IFO, where xx is the file we know from earlier the Layer Break will be placed.
Immediately your head will start to ache, your eyes will glaze over & your brain will wave a little white flag, as some serious mathematics suddenly appears (Well, that's what happened to me the first time. I was too fascinated to be confused - sheer bewilderment is perhaps the best expression. And I still don't know what most of it is for.
The one we are interested in can be found in the upper half, and is called "VTS_PGCITI".
Click on this, and a lot of little others will appear immediately below it.
You will see VTS_PGC_1 and so on until you run out of blocks.
The odds are high our layer break will be in the longest file - but this does not always hold true, so we start at the top & work our way rapidly down. What we are looking for is twofold.
1 - A Cell Start Sector within our range defined earlier.
2 - A cell Start Sector flagged as "NON Seamless playback.
If we can fill both these criteria, we have our layer break.
Write this number down, and enter it into our spreadsheet - and close down IFOEdit as we are done with it for today.
Back in the Spreadsheet we are almost done. Once we enter this number in, it will helpfully calculate exactly where in our Virtual image from earlier that sector lies, and will check to see if it is divisible by 16. Don't worry for now why, just know that it has to do this.
The chances are high it will not be, so the spreadsheet will tell you how many sectors the whole image has to be shifted forwards by, and what the new Cell Start Sector is in this revised image. This is automatic, and you get 2 figures.
1 - Offset. This number will be between 0 and 15.
2 - Layer Break Sector.
Time to go back to GEAR, and in our "Options" drop-down menu we will have another one called "Preferences". In this, we need to tell GEAR to ask us for the start sector to be entered for each file.
Now we create our project again - but this time GEAR will ask us for the start sector of VIDEO_TS_IFO, and the figure 640 will be highlighted.
Add our offset figure we were given earlier to this so if our offset was 11, enter in 651.
GEAR will do all the rest automatically for you.
One more job to do now.
Go Back to "Options/Preferences", and under DVD we need to tell GEAR we are changing the Layer Break. Click on the "Change" button, and use the up/down arrows to arrive at our newly discovered Layer Break Value.
Save the project - we're done. And write down that offset & Layer Break whatever you do.
You can now write to DVD-R DL, DLT tapes (and if you right-click on your DLT drive in the lower "Devices" screen, and choose "Properties", you can tell GEAR to verify the tape after writing too. It will write both layers first, then verify each one.
There is, however, a minor "GOTCHA" in GPME when writing DLT tapes.
It is allowed to set the IDENT.TXT file to be included on the DLT tape by means of a tick box. However, as this file is not actually required for replication in DVD-Video, but only in DVD-ROM - GEAR will not include the file
i even if the box is ticked
but it
i does
add a pointer to the file in the DDPID file instead. The upshot of this is that a DLT tape where IDENT.TXT has been selected to be included will be
i rejected by the factory as unusable.
This is because when they try to verify the DDP image on the tape it will fail as IDENT.TXT is NOT on the tape.
You must ensure this box is NEVER TICKED - I fell for this one recently, and had to rework 7 DLT tapes.
There is yet another way to get a DL project to the factory if you do not have a DLT machine, and do not have access to DL discs in the correct format.
Write the DDP images to 2 single layer discs instead!
This requires the use of GEAR Pro Mastering Edition again, and is incredibly easy to do.
What you need to do here is follow the original guides in the FAQ sections for setting the Layer Break manually, but instead of writing the project to DLT tapes or to DVD-R DL/DVD+R DL media, what we do next is write the project to a DDP file on the HDD instead.
This will result in 2 folders appearing - Layer 0 and Layer 1.
Each of these has the necessary information for the replication plant to manufacture the discs - all we need to do is get them onto 2 discs instead of 2 DLT tapes.
This is simplicity itself.
Launch your burning application.
Create a new DVD-ROM project.
Name it (Project)_Layer_1
Broswe to the 2 folders with the DDP files in them, and add the contents in this exact order
DDPID
CONTROL.DAT
IMAGE.DAT
(Checksum.txt - optional)
(Log file - optional)
Burn the disc.
Repeat for Layer 1.
That is all there is to it.
What will happen at the factory is the Eclipse verification system will look for the DDPID file at the root level of the disc. If it cannot find it, it will assume it is dealing with a standard DVD-ROM disc instead, but if it is there it will know what is going on, load the files, and ask for Layer 1 after it has finished in the normal manner.
I hope this helps out - if not, please post in the main forums, and I'll try to help out.Hi Ryan,
Yes, you'll only get the LB sector number when you format with one of the "tape images" (go with DDP 2.0). And unfortunately, Gear doesn't allow transfer of DDP or CMF Images to DLT.
Gear is working on a version that will incorporate DVD-9 making within the program.
Meanwhile, If you go with the instructions on their site to create a DVD-9, be sure to add: "correct VTS sectors" in the VIDEO_TS folder with IFOEdit, and set the region info in the VMGM_MAT to "0"; and be sure to flag all instances of a cell properly for the layer break, in the case they reside in any Stories that span the Layers.
But if I may; It's highly recommended that you hire out tests on the resulting DDP image to make sure the layer break did indeed fall where you expected, and that there are no other issues (Same goes with any DDP image destined for replication, created by any other program).
Or better yet, consider hiring someone to premaster for you (I wonder who? , who also includes navigation proofing, spec compliance testing (MEI and sometimes with a player bank) and verifying the finished Image (EclipseSuite); all for one low fixed price, i.e. no charge in the event a resubmission to me is required (pre consultation, also included, nips lots of common mistakes in the buds). This insures that only a bullet-proof Image is finally sent in to the replicator.
There I go with commercials again! But for sure, Gear's current DVD-9 method is not for the faint of head; and premastering in general, is not the innocuous activity it appears to be. Real trouble eventually awaits (unless measures are taken), due to the nature of the critter.
Take care,
Trai -
Can iMac not waking from sleep be caused be a corrupt file
I have had my 27" iMac from July of 2011 (running Montain Lion, 8 GB RAM, 2TB hardrive, 3.4 GHz,Intel i7) for over a year and a half and ever since I bought it, it has had a problem waking from sleep. I can hear the computer running, but when I click the mouse, keyboard, or power button, it stays asleep and I am forced to do a hard shut down. Apple has been trying to fix the issue, but to no success. They have replaced the hard drive, logic board, usb ports, RAM, mouse and keyboard, but it still happens. They finally threw in the towel and are replacing the machine. They offered to transfer all of our files (jpgs, mp3s, docs, videos, etc), but one thought occurred to me... what if the sleep issue is caused by a corrupt file? I highly doubt that is the case, but wonder if any of the experts out here would know better than I.
If we didin't have the data transfered, we would just keep it on an external hard drive instead. But, I would assume that it wouldn't matter if the files were on internal vs. external because either way, the computer would access the files. That being the case, if the sleep issue was caused by a corrupt file, the computer would still access it on the external and the sleep issue would resurface.
So, 2 questions:
Can a corrupt file cause the sleep issue?
If it is true that a corrupt file can cause the sleep issue, would it matter if the corrupt file was accessed from an external drive vs. internal drive?
Thanks so much!
ChrisPlease read this whole message before doing anything.
This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
The purpose of the test is to determine whether your problem is caused by third-party system modifications that load automatically at startup or login.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode* and log in to the account with the problem. The instructions provided by Apple are as follows:
Shut down your computer, wait 30 seconds, and then hold down the shift key while pressing the power button.
When you see the gray Apple logo, release the shift key.
If you are prompted to log in, type your password, and then hold down the shift key again as you click Log in.
*Note: If FileVault is enabled under OS X 10.7 or later, or if a firmware password is set, or if the boot volume is a software RAID, you can’t boot in safe mode. Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs. The next normal boot may also be somewhat slow.
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin. Test while in safe mode. Same problem? After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of the test. -
What to do if Windows displays an "iTunes.exe - Corrupt File" message
Greetings fellow Podders, Resident Furball here...
It is about time that I produced a single post for all the chkdsk issues that we've been discussing since November 2004. The Apple KB article seems to cover the major points succinctly, but we need to address the more serious variations and flavours of the problem.
<hr>
What to do if Windows displays an "iTunes.exe - Corrupt File" message
Many users are coming across this seemingly distressing error message in Windows when connecting their iPods. As described in Apple KB Article 300554, the message reads:
iTunes: iTunes.exe - Corrupt File
The file or directory \iPod_Control\iTunes\????????? is corrupt and unreadable. Please run the Chkdsk utility.
and the ????????? can be anything (eg. sysinfo, Temp1, DeviceInfo etc.).
<hr>
Don't panic!
If you do see this, don't worry, and don't panic. Contrary to what the error message reads, this issue actually has very little to do with iTunes. The iPod_Control is the key to this - because this folder doesn't even exist in iTunes... it's on the iPod!
...so! Installing and uninstalling iTunes really won't do you much good at all... it's the iPod that needs attention.
<hr>
What's causing this error?
To be honest, we don't know. We saw a massive number of reports of this issue back in November 2004, because iPod Updater 2004-11-15 contained a firmware bug that corrupted iPod system files when the Pod entered Deep Sleep.
But this firmware bug was corrected in iPod Updater 2005-06-26.
Of late, we have seen a resurgence in chkdsk errors on Discussions. Some of these are caused by the old buggy firmware that people still have. Some of the errors are more serious and are hardware and operating system-related. But we have still to pin down the exact cause of this error.
<hr>
Okay, so what do I do if I see this error?
In short, as Apple have recommended in their KB article:
Restore your iPod, using the latest iPod Updater.
Follow the instructions carefully. Ensure that you download the iPod Updater. Ensure that you install it, and then ensure that you run it with the iPod connected and follow the prompts to the letter.
The broad majority of the errors are painlessly fixed this way. Of course, it does mean that your iPod will be wiped, so make sure that you have your music/data backed up, and/or present in iTunes so you can resynchronise it when you have finished Restoring.
<hr>
Okay, I've Restored, but the error is still coming up
Are you sure you've Restored? Quite a number of folks are assuming that just downloading the iPod Updater is enough. It's not. And neither is downloading iPod Updater, and installing it on your computer. It needs to be implemented on the iPod, according to the iPod Updater instructions.
Okay, so if you have Restored your iPod, and you are still getting this error, then you have a variety of options available.
Chkdsk errors that are not fixed with a Restore are most likely down to two things:
1) A physical issue on the iPod itself
or
2) An issue on the computer's operating system
Here's where it gets woolly. There are a variety of things you could try...
Format the iPod in Windows
This would usually have the same effect as a Restore, but a deep-level format in Windows is something that Apple have recommended in the past, as a last resort to completely wipe the iPod before performing a Restore with iPod Updater. This process wipes the iPod.
To do this:
1) Enable Disk Mode on the iPod. You can do this either in iTunes (which is best), or manually on the iPod itself.
2) Open My Computer and locate your iPod
3) Right-click the iPod and select Format
4) Leave the parameters set at their defaults, and ensure Quick Format is unchecked
5) Hit Format
6) Then Restore your iPod as normal.
Run the Chkdsk utility
You could run the chkdsk utility on your iPod. But Restoring your iPod has the same effect as running chkdsk. Chkdsk does not wipe your iPod.
1) Enable Disk Mode as above
2) Determine the drive letter of your iPod from My Computer
3) Go to Start, Run
4) Type cmd. Hit Enter to take you to the Command Prompt.
5) Type chkdsk /f X:, where X is the drive letter of your iPod. Hit Enter, and any corrupt files are found and corrected.
Run Windows ScanDisk
ScanDisk is the Windows version of Chkdsk. It does not wipe your iPod.
1) Enable Disk Mode
2) Right-click the iPod in My Computer, select Properties
3) Select Tools
4) Select the option to scan the disk for errors
Try changing the Drive Letter of the iPod
Sometimes Windows confuses the drive letters, and this can cause the iPod to be adversely affected. Try the instructions detailed in Apple KB Article 93499 to change the drive letter of the iPod. This does not wipe your iPod.
Try changing Hardware Policies for the iPod
The Hardware Policies in Windows have been known to affect the way in which the iPod connects, synchronises, and disconnects. This does not wipe your iPod.
1) Enable Disk Mode so the iPod appears in My Computer
2) Right-click the iPod in My Computer
3) Select Properties
4) Select Hardware Policies
5) Select Optimize for Performance (instead of Optimize for Removal)
6) Restart your computer.
Contact Apple for a replacement iPod
Some chkdsk issues have been caused by faulty hardware. As a last resort, contact Apple Support by phone to report your issue, and/or request an iPod Service.
If you explain that you have followed all these steps, you should have a strong case for obtaining a replacement iPod.
<hr>
Thanks!
Thank you to everyone for their continued support, kindness and excellent troubleshooting skills here on Discussions. There are countless people that I am deeply grateful to for their assistance in handling this issue. Rest assured folks, you have made me the Discussions Furball that I am today.
Happy Podding folks!
Kind regards,
Gopha.
<hr>
References
1) The Original Corrupt iPod File thread from 2004. (Credit: AbbyM)
2) Our Summary and Index threads to consolidate the chkdsk issue at the height of its reign of terror.
3) Chkdsk is fixed by iPod Updater 2005-06-26.
4) Different flavours of chkdsk.
5) Happy Birthday chkdsk!.
6) Apple Level 2 Technical Support officially close the chkdsk casefile. (Credit: Apple Level 2)
7) Chkdsk can be fixed by changing the drive letter of the iPod. (Credit: daisysnroses, jchiu8)
8) Chkdsk can be fixed by changing the hardware policy. (Credit: Bruce Finn)
9) Chkdsk caused by faulty hardware. (Credit: Kiwi_Bloke)iPod Updater 2006-03-23 has been released
iPod Updater 2006-03-23 includes iPod Software 1.1.1 for the new iPod and new iPod Software 1.1.1 for iPod nano.
iPod Updater 2006-03-23 contains the same software versions as iPod Updater 2006-01-10 for all other iPod models.
What's new in iPod Updater 2006-03-23:
- Volume limit
- Bug fixes
I have been trying to ascertain from Apple Support Level 2 as to whether the latest iPod firmware improves or provides better resolution for the chkdsk issue. If anyone has been using iPod Updater 2006-03-23 to resolve their chkdsk woes, feel free to post in here just to say how things worked out for you...
Kind regards,
Gopha.
Maybe you are looking for
-
A Pop-Up has appeared on my opening screen which I cannot get rid of
There is a Pop-Up on my opening screen which says: Opening <filename>.exe. You have chosen to open http://aihdownload.adobe.com. Would you like to save this file or cancel. I cannot save/cancel this pop-up. This file is a binary file and I had not ev
-
Deactivate users who are no longer exist in AD but were added into resource pool
Hello forum members, does anyone know how to deactivate users who are no longer exist in AD , but were added into resource pool? I an trying to write some code that would update a custom value for each resource, but my code breaks whenever it encount
-
Freight Material why it is required and what are the configuration?
Hi experts, My clientsu2019 requirement is they want freight material to be configured in DIEN material type? I want to know why they want this and what are the steps to configure it apart from material master Plz need your help Thanks Krushna
-
Getting to a share from my Powerbook to my XP machine
I have a shared folder on my XP machine and I would like to get to it from my Powerbook G5. I have a workgroup defined as Connection and I also have a Linux server on the network. The Mac sees the Linux box and I can read/write to that machine with n
-
Creating hyperlink to a network file?
Hello All, I am having issues with Adobe Acrobat and hyperlink to a network file. I am using Acrobat XI and I have successfully created a link to a text that "Open a File" located on our network share. It works great, when others are executing the