IDVD Corrupt encoding / glitches / crashing : SOLUTION

Bought a G5 1.8ghz some time ago, loaded up with heaps of RAM so we could start using the (then) newly released Motion. All was good- the animation we did is doing the festival circuit and got a few seconds on Apple's showreel. Except...
I'd always had trouble with iDVD and DVD Studio Pro. I found myself making projects on the G5, then taking them across to the old G4, because as slow as it was, it still encoded without crashing or corruption.
I read up, scoured the net, checked forums and troubleshooting sites, ran Apple Hardware Test/Disk Util/Disk Warrior/Mac Sweeper, reinstalled iDVD, reduced to the base RAM, resintalled the system, reduced possible software conflicts- in short, spent bloody ages to track down the problem. In the end, I kept giving up and using the G4 just so I could get projects out the door.
It finally occurred to me to try base RAM, but by ditching the Apple DIMMs and keeping some of the 3rd party ones..
And now it encodes quickly and perfectly. Sigh.
(BTW, Patchburn patchburn.de was a huge help in saving me burning coasters while troubleshooting).
Hope this saves someone from the angst and wasted hours I went through.
Cheers
Minty
Nectarine

Expensive Apple RAM turned out to be less reliable than cheaper 3rd party RAM.

Similar Messages

IDVD 6.0 continually crashes for no apparent reason

I have only had my macbook for 2 months and I am starting to have problems with iDVD. Every time I attempt to build a project it freezes up my computer and sooner or later crashes. When I try to change the theme of my project, it runs extremely slow. I have tried a lot of the solutions online but nothing seems to work. Here are some of those things:
- reinstalled idvd
- background encoding is not on
- lots of free disk space is available (30GB)
- no other programs are running in the background
When I first bought my Macbook, there were no problems with iDVD (2 months ago!). I also dont have any problems with any other programs on my computer, many of which are much more demading than iDVD 6.0! Could somebody please help me because this program is causing me a lot of stress!
Thanks,
David
Macbook Core 2 Duo Mac OS X (10.4.8) Core 2 Duo 2.0 Ghz, 1GB Ram, 120Gb HDD

Hi David_p
Have you already repaired permissions & dragged the plist for iDVD to the trash and emptied it?
Looks like this (use the finder and copy and paste the following):
com.apple.iDvd.plist
Also please disconnect all ext. FW & USB devices and run apple's software updater to make sure all is current including QT and iDVD. Lastly try going into Macintosh HD >Applications > Font Book, then look for fonts that have a black dot beside them. Highlight these fonts, then from the menu bar select > Edit > Resolve Duplicates to turn these fonts off.
Here are a few helpful links as well.
http://docs.info.apple.com/article.html?artnum=302925
http://www.apple.com/ilife/tutorials/idvd/id2-3.html
http://www.kenstone.net/fcphomepage/idvd_6stone.html
http://docs.info.apple.com/article.html?artnum=302988
Good luck to you & hope this proves Helpful.

AE CC 2014 Corrupted and Glitched frames when rendering to Quicktime

Ever since upgrading to the newest version of After Effects, I've been getting corrupted and glitched frames when rendering videos with a Quicktime holder. My normal workflow is rendering the video straight out of AE, but it also happens when rendering with Adobe Media Encoder, or even while using the "BG Renderer" script for AE that renders from the terminal. It happens whether I have multiprocessing enabled or not.
The corruption differs depending on what codec I'm using, but in the Cineform Codec it shows up as green frames:
On DNxHD they show up as Red frames (don't have a screencap of this one but you get the idea).
Using the QT Animation Codec they show up as static or distortion:
I have not found a codec that does not become corrupted when encased in the QT holder. Image sequences render out fine, and Cineform with an AVI holder renders out fine.
Even more strangely, I can fix the problem if I link the AE composition to Premiere, then render the QT file out through Premiere itself. The fact that Premiere calls and renders the Comp fine but AE does not, makes me think this is a bug in AE's treatment of Quicktime rather then a driver/system incompatibility on my end. But I'm certainly willing to try any suggestions the community might have for me =]
Specs:
Windows 7 64-bit
AMD Firepro V7800
AMD Phenom II X6 1090T
16 GB RAM
Rendering to a local drive
Fully Updated AE
Latest version of Quicktime

