Minor bug report SoundTrack Pro

Hi,
I would like to report what seems to be a little bug in SoundTrack Pro wav file creation process and haven't found a page where to send a ticket so I'm posting this here
I am currently writing a programm to read simple WAVE fles with the basic scheme RIFF/WAVE/fmt /data and I am basically skipping any chunk whose ID differs from the four previous. Every chunk of meta in a WAVE file is supposed to be ChunkID on 4 bytes then, immediatly after, ChunkSize on 4 bytes too.
SoundTrack Pro seems to respects this format for the APPL chunk (contains a path) except for one little bug: the size I read is one byte too short for me. And only for this chunk of meta. (Not the storage of the size, which is on 4 bytes too, the actual size of the whole chunk). I have to manually read one more byte when the chunk is APPL.
Any ideas of where this should be reported ? Plus it is really minor, I don't really have a hope that this bug be corrected one day but anyway...
Tignus.

This is a user to user forum. To submit feedback to Apple, (with the program open) select Soundtrack Pro (the item just to the right of the Apple icon) then> Provide Soundtrack Pro Feedback. This will send an email to Apple.
In the FWIW catagory, STP is a dead program. There will be no additional development on it.
Good luck,
x

Similar Messages

The new Synaptics UltraNav: a few workarounds and minor bug report.

I only wanted to file bug report, but then decided to also share what I did with my touchpad configuration to make it more convenient for me. I have Thinkpad T540p so this might work differently or not work at all for other notebooks.
#1 Regedit
Configure as much as you can using UltraNav tab in mouse settings dialog. (It is mostly self-explanatory.)
If you didn't find some option, start regedit (using Win+R) and navigate to
HKEY_CURRENT_USER\Software\Synaptics\SynTP\something
This something is TouchPadSMB2c on T540p but you can find one you need by changing something in settings dialog and looking for changed values in regedit.
All the touchpad configuration registry keys are there. You need to relogin to apply changes made there.
But it might take a lot of trial and error to find out how these registry keys work.
#2 3-finger tap
As for me, I prefer tapping over clicking. While 3-finger press option is in settings dialog, 3-finger tap is not. But you can change it.
Set whatever option you want for 3-finger press. Then go to regedit and copy value from 3FingerPressButtonAction key to 3FingerTapAction.
#3 Button sizes and locations
You can change button bounds with keys like LeftButtonZoneX where X is L for left, R for right, T for top and B for bottom bounds. 0xFFFFFFFF ultimately means "unlimited in that direction". For finding other values defaults might be helpful. Trackpoint buttons keys are SlaveSomeButtonZoneX.
What for?
First, trackpoint buttons can cover the whole trackpad only when trackpad itself is disabled. By changing button sizes manually you can overcome this restriction. It is useful because trackpad does not respond well to pressing corners and when buttons cover it all you can press it somewhere in the middle.
Second, the same corner pressing problem exists for normal trackpad buttons so it is more convenient to use multi-finger taps or clicks. You can still hold trackpad pressed with one finger and use yet another finger to move mouse pointer.
At the same time when you tap or press with multiple fingers and one of them touches one of the buttons you get that button pressed instead of whatever you intended. It frustrated me a lot when I got context menu popups while trying to close chrome tabs with middle mouse button click. The solution is to set top bounds for left and right buttons to zero.
BUG (With the latest UltraNav drivers from support page)
When the middle trackpoint button (used for scrolling) is enabled, it is always enabled, no matter if you are using trackpont or touchpad. Left and right trackpoint buttons are properly disabled when you don't need them.
Even if you disable trackpoint completely without disabling that middle button first, it will remain enabled and will do nothing. (Blocking single- and multi-finger presses that touch it.)
I could not find a way to fix that problem with regedit.

Any problem can get official response and follow-up through a SR on Metalink/MOS (if you have a DB support contract), else you can post here and hope someone from development picks it up.
Regards,
K.

Help! Macbook Pro Keeps Crashing. Here Is The Bug Report

