CS4 Bin Naming Bug

When creating a new bin you cannot see what you are typing until you hit enter. Strange...

You have to initiate the rename process to be able to see what you're typing. I'm amazed that you even get to rename the clip when you press enter. In other words, creating the bin does not leave the bin name in "edit mode", you have to
put it in edit mode.
Cheers
Eddie
PremiereProPedia (
RSS feed)
- Over 300 frequently answered questions
- Over 250 free tutorials
- Maintained by editors like
you
Forum FAQ

Similar Messages

[CS4 Win] Weird 'Bug' giving overset text in duplicate object - stumped!

Hi all,
I am experiencing a perculiar 'bug' in InDesign CS4 (Windows).
I have a triangular text frame rotated by 45° with a 0.2mm inset.
This frame contains two words who's point size is just big enough to fit the text in the frame without it oversetting.
The leading is set to 100% of the point size.
When I duplicate the text frame either with the Duplicate command, cut 'n' paste or alt dragging, the new text frame is overset!
I cannot find any difference between the two objects what so ever.
If, in the original text frame, I change the text frame options inset to 0 and then back to the original 0.2 mm, I get overset!
Scaling the original up by any amount also causes overset, as does increasing the height of the frame and then returning it to its original height.
I have tried exporting as a snippet but the new placed text frame oversets.
Does anyone have any idea might be causing this behaviour.
It doesn't do it in CS3 or in CS5.
I have included a link to an example file, you will need to have the same font (HelveticaNeueLTPro-BlkCn) to see the problem.
I can't upload this for obvious copyright reasons - sorry.
http://dl.dropbox.com/u/7307068/flashes.indd
Thanks for ANY input.
Simon Kemp.

Hi Simon.
My initial reaction was it might have to do with the third party plugins, but I exported to .inx to strip them out, and then NONE of the frames had both words. I also thought it might be that the the frame isn't a right triangle and the slight angles on the vertical and horizontal might be a problem, but I made a new frame with the same hypotenuse but the correct legs, and that didn't make a difference, either. (I made it by drawing a rectangular frame exactly half as high as it was wide, adding a point at the center of the top path segment with the pen, then deleted the two upper corner points).
I have to say my conclusion is that the problem here is there really isn't enough room in the frame for both words with that inset. Adding 3% to the size of the frame (by clicking the chainlink to link changes to height and width, then typing +3% after the height [adding in the scale fields scales the type, too, so don't do it there] and pressing Enter) brings both words into view.
Curiously, When I opened the file in CS5, the words fit without messing around. Cutting and pasting the frames with overset made both words appear. This could be due to the new way ID deals with text in non-rectangular shapes. When I opened the .inx file without the plugin information in CS5 all the text was visible in all frames. I think the only reason the text ever fit in the original CS4 file might have to do with one of the plugins, but that's pure speculation. I don't think there's any sort of bug here.

5.4 Adjustment brus bug + File export naming bug

There appear to be two bugs in 5.4
1. I just finished editing an intense adjustment brush edit. I went to tweek it when I opened the brush there are no pins to activate even though the edits are there.
2. Export file naming not working correctly. I always use export "Title plus file number" or "Custom name - original file number" Neither of these exports include the file number.
3. Did 5.4 change somthing in the configuration settings. If not, is there a way to restore 5.3 until these bugs are fixed.
Jim

Regarding item 1, the pins can be visible or not visible or conditionally visible. The option to do this is at the lower left of the tool-options bar available when you press the T key to toggle it on and off. If you feel your pin-visibility options are set properly, please show a print-screen with the pins not there and the pin-visibility options set to Always.
Not sure about item 2 as I don’t use it.

Thoughts about the bin window - bugs or features and workarounds...