solutions for problems with QuickTime files in After Effects CC (12.0) because of conflict with DVCPROHDVideoOutput Quic…

Adobe Media Encoder CS4 Crashing Immediately

Hello,
I am running the CS4 Production Premium suite on a Windows 7 64-bit computer with 12GB RAM. Up til last week, the whole Adobe suite had been running smoothly. (I primarily use Premiere, Media Encoder, Photoshop, and Encore). However, Encore started locking up the computer any time I tried to work on authoring a Blu-ray (it locked up immediately upon opening a Blu-ray project, and only locked up on a new project when I switched from DVD to Blu-ray mode).
I assumed that some of Encore's source code had either been moved, overwritten by something else, or that there was possibly a program incompatibility with something else on my computer. So I took the step to uninstall and reinstall Encore from the install DVDs.
Upon a "successful" reinstallation, I then went into Premiere CS4 to encode a timeline to a P2 file. Premiere seemed to be doing its normal exporting process fine, but Media Encoder would crash after the red splash screen disappeared. To be more explicit, the red splash screen would disappear and be replaced by a window the normal size of the Encoder program, but nothing appeared on screen in the window other than a small white box in the upper left with the rest just being plain gray (see attached photo). At the same time this white window appeared, Win 7 popped up a box saying that Adobe Media Encoder has stopped working and that it would search for a solution to the problem, which it never could do.
I then tried deactivating the suite, uninstalling the full suite and reinstalling, updating so the patches would bring it up to date, and then tried running Adobe Media Encoder again, this time running from the Start menu rather than from Premiere. Yet, it was still the same response: the program crashes immediately.
I would appreciate any suggestions and help that people can provide.
Sincerely,
Kevin T
San Diego, CA

Here is the only relevant info I could find in the Event Viewer:
Faulting application name: Adobe Media Encoder.exe, version: 4.2.0.0, time stamp: 0x4af13937
Faulting module name: WatchFolder.dll, version: 0.0.0.0, time stamp: 0x4af1344e
Exception code: 0xc0000005
Fault offset: 0x00011f03
Faulting process id: 0x834
Faulting application start time: 0x01ca9d3e4234c82b
Faulting application path: C:\Program Files (x86)\Adobe\Adobe Media Encoder CS4\Adobe Media Encoder.exe
Faulting module path: C:\Program Files (x86)\Adobe\Adobe Media Encoder CS4\WatchFolder.dll
Report Id: 89095e2b-0931-11df-a5f1-00248c778de6
Does this seem fixable to anyone?

Export to windows media encoder-PPro crashes

Every time I try to export to Adobe Media encoder: windows media: PPro crashes.
I am working on a 64k computer using the 32k version of PPro CS3.
Every other format in the media encoder works fine.
Does anyone have any solutions or know why this happens?
Thanks,
J.

