Feature request! Respect my preferences

Because I don't see the value in displaying a channel number on my FiOS TV box 24 hours a day, I set it to display the time.
However, every time you (Verizon!) update my box, which has become frequent lately, you ignore my settings and reset it back to the channel number. This means I have to go back through your incredibly slow menu to reset it back to the time display for all three boxes. And frankly, why wouldn't the time display be the default to begin with?
I don't think it's a huge imposition to ask you to keep whatever settings I have set on the box when you reset it. And I will say that we've come a long way since the days when you used to turn off the box after an update. For those of us with DVRs that was a major PITA.

The other thing that I would find very useful is to be able to create repeating ToDos, the way you can in Palm Desktop.

Similar Messages

Feature request: make podcast "Keep" preferences specific to each podcast

I subscribe to many different podcasts of different types for various reasons. With some podcasts I want to retain all episodes in an archive. With others I want to delete them as soon as I have listened to them. With others I might want to keep them for a week or month and then delete them even if I have not gotten around to listening to them. It would be very nice to be able to set a default preference for how long to keep podcasts in the iTunes preferences, just as can be done now, but to be able to override that default preference on a podcast by podcast basis. Please give us this ability to make podcast-specific decisions on how long to keep individual episodes. Thank you for considering this request.

You can send feedback/feature requests directly to Apple at this link: Apple Product Feedback

Feature Request: Standard Keyboard Navigation in Media Browser and Project Panel