Hi there,
I really have big toubles using the bin window. It is even worse in OSX.5 (the only thing I don't like with OSX.5 and Logic8!).
There are some Problems:
1. I can't move any audio-files to wherever I want them to without Logic is copying them back into the audio-folder by saving the song. The problem is that I want Logic to copy imported audio files into the audio-folder but if I change something manually Logic should remember that without working against me. So for example: I am bouncing a lot of audio into the bounce folder. In Logic 7 all the finished bounces were located there on the hard drive. Easy to find and to organize. But in Logic 8 they are moved to the audio-folder and I have to search very carefully which files I want to send to my client. That's the biggest source of trouble for me right now.
2. If I am making groups, Logic is sometimes copying even that audio-files back into the normal audio-folder. The problem here is: sometimes. I really have no idea what the problem is. Sometimes just some audiofiles are staying in the group (on the hd) for a couple of Logic-saves and then are moved back at the 10th save or something.
3. I am not able to organize my groups and audio files very well. So if I have group that always is shown on top of the bin window and I have a audio-bounce called "zoo" it is the last one in the list. Then I have to move it the whole way up to the group. That costs me about a half our per day. Way too much. There should be some kind of easier handling. For example a second window for groups or something. The next one is that I have to call the group something like 001AASFX or ZZZ_SFX so that I am able to find it fast enough in the finder. It was so much easier to go the bounce folder in Logic 7 days.
4. The hide-regions keycommand was unstable with OSX.4.10 but now with OSX.5 it is not working at all. If I choose a audiofile in the bin window and hit the standard keycommand for hiding regions just the region for that audiofile is hiding and instantly shown again. I want to have a shorter way to move my bounced files into the group that is the whole way up to the list's beginning.
So I wonder if that are new features or if it is really buggy. I am not able to work with that structure right now and with that kind of unstable location behavior. Are there any workarounds, tips, tricks? Is there anyone who feels like me? May I hope for a update?
That's it
Xcell
Message was edited by: Axel Rohrbach

Hey Jim,
thanks for the support. Seems to be something Apple has to work on. There are some posts and questions about the bin window in every forum I know but there is never a "this is not want we want and there are bugs" - thread. In fact the whole Logic 8 structure with the one-window-gui is great and works much better than I expected. So it is no general "what the **** are they doing"-thing
Nevertheless, is there a way to get this to apple? I don't know if they are aware of these problems and perhaps the testers are making music with one bounce and that's it. Just one file is not that difficult to handle, organize and to find. But there are other users working in different ways (like us I think).
@ David: I am sorry but you are wasting time and thread-space. If you don't say anything if you do not feel comfortable nothing will change. You are not able to let it rain in Austria (yet) but there are real guys working at apple and it's not a kind of wonder that there is logic at all. So am trying to discuss here something and hope for any reaction or attention and don't need any "go deeply into your self and you will find a way"-stuff. Thanks anyway to bring god back to that forum.
Xcell
Message was edited by: Axel Rohrbach

Illustrator CS4 Action Palette bug

Does anyone know if the action palette bug has been addressed? I saw a thread from Nov 2008 that confirmed I am not an isolated incident. I can't get all the steps in my action to save when I reopen Illustrator. Particularly "show all layers". I am working in 10.4.11, and I don't see any Illustrator updates available to me at this time. Thanks!

That's funny it doesn't happen here and don' get this wrong but it seems odd that you have been working with CS 4 all this time and never brought this issue up before.
Of course you could be on windows and it could be a platform specific issue though it seems odd that all this time has passed and it is the first we are hearing about it.
This is what my CS4 looks like after I relaunch AI.

Photoshop CS4 brush cursor bug on Thinkpad T61p

I've got a Thinkpad T61p with a Nvidia Quadro FX 570M onboard (driver version: 6.14.11.7471). There seems to be a bug with the graphics driver in conjunction with the new Adobe Photoshop CS4. Photoshop now uses GPU-optimization with more brush capabilities. Unfortunately the cursor clips when using brush-sizes larger than 64px. One can see the bug on the nvidia cs4 promotion "brush resizing" at http://www.nvidia.com/object/adobe_photoshop.html. Nvidia corrects this bug in newer driver versions, but lenovo only offers a WinXP-display-driver from 2008-04-28.
Does anyone know any workround? I've tested somo older forceware drivers (178.24) with partial success. The display bug in Photoshop is fixed, but e.g. After Effects CS4 crashes while detecting the GPU.
Message Edited by mikey on 10-23-2008 03:20 AM

Today I've installed the latest Forceware Drivers 180.60 from http://www.laptopvideo2go.com/ to test the bug behaviour.
The brush cursor now seems to be able to handle big brush sizes but the performance is reduced noticable.When painting inside a new document the rendering of the brush path is done after painting over the area, even when using small brush sizes.
So let's wait until Nvidia/Lenovo roll out a new driver.
Message Edited by mikey on 11-24-2008 07:57 AM

Photoshop CS4 Snow Leopard Bugs: Cursor Position & Grains

Currently running OSX Snow Leopard (10.6.1), and just installed the latest Adobe updates this morning (9.22.09).
There are two bugs in Ps CS4 I've encountered, one minor but aesthetically unpleasant, and the other major and disrupting:
The first bug occurs at random when Ps is extended to "Full Screen Mode with Menu Ba." As seen in the image at the following link, graininess occurs in Ps's canvas background, and wont disappear until the screen mode is toggled (pressing the "F" key three times): http://img.skitch.com/20090922-tyxk4dfrak4dtf2f4rg7fgyn59.jpg Again, not a major bug, but simply annoying to look at.
The second, more annoying bug, has to do with the cursor and selection tools. I could not determine when exactly this happens and how it goes away, but a few times throughout the day the selection cursor is a few pixels off. When either the lasso, magic wand, marquee or other similar tools are selected, the actual area from which Ps begins to select is about 10-15 pixels below the cursor position, see image in link for clarification: http://img.skitch.com/20090922-1jyqdtj34xw99ysq4gjxhxx57c.jpg
I hope this notice gets the bugs fixed. If you're experiencing similar Snow Leopard side-effects and can detect how and when they occur, please let me know. The canvas background pixelation, I can live with...but the cursor selection bug makes my day twice as difficult and slows my workflow down to a snail's pace.

Not sure about the graininess as I have never seen it but it seems to be the same fix as for the curser being off by 10 pixels. cycle though the screen modes with the F key. this has nothing to do with Snow Leopard as it is present in both Tiger and Leopard as well.
This bug is only present when you create a new doc in full screen mode. If you are a new convert to Mac from Windows you might want to use the application frame, this will give you the gray background without those two annoyances. You can find the application frame at the bottom of the Window menu. this is a new feature on the Mac version with CS4.

Photoshop CS4 serious dragging bug

I'm running Photoshop CS4 in two different MacBook Pro's unibody, both with 10.6.4 installed, both PSD versions are separate copies with different licenses and both are updated to the latest release, 11.0.2.
In both machines I've experienced a serious dragging issue that so far seems to be related to something in Safari, particularly when I drag an image straight from the browser to the photoshop window. The bug consists of immediately any function that includes dragging something across the screen (painting, scaling, panning, cropping, rotating, you name it) becomes impossible to do, and the screen "stutters" all over the place for several seconds until the issue goes away itself. The problem has become super frequent in one of my computers, the newest one which I mostly use with an intuos 4, the other one I use with an intuos 3, as mentioned before both laptops are unibody, but one i got in december 2008 and the other one in february 2010.
The issue has gotten to the point where it is almost impossible to work with that computer, as it is happening sometimes up to 5 or 6 times each minute.
Any thoughts will be greatly appreciated.

From the PS CS4 manual:
Change the Color Picker
Instead of using the Adobe Color Picker, you can choose colors from your computer operating system’s standard Color Picker or from a third party Color Picker.
1 Choose Edit > Preferences > General (Windows) or Photoshop > Preferences > General (Mac OS).
2 Choose a Color Picker from the Color Picker menu, and click OK.
For more information, see your operating system documentation.
Note: To return to the Adobe Color Picker, choose it from the Color Picker menu in the General Preferences.

CS4 Crash 8Kb bug related

Dreamweaver crashes repeatedly. Believe the problem is related to the 8 kb bug. Have found several files with size 8 192 kb. Actual file size is less and differs but File size on disk always 8 192 kb.
Most, but not all, new saved html-files get this file size on disk even if edited outside of Dreamweaver in a text editor.
As adding new lines only effects the actual file size this is not a solution to the problem.
Have deleted the cache file - didn't help.
Also renamed the personal configuration folder but that didn't help either
Solution to this problem appreciated!!

I was the person who discovered the 8KB bug in Dreamweaver CS3. According to the Dreamweaver engineer who helped identify the cause of the problem, the bug was fixed in Dreamweaver CS4, so it's unlikely that it's the same problem, particularly since adding extra lines to change the size of the file was the workaround for the original bug.
You need to submit a detailed report of your problem to Adobe through the bug report form, which can be found at http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform.

Is This a CS4 Flash Remoting Bug?

I think I have discovered a bug, but am looking for others to comment and maybe somebody knows of somebody else that has experience with this issue.
I have a very large flash app I am working on for a multi-user RPG game, it relies heavily on flash remoting via AMFPHP so that flash clients logged into the game may communicate with each other and the main game server which handles database storage, the game heartbeat functions,etc.
I have been developing the app on Flash CS4 for Windows and never have had any trouble, it works fine in the IDE environment when testing the movie and the published version works fine as well.
Now I have a Mac version of CS4 and I am getting some crazy problems running the app in Test Movie mode in the IDE.
After I start the app in Test Movie mode and run it for a few seconds all flash remoting stops working, the game continues to run and no error messages are generated but all of the NetConnection calls do no do anything, they do not connect, they generate no errors. Ok, thats strange enough but now, if I kill the Test Movie and rerun it via Test Movie no NetConnection calls are made and the initial .connect call does not go through, I have watched the server logs on the other end and no attempts to reach the gateway.php are made. This continues until I unload all of the .fla and .as files associated with the project and then reload them, and then it starts again, works the first time for 5 seconds or so and then all NetConnections stop completely.
So to summarize what I think is a bug specifically for the Mac platform of Flash CS4 Professional:
1. Projects works fine in Flash CS4 for Windows
2. In Flash CS4 for Mac, the project runs for about 5 seconds in Test Movie Mode and then all NetConnection activity stops
3. No errors are generated for the NetConnection
4. Continues to fail even restarting the project until I close the files and re-open them in the IDE
Sounds like a bug, does anybody know of others with this problem, or does anyone have anything I can try?
Thanks,
Andy

The application doesn't hang but the TextBlock ends up on top the Button when you set its Text property. That's why you cannot click on the Button.
If you set the Text property of the TextBlock in the XAML markup you won't be able to click the Button when you run the app because of the same reason:
<TextBlock x:Name="OutputMsg" Text="sample text"
Margin="0,200,0,0"
HorizontalAlignment="Center"
FontSize="18" />
The solution is, like you have already discovered, to put the TextBlock in the StackPanel so it ends up
below the Button and not on top of it in the same Grid.
Please remember to mark helpful posts as answer to close your threads and then start a new thread if you have a new question.

Bridge CS4 No Scroll Bug

When you select Output workspace, you can't mouse scroll through the right hand pane. It doesn't matter what output option you have chosen, PDF or Web Gallery. However, in the Content tab mouse scrolling works fine as do all of the other workspaces.
I think this is a bug as it makes no sense as to why it doesn't work.

I think you might have misunderstood me. Let me try and explain a bit better.
- Open Bridge CS4
- Click on the Output tab in the top right hand or Command F4.
- Select PDF or Web Gallery
- Open all of the panel options, (Site Info, Color Palette etc for Web Gallery)
- The scroll bar is now visible, position your mouse over any of the open panels, now try and scroll up or down, nothing.
If you position the mouse pointer over the scroll bar, you can scroll. With the pointer over one of the open panels you can't scroll.
Now some would say that is normal since that particular panel is entirely visible but, if you position one of the open panels near the bottom so it is not entirely visible and hover the pointer over that panel, scrolling does not work. This is a bug IMHO.
OS 10.4.11, 2.66 GHz Intel
Bridge 3.0.0.464

Dreamweaver CS4 Search Folder Bug (?)

Just curious if anyone else has this issue:
When doing a search and wanting to only focus on a specific folder within the root, I have to go one folder deeper to have Dreamweaver select the folder I actually want.
For example, if I want to search files within /root/main/ I have to actually select /root/main/subfolder/ to have Dreamweaver actually search the "main" folder.
Is this a bug or just how the search folder works?
Dreamweaver CS4 (10.0 build 4117) for Windows 7

It's a well-known issue. See http://forums.adobe.com/thread/478327.

Fix Dreamweaver CS4 Color Eyedropper Bug

Dreamweaver locks up when using the eyedropper from the CSS
panel to select/match a color from any object in Design view.
Easiest to explain by describing a split view. Dreamweaver locks
every time -- when placing cursor in a background color code in a
style sheet, then going to the CSS panel and selecting the
background color swatch for that style, then with the eyedropper,
touching a color in the Design view part of the split screen.
Dreamweaver CS3 never locked up when performing these same
steps. Dreamweaver CS4, locks up whether selecting a color in a
bitmap or a CSS background color that is displayed in the Design
split view. Means I have to go to Fireworks to color match, and if
the color I want is in a range of a gradient, I have to make the
gradient a bitmap before selecting the spot with the eyedropper. I
even had some difficulty in Fireworks, as the selection wouldn't
show up in the color panel when I touched the bitmap with the
eyedropper. I could see the color code in the popup color selector
and clicked there for the color to show up in Fireworks' color
panel.
Kind of a hassle...would be nice to get an update fix for
this.

prjviera wrote:
> Dreamweaver locks up when using the eyedropper from the
CSS panel to
> select/match a color from any object in Design view.
This is a user-to-user forum. If you have found what you
believe to be a
bug, please file an official report giving as many details as
possible
to reproduce it. The official report form is here:
http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
David Powers, Adobe Community Expert
Author, "The Essential Guide to Dreamweaver CS4",
"PHP Solutions" & "PHP Object-Oriented Solutions"
http://foundationphp.com/

CS4 Floater Size Bug

I have some floaters which work fine in CS3 but when I view
them in CS4 the floaters are not sized properly. I can manually
resize the floaters, but neither windowDimensions() or
window.resizeTo() are working properly. window.resizeTo() actually
draws a grey area the proper size, but the actual floater window
does not change size.

fletc4her,
Please submit a bug report here:
http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
Thanks,
Randy
> I have some floaters which work fine in CS3 but when I
view them in CS4 the
> floaters are not sized properly. I can manually resize
the floaters, but
> neither windowDimensions() or window.resizeTo() are
working properly.
> window.resizeTo() actually draws a grey area the proper
size, but the actual
> floater window does not change size.

Edit Naming Bug

Just tried to edit a file name after editing in PS.
God it's painful to do, even after you work out how on earth to do something that is normally so trivially easy.
LR imports and displays a file called say
"2007-03-15 Betty 004 Provia+Lomo-ed.psd"
no problem, yet when I try to edit it to read
"2007-03-15 Betty 004 Provia + Lomo-ed.psd",
LR changes it to
"2007-03-15 Betty 004 Provia @ Lomo-ed a [email protected]",
Edit name again and I get
"2007-03-15 Betty 004 Provia @ Lomo-ed a bit@[email protected]"
where the @ symbol is actually a crossed out box in LR. ??????!!!!
Now after a bit of playing around, I discover that if you edit an name, LR adds extention automatically, even if it's aready there. Duh! So, if you edit a filename to correct a typo you also have to remember to delete the extension as LR adds it automatically. Not only that, undo doesn't correct the extention bug even though it corrects the name edit.
I assume it was thought by the designers, if you are going to edit a name, you replace all the name and do not have to worry about the extention. Obviously, nobody ever changed their mind or spotted a typo when designing this feature. Bridge allows single file reanming/editing simply and elegently. LR + Bridge are made by the same company aren't they?
Yet again LR takes a normally very simple thing, overcomplicates and breaks it and not only that, does it differently from other Adobe apps which weren't broken.
Plus - why can't I have a '+' sign in my file names or a ',' for that matter, they've worked until now with no problems. Are vowels going to be forbidden next?

Thanks for your reply Justin. I know how to name "audio objects" I've done it many times... but now with this new feature, where logic does it automatically, it does not seem to work properly. When I type in the name I want to be displayed, it does not change in the arrange window, as it used to, and should still. Anyway thx for your response.

CS4 Bin Naming Bug

Similar Messages

Maybe you are looking for