J.Charette, "Export to windows media encoder-PPro crashes" #, 15 Jan 2009 12:24 pm
This thread is getting a bit old now but I'm now having the exact same problem as J.Charette. I think I may have some light to shed on it as well. I was successfully running CS3 master collection and exporting to WMV files in PPro/AE for the past year under XP64. I was given a new computer (again XP64) and didn't have any problems until I installed Microsoft Windows Media Encoder 64 (I used to use the 32 bit version successfully and this time figured I'd just get the 64 bit one instead).
Now that I've installed WME I can't export as WMV from any AE/PPro CS3. As soon as AME comes up with the format selection screen, if I select WMV from the drop down box it immediately crashes. I've tried uninstalling WME, reinstalling it and even uninstalling WME & CS3 and reinstalling from scratch. Still doesn't work.
In my case at least, there is a definite correlation between installing WME64 and its interaction with Adobe Media Encoder... Anyone have any suggestions? It seems to me there must be some registry setting / config file for AME that is causing it to try to use WME64 for something which causes a crash (since 32 and 64 bit apps can't call each other).
Ideas?
Thanks,
Christopher Grant

Media Encoder CC Crashes Loading Looks 3

Every time I load Media Encoder it crashes when "Loading Looks3_AE10.plugin. I have no idea where to even start with trying to fix this. I just formated my primary drive and am in the process of reinsalling and setting everything up. So I just got all my stuff reinstalled and updated and was going to test something out in Media Encoder and I get this same issue every time. I've tried updating the OS, restarting, making sure everything else is up to date and nothing helps.
Crash Report:
Process:         Adobe Media Encoder CC [380]
Path:            /Applications/Adobe Media Encoder CC/Adobe Media Encoder CC.app/Contents/MacOS/Adobe Media Encoder CC
Identifier:      com.adobe.ame.application
Version:         7.2.0.43 (7.2.0)
Code Type:       X86-64 (Native)
Parent Process: launchd [143]
User ID:         501
Date/Time:       2014-02-05 11:39:48.893 -0600
OS Version:      Mac OS X 10.8.5 (12F45)
Report Version: 10
Interval Since Last Report:          48162 sec
Crashes Since Last Report:           4
Per-App Interval Since Last Report: 74 sec
Per-App Crashes Since Last Report:   4
Anonymous UUID:                      244D09B4-BE79-9EB3-AE75-A679C3AA1A7A
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
terminate called throwing an exception
abort() called
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib                  0x00007fff90521212 __pthread_kill + 10
1   libsystem_c.dylib                       0x00007fff96fd5b24 pthread_kill + 90
2   libsystem_c.dylib                       0x00007fff97019f61 abort + 143
3   libc++abi.dylib                         0x00007fff9321c9eb abort_message + 257
4   libc++abi.dylib                         0x00007fff9321a39a default_terminate() + 28
5   libobjc.A.dylib                         0x00007fff968cd887 _objc_terminate() + 111
6   libc++abi.dylib                         0x00007fff9321a3c9 safe_handler_caller(void (*)()) + 8
7   libc++abi.dylib                         0x00007fff9321a424 std::terminate() + 16
8   libc++abi.dylib                         0x00007fff9321b58b __cxa_throw + 111
9   com.adobe.dvacore.framework             0x000000010022814d dvacore::filesupport::DirHelper::Create() + 813
10 com.adobe.AMEAppFoundation.framework          0x0000000104f285e9 AME::foundation::AppUtils::GetUserPresetDir(bool) + 425
11 com.adobe.Batch.framework               0x0000000105c0a842 AMEBatch::Initialize() + 2194
12 com.adobe.ame.application               0x00000001000273cb AME::app::AMEAppInitializer::AMEAppInitializer(exo::app::AppInitArgs&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >&) + 811
13 com.adobe.ame.application               0x000000010000ad6a AME::app::AMEApp::InitApplication(exo::app::AppInitArgs&) + 2426
14 com.adobe.exo.framework                 0x000000010513e77a exo::app::AppBase::Initialize(exo::app::AppInitArgs&) + 1066
15 com.adobe.ame.application               0x00000001000141a8 AME::RunTheApp(exo::app::AppInitArgs&, std::vector<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >, std::allocator<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > > >&) + 1576
16 com.adobe.ame.application               0x0000000100056a38 main + 424
17 com.adobe.ame.application               0x0000000100003f74 start + 52
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib                  0x00007fff90521d16 kevent + 10
1   libdispatch.dylib                       0x00007fff9564edea _dispatch_mgr_invoke + 883
2   libdispatch.dylib                       0x00007fff9564e9ee _dispatch_mgr_thread + 54

I'm getting the same issue.
Here is my report:
Process:         Adobe Media Encoder CC [797]
Path:            /Applications/Adobe Media Encoder CC/Adobe Media Encoder CC.app/Contents/MacOS/Adobe Media Encoder CC
Identifier:      com.adobe.ame.application
Version:         7.2.0.43 (7.2.0)
Code Type:       X86-64 (Native)
Parent Process: launchd [197]
Responsible:     Adobe Media Encoder CC [797]
User ID:         501
Date/Time:       2014-02-05 13:23:34.764 -0500
OS Version:      Mac OS X 10.9.1 (13B42)
Report Version: 11
Anonymous UUID: 5093BAE8-5BE0-C005-7453-67715FA016E2
Sleep/Wake UUID: B36E4F65-7E25-490D-80BF-880D8A56C19D
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
terminating with uncaught exception of type dvacore::filesupport::dir_create_exception: $$$/dvacore/filesupport/DirCreate=The directory '@0' could not be created. Please check the parent directory protection or permission rights.
abort() called
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib                  0x00007fff9513e866 __pthread_kill + 10
1   libsystem_pthread.dylib                 0x00007fff93e3135c pthread_kill + 92
2   libsystem_c.dylib                       0x00007fff9408abba abort + 125
3   libc++abi.dylib                         0x00007fff9348c141 abort_message + 257
4   libc++abi.dylib                         0x00007fff934b1aa4 default_terminate_handler() + 240
5   libobjc.A.dylib                         0x00007fff943a0322 _objc_terminate() + 124
6   libc++abi.dylib                         0x00007fff934af3e1 std::__terminate(void (*)()) + 8
7   libc++abi.dylib                         0x00007fff934aee6b __cxa_throw + 124
8   com.adobe.dvacore.framework             0x000000010022814d dvacore::filesupport::DirHelper::Create() + 813
9   com.adobe.AMEAppFoundation.framework          0x0000000104f285e9 AME::foundation::AppUtils::GetUserPresetDir(bool) + 425
10 com.adobe.Batch.framework               0x0000000105c0a842 AMEBatch::Initialize() + 2194
11 com.adobe.ame.application               0x00000001000273cb AME::app::AMEAppInitializer::AMEAppInitializer(exo::app::AppInitArgs&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >&) + 811
12 com.adobe.ame.application               0x000000010000ad6a AME::app::AMEApp::InitApplication(exo::app::AppInitArgs&) + 2426
13 com.adobe.exo.framework                 0x000000010513e77a exo::app::AppBase::Initialize(exo::app::AppInitArgs&) + 1066
14 com.adobe.ame.application               0x00000001000141a8 AME::RunTheApp(exo::app::AppInitArgs&, std::vector<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >, std::allocator<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > > >&) + 1576
15 com.adobe.ame.application               0x0000000100056a38 main + 424
16 com.adobe.ame.application               0x0000000100003f74 start + 52
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib                  0x00007fff9513f662 kevent64 + 10
1   libdispatch.dylib                       0x00007fff8da7443d _dispatch_mgr_invoke + 239
2   libdispatch.dylib                       0x00007fff8da74152 _dispatch_mgr_thread + 52
Thread 2:
0   libsystem_kernel.dylib                  0x00007fff9513ee6a __workq_kernreturn + 10
1   libsystem_pthread.dylib                 0x00007fff93e31f08 _pthread_wqthread + 330
2   libsystem_pthread.dylib                 0x00007fff93e34fb9 start_wqthread + 13
Thread 3:: Dispatch queue: com.apple.root.low-priority
0   com.apple.CoreFoundation                0x00007fff94daa48f CFBasicHashSetValue + 3615
1   com.apple.CoreFoundation                0x00007fff94da9609 CFDictionarySetValue + 217
2   libCGXType.A.dylib                      0x00007fff9351a6ca copy_name + 105
3   com.apple.CoreGraphics                  0x00007fff8b755fc8 add_root_name + 65
4   com.apple.CoreGraphics                  0x00007fff8b755b3f CGFontNameTableCreate + 906
5   com.apple.CoreGraphics                  0x00007fff8b755794 get_name_table + 29
6   com.apple.CoreGraphics                  0x00007fff8b755760 CGFontCopyPostScriptName + 9
7   com.apple.CoreGraphics                  0x00007fff8b7551c6 CGFontCreateFontsWithURL + 455
8   com.apple.CoreText                      0x00007fff971a11bc CreateFontsWithURL(__CFURL const*, bool) + 22
9   com.apple.CoreText                      0x00007fff971a07ee CTFontManagerCreateFontDescriptorsFromURL + 54
10 com.adobe.CoolType                      0x000000010786e00f CTCleanup + 1005217
11 com.adobe.CoolType                      0x000000010787144f CTCleanup + 1018593
12 com.adobe.CoolType                      0x0000000107872c96 CTCleanup + 1024808
13 com.adobe.CoolType                      0x0000000107768f9b 0x10771a000 + 323483
14 com.adobe.FontEngine.framework          0x0000000107a76f1a CTT1_EnumFontFamilies(unsigned int (*)(void*), void*) + 1370
15 com.adobe.FontEngine.framework          0x0000000107a75a5e CTFontTypeT1::EnumerateFonts(IFTBase*, unsigned int) + 62
16 com.adobe.FontEngine.framework          0x0000000107a80e5f IFTBuildFontEnumeration + 159
17 com.adobe.TitleCG.framework             0x0000000107e68176 initFontDbase(HINSTANCE__*, bool) + 150
18 com.adobe.TitleCG.framework             0x0000000107e6c868 cgCoreInit + 152
19 com.adobe.TitleLayout.framework          0x0000000108085ca5 Inscriber::Implementation::Global::Global() + 613
20 com.adobe.TitleLayout.framework          0x00000001080859bc GetInscriberEnvironment + 44
21 com.adobe.TitleRenderer.framework          0x00000001087d0cb4 CG::(anonymous namespace)::StartupAsync() + 20
22 com.adobe.dvacore.framework             0x0000000100273d8f dvacore::threads::ExecuteTopLevelFunction(dvacore::threads::AllocatedFunctionT<boost::fun ction<void ()> > const&) + 31
23 com.adobe.dvacore.framework             0x0000000100273a8f dvacore::threads::WrapExecuteTopLevelFunction(void*) + 15
24 libdispatch.dylib                       0x00007fff8da722ad _dispatch_client_callout + 8
25 libdispatch.dylib                       0x00007fff8da7409e _dispatch_root_queue_drain + 326
26 libdispatch.dylib                       0x00007fff8da75193 _dispatch_worker_thread2 + 40
27 libsystem_pthread.dylib                 0x00007fff93e31ef8 _pthread_wqthread + 314
28 libsystem_pthread.dylib                 0x00007fff93e34fb9 start_wqthread + 13

IDVD 7.0.4 crashes while burning disc/image

When I try to 'burn' my project to disk or 'save as image' iDVD 7.0.4 crashes without any warnings after rendering the menues right at the beginning of the video render.
Main video in project is AIC (758x592, Quality: middle, Progressiv/Linear PCM, 48 kHz, 16 Bit) exported by iMovie'09 with some chapter markers and video-enhancement as recommended in the forum for best quality and then imported into iDVD.
Earlier project shared to iDVD directly from iMovie burned without problems. Can the codec be the issue? Dropzones use certain parts of the same videofile and they render without problems, I can see them completed in the iDVD-project-package.
Additional questions:
1. why is the file exported with iMovie that large (also with successful project; eg.: orig. file 3, 98 GB, exported file 11,95 GB)? (chapter markers and video-enhancement for the whole file?) Makes archiving a trouble.
2. is there a way to replace the main video in the iDVD-project without distroying the manual menu-/text-/... edits (more titles on one menu, etc.) I made earlier? When I import a whole new videofile in another format (for testing the codec issue), iDVD takes the chapters once more and creates the template-conform menues again, partly overlaying my older ones.

Just to offer condolences. I have been greatly disappointed in iDVD -- crashes more often than burns successfully. Lots of wasted time waiting for a burn to be successful, only to find toward the end of the process, I get a msg "rendering" a problem, or couldn't complete, or crashes and then I have to stand on my head to get the DVD to eject. Have the issue both with movies I've downloaded to iPhoto and with photos downloaded to iPhoto that I've turned into Slideshows. Wish I had awnsers for both of us -- or however many of us that are out there....

We have an issue when we send a film to the media encoder it crashes about half of the time for no particular reason. Anyone else got that too with Premiere Pro CC and the new Media encoder? Thanks! bedrijfsfilm Companyfilms

We have an issue when we send a film to the media encoder it crashes about half of the time for no particular reason. Anyone else got that too with Premiere Pro CC and the new Media encoder?

We have an issue when we send a film to the media encoder it crashes about half of the time for no particular reason
Anyone else got that too with Premiere Pro CC and the new Media encoder?
Lack of detailed info makes your question impossible for anyone to answer you!
eg. ...."Doctor it hurts...anyone else got something that hurts?"

Adobe Media Encoder CS5 crashes at a certain point while rendering

Adobe Media Encoder CS5 crashes at a certain point while rendering, I have also tried to render directly from Premiere Pro but this only makes PremPro crash instead.
The clip I am trying to render right now is 20 mins long, 1600x900 and is a .avi file. The output settings are H.264/HDTV 720p 29.97fps High Quality.
This all started happening after I re-installed windows.
Machine Specs:
Intel i5 3570k
8GB 1866MHz RAM
Intel HD 4000 graphics (yes I know I should get CUDA)
I made sure that CS5 was updated before posting this.

>1600x900 and is a .avi file
That size description makes me think this is a screen capture, not a camera file... if it is a screen capture, what codec/software did you use?
Read Bill Hunt on a file type as WRAPPER http://forums.adobe.com/thread/440037
What is a CODEC... a Primer http://forums.adobe.com/thread/546811
What CODEC is INSIDE that file? http://forums.adobe.com/thread/440037
Report back with the codec details of your file, use the programs below... a screen shot works well to SHOW people what you are doing
http://forums.adobe.com/thread/592070?tstart=30
For PC http://mediainfo.sourceforge.net/en or http://www.headbands.com/gspot/

IMOVIE 6 won't recognize DV camera while IDVD is encoding or burning

I am in the process of encoding and burning a dvd in idvd 6. Given the length of this process, I want to also import some video into an imovie 6 project. However, while idvd is encoding, imovie won't recognize my camera.
I understand I can stop idvd, but then will I lose the encoding that has already occurred?
Will imove recognize the camera if I launch idvd after beginning the import into imovie?
Is there a software fix that will prevent idvd from monopolizing the firewire port when it is just encoding video from an imovie project?
This is a very irritating conflict given the time encoding takes in idvd.
Thanks,
Knapper
Dual 1 GHz PowerPC G4 Mac OS X (10.4.5)

As Sue suggests, it's not surprising that iDVD doesn't want you to access the camera with iMovie. It's not unusual for applications that perform FireWire-intensive functions—as both iDVD and iMovie do—to want to control the device. If iDVD can't control the camera, it may not be able to perform a task you want it to do. (Remember, iDVD offers several camcorder-dependent functions, including OneStep DVDs.)
While it may be a bit treacherous, you CAN go behind iDVD's back to get it done. The trick is to grab control of the camera before iDVD does. So Quit iDVD after you create, then save the iDVD project, then grab control of the camera with an iMovie HD project, THEN re-open the iDVD project and start encoding. (I tested exporting the iDVD project to a disk image, which is probably safer than burning a physical DVD. Use Disk Utility later to burn the disk image to a physical DVD.)
The iMovie video looked fine here, but your mileage may vary.
Karl

I am using PP 2014 CC and it and or Encoder keep crashing.. using iMac computer with Yosemite OS anyone have any ideas about this issue?

I am using PP 2014 CC and it and or Encoder keep crashing.. using iMac computer with Yosemite OS anyone have any ideas about this issue?

Hi,
Please give this a try: Premiere Pro CC, CC 2014, or 2014.1 freezing on startup or crashing while working (Mac OS X 10.9, and later)
Thanks,
Rameez

Crystal reports 2008 and outlook. corrupted encoding

Hello everyone!
I have a problem: when i'm creating connection from crystal reports 2008 (v1, hf16) to outlook with data source outlook or outlook/exchange, crystal report show in subjects texts with corrupted encoding.
I have outlook 2008 and windows vista localized in russian language.
For example, when i'm creating connection through data source based on the ВО universe - texts shows correctly.
Have any ideas how to fix problem with outlook corrupted encoding?
10x and sorry for my english.

Hi,
I would suggest to issue a message to SAP ( [http://service.sap.com/support] ) about this.
Regards,
Stratos

IDVD 6 encoded takes twice as long as iDVD 5?

I did a quick search of archives but if this has been answered and I missed it, I apologize.
I tried upgrading to iLife 6 (since this computer was purchased in December it came with iLife 5). Even using the identical menus I used from iDVD 5 in iDVD 6, encoding times are -at least- double in iDVD 6. To confirm this I deleted iLife 6 and reinstalled iLife 5 and encoded the same projects in iDVD 5 and the time difference really is a factor of 2! I tried the usual: repair permissions, installed the latest updates to iDVD 6 but the differenence remains with iDVD 6 taking twice as long to encode the same project.
Is this consistent with others' experiences?
Is there something I'm missing here?

Thanks John, the old discussion was helpful. It seems that others have found iDVD 6 to be a dog on non-Intel Macs as well and, in some cases, experienced even worse than a 100% slowdown if I read some of the posts correctly.
I hate to think that -this- is how Apple is claiming that Intel Macs are so much faster, by creating Universal Apps that run terribly on non-Intel Macs! My computer is a currently shipping model (I was stupid enough to believe the story that that Intel Pro machines wouldn't be released until 2007). If Apple software isn't optimized for it's own shipping hardware, which seems to be the case... sorry to digress
Anyway, I'll try to have some specific comparison results later after I reinstall 6. I checked and iDVD 5 was running consistently at 230-240% CPU usage with peaks of 270% so it is doing a good job of using the multiple processors (processor performance set to "automatic"). It'll be interesting to see what iDVD 6 does in that regard.

Corrupted innodb table crashing mysql instance how to recover table?

Hello,
Running a simple query against corrupted innodb table is crashing mysql instance .
table test.xyz got corrupt during crash and truncate table command was in progressing when mysql crash , now
running a simple select * query is also crashing db .
mysql> use test;
Database changed
mysql> select * from xyz;
ERROR 2013 (HY000): Lost connection to MySQL server during query
mysql>
mysql>
mysql> select * from xzy;
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
ERROR:
Can't connect to the server

Try to start mysql with innodb_force_recovery = 6
Or to try to restore by means of the tool:
MySql Recovery Toolbox and find out how you can use the corrupt MySQL recovery tool for damaged database restoration and easily repair known issues or already known problems, occurred in MySql files. This MySql repair utility offers many benefits
like:
Supports all MySql file versions and parses even very large documents on older PC computers;
Supports primary and external keys, tables, views, indexes and other objects;
Allows previewing recovered data in freeware mode so you can get results without purchasing MySql Recovery Toolbox
For more information: http://www.mysqlrecoverytoolbox.com/
As you can look for the answer here:
http://www.filerepairforum.com/forum/databases/databases-aa/mysql/197-corrupted-innodb-table-crashing-mysql-instance-how-to-recover-table

Media Encoder CS6 crash from Pr6 Queue button

Media Encoder CS6 crash from Pr6 Queue button, any suggestion on how to solve this?

http://blogs.adobe.com/kevinmonahan/2014/01/13/computer-shuts-down-with-premiere-pro-or-af ter-effects/

IDVD Corrupt encoding / glitches / crashing : SOLUTION

Similar Messages

Maybe you are looking for