It's been a while since I've had time to submit a feature request. I've wanted to see this one for a while. If you agree, please submit your own feature request here: http://www.adobe.com/go/wish/
System Navigational Keyboard Shortcuts in Media Browser and Project Panel
Windows (and I'm sure Mac) has a standard set of keyboard and mouse navigational shortcuts for keyboard and mouse. I'm so used to using them in daily browsing (both in Windows Explorer and in any web browser) that missing them in the PPr Media Browser, or getting a different result in the Project Panel, is still very jarring and slows my workflow (even after having used Premiere Pro [again] since version CS4).
I propose that the Media Browser and Project Panel should honor the OS defaults for keyboard and mouse folder/file navigation. A few of the standard (Windows) keyboard and mouse navigational shortcuts are listed below (listed in order of most helpful to my own work):
Moust Back Button = "BACK"
ALT + LEFT ARROW = "BACK"
UP, DOWN, LEFT, RIGHT = steps through the various folders within the view.
UP, DOWN walks through the directory tree while RIGHT expands the currently selected folder and LEFT contracts that directory (twirl down, etc).
ENTER opens a folder.
ALT + UP = "Folder Above"
ALT + RIGHT ARROW = "FORWARD"
F2 Renames a folder
ENTER "takes" that name to the clip. (current functionality used ENTER to rename a file/folder).
ESC cancels the renaming operation.
Pressing Enter on any piece of Media or Title, etc should take an "expected" action acording to it's context. (i.e. ENTER on a video clip would load it inot the Source Monitor. ENTER on a Title would open it in the Title Editor. ENTER on a folder would take us into that folder).
These functions exist in both Windows Explorer as well as most modern Web browsers. When browsing files and Project folders, it's what I've come to expect. It's muscle memory, if not intuitive. I realize that many of these keyboard commands are already in use in other windows/panels of the application, therefore, these commands should be Panel-specific (i.e. ALT+LEFT works differently in the Media Browser and Project Panel than it does on the Timeline/Sequence). And as always, when making such changes (i.e. changing the behavior of ENTER to F2), this set of keys should be highly configurable based on preference:
Preference:
checkbox: Use OS-specific navigational keyboard and mouse commands in Media Browser and Project Panel
checkbox: Use the (very few) "classic" Adobe keyboard commands in the Media Browser and Project Panel
The most common habit I find myself doing in the Media Browser is clicking the BACK button on my mouse—only to realize, yet again, it doesn't work that way in PPr.
The most common habit I find myself doing in the Project Panel is pressing F2 to rename a folder/bin. Of course that doesn't work. And when I've renamed it, I press ENTER to save the name, but that only moves me to the next folder ready to rename it, too. I also find, out of habit, I try to navigate the bins using the arrow keys and then open the bin/folder using ENTER. Instead, my bin is asking for a new name and I hit ESC to avoid renaming it—now THERE's a shortcut that works the way it should.
I realize this feature may be controversial to some, since it's not the way we're used to doing things in PPr. However, I'm sure there are just as many out there, like me, who are confounded as to why PPr has never worked with the "conventional" navigation shortcuts found throughout the rest of the operating system, be it Windows or Mac.
If you agree with this feature request, please submit your own feature request here: http://www.adobe.com/go/wish/

Nice ideas Jeff.
There is a site - Flash Catalyst Wishlist/Ideas where you can post these ideas so that the community can vote on them.

Feature Request (again); Adobe Bridge Cache Manager

In Adobe Bridge, the Cache is still a problem and a huge memory hog. I asked for a good Cache Manager over 3 years ago when it was needed CS4.
Now in CS6, I am disappointed that the cache system in Bridge has not changed. Why do you have a section in the Adobe Forums that asks for 'Feature Request' and then ignore them?
http://forums.adobe.com/message/2652688#2652688
"I would personally like a tool within Bridge that allows me to manage and control the Cache in a more personal and effective way. I would like a toggle that would keep '100% previews' in one folder for a selected period of time (1 day to 1 month) before the folder's cache is automatically purged. And another toggle that would give me the option to keep a selected folder's cache permanently intact (such as an Important Portfolio Folder or an Edited Images Folder).
As a photographer, I take and edit a lot of photos. When I import a photoshoot with 1,500 photos (not uncommom at all) I enjoy having the Bridge Previews at 100%, but for only a limited time. Unfortunately, I forget to purge the individual cache of that folder and the cache builds to a point that makes Adobe Bridge CS4 very slow. I then have to Purge the whole Bridge Cache in order to make Bridge run smooth again.

gumbogood wrote:
A Cache Manager tool that lets me either schedule a cache cleaning on a folder, or keep it permanent, would be a huge help. And I don't think that it is unreasonable for me to ask this of Adobe.
If you submit a feedback poll where Yammer pointed you, and it gets a couple of hundred (thousand?) users agree you might get Adobe's attention.
I agree with Yammer that Bridge is a low priority project with Adobe. Think their target audience is the casual user with a few hundred photos added each year. Your use pattern is more specialized and you either have to adapt with scripts or move to another product IMO.
The size of cache takes a lot of people by surprise. It can grow humongous if you use HQ thumbs and save 100% previews. One can dump the cache in preferences, but many are reluctant to to this as they think it will delete all their keywords and edits. In addition, to do a search you have to re-index all your files, which can take a long time.
If you have "export cache to folders" checked, dumping the cache in preferences only dumps the central cache. To dump the folder cache you have to visit each folder and click on Tools/cache/purge cache for xxx folder. Again, most people do not recognize this. This technique purges both the central and folder cache for this folder only.
It the 100% previews are the problem for you it would seem like a simple task for the script people to write one that would delete it after xx days as the 100% previews are held in a specific folder.
Bridge is not a good digital asset manager. You are probably in that arena dealing with several hundred thousand images. Omke uses a DAM as it does some functions better than Bridge, but Bridge is still his main program. Can't remember the name, but if you read these posts you might have seen it.

+ Camera Raw Feature Requests +

UPDATE:
We're interested in what changes you would like see in our products. Do you have an idea for a feature that would help your workflow? Is there a small change that could be made to make your life a little easier? Let us know! Share an Idea, Ask a Question or Report a Problem and get feedback from the Product Development Team and other passionate users on the Photoshop Family product Feedback Site on Photoshop.com.
In future it would helpful if you could use this thread as a means to add
"Features" that you would like to see in future releases of Adobe Camera Raw.
Please do NOT create additional new Topics and try not to duplicate requests by other users. Also, be thorough in your description of the feature and why you think Adobe should consider it.
Oh, and if you find it necessary to comment on someone's feature request/suggestion, try not to get into a shouting match. The penalty for doing so is...
b If you're asking that a particular camera is supported in a future release or just taking the opportunity to carp that yours isn't then please do so in another thread!
IanLyons
Forum Host

Here's my wishlist for ACR. I'll list the feature first and then in a separate section afterwards, I'll explain why I want it.
1) Shadow/Highlights
2) Multi-instance and modeless behavior for ACR so I can truly have ACR open, Bridge open, PS open and work in all three and even open another ACR window.
3) The ability to open one image into PS and keep the rest going in ACR when you have multiple images open in ACR.
4) The point locator feature for curves like curves has in PS so you can find out what tone area on the curve a given area in the photo is, just by clicking/dragging over an area on the photo.
5) White balance assist to make it easier to get skin tones right when there are no good grayscale references in the photo.
6) An ACR pref to have a suffix automatically added to each filename when it goes into PS so after editing it in PS, I can just hit Ctrl-S and not have to manually add a suffix onto every single image I edit in CS.
7) A drag/drop bin for recently used saved settings in ACR and shortcut keys for cycling through a preview of those settings (described in more detail below).
8) A pref to allow the Save Images folder in the Save dialog in ACR to default to the directory of the RAW files rather than the last directory used.
9) More sophisticated sharpening in ACR (like smart sharpening).
10) Ability to set label or rating when only one image open in ACR.
11) Ability to delete and close when only one image open in ACR.
12) An easier way to see how a rotated image looks. There is no way in ACR to see the straight version of an image you've rotated slightly.
13) Shortcut keys to cycle through saved curve settings.
Here's the explanation for why I want each of these:
1) Shadow/Highlights. A significant percentage of my images need no other adjustments in PS except shadow/highlights and it's a big workflow savings to be able to finish a picture in ACR instead of having to take it into PS.
2) Multi-instance and modeless. The CS2 behavior is better than it was before because you can set it up for Bridge to host ACR and still be able to use PS. But, I often open many images in ACR and the current design still forces me to serially finish all those images in ACR before I do anything else becuase I'm blocked from going back to either Bridge or PS (depending upon who's hosting ACR) and I can't open any other images in ACR. This forces a serial workflow when sometimes I'd like to be able to be in the middle of one workflow (a hundred images open in ACR), but go do something else in Bridge and PS for a short period of time. I can't do that today.
3) The ability to open one image from ACR into PS while keeping the other images in ACR. When I see the preview in ACR, this is often the first time I've seen my images at any decent size. I often find I want to take a few into PS just to see how well they fix up with certain changes or to see if they benefit from things I can do in PS and can't in ACR, without discarding all the other images I have in ACR at the time. So, again, I am forced to serially finish all the image I have in ACR before I can take any into PS. I'd like to be able to open the selected images in PS and keep the others in ACR.
4) The point locator feature that PS has in the curves dialog is very valuable for finding out where on the curve a given feature in the photo is. I'd like that feature in the PS curves.
5) White balance assist for skin tones. One of the hardest things in ACR is getting the white balance right for skin tones when there is no easy gray reference in the photo. I don't know how it would work (I think this is an area for your invention and cleverness), but I'd like some sort of white balance assist that helps me pick a white balance that leads to a pleasing skin tone. I'd be willing to tell ACR where the skin tone is by pointing at it.
6) I add a suffix of "-edited" to ALL images that I open in PS from ACR. That means I have to type that suffix on every image when I hit the Save command in PS. I'd like a preference in ACR to automatically append a suffix onto the filename when it goes into PS to save me that typing on every single image. I've even tried to figure out if I could write a script in PS to do this for me (if file extension is a RAW file extension when user hits save, then add default suffix to the filename before Save dialog comes up), but I haven't figured out whether it can be done via script or not. I know that others save their PSD or JPEG files to a different directory than their RAW files (I keep all of mine in the same directory so this isn't an issue for me), so I imagine they'd like the ability to specify a default relative path also to save having to point every PSD they save in PS to a new directory.
7) Drag/drop bin for RAW settings. In a workflow of processing 200-800 RAW files, I'd like the ability to easily and temporarily save a small number of RAW file settings (10 would do). I know you can do it in the pull right menu in ACR today, but that's too much typing and clicks to make it worth it. I'm looking for something that allows me to pick a bunch of files from a shoot, identify a representative "sunny" shot and drop it's settings into a bin that I quickly label sunny. Then, when other sunny shots come up, rather than having to scroll around to find that image or go back to bridge to find that image, I just drag it out of the bin an drop it on the selected images. I don't want it to persist globally because then they pile up and I have to clean them up. I do need them to persist between ACR sessions as long as Bridge or PS is still running because I often process my RAW files in many ACR sessions. The whole point is to make an easy place for me to deposit a small number of saved settings so I can easily (very few mouse clicks or keystores) use them again while processing the same shoot. It's all about speeding up the workflow and letting me re-use work I've done earlier in the workflow. In my experience, this happens most often for white balance and curves since I'm more likely to tweak exposure on nearly every shot anyway.
8) When I hit Save Images in ACR, it remembers the previously set directory. In my workflow, I want it to default to the directory of the first image I'm saving. The way it is now, it is NEVER the right directory so I always have to change it. It could be smart enough so my normal workflow never has to change it. Even better, I'd get to set a pref that was a relative path from where the first image is located. So, when I'm saving JPEGs, I could have a default path of ./JPEG (a sub-directory under where the RAW files are located). Other people would want ../JPEG (a sub-directory at the same level as where the RAW files are stored).
9) In the spirit of getting as much of my work done in ACR as possible, I'd like to see a unification of the sharpening functionality so that ACR can do smart sharpening with all the same features. That would again keep many of my images out of PS and drastically improve my workflow.
10) I'd like the ability to set a label or rating when there's only one image open in ACR. Because you can do this when you have multiple images open in ACR, I'm programmed to set this in ACR, but that workflow programming is busted when I only have one image open.
11) I'd like the ability to delete an image from ACR when there's only one image open in ACR. Just like with labels and ratings described above, I'm programmed to want to delete a ruined image when I see it up close in ACR and determine it's no good. In this case, I think I'd like to just hit the trash can icon and have the ACR window close and have the image deleted in one single step.
12) When I straighten an image in ACR, there's no good way to see how the rotated version looks at full size. All you get to see is a thumb in ACR (if you have multiple images open) or a thumb in Bridge. To see whether it rea

