MX:Module causing a bug??

Hi all,
I have an MXML application running without a problem. But,
when I change the MXML application to a module and call it from a
shall application, sometimes, when I click on a data grid or a
combo box, I get an error message as follows:
TypeError: Error #1009: Cannot access a property or method of
a null object reference.
at mx.managers::DragManager$/get isDragging()
at
mx.controls.listClasses::ListBase/mx.controls.listClasses:ListBase::dragScroll()
at Function/
http://adobe.com/AS3/2006/builtin::apply()
at ()
at
flash.utils::SetIntervalTimer/flash.utils:SetIntervalTimer::onTimer()
at flash.utils::Timer/flash.utils:Timer::_timerDispatch()
at flash.utils::Timer/flash.utils:Timer::tick()
What do you think?
Best regards

Yes the mistake was I was using the Flex 2.0 sdk. Thanks
Peter for pointing out.....Now my code works.
Thanks,
Vijay Karthik

Similar Messages

Using 2 memory modules causes kernel panic

In early 2009 I upgraded my memory from 512 to 2 GB, 2 modules of 1GB each. This past January (just shy of 2 years later) I got a kernel panic. I tested running with a single module, and one module caused panic, the other was fine. Both slots function with the good module. So I got two new matched replacement chips from OWC, put them in and got kernel panics during the boot process. Yesterday I spent testing memory configurations and found this:
1. chip 1 alone runs fine and passes all Rember memory tests in slot 1.
2. chip 2 alone runs fine in slot 1 and 2, passes all memory tests in slot 2.
3. chips 1 and 2 together, in either slot, cause kernel panics before the OS is loaded.
Has anyone seen this problem? Will it go away if I use top of the line (Apple) memory chips?
When the kernel panics started back in January, an AppleCare advanced advisor said he had the same problem and he had to remove one module to stop the kernel panics. Running on 1GB doesn't work for me because I tend to max out the memory and programs like Mail, Safari, Photoshop, etc. become unreponsive all together.
thanks -

I have spent more time on the phone with OWC about this than I care to remember. Their latest request is that I use an eraser to clean the metal contacts on the chips; if that fails, I get to send the chips back. Whether I get a refund or yet another set of replacement chips, I don't know. They are not experts on Apple machines, that is clear.

Multiple output modules cause render to fail?

Is anybody else having trouble with using multiple output modules in after effects? Let me elaborate: so I'm working on a 3d film, and my worflow is to simply work with the footage side by side in a single comp (we're at HD, so the comp size is 3840x1080). Very often, I need to fire off a quick render to show to the director. Most of the time, I just do the left eye by cropping to that 1920x1080 area in the output module. Other times I need to deliver both eyes, so instead of cropping to 1920x1080, I resize the frame in the output module to 1920x1080. Yea, we lose half of our horizontal resolution, but that's not such a big deal for us when just working on approvals.
Here's the thing: sometimes I like to export multiple variations of this at once (ie one output module for the left eye, one for the right eye, and another for the squished side-by-side left-right video). Whenever I try to output multiple modules with quicktime, it fails. Every time.
When it fails, I get two messages: the first (a warning) says "After Effects warning: last frame was written to one or more output modules, but not all! ( 26 :: 153 )"
The second message (an error) shows up once for each output module: "After Effects error: Rendering error while writing to file "C:\blahh blah blah\whereIputmyfiles\the_render.mov". An output module failed. The file may be damaged or corrupted. (-1610153464)." Once it fails, I cannot output to quicktime AT ALL (multiple output modules, or not) without restarting After Effects.
I tried outputting multiple modules as a PNG sequence... and that worked just fine (if "slow as hell" can ever be called "fine" .... but it worked! )
I tried outputting to the multiple formats I wanted with one output module per render item (rather than having one render item with multiple modules) as quicktime, and that worked just fine (of course... it takes N times as long though... for N number of outputs).
I am on Windows 7 64-bit... running After Effects CC 2014... I never had this trouble back when I was working on the CC version (the not 2014 cc version... that is too confusing...). However, I just went back and tried it with the older version, and it no longer works there either! What gives?
When outputting quicktime, I'm using the h.264 codec.
And before anybody suggests it, no I can't just use AME because that can't resize video (it forces you to keep the aspect ratio through letterboxing) or crop video.