Please, please, please can someone help me my mac keeps crashing for the last week and I dont know why.
I keep getting the grey screen of death
I have included the bug report below.
Mac Specs
I have a Macbook Pro 17"
Model Identifier: MacBookPro8,3
Late 2011 Version
2.2ghz Intel Core i7
Intel HD Graphics 3000 512 MB
Software OS X 10.9.4 (13E28)
I am running the OS off an SSD 750 GB Drive connected internally (have been for over a year with no issues)
The drive that came with my mac got corrupted so I replaced it with the SSD
I am using an external monitor AOC connected via thunderbolt (have had this set up for over 1.5 years with no issues.
Bug Report
Anonymous UUID: DDEA4723-7244-E776-B61A-34B381E8523F
Tue Jul 29 23:34:57 2014
panic(cpu 5 caller 0xffffff8003e4e5ca): "A kext releasing a(n) GenericUSBXHCI has corrupted the registry."@/SourceCache/xnu/xnu-2422.110.17/libkern/c++/OSObject.cpp:218
Backtrace (CPU 5), Frame : Return Address
0xffffff81ee4cbe00 : 0xffffff8003a22f79
0xffffff81ee4cbe80 : 0xffffff8003e4e5ca
0xffffff81ee4cbed0 : 0xffffff8003e9b6e7
0xffffff81ee4cbef0 : 0xffffff8003ea9d0f
0xffffff81ee4cbf30 : 0xffffff8003eaf292
0xffffff81ee4cbf80 : 0xffffff8003eaf367
0xffffff81ee4cbfb0 : 0xffffff8003ad7417
BSD process name corresponding to current thread: kernel_task
Mac OS version:
13E28
Kernel version:
Darwin Kernel Version 13.3.0: Tue Jun 3 21:27:35 PDT 2014; root:xnu-2422.110.17~1/RELEASE_X86_64
Kernel UUID: BBFADD17-672B-35A2-9B7F-E4B12213E4B8
Kernel slide: 0x0000000003800000
Kernel text base: 0xffffff8003a00000
System model name: MacBookPro8,3 (Mac-942459F5819B171B)
System uptime in nanoseconds: 49357323350
last loaded kext at 46443091940: com.apple.driver.AppleBluetoothMultitouch 80.14 (addr 0xffffff7f858c1000, size 77824)
loaded kexts:
com.bresink.driver.BRESINKx86Monitoring 9.0
com.avatron.AVExFramebuffer 1.7
com.displaylink.driver.DisplayLinkDriver 2.1
net.telestream.driver.TelestreamAudio 1.1.0
com.techsmith.TACC 1.0.2
com.logmein.driver.LogMeInSoundDriver 1.0.3
com.avatron.AVExVideo 1.7
com.sonnet.driver.SXHCD 1.27.9b2
net.osx86.kexts.GenericUSBXHCI 1.2.7
com.apple.driver.AppleBluetoothMultitouch 80.14
com.apple.driver.AppleHWSensor 1.9.5d0
com.apple.filesystems.autofs 3.0
com.apple.iokit.IOBluetoothSerialManager 4.2.6f1
com.apple.driver.AGPM 100.14.28
com.apple.driver.AppleTyMCEDriver 1.0.2d2
com.apple.driver.AppleMikeyHIDDriver 124
com.apple.driver.ApplePolicyControl 3.6.22
com.apple.driver.AppleMikeyDriver 2.6.3f4
com.apple.driver.AudioAUUC 1.60
com.apple.driver.AppleUpstreamUserClient 3.5.13
com.apple.iokit.IOUserEthernet 1.0.0d1
com.apple.kext.AMDFramebuffer 1.2.4
com.apple.driver.AppleHDAHardwareConfigDriver 2.6.3f4
com.apple.iokit.IOBluetoothUSBDFU 4.2.6f1
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.2.6f1
com.apple.driver.AppleHDA 2.6.3f4
com.apple.driver.AppleHWAccess 1
com.apple.AMDRadeonX3000 1.2.4
com.apple.driver.AppleIntelMCEReporter 104
com.apple.driver.AppleIntelHD3000Graphics 8.2.4
com.apple.driver.AppleLPC 1.7.0
com.apple.driver.AppleThunderboltIP 1.1.2
com.apple.kext.AMD6000Controller 1.2.4
com.apple.driver.AppleSMCPDRC 1.0.0
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.driver.AppleSMCLMU 2.0.4d1
com.apple.driver.SMCMotionSensor 3.0.4d1
com.apple.driver.AppleIntelSNBGraphicsFB 8.2.4
com.apple.driver.AppleMuxControl 3.6.22
com.apple.driver.AppleBacklight 170.3.5
com.apple.driver.AppleMCCSControl 1.2.5
com.apple.driver.AppleUSBTCButtons 240.2
com.apple.driver.AppleUSBTCKeyEventDriver 240.2
com.apple.driver.AppleUSBTCKeyboard 240.2
com.apple.driver.AppleIRController 325.7
com.apple.driver.AppleFileSystemDriver 3.0.1
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeLZVN 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 35
com.apple.driver.XsanFilter 404
com.apple.driver.AppleUSBXHCI 683.4.0
com.apple.driver.AppleUSBHub 683.4.0
com.apple.iokit.IOAHCIBlockStorage 2.6.0
com.apple.driver.AppleFWOHCI 5.0.2
com.apple.driver.AirPort.Brcm4331 700.20.22
com.apple.iokit.AppleBCM5701Ethernet 3.8.1b2
com.apple.driver.AppleAHCIPort 3.0.5
com.apple.driver.AppleUSBEHCI 660.4.0
com.apple.driver.AppleUSBUHCI 656.4.1
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleACPIButtons 2.0
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleSMBIOS 2.1
com.apple.driver.AppleACPIEC 2.0
com.apple.driver.AppleAPIC 1.7
com.apple.driver.AppleIntelCPUPowerManagementClient 217.92.1
com.apple.nke.applicationfirewall 153
com.apple.security.quarantine 3
com.apple.driver.AppleIntelCPUPowerManagement 217.92.1
com.apple.driver.IOBluetoothHIDDriver 4.2.6f1
com.apple.driver.AppleMultitouchDriver 245.13
com.apple.kext.triggers 1.0
com.apple.iokit.IOSCSIArchitectureModelFamily 3.6.6
com.apple.iokit.IOSerialFamily 10.0.7
com.apple.iokit.IOSurface 91.1
com.apple.iokit.IOBluetoothFamily 4.2.6f1
com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.2.6f1
com.apple.driver.DspFuncLib 2.6.3f4
com.apple.vecLib.kext 1.0.0
com.apple.iokit.IOAcceleratorFamily 98.22
com.apple.driver.AppleThunderboltEDMSink 2.1.3
com.apple.driver.AppleThunderboltDPOutAdapter 3.1.7
com.apple.driver.AppleSMBusPCI 1.0.12d1
com.apple.kext.AMDSupport 1.2.4
com.apple.AppleGraphicsDeviceControl 3.6.22
com.apple.iokit.IOFireWireIP 2.2.6
com.apple.driver.AppleHDAController 2.6.3f4
com.apple.iokit.IOHDAFamily 2.6.3f4
com.apple.driver.IOPlatformPluginLegacy 1.0.0
com.apple.driver.IOPlatformPluginFamily 5.7.1d6
com.apple.driver.AppleUSBAudio 2.9.5f8
com.apple.iokit.IOAudioFamily 1.9.7fc2
com.apple.kext.OSvKernDSPLib 1.14
com.apple.driver.AppleSMC 3.1.8
com.apple.driver.AppleGraphicsControl 3.6.22
com.apple.driver.AppleBacklightExpert 1.0.4
com.apple.iokit.IONDRVSupport 2.4.1
com.apple.driver.AppleSMBusController 1.0.12d1
com.apple.iokit.IOGraphicsFamily 2.4.1
com.apple.driver.AppleThunderboltDPInAdapter 3.1.7
com.apple.driver.AppleThunderboltDPAdapterFamily 3.1.7
com.apple.driver.AppleThunderboltPCIDownAdapter 1.4.5
com.apple.driver.AppleUSBMultitouch 240.9
com.apple.iokit.IOUSBHIDDriver 660.4.0
com.apple.driver.AppleUSBMergeNub 650.4.0
com.apple.driver.AppleUSBComposite 656.4.1
com.apple.driver.AppleThunderboltNHI 2.0.1
com.apple.iokit.IOThunderboltFamily 3.3.1
com.apple.iokit.IOUSBUserClient 660.4.2
com.apple.iokit.IOFireWireFamily 4.5.5
com.apple.iokit.IO80211Family 640.36
com.apple.iokit.IOEthernetAVBController 1.0.3b4
com.apple.driver.mDNSOffloadUserClient 1.0.1b5
com.apple.iokit.IONetworkingFamily 3.2
com.apple.iokit.IOAHCIFamily 2.6.5
com.apple.iokit.IOUSBFamily 683.4.0
com.apple.driver.AppleEFINVRAM 2.0
com.apple.driver.AppleEFIRuntime 2.0
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 278.11.1
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet 7
com.apple.driver.AppleKeyStore 2
com.apple.driver.DiskImages 371.1
com.apple.iokit.IOStorageFamily 1.9
com.apple.iokit.IOReportFamily 23
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.driver.AppleACPIPlatform 2.0
com.apple.iokit.IOPCIFamily 2.9
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.pthread 1
com.apple.kec.corecrypto 1.0

Looks like the Open Source USB 3.0 driver GenericUSBXHCI is causing this. I'd suggest uninstalling it.

FAQ: How do I submit a bug report or feature request or otherwise give feedback about Premiere Pro?

The best way to submit a bug report or feature request is to use the bug-report/feature-request form.
The Premiere Pro team doesn’t necessarily see and record every post on every forum and social network, but we do see, record, and track every entry through the the official feature-request/bug-report form.
It also helps a lot if you opt into the Product Improvement Program.
Also, be sure to use the crash reporter.
We really do read all of the bug reports and feature requests, and the software really does get a lot of benefit from detailed crash reports.
Don’t forget about contacting Adobe Technical Support or Customer Service, too. For information on how to contact Adobe Technical Support, see this page. (Note that you must register your product before you can open a technical support case for it.)
If you have tried to get help from our support staff, but the service was inadequate, I can help you to escalate your issue if you send me your case number at kopriva at adobe dot com. You must provide me a case number. I am not offering to solve your problem myself; rather, I am willing to forward your information to someone if you have already hit a dead end with our Technical Support or Customer Service.
If you have feedback about the content of the Premiere Pro Help document, then please add a comment at the bottom of the relevant page. You can add comments to add information, to add links, to make corrections, or to ask for clarification.
If you want to keep up with the Premiere Pro team, then you can follow our blogs, Facebook page, and Twitter feed and so on.
Oh, and I can’t resist this opportunity to remind you to update to the most recent version of the application. Don’t be surprised when the first thing that you hear back from us is that you need to install the latest updates. We fix a lot of things in updates, and we don’t want to go chasing bugs that we’ve already fixed. We’ll keep you posted on our blogs, Facebook page, and Twitter feed about updates as they become available.

Hi qwerty,
Dun tink that creative customer support sucks cos I had been dealing with them in the past and I can say that their service are quite gd and fast. If you wanted a refund, I tink you need to contact the store that sells you the product. Dun tink creative will refund you though.

Why can't we submit bug reports for Flash Pro?

I've been looking to submit some bug reports regarding CS5.5 Pro and there just isn't an option in the "Report a Bug/Feature Request" form. WHY not?? I paid for CS5.5 and autoformat breaks my code, but there's no way to report it.

You aren't the first to have a problem with the choices provided. It would be nice if they listed "Flash Pro" uniquely in the list of options at...
http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
... since they dio for the rest of the Adobe products. But you should feel free to pick any one of them. I'd choose "Flash Authoring" since I've no idea what it is other than maybe something to do with Flash Pro.

Logic Pro 5.1 ch plugin subwoofer channel bug report

hello,
I had found out that Native Instruments absynth 5.1 ch synthesize sofware , which in stand alone mode
outputs the subwoofer channel audio properly, does not output subwoofer channel audio in Logig Pro surround
plugin in 64 bit mode.
I contacted Native Instruments about this and after a certain time, they say that they did deeper invstigation
and found out that it is the Logic bug.
I just don't know how to bug report to the apple, so I put this here.
Please confirm and fix it.

The crashed thread (7) mentions logic's preferences file. (com.apple.logic.pro). Drag it to the desktop (so you can reclaim you key commands if it works) and restart logic. Logic will create a new preferences file. Worth a try..

SoundTrack Pro 2.0.2 has bugs along with AUL

Does anyone know if Apple will be releasing a new update for SoundTrack Pro? A few things that I am encountering.
-I CANNOT export a audio file from FCP to STP. I've done everything including reinstalling a clean install of the software but I am still not able to send a file to FCP. What occurs is that the file is sent and STP opens up but that **** beach ball just spins and spins and I have to close down because "APPLICATION NOT RESPONDING". pure frustration.
- I also use Logic Studio 8 and everything works there just fine. What I've noticed is that If I open STP Independently and choose an audio file to place on the timeline I get nothing but a "SCRATCHY" return. I've made sure that all things related were either connected or programmed right as far as input and output of my speaker system and Ultralite Motu Interface. I also happen to notice too that Apple's Utility Loop player does the exact same thing. I've done all the updates and I am still having problems. Does anyone know about any of this? Please let me know because I am completely disgusted and frustrated.
TAZZ1

DISREGARD POST PROBLEM SOLVED.
DISCOVERED A PLUG THAT WAS CONNECTED TO MY AUDIO CONNECTION IN THE BACK OF MY COMPUTER WAS DISCONNECTED. EVERYTHING SEEMS TO BE WORKING OK. WOW, A LITTLE PLUG CREATED THIS ENTIRE MESS. ABLE TO SEND FILES TO FCP TO STP WITH NO PROBLEMS. AFTER RE-CONNECTING THE PLUG AND RESTARTING MY COMPUTER EVERYTHING IS A-OK. SORRY,
TAZZ1

Bug Report: The keyboard focus doesn't automatical...

Bug Report: When a conversation window opens, the focus doesn't automatically land in the chat entry text field.
Since the new interface for Skype was introduced officially in Skype 7.0, there is a bug with the system/keyboard focus for a new conversation window. When Skype is in "Split Window View" and each new conversation automatically pops up in a separate window, the system/keyboard focus doesn't land in the chat entry edit field. Instead, the user has to press Shift+TAB a couple of times, to move it there and reply to the chat message received. This especially problematic for screen reader users, who rely on keyboard navigation. This mainly occurs when a new conversation is started with an incoming message, but it sometimes occurs when moving the focus out of that conversation window and later back in it again (while it is still opened).
Steps to reproduce it:
1. From "View" menu, activate the "Split Window View", if it is not already enabled.
2. From Tools -> Options -> IM & SMS -> IM settings, enable "Open a new window when I receive a new message in Split Window View", if it is not already enabled.
3. From Tools -> Options -> Advanced, activate "Enable accessible mode", if it is not already enabled.
4. Activate the "Save" button, to save the changes.
5. Close all windows, related to Skype. You may keep only the main window opened.
6. Tell someone to send you a chat message. When the message arrives, Move the system focus to the conversation window in question, preferably with Alt+TAB. The system/keyboard will not land in the chat entry edit field as it did in Skype 6.21 and earlier and as it should by default, but in some unknown place in the window.
7. Move the system/keyboard focus in the chat entry edit field and keep it there.
8. Switch to another window, preferably from another application.
9. With Alt+TAB, switch back to the window of the opened Skype conversation. There is a chance that the system/keyboard focus will not land in the chat entry edit field as it did in Skype 6.21 and earlier and as it should do by default, but again in some unknown place in the conversation window. But that is harder to reproduce.
Test environment:
- Operating system: Windows 8.1 Pro N, 64-bit, in Bulgarian with all locale settings set to "Bulgarian".
- Skype version: 7.0.0.102 for Desktop.

This is a known problem, but Skype have not given us an estimated time for a fix.
Traditionally, Skype updates have been roughly monthly, so we are due a new version sometime soon. Many of us here are hoping that is has a bunch of fixes for the UI, the focus problem being one of them.
Sean Ellis - uses Skype chat for serious work
Click here to read my blog post on Skype 7 and basic principles of GUI design

Bug report: Naming a Bin after creating it with drag'n'drop

There seems to be a small bug when giving a newly created bin a name after creating it by drag'n'drop of several clips onto the "New Bin" icon.
To reproduce:
Select some clips in your project browser
Drag them onto the New Bin button
A new bin is created with the clips in it
- the bin name for it appears to be selected, and editable - just as if you had created a new empty bin by clicking the New Bin button
- type in a new name - it accepts the name fine, now press enter.
- your new name disappears, and *now* you are really in the mode to edit the bin name
- type your name again, and it works.
Work around:
When creating new bins by using drag'n'drop of clips onto the New Bin button, first press enter once to enter into the proper edit mode before giving the bin a new name.
(is there a better place to file bug reports?)
Version 6.0.1 (014 (MC: 264587))
Hardware Overview:
Model Name:          Mac Pro
Model Identifier:          MacPro5,1
Processor Name:          Quad-Core Intel Xeon
Processor Speed:          2.8 GHz
Number Of Processors:          1
Total Number Of Cores:          4
L2 Cache (per core):          256 KB
L3 Cache:          8 MB
Memory:          8 GB
Processor Interconnect Speed:          4.8 GT/s
Boot ROM Version:          MP51.007F.B03
SMC Version (system):          1.39f11
SMC Version (processor tray):          1.39f11
OS X 10.6.8

Er, just answered my question about bug reports by reading the "read this before posting" link above
But I'll leave this here for the work-around in case anyone else needs it.

Bug Report: Shortcuts for Adjustments in 3.1

I have verified that bug with a brand new test account (Aperture 3.1 and OS 10.6.4 with latest Pro Update):
- Make an adjustment to an NEF-file
- save that adjustment as a preset
- assign a keyboard shortcut to that specific adjustment
Switch to the next NEF-file and make your usual adjustments:
- initiate that shortcut to apply the already saved preset/adjustment
All of a sudden, all already applied adjustments are set back to defaults!!!!
To sum up:
Shortcuts are presently not useable!
Bug Report was filed!
Any observations???

I got it myself. My shortcut combination contained the option key. That causes AP to replace any adjustments already made to the image. You have to use a keyboard short cut combination without the option key.
The question is, why AP 3.1 is not smart enough to refuse such a combination??? In version 3.0.x everything worked fine!!!

Bug report: A keyboard layout is incorrect on the remote with Japanese keyboard

This is a bug report for Microst Remote Desktop
===================================================
## Summary
A keyboard layout is incorrect on the remote with Japanese keyboard
## Version Information, I tested
* Client
   * Case 1
       * MacBook Pro with JIS106 Keyboard
       * Mac OS X Lion 10.7.5
       * Microsoft Remote Desktop 8.0.24308
   * Case 2
       * MacBook Pro with JIS106 Keyboard
       * Mac OS X Mavericks 10.9.1
       * Microsoft Remote Desktop 8.0.24308
* Remote
   * Case 1
       * Windows 7 Professional Japanese
   * Case 2
       * Windows Server 2008R2 Datacenter Japanese
   * Case 3
       * Windows Server 2012R2 Datacenter Japanese
## Detail of bug
When login from Mac OS X with Microsoft Remote Desktop, the keyboard layout is always incorrect on the remote.
The client machine have a built-in keyboard of JIS 106 layout,
and the primary language is set to Japanese.
But on the remote, the keyboard layout is US 101.
So a input of Shift+2 does not result " but @.
I've seen the above behavior on the 3 remote enviornments described the above.
This bug did not occcur with Microsoft Remote Desktop Connection Client for Mac 2.1.1, even if the system language is English and keyboard layout is Japanese.
## Captures
I've took some of screen captures.
I'm sorry for the capture includes Japanese words, so I added description in English.
Capture 1:
Mac OS X Keyboard Setting
Capture 2:
Windows Server 2012R2 Screen Keyboard
Capture 3:
Windows Server 2012R2 Screen Keyboard, with a additional registry key configured.

This bug also affects the Canadian English settings. If the client is set to Canadian English with a US keyboard the remote server is setup using a Canadian French keyboard. Using the language selection in the toolbar you can temporarily correct
the problem but the keyboard resets to french at the most inopportune times. The was a problem in the earlier RDP client and was fixed so it's sad to see it reoccur in the new client.
Lawrence

Bug report: A keyboard layout is incorrect on the remote with Hungarian and other "exotic" keyboard layouts

This is a bug report for Microst Remote Desktop
===================================================
## Summary
A keyboard layout is incorrect on the remote with Hungarian keyboard
## Version Information, I tested
* Client
   * Case 1
       * MacBook Pro with HU101 Keyboard
* Locale: Hungarian
       * Mac OS X Maverics 10.9.2
       * Microsoft Remote Desktop 8.0.6
* Remote
   * Case 1
       * Windows Server 2003 R2 (English)
   * Case 2
       * Windows Server 2008 R2 (English)
   * Case 3
       * Windows 8.1 (Hungarian)
## Detail of bug
When I connect to the listed remotes the client sets the keyboard layout to Latvian which is a completely different layout than Hungarian (not even close...).
- On Windows 8 if I set the language on the login screen it stays on that language after the login.
- On Windows Server 2003R2 and 2008R2 even if I set the language at login it will switch back to LV after the login.
## Attachments
Unfortunately cannot include my shots because I'm not allowed to do this...
## End of report
Please allow the users to set the correct "target" language on connection basis because the automatic method the app use to determine that is unreliable.

Hi,
Thanks for the feedback.
I will forward this to the product team.
Thanks.
Jeremy Wu
TechNet Community Support

Bug Report: New conversation window stills the sys...

Bug Report: Skype Desktop: New conversation window stills the system/keyboard focus.
When the UI is in multi-window mode and a conversation window pops up (due for example to a newly received chat message), that window steals the system/keyboard focus, even though it appears in a minimized state in the Windows taskbar. And this should not happen by default, because it is impractical (especially for screen reader users). And it didn't happen in Skype 6.21 and earlier. But since the new UI was introduced officially in Skype 7.0, it started happening constantly.
Steps to reproduce it:
1. From "View" menu, activate the "Split Window View", if it is not already enabled.
2. From Tools -> Options -> IM & SMS -> IM settings, enable "Open a new window when I receive a new message in Split Window View", if it is not already enabled.
3. From Tools -> Options -> Advanced, activate "Enable accessible mode", if it is not already enabled.
4. Activate the "Save" button, to save the changes.
5. Close all windows, related to Skype. You may keep only the main window opened.
6. Move the system focus to another application.
7. Tell someone to send you a chat message. When the message arrives and the conversation window pops up minimized in the Windows Taskbar, everything seams to be as it should. A few seconds after that however, the system/keyboard focus gets moved to that new conversation window, even though it is neither restored/maximized (it is minimized), nor it is visible on the screen (except as a button in the taskbar).
Actual results:
When a new conversation window pops up in the Windows taskbar, it stills the system/keyboard focus to itself from the currently focused application.
Expected results:
Skype's popping up new conversation windows should not still the system/keyboard focus to themselfs from the currently focused application.
Test environment:
- Operating system: Windows 8.1 Pro N, 64-bit, in Bulgarian with all locale settings set to "Bulgarian".
- Skype version: 7.0.0.102 for Desktop.

This is a known problem, but Skype have not given us an estimated time for a fix.
Traditionally, Skype updates have been roughly monthly, so we are due a new version sometime soon. Many of us here are hoping that is has a bunch of fixes for the UI, the focus problem being one of them.
Sean Ellis - uses Skype chat for serious work
Click here to read my blog post on Skype 7 and basic principles of GUI design

Soundtrack Pro 2 keeps crashing...please somebody help :(

So here's my problem.
I am running Soundtrack Pro 2 on my Mac Pro along with my Digi003. Both Final Cut Studio 2 and Logic Studio 8 are installed on my computer. Every application works fine except for STP2 that keeps crashing all the time.
I tried to uninstall it, reinstall it, reinstall Compressor, downloaded updates, Core Audio updates as well for the 003, downloaded the last Pro Applications Support but nothing seems to cut it.
The issue is as follow. I launch STP, the application scans (for the hundredth time) my plugins and detects something like 287 plugins. HOWEVER, the application crashes when the counter goes to 290.
My personal feeling is that the problem might come from either a conflict between Final Cut Studio 2 and Logic Studio 8 that installed both STP2 or, most likely, three plugins (the difference between 290 and 287) that STP2 has a problem with.
These last plugins scanned seem to be Amplitube X-Gear, a demo I deleted, Melodyne, that I downloaded lately and I guess something else. Also, I precise that I have not been able to rn STP for almost a year and as I am about to work on the post of a new film, I would love to use it.
The last thing I did was running the Terminal app that gave me a detailed report of the problem. I don't understand where it comes from though. So here's the report. If somebody can help, I greatly appreciate it!
Terminal Report :
Last login: Tue Nov 4 12:04:29 on console
/Applications/Soundtrack\ Pro.app/Contents/MacOS/Soundtrack\ Pro; exit
Welcome to Darwin!
romain-battaglias-computer:~ Romain$ /Applications/Soundtrack\ Pro.app/Contents/MacOS/Soundtrack\ Pro; exit
Soundtrack Pro(501,0xa000d000) malloc: * Deallocation of a pointer not malloced: 0x740073; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug
Soundtrack Pro(501,0xa000d000) malloc: * Deallocation of a pointer not malloced: 0x2f003c; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug
1
2
Soundtrack Pro(501,0xa000d000) malloc: * Deallocation of a pointer not malloced: 0x10d8b000; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug
IKDriverAPI::Allocate
IKDriverAPI::IKDriverAPI
IKDriverAPI::Connect
IKDriverAPI::Disconnect
IKDriverAPI::Free
com.apple.soundtrackpro
2008-11-04 12:34:19.153 Soundtrack Pro[501] NSExceptionHandler has recorded the following exception:
NSUncaughtSystemExceptionException -- Uncaught system exception: signal 11
Stack trace: 0x95a5c521 0xffffffff 0x9011072c 0xffffffff 0x2949295d 0x90ccf800 0x90ccf7da 0x90ccece2 0x90cd4354 0x0016a859 0x0016aad3 0x0016be76 0x0016c3bb 0x0016b527 0x9326fc9f 0x9326f8fc 0x9326ee45 0x93266479 0x93265ea9 0x93265b0a 0x95f2fd2d 0x95f2fff0 0x95f2ff10 0x0016dbc6 0x0016b4a6 0x0027fab4 0x927f2237 0x908553d2 0x9084cb51 0x927ea7c8 0x927f1769 0x9327a976 0x9327a860 0x9327a35d 0x93279f28 0x927f7f21 0x927f7d4b 0x915226c5 0x915225f6 0x915224c2 0x92df5084 0x9327811d 0x93277b37 0x932718c4 0x95e011b3 0x0027d129 0x0000352e 0x00003455 0x00000001
2008-11-04 12:34:19.153 Soundtrack Pro[501] Exception raised during posting of notification. Ignored. exception: Uncaught system exception: signal 11
Killed
logout
[Process completed]

Probably an imcompatible plug-in.
Try renaming the plug-in folder momentarily, see if it boots okay.
If it does then you'll have to isolate which plug-in is causing the problem.

Bug Report: DW CS5.5 Crashes Every Time On An Image Map

I am posting this in lieu of contacting Adobe support. I went to my account to send Adobe a bug report and was told I needed to contact support via phone. That's pretty crappy. As a licensed user who's owned it less than three months, there's no direct path to tell you guys that your software is broken?
Here's the deal: I am working on an HTML landing page with one image map attached to one image. Literally, every time I make a modification to the code near the image (tied to the image map) then click into the live preview window, Dreamweaver CS5.5 crashes like a 70-year old on a bar of soap on the floor of the shower. It crashes hard. My only relief is to save the file before clicking into the live preview window. That's my only workaround to the problem.
But I'm left amazed that I can crash it every single time over an image map, flicking from the code to the preview pane. You would think that at version 11.5, a minor thing like that wouldn't hemorrage the supposed creme de la creme of web design software.
Here's the code I'm editing that causes it to crash:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
          <?php
          require_once("/var/www/html/c/index.php");
          $recip_name = $subscriber['first_name'].' '.$subscriber['last_name'];
          ?>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<link href="/c/print.css" type="text/css" rel="stylesheet" media="print">
<title>Membership Special - No Commitment</title>
</head>
          <?php // Google Link Tracking Code ?>
          <script type='text/javascript' src='/c/google-analytics-code.js'></script>
          <?php // End Google Link Tracking Code ?>
    
          <link rel="stylesheet" type="text/css" href="http://yui.yahooapis.com/2.9.0/build/reset/reset-min.css">
    <style type="text/css">
                    body {font:normal 14px/1.25em Georgia, "Times New Roman", Times, serif;}
                    h1,h2,h3,h4,h5,h6 {font-weight:bold;color:#333333;}
                    h1 {font:normal 28px/1.5em "Trebuchet MS", Arial, Helvetica, sans-serif;}
                    h2 {font:normal 24px/1.5em "Trebuchet MS", Arial, Helvetica, sans-serif;}
                    h3 {font:normal 20px/1.5em "Trebuchet MS", Arial, Helvetica, sans-serif;}
                    h4 {font:normal 16px/1.5em "Trebuchet MS", Arial, Helvetica, sans-serif;}
                    h5 {font:normal 12px/1.5em "Trebuchet MS", Arial, Helvetica, sans-serif;}
                    h6 {font:normal 8px/1.5em "Trebuchet MS", Arial, Helvetica, sans-serif;}
                    a, a:link, a:visited, a:active {color:#0055FF;}
                    a:hover {color: #002AFF;}
                    #wrapper {margin:0 auto;width:432px;}
                    #header, #footer {margin:20px auto;text-align:center;position:relative;}
                    #footer {margin:40px auto;}
                    #coupon {position:relative;}
                    #coupon, #coupon img {margin:0 auto;text-align:center;}
                    .personalization {position:absolute;width:100%;text-align:center;text-transform:uppercase;}
                    .printcoupon {text-transform:uppercase;}
          </style>
<body>
<div id="wrapper">
<div id="header">
          <h3 class="printcoupon"><a href="javascript:window.print();">Click here to print your coupon</a></h3>
</div>
<div id="coupon">
          <img src="images/19415coupon-01.jpg" width="432" height="432" />          
<img src="images/19357coupon-02.jpg" width="550" height="602" usemap="#imagemap" class="dontprint"/>
</div>
<div id="footer">
          <h3 class="printcoupon"><a href="javascript:window.print();">Click here to print your coupon</a></h3>
</div>
</div>
<map name="imagemap">
          <area coords="29,69,521,197" shape="rect" href="javascript:window.print();">
          <area coords="29,212,521,339" shape="rect" href="http://www.google.com" target="_blank" onClick="recordOutboundLink(this, 'Landing Page', 'http://www.google.com');return false;">
                    </map>
</body>
</html>

Bug Report and Feature Request https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

Minor bug report SoundTrack Pro

Similar Messages

Maybe you are looking for