Feature Request: Destructive editing with AUs in Sample Editor

I would like to be able to apply edits destructively in the sample edit window with Audio Units like we could in Logic on MacOS9 (which used AudioSuite plugins). This is an ongoing request, year after year, among veteran Logic users. In every update it is ignored. The feature requires no redesign of the sample edit window, just another menu sub item droplist. While the bounce in place feature is a welcome addition, it is not a replacement for this feature that was removed in the migration to MacOSX and has been sorely missed ever since.
Here's just one recent sentiment from a user on the NYC Logic Users Group:
"I recently changed over to Logic from Pro Tools and I really miss this feature! For handling plosives and de-essing small fragments."
I also know a very prominent producer who boycotted Logic 8 and 9 for this reason alone. While I would never do that (since I happen to love all the new features and feel comfortable with the workflow of Logic 9), I sympathize with this person's frustration over the lack of this feature. I find myself constantly in the position of wishing I had destructive editing back in my Logic tool belt.

With all due respect, I personally cannot stand soundtrack. A lot of effort was put into the app that should have gone into Logic. As you allude to, I can trigger that Logic keystroke to open any sample editor, which is what I do. I just want the functionality back that was taken away from us many moons ago. I'm not looking for workarounds. This is just a simple feature request. But thank you for the suggestion.

