Odd problem adjusting scale of rotoshape layer

Using Mocha I've rotoscoped my actor out of some footage in order to composite him on top of something else.
After pasting the shape data to his layer in AE, I'm happy with the roto but now I need to adjust the position and scale. Changing the position parameter in layer properties works fine, but when I adjust scale, the rotoshape starts to go haywire. As the layer size increases, the mask around the rotoshape gets left behind, despite being on the same layer. Then if I scrub forward in time, the position of the roto mask has gone back to its original place too. There are no keyframes on it, the only thing I have applied is the Mocha shape data. Am I doing something wrong, or is this a glitch?
Cheers.

It works as it should - all mocha data is treated as absolute based on the size of the mocha project and then relative to the AE comp, not the layer. You cannot simply scale later. Pre-compose, then scale or insert the mocha shapes as masks...
Mylenium

Similar Messages

Odd problems with reading DVD media [concluded]

There is an odd problem I've encountered...(I'm not sure if its a bug with Arch Linux or Linux in general).
Firstly, the details:
* I've updated the systems (using "extra", "current", and "community" respositories). So its the current one (0.80 "Voodoo"). I'm NOT using "Unstable" respository.
* I've already added the user to the "optical" and "storage" groups. So there's no problems in relations to permissions.
* My fstab entries for the CD and DVD drives are default (I didn't touch them)...That is, "iso9660" and "udf" respectively.
* My desktop environment is KDE 3.5.5...And I have changed the behaviour of the desktop icons such that DVD media, CD media, and USB devices will have an icon pop-up as soon as you plug them in.
* I have "hal" loaded in the DAEMONS of /etc/rc.conf
* I'm using 4 different Linux systems with the following DVD burners.
=> Pioneer DVR-108
=> Sony DW-Q120A
=> Hitachi-LG GCC-4240N (DVD-ROM/CD-burner combo)
* There are three Sempron 2800+ (Socket 754, 1.6Ghz) boxes and the last one is on an IBM R40 ThinkPad, and I know you can't read DVD-R media on that. But it should be able to read DVD+R media without issue.
* Two of the Semprons are running Arch, as well as the ThinkPad. The final Sempron box is running Ubuntu 6.06.1
* When I installed K3b I did: pacman -S k3b dvd+rw-tools
* All the DVD media is Verbatim DataLifePlus ones.
Here's what I've done...
I've burnt two DVD media (they're just video files from last year's Blender 2006 conference thing, so its legal stuff).
One is a DVD+R and the other is DVD-R media. Both were done on a Windows 2000 Pro SP4 box using Nero 6.6.1.4
What's the problem?
Well, KDE in the Arch Linux boxes doesn't recognise the media!...There is no DVD icon that automatically pops up on any of the Arch Linux boxes!
When I run dmesg on the Arch boxes, the only relevant info I get is:
ISO 9660 Extensions: Microsoft Joliet Level 3
ISOFS: changing to secondary root
Now if I re-insert these DVD media onto an Ubuntu 6.06.1 LTS box...The DVD+R works perfectly! While the DVD-R does not.
When I run dmesg on this box, I get the following:
[17179654.808000] hdc: cdrom_decode_status: status=0x51 { DriveReady SeekComplet e Error }
[17179654.808000] hdc: cdrom_decode_status: error=0x40 { LastFailedSense=0x04 }
[17179654.808000] ide: failed opcode was: unknown
[17179654.808000] hdc: cdrom_decode_status: status=0x51 { DriveReady SeekComplet e Error }
[17179654.808000] hdc: cdrom_decode_status: error=0x40 { LastFailedSense=0x04 }
[17179654.808000] ide: failed opcode was: unknown
[17179654.808000] hdc: cdrom_decode_status: status=0x51 { DriveReady SeekComplet e Error }
[17179654.808000] hdc: cdrom_decode_status: error=0x40 { LastFailedSense=0x04 }
[17179654.808000] ide: failed opcode was: unknown
[17179654.812000] hdc: cdrom_decode_status: status=0x51 { DriveReady SeekComplet e Error }
[17179654.812000] hdc: cdrom_decode_status: error=0x40 { LastFailedSense=0x04 }
[17179654.812000] ide: failed opcode was: unknown
[17179654.812000] hdc: DMA disabled
[17179654.812000] hdc: ide_intr: huh? expected NULL handler on exit
[17179654.860000] hdc: ATAPI reset complete
[17179655.364000] ISO 9660 Extensions: Microsoft Joliet Level 3
[17179655.412000] ISOFS: changing to secondary root
[17179725.140000] Unable to identify CD-ROM format.
[17179729.348000] Unable to identify CD-ROM format.
[17181395.032000] ISO 9660 Extensions: Microsoft Joliet Level 3
[17181395.032000] ISOFS: changing to secondary root
If I re-burn the data onto a DVD+RW, Arch and Ubuntu immediately sees it, and KDE (or Gnome in Ubuntu), will have a DVD icon popping up! I can view the video clips without issue!
Now here's the really odd part...
When I load up K3b on either Arch OR Ubuntu, they recognise all DVD media! (As in, they can read the media disc information!)...Tools => DiskInfo
If I click on the PIONEER - DVD-RW DVR-108 on the tree menu on the left side in K3b, (to view the contents of the DVD-R or DVD+R media), it can't read and pops up an error message informing about a read problem. It suggests I try dmesg|tail to see what's wrong.
When I do that, I get...
# dmesg|tail
grow_buffers: requested out-of-range block 18446744073708569376 for device hdc
UDF-fs: No partition found (1)
grow_buffers: requested out-of-range block 18446744073708569376 for device hdc
UDF-fs: No partition found (1)
grow_buffers: requested out-of-range block 18446744073708569376 for device hdc
UDF-fs: No partition found (1)
grow_buffers: requested out-of-range block 18446744073708569376 for device hdc
UDF-fs: No partition found (1)
grow_buffers: requested out-of-range block 18446744073708569376 for device hdc
UDF-fs: No partition found (1)
I repeat the same procedure on DVD+RW, and it works perfectly!
Should I use another burning application instead of Nero on the Windows box?
Could it be the way I burn things?
(Some DVD+R and DVD-R are burnt with multisession while others aren't.)
Has anyone else experienced similar issues?
What are your "workarounds" or fixes?

It *should* work...But they don't.
I tried this...
mount -t auto /dev/dvd /mnt/dvd
I get this...
mount: block device /dev/dvd is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/dvd,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
I then do dmesg|tail
grow_buffers: requested out-of-range block 18446744073708569376 for device hdc
UDF-fs: No partition found (1)
If I try this...
mount -t iso9660 /dev/dvd /mnt/dvd
I get this...
mount: block device /dev/dvd is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/dvd,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
I then do dmesg|tail
Unable to identify CD-ROM format.
If I stick in a DVD-R that is burnt in one go without multisession, I get this in the dmesg
UDF-fs: Partition marked readonly; forcing readonly mount
UDF-fs INFO UDF 0.9.8.1 (2004/29/09) Mounting volume 'SW', timestamp 2006/11/07 19:37 (1000)
It reads this disc perfectly and KDE pops up a DVD icon.
I'm scratching my head as I'm not sure what is the problem.
Could it be hal or the way the DVD media was formatted?

An odd problem when error handling

hi experts
I encountered a very odd problem when trying to show up an error message... and hope someone can help me out.
I defined a standard action in the view, and wrote some lines of code to check the input data in the predefined methodWDDOBEFOREACTIONwhich will call a method from component controller, and that method will call message_mananger->report_t100_message to show up an E type message if any error happened. But the problem is the program does not stop there but go into the action handler(ONACTIONACT_XXX).
I think it should actually stop and show up the message rather than get into the action handler because of the action is standar...
can anyone help?
many tkx

hi,
i went through your code.....the code is fine but as you told that it goes to the exception handler after coming to the message part ...this is because you are using
CALL METHOD LO_MESSAGE_MANAGER->REPORT_T100_MESSAGE
EXPORTING
    MSGID                     =
    MSGNO                     =
    MSGTY                     =
   P1                        =
   P2                        =
   P3                        =
   P4                        =
   MSG_USER_DATA             =
   IS_PERMANENT              = ABAP_FALSE
   SCOPE_PERMANENT_MSG       = CO_MSG_SCOPE_CONTROLLER
   VIEW                      =
   SHOW_AS_POPUP             =
   CONTROLLER_PERMANENT_MSG =
   MSG_INDEX                 =
   CANCEL_NAVIGATION         =
   ENABLE_MESSAGE_NAVIGATION =
RECEIVING
    MESSAGE_ID                =
this function will simply report that message but will not hold the control to the same screen..
so use
CALL METHOD LO_MESSAGE_MANAGER->REPORT_FATAL_ERROR_MESSAGE......
and tell me whether it solved the problem or not....
@ sarbjeet i think that Raise_T100_error is an obselete function...rite?
thanks and regards,
sahai.s

Problem adjusting dates in PSE 12

I'm having problems adjusting the Date/time. Moments after I've made the change, the photos reappear with the date unchanged. What's going on?

I have figured out a "work around". If the wrong date is less than 60 years different than the correct date, use the "up" and "down" arrows to change the year. If you try to delete the wrong year and type the correct year it will not work. In fact, the date will become even "more" wrong. You must use the arrows. If the wrong date is more than 60 years different than the correct date, you'll have to use the arrows to adjust the date as many times as necessary as long as you stay under the 60 year change per adjustment. So, I had one date of 1231, that I had to adjust about 15 times until I got it to 1979.

Premier 7 Odd problem

This may be something someone out there can clue me in on !!! I am capturing from a non digital cam and using another program to capture and then getting the clips from that program into Premier , this part is no problem as long as I save to my PC as soon as I save to my external and try importing to premier , premier tells me it does not recognize the file why is that?? how can I change that?/

Good Day Hunt , happy thanksgiving to all!! I have tried the Gspot and the same codec comes up for both places of storage on my PC it comes as DIB(_RGB And On The Maxtor stirage device it is the same DIB(_RGB also states no codec needed Do Not know waht it all means but I go back to what You said earlier that the external HD is The problem , Is there an external that can handle this or all the same ?? John
From The Home Of JC & M
Date: Thu, 8 Oct 2009 18:50:15 -0600
From: [email protected]
To: [email protected]
Subject: Premier 7 Odd problem
OK, you have used the Corel program, so you have a file to test with. Get http://www.headbands.com/gspot and install it. When you open it, give it time to survey your system for properly installed CODEC's. Then, drag one of the Corel files to it, and read the details.
You might be able to get this info right from Corel, though probably not in great detail.
Here's a look at the G-Spot GUI.
http://forums.adobe.com/servlet/JiveServlet/showImage/12983/G-Spot_Screen_02.jpg
Good luck,
Hunt
>

G4 Sawtooth odd problems

I have an older G4 Sawtooth. It has an upgraded processor at 1ghz and 1.3 gig ram. I've upgraded the hard drives with a 60 G and a 120 G drives. There is also a pci ethernet card installed.
I moved recently, and the tower stayed in a box for a few months. I have it up and running, but am now experiencing an odd problem. The drop down menus in all programs other than finder, do not work. I've tried disk utility and Techtool Pro. Disk utility looses contact with the 60G HD I have the operating system on. I didn't have much yet on the 120 G, so I tried to install in that, and there were 'errors.' Techtool will only try to boot, but will never actually load.
I haven't tried resetting PRAM, but I will try. Any other ideas. Help
Thanks

Well, it still has the original battery in the computer, so i will change it today. I don't believe that is the problem though, or only problem.
I installed the OS the other HD and it is working fine. I then tried to run Mac disc utility on the main drive and got the following.
Missing thread record (id = 4871)
Checking multi-linked files.
Checking Catalog hierarchy.
Invalid volume directory count
(It should be 48514 instead of 48515)
Invalid volume file count
(It should be 193965 instead of 193968)
Checking volume bitmap.
Checking volume information.
Repairing volume.
Missing directory record (id = 4871)
The volume Mac HD could not be repaired.
Error: The underlying task reported failure on exit (-9972)
My Techtool Pro CD doesn't seem to want to load. Any ideas?
I didn't remove all the video card, but I did make sure all the connections were secure inside.
Thank you

An odd problem importing footage...ideas please!!

I'm having an odd problem with iMovie that has me stumped so far. I'm currently using a borrowed DVcamcorder to import my footage. So far I can only import footage that was taped using that exact camcorder. I have other footage, (also miniDV format) that was created on a different camera, and it won't import properly. It comes out very jumpy, almost as if the frame rate is off or it's not scanning the fields properly, playing only every other one. The camera also gives me a "clean heads" message that only appears when I try to use the "foreign" video. The heads don't need cleaning, and I've checked the frame rate. Does anyone have any ideas? I'm lost so far!!
I'm using an iMac G5, with iMovie HD.
Thank-you!

Welcome to iMovie Discussions!
It may be that the "foreign" tape (..i.e; not recorded in that camcorder you're using..) was recorded at LP (Long Play) - a slow tape speed - or even slower than LP.
This makes recordings on extremely narrow video tracks (..because the tape hardly moves forwards while the spinning recording head turns round..) which may not quite co-incide with the exact head position of another camcorder ..i.e; the tolerance is too fine to match properly.
Most manufacturers mention this ..in very obscure language.. in their camcorder manuals, saying that LP tapes from other camcorders might not play properly, or tapes recorded in LP mode might not play in other camcorders.
Most (all?) Sony DV camcorders will play back footage recorded faster than normal, on 'professional' 'DVCAM' recorders. These tapes move faster through the camera than ordinary DV, so they produce a wider track which is less likely to cause signal 'drop-out' failure. I don't know if other makes of camcorder can play back DVCAM material.
If the "foreign" tapes were shot at DVCAM speed (..e.g; on a Sony PDX10 camcorder, or similar), then although they should play back in other, normal 'domestic' Sony cams, they might not play back in another make of camcorder. Could these be DVCAM tapes?
Finally, it might also be that the "foreign" tape really is a Foreign tape: i.e; the recording was made to a different standard. So if it's an American-recorded (NTSC) tape and it's played in a UK (PAL TV system) camcorder, the frame-rate will be wrong, the number of scan-lines will be wrong, the colour info will be wrong, etc. [..But as you mention "fields", you probably know enough not to have made that mistake.]
NOTE: Ooops, sorry, Karl: we must have both been typing at the same time ..didn't mean to step on your toes.

Odd Problem With MDT 2012 Deployment

Disclaimer: I'm an MDT n00b and barely know how to do anything other than the basics.
The odd problem: Computers that I deploy Windows 7 to using MDT will NOT (after deployement is complete) pass credentials to our proxy (Smoothwall - NTLM Authentication) and cannot not access the internet. It doesn't matter the flavor of Windows
7: 32bit/64bit or Pro/Ultimate same result. Does this on an unpatched machine with only IE8 or a fully patched machine with IE9. I've diddled all the security and connection settings in IE that I know to diddle with the same result. And it's not
just an IE problem. It does it with Firefox, too. Now getting to intranet sites is no problem... this is strictly an internet proxy authentication issue.
Now... why am I asking the MDT forum about this? Because I can load Windows 7 the old fashioned way with a DVD made from the same ISO that I used when setting up MDT and it works fine.
So MDT must be doing something differently when deploying Win 7. As a side note, when I deploy Windows 8 using MDT we do not have this issue. Maybe Microsoft just wants me to upgrade? :)
Everything else about the computer seems quite normal. No undetected drivers. Windows activates normally. I can join the domain either during or after the process. Install applications automatically. I mean the whole MDT process
seems to be working great otherwise.
Help? Please?

Yes, I found a way to undo this in my environment without needing to reimage all of the computers.
There are two problems:
1. GP items in the Administrative Template were modified.
2. GP items in the Security section were modified.
Problem 1
To address problem #1 delete the folder "%SystemRoot%\System32\GroupPolicy":
rd /s /q "%SystemRoot%\System32\GroupPolicy"
Problem 2
To address problem #2, it gets a little more complicated since there is no easy way to "revert" to the default in Win7. The only workaround is to import new settings. To accomplish this, I ran the following from a FRESHLY installed non-domain
joined computer that did not have the local GPO pack applied:
secedit /export /cfg secConf.inf
Then on the "bad" system that had the local GPO applied, I ran:
secedit /configure /db secedit.sdb /cfg secConf.inf /overwrite /quiet
I also found that I needed to delete the following keys since they did not exist on my safe/good image:
reg delete "HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System" /v "DisableCAD" /f
reg delete "HKLM\System\CurrentControlSet\Control\Lsa" /v "LmCompatibilityLevel" /f
reg delete "HKLM\System\CurrentControlSet\Control\Lsa" /v "SCENoApplyLegacyAuditPolicy" /f
And for some reason (and this was not consistent), I also found that I needed to delete the following on some systems:
reg delete "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU" /f
Full Solution
Here is everything I ran against my "bad" systems that were domain joined in production use:
Batch File
rd /s /q "%SystemRoot%\System32\GroupPolicy"
secedit /configure /db secedit.sdb /cfg "%~dp0SecurityPolicies-Defaults.inf" /overwrite /quiet
reg delete "HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System" /v "DisableCAD" /f
reg delete "HKLM\System\CurrentControlSet\Control\Lsa" /v "LmCompatibilityLevel" /f
reg delete "HKLM\System\CurrentControlSet\Control\Lsa" /v "SCENoApplyLegacyAuditPolicy" /f
reg delete "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU" /f
SecurityPolicies-Defaults.inf
[Unicode]
Unicode=yes
[System Access]
MinimumPasswordAge = 0
MaximumPasswordAge = 42
MinimumPasswordLength = 0
PasswordComplexity = 0
PasswordHistorySize = 0
LockoutBadCount = 0
RequireLogonToChangePassword = 0
ForceLogoffWhenHourExpire = 0
NewAdministratorName = "Administrator"
NewGuestName = "Guest"
ClearTextPassword = 0
LSAAnonymousNameLookup = 0
EnableAdminAccount = 1
EnableGuestAccount = 0
[Event Audit]
AuditSystemEvents = 0
AuditLogonEvents = 0
AuditObjectAccess = 0
AuditPrivilegeUse = 0
AuditPolicyChange = 0
AuditAccountManage = 0
AuditProcessTracking = 0
AuditDSAccess = 0
AuditAccountLogon = 0
[Registry Values]
MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Setup\RecoveryConsole\SecurityLevel=4,0
MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Setup\RecoveryConsole\SetCommand=4,0
MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\CachedLogonsCount=1,"10"
MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\ForceUnlockLogon=4,0
MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\PasswordExpiryWarning=4,5
MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\ScRemoveOption=1,"0"
MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\ConsentPromptBehaviorAdmin=4,5
MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\ConsentPromptBehaviorUser=4,3
MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\DontDisplayLastUserName=4,0
MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\EnableInstallerDetection=4,1
MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\EnableLUA=4,1
MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\EnableSecureUIAPaths=4,1
MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\EnableUIADesktopToggle=4,0
MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\EnableVirtualization=4,1
MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\FilterAdministratorToken=4,0
MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\LegalNoticeCaption=1,""
MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\LegalNoticeText=7,
MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\PromptOnSecureDesktop=4,1
MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\ScForceOption=4,0
MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\ShutdownWithoutLogon=4,1
MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\UndockWithoutLogon=4,1
MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\ValidateAdminCodeSignatures=4,0
MACHINE\Software\Policies\Microsoft\Windows\Safer\CodeIdentifiers\AuthenticodeEnabled=4,0
MACHINE\System\CurrentControlSet\Control\Lsa\AuditBaseObjects=4,0
MACHINE\System\CurrentControlSet\Control\Lsa\CrashOnAuditFail=4,0
MACHINE\System\CurrentControlSet\Control\Lsa\DisableDomainCreds=4,0
MACHINE\System\CurrentControlSet\Control\Lsa\EveryoneIncludesAnonymous=4,0
MACHINE\System\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy\Enabled=4,0
MACHINE\System\CurrentControlSet\Control\Lsa\ForceGuest=4,0
MACHINE\System\CurrentControlSet\Control\Lsa\FullPrivilegeAuditing=3,0
MACHINE\System\CurrentControlSet\Control\Lsa\LimitBlankPasswordUse=4,1
MACHINE\System\CurrentControlSet\Control\Lsa\MSV1_0\NTLMMinClientSec=4,536870912
MACHINE\System\CurrentControlSet\Control\Lsa\MSV1_0\NTLMMinServerSec=4,536870912
MACHINE\System\CurrentControlSet\Control\Lsa\NoLMHash=4,1
MACHINE\System\CurrentControlSet\Control\Lsa\RestrictAnonymous=4,0
MACHINE\System\CurrentControlSet\Control\Lsa\RestrictAnonymousSAM=4,1
MACHINE\System\CurrentControlSet\Control\Print\Providers\LanMan Print Services\Servers\AddPrinterDrivers=4,0
MACHINE\System\CurrentControlSet\Control\SecurePipeServers\Winreg\AllowedExactPaths\Machine=7,System\CurrentControlSet\Control\ProductOptions,System\CurrentControlSet\Control\Server Applications,Software\Microsoft\Windows NT\CurrentVersion
MACHINE\System\CurrentControlSet\Control\SecurePipeServers\Winreg\AllowedPaths\Machine=7,System\CurrentControlSet\Control\Print\Printers,System\CurrentControlSet\Services\Eventlog,Software\Microsoft\OLAP Server,Software\Microsoft\Windows NT\CurrentVersion\Print,Software\Microsoft\Windows NT\CurrentVersion\Windows,System\CurrentControlSet\Control\ContentIndex,System\CurrentControlSet\Control\Terminal Server,System\CurrentControlSet\Control\Terminal Server\UserConfig,System\CurrentControlSet\Control\Terminal Server\DefaultUserConfiguration,Software\Microsoft\Windows NT\CurrentVersion\Perflib,System\CurrentControlSet\Services\SysmonLog
MACHINE\System\CurrentControlSet\Control\Session Manager\Kernel\ObCaseInsensitive=4,1
MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management\ClearPageFileAtShutdown=4,0
MACHINE\System\CurrentControlSet\Control\Session Manager\ProtectionMode=4,1
MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems\optional=7,Posix
MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\AutoDisconnect=4,15
MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\EnableForcedLogOff=4,1
MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\EnableSecuritySignature=4,0
MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\NullSessionPipes=7,
MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\RequireSecuritySignature=4,0
MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\RestrictNullSessAccess=4,1
MACHINE\System\CurrentControlSet\Services\LanmanWorkstation\Parameters\EnablePlainTextPassword=4,0
MACHINE\System\CurrentControlSet\Services\LanmanWorkstation\Parameters\EnableSecuritySignature=4,1
MACHINE\System\CurrentControlSet\Services\LanmanWorkstation\Parameters\RequireSecuritySignature=4,0
MACHINE\System\CurrentControlSet\Services\LDAP\LDAPClientIntegrity=4,1
MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters\DisablePasswordChange=4,0
MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters\MaximumPasswordAge=4,30
MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters\RequireSignOrSeal=4,1
MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters\RequireStrongKey=4,1
MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters\SealSecureChannel=4,1
MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters\SignSecureChannel=4,1
[Privilege Rights]
SeNetworkLogonRight = *S-1-1-0,*S-1-5-32-544,*S-1-5-32-545,*S-1-5-32-551
SeBackupPrivilege = *S-1-5-32-544,*S-1-5-32-551
SeChangeNotifyPrivilege = *S-1-1-0,*S-1-5-19,*S-1-5-20,*S-1-5-32-544,*S-1-5-32-545,*S-1-5-32-551
SeSystemtimePrivilege = *S-1-5-19,*S-1-5-32-544
SeCreatePagefilePrivilege = *S-1-5-32-544
SeDebugPrivilege = *S-1-5-32-544
SeRemoteShutdownPrivilege = *S-1-5-32-544
SeAuditPrivilege = *S-1-5-19,*S-1-5-20
SeIncreaseQuotaPrivilege = *S-1-5-19,*S-1-5-20,*S-1-5-32-544
SeIncreaseBasePriorityPrivilege = *S-1-5-32-544
SeLoadDriverPrivilege = *S-1-5-32-544
SeBatchLogonRight = *S-1-5-32-544,*S-1-5-32-551,*S-1-5-32-559
SeServiceLogonRight = *S-1-5-80-0
SeInteractiveLogonRight = Guest,*S-1-5-32-544,*S-1-5-32-545,*S-1-5-32-551
SeSecurityPrivilege = *S-1-5-32-544
SeSystemEnvironmentPrivilege = *S-1-5-32-544
SeProfileSingleProcessPrivilege = *S-1-5-32-544
SeSystemProfilePrivilege = *S-1-5-32-544,*S-1-5-80-3139157870-2983391045-3678747466-658725712-1809340420
SeAssignPrimaryTokenPrivilege = *S-1-5-19,*S-1-5-20
SeRestorePrivilege = *S-1-5-32-544,*S-1-5-32-551
SeShutdownPrivilege = *S-1-5-32-544,*S-1-5-32-545,*S-1-5-32-551
SeTakeOwnershipPrivilege = *S-1-5-32-544
SeDenyNetworkLogonRight = Guest
SeDenyBatchLogonRight =
SeDenyInteractiveLogonRight = Guest
SeUndockPrivilege = *S-1-5-32-544,*S-1-5-32-545
SeManageVolumePrivilege = *S-1-5-32-544
SeRemoteInteractiveLogonRight = *S-1-5-32-544,*S-1-5-32-555
SeImpersonatePrivilege = *S-1-5-19,*S-1-5-20,*S-1-5-32-544,*S-1-5-6
SeCreateGlobalPrivilege = *S-1-5-19,*S-1-5-20,*S-1-5-32-544,*S-1-5-6
SeIncreaseWorkingSetPrivilege = *S-1-5-32-545
SeTimeZonePrivilege = *S-1-5-19,*S-1-5-32-544,*S-1-5-32-545
SeCreateSymbolicLinkPrivilege = *S-1-5-32-544
[Version]
signature="$CHICAGO$"
Revision=1
Thanks to Darren Mar-Elia for leading me in the right direction with this.
Good luck!

Problem when pre-composing masked layer

Ok, i am having a problem when masking a Twixtored layer.
this is what happens:
i have the original footage in a comp, i used twixtor to slow it down to 3% speed
Seen here: http://prntscr.com/zbicc
I Then pre composed that slowed down layer into a comp of it's own and masked around that parts i wanted and named this comp "masked comp 1"
Seen here: http://prntscr.com/zbitw
and here: http://prntscr.com/zbiyc
i then precomposed the masked layer into another comp called "sky replacement" and this is when i hit the problem, it dosn't show up, it just gives me a black screen.
Seen here: http://prntscr.com/zbj9n
and here: http://prntscr.com/zbjcn
I tried rendering out "Masked comp 1" and "sky replacement" and with both it just renders a black screen, but if i render the Twixtored comp that renders fine. So i think it has somthing to do with the mask but i can't figure it out.
Please help.

The black screen notwithstanding, I see two VERY big problems in the workflow as described... or at least as how I understand your workflow.
You used Twixtor to slow down video to 3% of its normal speed: that represents tons and tons of speed redeuction, and you're lucky that Twixtor was able to give you a useful image AT ALL. Then you precomped it, too boot.
Then you hoped against all hope that you could effectively mask the precomp... which was presumably at the target frame rate.
Give yourself a fighting chance to come up with something: once you use Twxtor, prerender it. And I have to tell you: if you are actually using Twixtor to slow down footage to 3% of normal speed, it probably won't look good. Twixtor is great for minor speed variations, but for 3% of normal? It can't work miracles......

K7T266Pro2 odd problem

Hi all, i have an odd problem thats driving me to distraction.
Firstly i am using Winxp pro, with 512MB ram, xp cpu 2000+ and 3 hard disks plus other cards etc..
now i had an old 3d prophett ddr dvi card, which appeared to be ok, but a bit slow, so i went out and bought a brand new (boxed) creative geforce 4 mx 420 video card, inserted it, and the pc upon starting beeped 8 times, the display remained dark yet the hard disks appeared to be loading, i then reinserted the prophett and all ok, reinsert the creative card and same error.
apparently it is the memorry on the video card, but hwy? what is causing this, and yes i have flashed the bios to the latest release..

and also..
now i play around with it some more, sometimes when it does boot, it distorts the blocks around on screen, which if my memorry serves me is a video card memorry leakage problem, as the card is half a day old, i think i will take it back to the shop tomorrow with my base unit and demonstrate it in situ, alsomeans if they do swop the card i can see the frikin thing working rather than swop a duff for a duff
i also reinstalled my old 3d prophett which now loaded windows fine with no bluescreen, i think i got sold a duff card, but if anyone can explain why the beeps id be greatful..

FIXED! K8N Plat. SLI: Odd problem Did Reformat Now Won't Post...:/

Heeeellloo MSI community! After all the madness I went through; I followed up on wevsspot's link (see his post) & read the bejeebus outta this thread here.
NOTE: The above link is for all NForce 3/4 Mobo owners w/ RAID problems attempting a reformat/upgrade using Window's XP and then suffering an UNENDING cycle of "quick-flash BSOD + auto reboot" assualts...!
In brief, the solution is:
1) Make a slip-streamed OS CD w/ Nvidia's Nforce 6.70 RAID drivers (or latest version) integrated using Nlite. (not sure about Autostreamer...)
-1) But before that, you must have the latest Bios flashed or these "new" Nvidia drivers won't be recognized during OS installation!
The link above is VERY informative & I would not be here yapping about if it wasn't for the sleuthing abilities of one wevsspot!
Cheers to Indigian & all who've taken the time to post!
Evening all. I usually don't come for help but I feel I've earned a second opinion after working on my PC for 3 days. After all I've done, this issue is really beginning to worry me. On Friday I was playing some SP BF2 and then my PC suddenly restarted. So I started up again & shut down normally and then I fired up CS: Source, after a few maps, another restart.
Hmm, then I uninstalled Nvidia's current graphics drivers and installed the previous version. Tried CS, same outcome. Well, I have reformated my PC before w/ success so I figured "its been several months" & now this issue surfaces so why not?
Well, I backed up and dived in. Had my original MSI Raid driver floppy ready but there was an error so I followed MSI's directions here & loaded up a new floppy and things went fine (I tried both versions- the version at that link & the most current Raid driver version, 5.53 via Nvidia's site. However, for both versions, the file "nvatabus.inf" in which MSI claims to be there is no where to be found). Now fasy-forward to the 1st Window's loading screen (loading bars...) after OS installation, I see a BSOD flash and then restart, and restart, etc...
Facts & POE attempts in no particular order:
-My Bios is the original, 3.1. Apart from the problems I've read here, I have never upgraded it being that I've never really had to.
-I've noticed that rite after OS installation, where I see my status of my Raid config., the version is still 4.81... & then, the damn restarting begins...
-I have tried switching serial ports from 3 & 4 to 1 & 2. Also disabling the unused ports in the Bios after switching. As I switched ports for the 1st time, I even deleted my Raid config. and built a new one.
-I have tried unpluging my pata cables, unpluging my USB devices, & unseating my memory as mentioned in a several threads I read here about seeing a BSOD just before Windows loads.
-Whenever I reformated, I had to remove one of my BFG cards and thus "flipping" over the SLI chip on the mobo. I learned that XP wouldn't load my SLI rig on its 1st run...
-I tried installing XP originally w/ SP1 or slipstreamed w/ SP2, no go.
-Inbetween these hairpulling attemps @ process of elimation, I tried just one of my Maxtors w/ no floppy help and it WORKED. So that points me to this being a Raid issue.
I apologise for the wall of text. I think I have tried all avenues to getting this odd problem fixed. Any advice or instructions would be great. Thanks for reading.

Cowbell,
During your chipset drivers update (or even possibly during the Windows OS install routine itself) you may have corrupted your original Raid Array. My suggestion would be to enter your Raid Setup Bios and delete the existing array the build one from scratch. If you have another computer, extract the RAID drivers from the original MSI setup CD that came with your motherboard and put them on a floppy. Or if you so choose you could use the RAID drivers from a later chipset driver pack. I'll leave that up to you. After you rebuild your RAID array, turn off computer, turn off power supply, remove power cord from power supply,remove m/b battery and move CMOS jumper pin to the clear position. Leave it like that for at least 10 minutes. Move CMOS jumper back to save position. Reinstall motherboard battery and connect power back to your power supply. Reboot and enter BIOS again. Re-enable the SATA or IDE ports you are using for your array, enable RAID in the BIOS. Exit, reboot and enter RAID Bios setup again, make sure your RAID array is present and make sure it is set as a bootable ARRAY. If everything looks good, reboot once more and enter BIOS. Make sure your RAID array is showing as a bootable device. Do the normal stuff such as making sure your optical drive is set as the first boot device etc.
Save, exit. If all goes well you will be prompted to press F6 to install 3rd party RAID drivers upon the initial Windows OS installation routine.
Good luck.

CS5 problem Adjustment layers only affect one layer instead of all

I am getting this problem with Photoshop CS5 I think one of the settings got changed by accident but for some reason I cannot get any of the adjustment layers Levels,Curves etc to affect all layers under them. Instead it just changes the brightness of one layer only which is the one just below the adjustment layer but not all of the others. I use Photoshop for Digital art and I was all of the layers under the adjustment to change the look of the full image instead of just one layer. Is there any way of fixing this problem? I dont know what to do

I think I know what the problem may be:
When you're adding a new adjustment layer the following checkbox is coming on by default:
You probably changed the default for this. Here's how to change it back:
Make the Adjustments panel visible by clicking the Window - Adjustments menu.
Click the little fly-out menu icon at the upper-right.
Clear the Clip To Layer checkbox.
-Noel

Problem Adjustment Layer PP CS6

Hello everyone, you have the same bug as me in the first pro CS6 and layers of effects.
Mounting with the gpu, in a sequence dslr, I put an adjustment layer on top of a video, I use a level on the adjustment layer (so far so good, the effect is clearly visible) and as soon as I play on the opacity effect (to fade on two key eg), the effect is no longer visible.
If you have any feedback I'm interested. thank's in advance

Ok, here is the info:
*Premiere cc
*updates are installed as far as I know..
*Windows 8 pro
*Video files: MTS files (sony fs700)
*Error message when exporting: "Error compiling movie. Uknown error"
The culprit from my point of view is the adjustment layer. As soon as I remove it from the timeline it seems to work..
I think it has been working in the past..
No other software is running in the background of notice as far as I am concerned...
I have third party codecs installed but none of them where used here. I used fast collorcorrection and procamp on the adjustmentlayer.
Hardware:
intel i7 3930K
32GB RAM
nvidia 680 GTX 4GB
samsung 840 pro ssd
Im using mercury playback engine GPU accelerator
this only happends when doing final export as far as I know. I can play the clip in the timeline even if the effects on adjustmentlayer isnt working properly when using opacity keyframes.

Transform Effect problems when used with 3D layer's depth

Here is my set up.
I have PreComp with graphics illustrator imported layer with continuosly rasterise enabled.
This graphics has a reflection underneath it. I made the reflection by applying Transform effect, setting offset to -100 and adjusting the Anchor point.
As far as graphics move left to right (X,Y) there is no problem and Anchor point is in its place.
As soon as I make the layer 3D and start changing depth values the reflection starts to jump around.
My guess is - it happens because anchor point is a constant value and since reflection is based off its value it does not follow the base of the graphics. Purhasps there is a code snippet which need to be used to link the Anchor Point value to the Zoom Value? Adjusting Anchor point values with key frames proved too difficult.
In another words I would like to keep the reflection at a constant distance from the base of the graphics and once the graphics move out or in the reflection does not follow.
I PreComposed this graphics and imported it into the new Compostion and applied XY and Z movement using camera and Null layers. It was the same effect and reflection did not stick to the base of the graphics.
I need to keep Collapse Transformation enabled on all the consecutive Comps/PreComps to make sure the vector art renders at high quality.
What would be a proper way to make a reflection of a 3D layer/preComp in the Comp where movement controlled with Camera and Null layers, with Continuosly Rasterise/Collapse Transformations enabled?

Great! At least I know not to spent my time in a wrong direction.
Two questions:
Do I need to enable "Collapse Transformations" in the final rendering Comp in order to keep "Continuously Rasterize" settings within the nested PreComps enabled (for illustrator files rendering sharp). I have a few nested preComps and originally activated "Continuously Rasterize" throughout the project in all of them.
"How" to create reflections seem clear from your comment. Do not use any effects but rather create a copy of a layer I would like to have a reflection of and scale it to -100. "When" seems to be a mystery. Should I apply reflection in the very first preComp or very last or the one where I create all the major animation for my graphics?

Burn Problem with a 4GB project: "Layer 0 Exceeds"

First off this is not the usual Dual-Layer problem. I know all about Layers how they work and how to make them. Although the error I receive deals with DL my projects or nowhere near that size.
I recently had DVDSP 4 crash on me. Ever since than its been running really funny. The biggest issue I am having is that it won't allow me to burn a DVD 5. My projects usually range from 2.5GB - 4.5GB. Let me also say that DVDSP 4's Disc meter has always been a pretty good gauge as far as I am concerned. It's always been right on telling me if something was going to fit on a DVD 5 or 9.
My problem ever since the crash is that DVDSP will not allow me to burn a DVD unless the project is under 3.5GB. I have tried everything, including a Full Re-install of DVDSP. Every time I try to burn a DVD I get the following error message:
+"Formatting was not successful. Layer 0 exceeds the maximum layer size allowed. Please choose a suitable marker location that will support this condition."+
My latest project is dealing with a 4.4Gb (according to Meter) 4.32GB actually. It is impossible for me to burn a DVD because of the error message above. I can however run the project out on a Single DLT. How does that work?
Has anyone else had a problem like this? Does anyone have an suggestions?
I have checked all the obvious settings in DVDSP and all seem to be right. I can't figure this one out.

I've never had a problem burning a 4.4 disc on a DVD 5 until now. I actually went back to some of my previous project that were a DVD-5 and I am unable to burn those now too. Everything really got screwed up on that last Crash.
Yes. I am using AC3 audio.
I have not yet tried burning my DVD project through another program...but thats a good idea.
I usually burn a DVD and DLT for the replicators...but I know they prefer a DLT. What I find odd about all of this is that I am able to run out a DLT with no errors at all. It only seems to be on the DVD side.
In regards to the uninstall...I used the exact program. I am actually in the process of doing a full reinstall of FCP2 Suite.
I'll let you know how it goes. Thanks for the suggestions.
Mike A.

Odd problem adjusting scale of rotoshape layer

Similar Messages

Maybe you are looking for