>The most likely culprit is the h.264 Quicktime. It should have never been included as an option. It doesn't even work well in Quicktime Pro or in Final Cut...
I'll come to Apple's (partial) defense here:
Their H.264 codec was written and released at a time when it was difficult to imagine that mainstream computers would have as many CPUs as they do now, so it's somewhat understandable that the severe failures that this codec has with large numbers of threads occurs. Of course, we may all wish that Apple hadn't decided to end development on the QuickTime platform, since this has meant that bugs like this are likely to persist.
That said, this is why we increasingly recommend that people use other H.264 codecs and not use QuickTime for such things. See the H.264 options currently in Adobe Media Encoder.

Adobe Lighroom v5.2 - Develop Module Sync Settings Bug?

Hello Everyone,
I`m working on a batch of files (about 200) and I just noticed something weird going on in the Develop module.
Here is what I want to do and it doesn`t really work as it should:
Pick a value for "Highlights" for one photo
Do "Ctrl+A" to select all the other ones
Choose "Sync"
Select "Highlights" and like always, "Process Version"
Logically this should apply the same value for "Highlights" to all other photos but it`s buggy. It does it for several photos but not for all of them, which makes no sense.
Hardware information:
Adobe Lighroom v5.2 , Windows 7 64 bit installed on a "beast": 32GB of RAM, Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz, 3501 Mhz, 4 Core(s), 8 Logical Processor(s)
Has anyone noticed this bug?
P.S.
I chose "Highlights" just as an example because the same thing happens when I try to sync "Contrast", "Whites" or "Blacks".
Cheers:)
Nelu

Nelu Goia wrote:
like always, "Process Version"
I never sync "Process Version".
Why not? Lr does not properly convert process version upon sync (or at least it didn't used to), and if process versions are already the same, it does no good.
I recommend instead:
1. convert all photos to desired process version, if not already.
2. sync other develop settings (not process version).
For same reason, I never save process version in presets. YMMV...
Rob

Flex 4 Modules Creation Cycle bug ?

http://filip.nedyalkov.net/creationcycle/ - view source is enabled, download and see the traces
Ok so here is what happens in this application:
Some elements are created in the main application and also a module is loaded. As soon as it is ready the button in the main app goes visible. When you click it the module is added to the main application.
There is where it gets weird. If the module loader is not added to the main application before the module is ready, everything I've set into the module gets created kinda randomly. For example if I have a button in the module, it should fire button created and then module created, but here it doesn't sometimes. Check out the application I've provided to see what I mean.
I think that it shouldn't matter if the module loader is added or not, and the module should fire the creation complete events in the normal order, from bottom to top (top is the module itself).
So I hope someone familiar with modules life cycle behaviour could say if what I see is a bug or not and how it can be fixed. Of course I could add the module loader before the module is loaded but make the moduleloader visible=false, and when I need it visible=true, but that's not the point here.
Thanks

Go to this thread: http://forums.adobe.com/thread/764956 - this is with better example.

Can a broken Display Switch module cause my screen to not turn on or be recognized?

Hi All,
I have recently been having some issues with my LCD screen in my HP Pavillion dv9700. Ever since I replaced the left hinge on my notebook, I have had to fiddle with my screen by closing and opening it during booting to get it to turn on. This only happened when booting into linux. When booting into vista, the screen would turn on without a problem. This morning I was so fed up with this, that I thought maybe some switch was not getting pressed to tell the notebook that the lid was opened. After looking at all the cables and putting everything back together, my screen now no longer turns on no matter how much I open and close the lid. It wont even turn on in vista. I am however able to connect a vga cable to my notebook and use an external monitor without any problems. I opened up the nvidia control panel in both windows and linux and it does not recognize my notebook monitor, only the external monitor shows up. Could this be caused by a broken display switch module? How can I diagnose this problem? Is there a way to bypass the display switch module by jumping two wires?
Any ideas are appreciated,
Thanks in advance
OS: Latest version of Ubuntu Linux 11.10 dual booting with Windows Vista
Problem: LCD Monitor not turning on / being recognized
possible cause: LCD Display Switch Module

Update:
I just figured out that it cant be my display switch module because when i close the lid to my notebook, the external monitor shuts off and the computer goes into standby mode. I now think this might be an issue with the ribbon cable. Is there anything else which might be causing this problem which I am overlooking?

Switching to Develop module causes crash in Lightroom 4.2

I recently updated Lighroom 4.1 to 4.2 successfuly, but now any time I go into the Develop module, Lightroom pauses, then crashes and forces me to quite the program. Is this a bug than needs to be ironed out, or is there something else going on?

That shouldn't happen. You probably have a corrupted file in the camera raw cache. Go to Lightroom's preferences->File handling and hit "purge cache".

Pt880 restarts caused by bug check

lately or for the last few days my system will crash due to a bug check?
1. What are the main reasons why this happens?
2. would a weak power supply cause this?
3. Also I was using 512 megs of infineon memory without any problems, but just lately I added another 512 stick of the same ram in order to get dual channel.
4. Also right now I'm using a power supply with these specs, (as my enermax in my sig was damaged when it arrived) should be here in a day or two.
3.3v 28 amps/5v 40amps/12v 18 amps
I adjusted my ram timings from cas 3, 4,4,9 to cas 2.5,3,3,8, and upped ram voltage to 2.7. I'll prolly have to wait till tomorrow for another blue screen, as it only happens once a day, usually when using winamp or media player, but once it crashed when i went to use my web browser.
I formatted to try and resolve issue but it still remains.
I can't see it being the ram, as it is on the supported list for my mobo, but if it is the ram i'm hoping different timings might help or that it is in fact the power supply.
Any suggestions?

Quote
Originally posted by Billaa
I'm getting tired of saying this but my PSU won't be here till later today.
I like the 865 mainboard and they did have one in stock but not sure which one. I'm also quite happy with this board, but I don't want to go through the hassle of borrowing my friends northwood again.
I should take the bios chip off this one and put it on new one. (joking)
Any how i'll know soon enough whether it's psu or mobo. Cause it's not ram cause right now i've got it running in my K7 board at 2- 2- 2- 5 dual channel and it's stable as can be. I guess that's good timing? For Infineon
Hi Billaa,
There is no rush........mistakes might be made........
Yeah, I like the BIOS switch.......
Infineon, is under-rated...... it is good budget mem But, I did have trouble with PT880 and Infineon
We will see how everything goes.........
In the meantime........ have browse here....... Red Rockets....... MSI F@H Team
I think you would go past me very quickly...........
Will await reply
Del

MBP Retina and Loginox1.0.6B6 on Mac OS 10.7.4 cause Icon bug

Hello,
just want to inform you. I had this icon bug and apple told be to reinstall the new MBP Retina. I have reinstalled and the bug come again. I have informed the Loginox Support team aswell. If you restore back to the default image in Loginox the bug is gone. All Icons such as forward and backward or fullscreen will be deformed. Take a look at the screen shots.
Here the Icon bug:
Before:
After:

Hi Spillerz,
the new verison of Loginox should be working. I donot use it anymore after the issue.
Important is a reboot after changing to the default, and all should work.
Mad73

Fm modulator causing screen discoloration

I purchased a 20 gig Ipod Photo less than 2 weeks ago. I have tried 2 types of fm modulators in my car, a Belkin that plugs into the headphone jack, and a DLO Transpod docking type.
The problem I have is that when I used either transmitter, it would cause a straight vertical line down the center of my screen. The left side becomes very dark and the right side of the screen changes colors, but stays a bit brighter then the left side.
Once I unplug it from the transmitter, it usually takes less than 10 minutes for the screen to come back to normal.
Any Ideas?? Bad Ipod??

Try doing a SMC reset, it may need to be done 2-3 times.
SMC RESET
Shut down the computer.
Unplug the computer's power cord and all peripherals.
Press and hold the power button for 5 seconds.
Release the power button.
Attach the computers power cable.
Press the power button to turn on the computer.
PRAM RESET
Shut down the computer.
Locate the following keys on the keyboard: Command, Option, P, and R. You will need to hold these keys down simultaneously in step 4.
Turn on the computer.
Press and hold the Command-Option-P-R keys. You must press this key combination before the gray screen appears.
Hold the keys down until the computer restarts and you hear the startup sound for the second time.
Release the keys.

Datagrid column in module causing memory leak

Hi All
I'm having trouble with a DataGrid column preventing a module from being release properly. I can't imagine this is the intended behaviour.
Using this simple test case, a WindowedApplication and an mx:Module I wonder if anyone else can reproduce this problem. The issue goes away if you simply comment out the GridColumn Instance.
Can anyone offer any advice?
Many thanks
James
DataGridTest.mxml
<?xml version="1.0" encoding="utf-8"?>
<s:WindowedApplication xmlns:fx="http://ns.adobe.com/mxml/2009"
                       xmlns:s="library://ns.adobe.com/flex/spark"
                       xmlns:mx="library://ns.adobe.com/flex/mx">
    <fx:Script>
        <![CDATA[
            import mx.core.IVisualElement;
            import mx.events.ModuleEvent;
            import mx.modules.IModuleInfo;
            import mx.modules.ModuleManager;
            private var assetModule:IModuleInfo;
            protected function load_clickHandler(event:MouseEvent):void
                assetModule = ModuleManager.getModule('DataGridTestModule.swf');
                assetModule.addEventListener("ready", getModuleInstance);
                assetModule.load();
            public function getModuleInstance(event:ModuleEvent):void
                var sm:DisplayObject = assetModule.factory.create() as DisplayObject;
                sm.addEventListener("close", closeModule);
                contentHolder.addElement(sm as IVisualElement);
            private function closeModule(event:Event):void
                event.target.removeEventListener("close", closeModule);
                contentHolder.removeElement(event.target as IVisualElement);
                assetModule.unload();
                assetModule = null;
        ]]>
    </fx:Script>
    <s:VGroup width="100%" height="100%">
        <s:HGroup >
            <s:Button id="load" label="Load" click="load_clickHandler(event)"/>
        </s:HGroup>
        <s:BorderContainer id="contentHolder" width="100%" height="100%"/>
    </s:VGroup>
</s:WindowedApplication>
DataGridTestModule.mxml
<?xml version="1.0" encoding="utf-8"?>
<mx:Module xmlns:fx="http://ns.adobe.com/mxml/2009"
                      xmlns:s="library://ns.adobe.com/flex/spark"
                      xmlns:mx="library://ns.adobe.com/flex/mx"
                      layout="absolute" xmlns:components="components.*">
    <fx:Script>
        <![CDATA[
            protected function close_clickHandler(event:MouseEvent):void
                dispatchEvent(new Event('close', true, false))
        ]]>
    </fx:Script>
    <s:BorderContainer id="contacts"
                       width="100%" height="100%"
                       backgroundAlpha="0"
                       borderVisible="false">
        <s:layout>
            <s:VerticalLayout/>
        </s:layout>
        <s:Button id="close" label="Close" click="close_clickHandler(event)"/>
        <s:DataGrid id="queries" >
            <s:columns>
                <s:ArrayList>
                    <s:GridColumn/> 
                </s:ArrayList>
            </s:columns>
        </s:DataGrid>
    </s:BorderContainer>
</mx:Module>

OK, So I've done some more testing. Creating the GridColumn in AS during the creationComplete event is a slight improvement. It seems to allow the DataGrid and the Module be GC'd, but it's still leaking memory somewhere. I just can't get my head around the Profiler. Also, it's going to be a massive headache if we have to rewrite our application to create all the GridColumns in AS. Surely this shouldn't be necessary?
New test case below:
DataGridTest.mxml
<?xml version="1.0" encoding="utf-8"?>
<s:WindowedApplication xmlns:fx="http://ns.adobe.com/mxml/2009"
                       xmlns:s="library://ns.adobe.com/flex/spark"
                       xmlns:mx="library://ns.adobe.com/flex/mx">
    <fx:Script>
        <![CDATA[
            import mx.collections.ArrayList;
            import mx.core.IVisualElement;
            import mx.events.ModuleEvent;
            import mx.modules.IModuleInfo;
            import mx.modules.ModuleManager;
            import spark.components.gridClasses.GridColumn;
            private var assetModule:IModuleInfo;
            private var sm:DisplayObject;
            protected function load_clickHandler(event:MouseEvent):void
                assetModule = ModuleManager.getModule('DataGridTestModule.swf');
                assetModule.addEventListener("ready", getModuleInstance);
                assetModule.load();
            public function getModuleInstance(event:ModuleEvent):void
                sm = assetModule.factory.create() as DisplayObject;
                sm.addEventListener("close", closeModule);
                contentHolder.addElement(sm as IVisualElement);
            private function closeModule(event:Event):void
                event.target.removeEventListener("close", closeModule);
                contentHolder.removeElement(event.target as IVisualElement);
                assetModule.unload();
                assetModule = null;
        ]]>
    </fx:Script>
    <s:VGroup width="100%" height="100%">
        <s:HGroup >
            <s:Button id="load" label="Load" click="load_clickHandler(event)"/>
        </s:HGroup>
        <s:BorderContainer id="contentHolder" width="100%" height="100%"/>
    </s:VGroup>
</s:WindowedApplication>
DataGridTestModule.mxml
<?xml version="1.0" encoding="utf-8"?>
<mx:Module xmlns:fx="http://ns.adobe.com/mxml/2009"
                      xmlns:s="library://ns.adobe.com/flex/spark"
                      xmlns:mx="library://ns.adobe.com/flex/mx"
                      creationComplete="module1_creationCompleteHandler(event)"
                      layout="absolute" xmlns:components="components.*">
    <fx:Script>
        <![CDATA[
            import flash.utils.setTimeout;
            import mx.collections.ArrayList;
            import mx.events.FlexEvent;
            import spark.components.gridClasses.GridColumn;
             [Bindable]
            private var _col:ArrayList = new ArrayList();
            protected function close_clickHandler(event:MouseEvent):void
                dispatchEvent(new Event('close', true, false))
            protected function module1_creationCompleteHandler(event:FlexEvent):void
                var gc:GridColumn = new GridColumn();
                gc.headerText = 'Test Column';
                _col.addItem(gc);
        ]]>
    </fx:Script>
    <s:BorderContainer width="100%" height="100%">
        <s:layout>
            <s:VerticalLayout/>
        </s:layout>
        <s:Button id="close" label="Close" click="close_clickHandler(event)"/>
        <s:DataGrid id="queries" columns="{_col}"/>
    </s:BorderContainer>
</mx:Module>

Pcimxi module causing system panic

We have an UltraSparc Solaris 9 system which is panicing relatively often. The panic seems to be coming from a NULL pointer being dereferenced in the pcimxi module.
Sep 20 12:42:41 p02rfu01 panic[cpu0]/thread=2a100045d40:
Sep 20 12:42:41 p02rfu01 unix: [ID 340138 kern.notice] BAD TRAP: type=31 rp=2a100045740 addr=8 mmu_fsr=0 occurred in module "pcimxi" due to a NULL pointer dereference
We are running version 2.0.0 of the NICpcimxi package. I don't see any newer versions or patches available. Has anybody else experienced this problem? If so, any suggestions. Thanks!

I've gotten some more info from our engineers regarding the problem as well. Evidently the system only panics when they are talking to the Spectrum Analyzer via PCI attached GPIB. You would think it is a GPIB problem, but the panic is from the pcimxi module. It doesn't always crash when connecting to the SA, however it can be frequent. The NIpcigpib software is 2.3, NICpcimxi is 2.0.0, and NICvisa is 3.1. The crash string is as follows:
Sep 27 10:04:23 p02rfu01 ^Mpanic[cpu0]/thread=2a100045d40:
Sep 27 10:04:23 p02rfu01 unix: [ID 340138 kern.notice] BAD TRAP: type=31 rp=2a100045740 addr=8 mmu_fsr=0 occurred in module "pcimxi" due to a NULL pointer dereference
Sep 27 10:04:23 p02rfu01 unix: [ID 100000 kern.notice]
Sep 27 10:04:24 p02rfu01 unix: [ID 839527 kern.notice] sched:
Sep 27 10:04:24 p02rfu01 unix: [ID 520581 kern.notice] trap type = 0x31
Sep 27 10:04:24 p02rfu01 unix: [ID 381800 kern.notice] addr=0x8
Sep 27 10:04:24 p02rfu01 unix: [ID 101969 kern.notice] pid=0, pc=0x78154524, sp=0x2a100044fe1, tstate=0x4400001604, context=0xc6
Sep 27 10:04:24 p02rfu01 unix: [ID 743441 kern.notice] g1-g7: 780292d8, 1c00, bb, fffffffffffffffe, 3000027e590, 10, 2a100045d40
Sep 27 10:04:24 p02rfu01 unix: [ID 100000 kern.notice]
Sep 27 10:04:24 p02rfu01 genunix: [ID 723222 kern.notice] 000002a100045470 unix:die+80 (31, 2a100045740, 8, 0, 7802bc27, 30004bc0c0b)
Sep 27 10:04:24 p02rfu01 genunix: [ID 179002 kern.notice] %l0-3: 0000000000000000 00000000014135f0 000002a100045740 000002a100045638
Sep 27 10:04:24 p02rfu01 %l4-7: 0000000000000031 000003000000e898 0000000000000000 0000000001111824
Sep 27 10:04:25 p02rfu01 genunix: [ID 723222 kern.notice] 000002a100045550 unix:trap+874 (2a100045740, 0, 10000, 10200, 0, 1)
Sep 27 10:04:25 p02rfu01 genunix: [ID 179002 kern.notice] %l0-3: 0000000000000001 0000000000000000 0000000001437b28 0000000000000031
Sep 27 10:04:25 p02rfu01 %l4-7: 0000000000000005 0000000000000001 0000000000000000 0000000000000000
Sep 27 10:04:25 p02rfu01 genunix: [ID 723222 kern.notice] 000002a100045690 unix:ktl0+48 (fffffffffffffffe, 3000027e590, 101, 7802bc18, 2a10072ae9c, 2a10072ae98)Sep 27 10:04:25 p02rfu01 genunix: [ID 179002 kern.notice] %l0-3: 0000000000000005 0000000000001400 0000004400001604 000000000102bf54
Sep 27 10:04:25 p02rfu01 %l4-7: 000000007802bc18 fffffffffffffffe 0000000000000006 000002a100045740
Sep 27 10:04:26 p02rfu01 genunix: [ID 723222 kern.notice] 000002a1000457e0 pcimxi:HandleVIRQLevel+78 (0, ffffff50, 1, 7802bc18, ffffffffffffffff, 2a10072b0d4)
Sep 27 10:04:26 p02rfu01 genunix: [ID 179002 kern.notice] %l0-3: 0000000000000000 0000000000000000 0000000000000000 0000030004e1a000
Sep 27 10:04:26 p02rfu01 %l4-7: 000003000000b170 000003000000b198 000003000000b1c0 00000300038c4c88
Sep 27 10:04:26 p02rfu01 genunix: [ID 723222 kern.notice] 000002a1000458f0 pcimxi:HandleVSID+140 (0, ffff2900, 20, 0, 100c4f4, 0)
Sep 27 10:04:26 p02rfu01 genunix: [ID 179002 kern.notice] %l0-3: 0000000000000000 0000000000000280 0000000000000000 0000000001400428
Sep 27 10:04:26 p02rfu01 %l4-7: 0000000001400000 0000000000000016 00000000014007e8 0000030003c231f8
Sep 27 10:04:27 p02rfu01 genunix: [ID 723222 kern.notice] 000002a1000459c0 pcimxi:handleEvent+d0 (ffff2900, 2a100045d40, 20, 0, 29, 0)
Sep 27 10:04:27 p02rfu01 genunix: [ID 179002 kern.notice] %l0-3: 0000000078029
800 0000000078154290 0000000000000000 00000000ffff2900
Sep 27 10:04:27 p02rfu01 %l4-7: 00000000000000c2 00000000000019c8 00000000780281e8 0000000000000008
Sep 27 10:04:27 p02rfu01 genunix: [ID 723222 kern.notice] 000002a100045a80 pcimxi:vxi_softintr+74 (30004a01cf8, 85d, 1400000, 2a100045d40, 10ba0, 78142d38)
Sep 27 10:04:27 p02rfu01 genunix: [ID 179002 kern.notice] %l0-3: 00000000ffff2900 0000030004a01cf8 0000000000000001 0000000000000001
Sep 27 10:04:27 p02rfu01 %l4-7: 0000030000265ae8 00000000780281e8 00000000014d2000 00000000014d2000
I can get you a crash dump if it will help any (we have lots of them). Thanks.
Randy

Slideshow module causes system to crash

Hi,
I have a strange problem with Lightroom on Win XP SP3. When using the Slideshow module, I can typically play the slideshow for a couple of shots and then the whole system crashes. Typically so that the screen just goes blank and the computer reboots. This occures in two different computers, and the only common thing in these are Windows XP SP3 and Matrox G550 (latest stable drivers). The error also occures with both LR 2.1 and 1.3. I haven't been able to reproduce this with any other applications on these computers.
Has anyone else seen this? Have you been able to fix it? The way the computer crashes would indicate that the problem is in a low level driver, but there must be something in Lightroom that trigggers this.
Regards,
Mike

Thanks for replying,
> Possible solution YES.
Well, not in my case. I can reproduce this reliably even if I render 1:1 previews for all photos right before going into Slideshow.
>Can you post a crash report from the control\admistrative tools\event viewer logs for that particular crash.
No. The system just dies and reboots. Nothig is written to the event log, nor are there any crashdumps generated. And this is the same on both computers.
> How much memory do you have?
4 GB on both. Tried both with and without the /3GB switch, same problem regardless of this setting.
(Btw, system one is Asus MB, Pentium 4 HT, Matrox G550 AGP, single DVI monitor. System 2 is Intel MB, Core 2 Duo, Matrox G550 on PCIe, double DVI+VGA monitors.)
Mike

LR 3 Web Module Cell Number Bug ?

Hi, folks, when in the web module and creating a basic web page with 3 digit numbered cells these numbers are obscured with photos in portrait orientation. No good for a client who is looking at portrait shots and wants to reference a photograph number.
I use a file name for now but this should be corrected asap unless I am doing something wrong here.
Cheers Mark

Same thing occurs in Library Grid view when cells are in Compact mode. It's been this way since January 2006 and I don't see it changing any time soon. Also, using the cell number for any form of selection is fraught with dangers is in no way linked tot he actual image. Delete and image and every thing moves by one. Best solution is to use the file name.

FxFactory Plugins Causing Audio Bug

Hiya,
So...I seem to be dealing with a bug within FCP when Noise Industries FxFactory plugins are installed. I'm confident that I've narrowed it down to this plugin suite.
Basically, when FxFactory is installed and Final Cut is running, if you affect any of the audio meters in the Audio Mixer window, the video lags to a stuttering stop and no level information is imparted to the tracks.
I can level the audio when the playhead is at a standstill and not playing, but one cannot mix live.
I'm curious if anyone is suffering the same issue, or knows of any patch, as we need to be able to mix live and utilize these plugins if possible.
Thank you for any and all replies!
Cheers,
asher.

For the benefit of anyone watching this thread (or simply stumbling upon it during a search) the issue was discovered and fixed in FxFactory 2.0.7. If you experience this problem, please download and install a fresh copy of FxFactory from our website:
http://www.noiseindustries.com/fxfactory/download
Regards,
Gabe
Noise Industries, LLC

MX:Module causing a bug??

Similar Messages

Maybe you are looking for