Feature request: option to deactivate builtin screen when monitor connected

This is a feature request for laptops, or rather for the Air specifically. To see why it might be a good thing, see this thread:
http://forums.macrumors.com/showthread.php?t=449778
I'd like a checkbox in the display preferences to deactivate the internal monitor when an external monitor is plugged in. This would save load on the Air's GPU and reduce heat while using an external monitor.
Users of the regular Macbook might want this as well.

Apple doesn't monitor the forum for feature requests and the like. It's just for user-to-user help.
Also note that this feature already exists: all Mac laptops sold in the past few years, including the MacBook Air, can be run with only an external monitor. It's called closed-lid mode.
http://docs.info.apple.com/article.html?artnum=86286
http://docs.info.apple.com/article.html?artnum=307315
If you then want to open the lid to increase cooling, you can. Once the external display is attached, the internal display does not come on automatically when you open it.
If you still want to give Apple feedback on another issue relating to the MacBook Air, the link is:
http://www.apple.com/feedback/macbookair.html

Feature requests

I'd like to submit some feature requests and complaints I've had with both the desktop and mobile apps.
1. Larger "add to queue" buttons for mobile- I always end up accidentally playing the track when I try to add it to the queue. This is extremely annoying because it stops the current song, and there is no way to easily go back to it.
2. Ability to jump to alphabetized artist in "your music" by typing the letters of their name like on iTunes, or some filter/search method. I have lots of artists and songs in that section, and it's incredibly annoying to have to spend so much time scrolling just to get to "z"
3. Always go back to specific location in scroll when hit "back" button.
4. Easy ability to remove item from playlist from "current song" screen as it's playing on mobile (and just in general, I couldn't figure out how to remove a song from playlist on mobile)
5. Ability to make each artist in your music as a small, narrow list element for ease of jumping around (both desktop and mobile)
6. Side alphabetical thing that you can tap to jump to a letter as in iPod music
7. Easy explicit versions of tracks. Sometimes a track will even say it's explicit but will be edited to have cuss words removed. This is ridiculous

Updated: 2015-07-27Hello there!
Thanks for the feedback, as mentioned, unfortunately we can only handle 1 feature request per topic, otherwise it's impossible to manage the received kudos / give the idea a proper status.
If you want to start a general feedback topic, that's great! But please use the respective help forum then. ;)
When you're re-posting those ideas in separate topics, please make sure to use the search function, since a lot of ideas might already be out there in the ideas forum. Thanks again!

Feature Request: Corner Window snapping.

Is this the correct forum for feature requests?
I would like to request a feature that would be extremely useful for multitasking. When you drag a window to the corner of your monitor or the upper corner of the task bar the window resizes to half the screen
width and height, and snaps to the corner.
To calculate these points you could do this:
Notes:
TL, TR, BL, BR represent the points of top left, top right, bottom left, and bottom right respectively.
var X-1=Monitor Length (in px)
var Y-1=Monitor Height (in px)
var T=Task bar Height (in px)
var B=Task bar Length (in px)
var x=point of x coordinate (from top left)
var y=point of y coordinate (from top left)
When task bar is on bottom:
TL: x=0, y=0
TR: x=X, y=0
BL: x=0, y=Y-T
BR: x=X, y=Y-T
When task bar is on top:
TL: x=0, y=T
TR: x=X, y=T
BL: x=0, y=Y
BR: x=X, y=Y

..."Using multiple applications - Maximized so as to concentrate on what I am doing - then using Exposé to quickly switch between them would be ideal. "...
If you are primarily concerned with applications and not windows, why don't you just use "Spaces"? It's available now, and allows you to assign an application to a particular space.
These days, the behaviour of the "zoom" button appears entirely up to the developer so suggestions might be better directed toward the ones who make the "design applications" you primarily use.
But back in good old days when Macs actually were designed to be easy to use (and not just pretty to look at), there seemed to have been a convention - not strictly adhered to in all quarters but a convention nonetheless - to use the "zoom" button to fit content, but "Option" + "zoom" to "maximize". If Apple would only go back to that idea, I suspect most people would find that satisfactory...

Feature Request: Export catalog for 2nd editor/machine

Since there isn't a shared network environment for LR, to involve multiple editors or multiple locations for the same editor on large projects, I often need to export a subset of a catalog so someone else can work on it, or I can work on it off my laptop somewhere other than the studio, using only the proxy 1:1 previews to make my decisions from and then re-assimilate those edit changes to the master catalog of that job, usually back on my primary workstation. This process also allows me to start processing out parts of the job while other parts are being edited on other machines, or letting my primary workstation process while I use a 2nd workstation to continue editing at speed on.
I can make this happen, but it's all on me to remember which portions of the catalog have been exported, where their destination was/is, remember not to make any changes to that portion of the library while the subsection has been exported, and an over-lengthy and complicated merging of exported and internal catalogs.
It would be incredibly useful if LR could show the status (checked out for primary edit, checked out for client approval, etc.) of any exported catalog by mousing over that visibly different section and build in a preference for those varied conditions to potentially limit any changes to that subset of images while the export is still 'checked-out.' A true merge would be nice to allow possible overlaps of work on the same images, but a managed lock-out would be sufficient to start with.
As it is, the re-assimilation process for me involves removing images from the master catalog leaving the raw files in place, and re-importing the exported catalog which also necessitates the needless redundancy of bringing the 1:1 previews back in as well. At the scale I'm doing this it's overly time consuming, compared to the speed of just bringing in the library itself. The process also puts me in the place of deleting images from a catalog while they're essentially still in use, which is scary from a file management standpoint, usually with me having 4 and 5 copies of that library lingering around until all the manual merging actions are finished.

That's a feature I've asked for myself Brad, in the absense of true network use. As it's not likely to make the final release, and we wouldn't want the request to get lost in beta land, might I suggest adding it as a suggestion on the Feature Request forum http://feedback.photoshop.com/photoshop_family where it can easily be tracked? If you post the link to your request here, others can also vote on your request.

Feature request for JSF i18n.

First of all, bear with me for my english is poor.
Utilizing JSF's i18n support, I created a small site that can display each of
its pages in three different languages: English(en), Spanish(es) and Korean(ko).
The page's view defaults to english but a user can view the pages in other languages, so the site can be viewed according to the user's preferred language. The user's language preference is stored in a session-scoped backing bean (preference.locale) so that the tag
<f:view locale="#{preference.locale}">will show each page in the user's prefered locale.
But the problem is this: If the user visited my site, selected the Korean
locale and found some content interesting, he would probably copy the page's URL
http://mysite/myapp/somedir/page1.jspand send it to a friend saying,
"Hey buddy! go to this URL and read the article. Don't worry, you will surely
understand the text because it's in Korean language."
Then, his friend will reply saying,
"Are you crazy? The URL you've given me is not in Korean, it's in English."
Of course this will be the behavior of my site because the "preference" backing
bean that determines the site's locale lives only in session scope; and, without
this backing bean set to another langauge, all pages will initially be in English
which is the default locale.
But this problem could be fixed if the default locale of each page in my webapp relies not on a backig bean but on some pattern in the URL. For example, when the page
http://mysite/myapp/somedir/page1.jspis accessed with this URL
http://mysite/myapp/ko/somedir/page1.jspthe <f:view> of my application will default to Korean, indicated by the /ko/ pattern in the URL. It may also be http://mysite/myapp/en_US/somedir/page1.jsp
that defaults to US English locale or http://mysite/myapp/es/somedir/page1.jsp
that defaults to Spanish locale.
I think if JSF has this feature, bookmarking problem on internationalized site could also be fixed and the contents of the website in different languages can also be indexed by search engines.
I think, URL=accessibility.
I don't want to use the querystring thing as the solution for this because of the reason that's hard for me to explain.
If you get what I'm trying to express and this feature request sounds stupid, please educate my ignorance. If anyone has an idea of a better solution for this,
please share. Thanks to all.

You could use a Phase listener to check the current
URL.
I would rather use a URL with a request parameter, as
follows:
http://mysite/myapp/somedir/page1.jsp?locale=koIn your Phase listener, I would look for the locale
parameter in the URL and set the local accordingly if
it exists, otherwise, I would use the default one.
Does that help?The pages in my site contains a lot of links and I dont want all those links to look like this:
go to page 1
or
<h:outputLink value="page1.jsp">
<f:param name="locale" value="#{preference.locale}"/>
</h:outputLink>
that's why I wanted all views in my pages to just rely on the preference.locale which is a session-scoped backing bean. But this approach has the problem I stated in my original post. I think it would be very nice for JSF if the <f:view> will be set by default according to some pattern in the URL (but not like query string).

Feature request: Support for more than 2 monitors

I currently use an external monitor for my critical editing/evaluation as my iMac display doesn't reproduce reds very well. I understand newer iMacs can support 2 external displays, obviously desktop machines can support as many displays as there are open slots for video cards.
While editing a photo shot in portrait on a monitor set for landscape is not a problem, it would <really> be cool to have two external color-accurate monitors for developing/loupe views, one oriented in portrait, one in landscape, with the third (iMac in this case) showing the develop controls. Even if the two external monitors showed the same image, one would always be fullscreen in the correct orientation.
MacOS and Windows both give the user control over all the displays connected to a given system, so driving a portrait and a landscape monitor simultaneously shouldn't be a problem from an OS/hardware standpoint.
Is this something that can be rolled into LR4?
Respectfully,
Andre

I use 3 or 4 monitors too, so that's one I'd like to see too. We wouldn't want the request to get lost in beta land, so might I suggest adding the request to the Feature Request forum http://feedback.photoshop.com/photoshop_family where it can easily be tracked? If you post the link to your request here, others can also vote on your request.

CS5 feature request - audio import?

Does anyone else think a feature request to add an "ask" option for PREFERENCES-AUDIO-DEFAULT TRACK FORMAT would be a great idea?
I'm constantly having to switch between stereo and mono etc when importing different types of files from different camera types etc. A pain.
Paul.

Paul,
Not sure exactly what you are looking to do here. One can set up a default Sequence layout, and that will be what is initially shown, with New Sequence.
My default is 2 Mono, 4 Stereo and a DD 5.1 SS Master. If I know that I will have a Sequence with more SFX Mono Tracks, I just bump that count up, when doing New Sequence. Same of Stereo, if I know that I will have, say more Music Tracks.
Are you saying that you'd like "floating channel-counts" for Tracks, so that they could be either Mono, or Stereo? If so, I do not see that happening.
If you are asking for maybe a Click+drag on Audio Tracks to rearrange them, like many DAW programs, that would be different. Though I use the PrPro method of Create/Delete Tracks, to get the order/arrangement that I need, the Click+drag is not a bad idea, and many have filed that Feature Request, including myself, though I am comfortable with the current method, and can easily live with it.
Can you clarify a bit more?
Thanks and good luck,
Hunt

A few Feature Requests for Leopard

Apple, I have a few feature requests that I would like to see added into Leopard ASAP and I am sure there are a few other here that I am missing (Please feel free to contribute to this thread).
SPACES - I want to have a different desktop picture for each "space" I create. I would also like to be able to use a combination of hotkeys to bring spaces into view and not just a single "F" key.
STACKS- This is a cool feature but would be even cooler if you could use the contextual menu on items within a stack to delete them without opening the enclosing folder.
FINDER- I would like to see the preference "Save view preferences for this window only" brought back. Some finder windows I like to view in list mode, others in column view.
TIME MACHINE - I would like an "Advanced Options" tab that would allow me to schedule my backups other than an incremental every hour. During the day when I am not at my home computer I do not need Time Machine to back up my drive every hour but perhaps every four hours. Then, when I am back at home, during certain hours I wouldn't mind its out of the box configuration.
SAFARI- A feature Safari has been constantly lacking is the ability to close the downloads window when a download completes. Another feature would be the saving of the last workspace so that when I quit and re-launch Safari I could start exactly where I left off. Now, there are third party applications which add this functionality but I would like to see it built-in by default.
These are a few things that I have found thus far that I would like to see fixed in an update to Leopard. Otherwise I would say I am very impressed with Leopard and will be recommending it to all my friends, family, and coworkers.

Actually, you need to put this on the "Feedback to Apple" on Apple's web site--it won't get to them here. This is just a user to user forum.

Reimport XMP automatically feature request

I continue to use the latest version of Adobe Camera Raw (ACR) whose editing controls are basically the same as the LR develop module, but with a UI I dramatically prefer (that's another topic). But I use LR for other reasons. I'm finding it a big nuisance to manually use the "Import XMP" feature every time I want to sync LR's XMP data (for my DNG edits) with edits I made with ACR (which are totally compatible and work correctly AFAIK).
What I want is an preference option, similar to the option to automatically export XMP data for edits in LR, to automatically import XMP data whenever LR notices a modification date change on the referenced file.

The Feature request thread is here:
http://www.adobeforums.com/cgi-bin/webx/.3bc33f32/32
Don
Don Ricklin, MacBook 1.83Ghz Duo 2 Core, Pentax *ist D
http://donricklin.blogspot.com/

Trivial bug/feature request

It's sort of a simple thing, but here goes.
In /etc/fstab /dev/cdrom has a default (standard Arch install) filesystem parameter of as iso9660
and /dev/dvd has a default (standard Arch install) filesystem parameter of udf. I'm using thunar-volman and I put a CD in my DVD drive and I got an error about it not being able to be mounted. I just changed the respective filesystems for /dev/dvd and /dev/cdrom to auto and it worked fine (no reboots at all).
IMO, something the default setting for /dev/dvd should be auto, possibly even /dev/cdrom. It's a simple fix, but could it be done when Arch is installed, instead of having the user manually make this change?

It is best to submit feature requests to the bug tracker. Things get lost/overlooked in the forums.

Feature request! Respect my preference​s

Similar Messages

Maybe you are looking for

Feature request! Respect my preferences