Does the frequency selection tool still exist in audition?

Does this tool still exist in audition? I am sure it was available in soundbooth
Very useful if you are trying to remove a constant buzzing of a certain frequency from an audio file.

Thanks for your answer!
Disappointing that it's gone. Will definitely submit a feature request.
The frequency selection tool was convenient, especially in the spectral view, because you could manually select one frequency across the entire file, while being zoomed in at only one specific time segment. You always risk forgetting/not catching something at the beginning or end of the file, when doing the manual selection tools, like the rectangle selection. Plus you'll have to be zoomed out all the way, so it's a bit harder to exactly select the frequency you need.
The automated tools are useful, but in early 2015 I still value the human pattern recognition systems and artistic and aesthetic judgement over that of an AI. (We'll see for how much longer,...)

Similar Messages

Why does the vector selection tool (white arrow) change layer selection to another vector mask?

I have been continually annoyed, when creating a vector mask-heavy document, with trying to select vector mask points by dragging a rectangle only to find that it instead selects a layer higher up which has a larger vector mask.
The only workaround is to manually select the points of my mask or to drag a rectangle from outside the canvas, meaning I have to zoom out or scroll to the edge - sometimes annoying if I am zoomed in quite far.
Does anyone know any resolution for this?
I know that the move tool can be set to automatically select a layer, depending on what part of the image is clicked, but why is there not an option to turn this off for vector editing?

What version of Photoshop are you using????
The White Arrow tool is the direct selection tool and it work best way you point it at a path segment line and click once. When you do all the control points in a close path segment will be marked with little squares and the two control point adjacent to where you clicked will have handles you can adjust.
You can also drag out a rectangle with the direct selection tool. When you do you may select many closed paths in a path a path may have many sub paths and each has a mode like add, subtract, intersect etc, and each has a stacking order like in a layer stack. So if you drag out a rectangle many paths control points will be marked and control point adjacent to crossing rectangle will have handles. Can be very confusing.
Here are two screen capture the first on shows the layer palette and path palette. You can see many shapes and path with sub paths and modes. I also targeted layer a vector mask. The selected the direct selection tool and in the image window I pointed at the 45 degree oval path near the top right. You cab see the four control points and two with handles. The second screen capture I only captured the image window. I used the direct selection tool and draged out a rectangle and you cab see many segments control points and many have handles. I have no problem selecting what I want to select

Does the Advanced selection still exist in iTunes 12.1

Does the "Advanced" selection still exist in iTunes 12.1?
That is the selection where i can select to replace the "contacts" and "Calendar" on my iPhone/iPad
with the Contacts and Calendar on my MacBook Pro. I DO NO sync from the cloud.
MacBook Pro is the master, and always wipe/replace from my mac.
Thanks

Sure, you can see that in the source code.
*http://mxr.mozilla.org/mozilla-central/source/content/xul/document/src/nsXULPrototypeCache.cpp#35

The arrow select tool does not marquee

The arrow select tool does not work properly. At times it marquees and some other times it doesn't.
Please help.

Judy,
Has it worked with Yosemite before?
Did you upgrade to Yosemite, then reinstall? That is the recommended way/order.
Especially if the tool has just stopped working, there may be some kind/level of corruption/disturbance, and you may try the list.
The following is a general list of things you may try when the issue is not in a specific file, and when it is not caused by issues with opening a file from external media, see below. You may have tried/done some of them already; 1) and 2) are the easy ones for temporary strangenesses, and 3) and 4) are specifically aimed at possibly corrupt preferences); 5) is a list in itself, and 6) is the last resort.
If possible/applicable, you should save current artwork first, of course.
1) Close down Illy and open again;
2) Restart the computer (you may do that up to at least 5 times);
3) Close down Illy and press Ctrl+Alt+Shift/Cmd+Option+Shift during startup (easy but irreversible);
4) Move the folder (follow the link with that name) with Illy closed (more tedious but also more thorough and reversible), for CS3 - CC you may find the folder here:
https://helpx.adobe.com/illustrator/kb/preference-file-location-illustrator.html
5) Look through and try out the relevant among the Other options (follow the link with that name, Item 7) is a list of usual suspects among other applications that may disturb and confuse Illy, Item 15) applies to CC, CS6, and maybe CS5);
Even more seriously, you may:
6) Uninstall (ticking the box to delete the preferences), run the Cleaner Tool (if you have CS3/CS4/CS5/CS6/CC), and reinstall.
http://www.adobe.com/support/contact/cscleanertool.html

I have a comment. I am very upset with Photoshop and all your tutorials regarding the quick select tool. I have watched many tutorials and read instructions until I am blue in the face. This tool does not work. It is all over the place and all of your

I have a comment. I am very upset with Photoshop and all your tutorials regarding the quick select tool. I have watched many tutorials and read instructions until I am blue in the face. This tool does not work. It is all over the place and all of your tutorials make it look so simple. How can you advertise this as a viable tool when it just doesn't work?

It is all over the place and all of your tutorials make it look so simple.
This is a user to user Forum, so you are not really addressing Adobe here, even though some Adobe employees thankfully have been dropping by.
How can you advertise this as a viable tool when it just doesn't work?
Concluding something does not work because you fail at using it is not necessarily always justified.
The Quick Selection Tool certainly has limitations, but your post seems to be more about venting than trouble-shooting – otherwise you might have posted an image where you failed to get an expected result.

How do I constrain anchor angle when I tug on a path with the direct select tool?

How do I constrain anchor angle when I tug on a path with the direct select tool like it did in every version of Illustrator since 1988? New behavior is costing me time.

That solves it!
I was not able to find this in the online materials about the pen tool. In fact, Illustrator Help | Adjust path segments does not show the new functionality at all. They need to update that article.
Better way to implement the new functionality
It would have been nice if Adobe added to the chording controls for the direct select tool the ability to toggle this setting temporarily by holding down the space bar after mouse down to drag a segment.
Before mouse down this would give the user the hand tool.
If, after mouse down, I could hold space bar and have the behavior switch from the historical capability where dragging a segment cannot change adjacent segments to the new behavior where dragging the segment cannot move anchors but can rotate them, I am sure I would find times when the tool saved time. If, before mouse up, I release spacebar, turn the constraint back on with anchors pointing in their new directions and allow me to stretch the curve protecting the new shapes of adjacent curves.
Using space bar for this would be intuitive to me because holding down the space bar is something I already do to organically drag the page around with the hand tool. The new tool allows me to more organically stretch artwork around, something that is distantly analogous, but close enough to remember.
For long time Illustrator users, the chording features holding Ctrl/Alt/Shift/Space or Ctrl/Command/Shift/Space in different combinations while using the direct select tool and pen tool is the killer app part of Illustrator that keeps us using it. This what we did on Illustrator 88 on a Mac Plus in 1988 and is still the most productive way to produce vector art when precision is required.

Gradients gets cropped with the Direct selection tool

I discovered another strange thing with gradients in InDesign.
I could see this problem in both CS6 and CC.
1. Make a gradient fill and apply it to a square object
2. Use the Direct selection tool and select two corners
3. Move the corners and you will see the gradient fill being cropped away
4. Change to the Selection tool and make the object wider. It does not reveal any more colors. They are cropped away for good now.
According to the color palettes this is still a gradient fill but it looks like one color now more or less. I couldn't find any way to release the cropping. I suppose it would have to be reveresed with the Direct selection tool.
The gradients in Illustrator stay inside the object when using the Direct selection so both selection tools works the same way. I also tried with vector objects in Photoshop and the gradient fill effect. Both selection tools in Photoshop works the same way as Illustrator. Gradient stays inside the object.
So is it a bug or feature?

Adobe has provided a very large tool box. Why not just do this in
Illustrator and place or copy/paste the frame. You obviously don't like
InDesign's way of doing things and you have at your disposal a tool that
does work the way you like.
I like InDesigns way of doing things very much. It's easily my all time favorite software after 25 years in this business.
And I can understand different behavior between the Adobe apps. This app can only do a little bit of what the other app can do.
But it don't like when three apps have the exact same tools, and one app is programmed to do something else with these tools, when it just as easily could have been programmed to do the same thing.

The Bug about 'DB_SECONDARY_BAD' still exists in BerkeleyDB4.8!

The Bug about 'DB_SECONDARY_BAD' still exists in BerkeleyDB4.8?
I'm sorry for my poor English, But I just cannot find anywhere else for help.
Thanks for your patience first!
I'm using BDB4.8 C++ API on Ubuntu 10.04, Linux Kernel 2.6.32-24-generic
$uname -a
$Linux wonpc 2.6.32-24-generic #43-Ubuntu SMP Thu Sep 16 14:17:33 UTC 2010 i686 GNU/Linux
When I update(overwrite) a record in database, I may get a DB_SECONDARY_BAD exception,
What's worse, This case doesn't always occures, it's random. So I think it probably a bug
of BDB, I have seen many issues about DB_SECONDARY_BAD with BDB4.5,4.6...
To reproduce the issue, I make a simplified test program from my real program.
The data to be stroed into database is a class called 'EntryData', It's defined in db_access.h,
where also defines some HighLevel API functions that hide the BDB calls, such as
store_entry_data(), which use EntryData as its argument. The EntryData have a string-type
member-data 'name' and a vector<string>-type mem-data 'labels', So store_entry_data() will
put the real data of EntryData to a contiguous memory block. The get_entry_data() returns
an EntryData builed up from the contiguous memory block fetched from database.
The comlete test program is post following this line:
/////////db_access.h////////////
#ifndef __DB_ACCESS_H__
#define __DB_ACCESS_H__
#include <string>
#include <vector>
#include <db_cxx.h>
class EntryData;
//extern Path DataDir; // default value, can be changed
extern int database_setup();
extern int database_close();
extern int store_entry_data(const EntryData&, u_int32_t = DB_NOOVERWRITE);
extern int get_entry_data(const std::string&, EntryData*, u_int32_t = 0);
extern int rm_entry_data(const std::string&);
class DBSetup
// 构造时调用database_setup, 超出作用域自动调用database_close .
// 该类没有数据成员.
public:
DBSetup() {
database_setup();
~DBSetup() {
database_close();
class EntryData
public:
typedef std::vector<std::string> LabelContainerType;
EntryData() {}
EntryData(const std::string& s) : name(s) {}
EntryData(const std::string& s, LabelContainerType& v)
: name(s), labels(v) {}
EntryData(const std::string&, const char*[]);
class DataBlock;
// 直接从内存块中构建, mem指针将会从数据库中获取,
// 它就是EntryData转化成的DataBlock中buf_ptr->buf的内容.
EntryData(const void* mem_blk, const int len);
~EntryData() {};
const std::string& get_name () const { return name; }
const LabelContainerType& get_labels() const { return labels; }
void set_name (const std::string& s) { name = s; }
void add_label(const std::string&);
void rem_label(const std::string&);
void show() const;
//　get contiguous memory for all:
DataBlock get_block() const { return DataBlock(*this); }
class DataBlock
// contiguous memory for all.
public:
DataBlock(const EntryData& data);
// 引进一块内存作为 buf_ptr->buf 的内容.
// 例如从数据库中获取结果
DataBlock(void* mem, int len);
// 复制构造函数:
DataBlock(const DataBlock& orig) :
data_size(orig.data_size),
capacity(orig.capacity),
buf_ptr(orig.buf_ptr) { ++buf_ptr->use; }
// 赋值操作符:
DataBlock& operator=(const DataBlock& oth)
data_size = oth.data_size;
capacity = oth.capacity;
if(--buf_ptr->use == 0)
delete buf_ptr;
buf_ptr = oth.buf_ptr;
return *this;
~DataBlock() {
if(--buf_ptr->use == 0) { delete buf_ptr; }
// data()函数因 Dbt 构造函数不支持const char*而被迫返回 char*
// data() 返回的指针是应该被修改的.
const char* data() const { return buf_ptr->buf; }
int size() const { return data_size; }
private:
void pack_str(const std::string& s);
static const int init_capacity = 100;
int data_size; // 记录数据块的长度.
int capacity; // 已经分配到 buf 的内存大小.
class SmartPtr; // 前向声明.
SmartPtr* buf_ptr;
class SmartPtr
friend class DataBlock;
char* buf;
int use;
SmartPtr(char* p) : buf(p), use(1) {}
~SmartPtr() { delete [] buf; }
private:
std::string name; // entry name
LabelContainerType labels; // entry labels list
}; // class EntryData
#endif
//////db_access.cc/////////////
#include <iostream>
#include <cstring>
#include <cstdlib>
#include <vector>
#include <algorithm>
#include "directory.h"
#include "db_access.h"
using namespace std;
static Path DataDir("~/mydict_data"); // default value, can be changed
const Path& get_datadir() { return DataDir; }
static DbEnv myEnv(0);
static Db db_bynam(&myEnv, 0); // using name as key
static Db db_bylab(&myEnv, 0); // using label as key
static int generate_keys_for_db_bylab
(Db* sdbp, const Dbt* pkey, const Dbt* pdata, Dbt* skey)
EntryData entry_data(pdata->get_data(), pdata->get_size());
int lab_num = entry_data.get_labels().size();
Dbt* tmpdbt = (Dbt*) malloc( sizeof(Dbt) * lab_num );
memset(tmpdbt, 0, sizeof(Dbt) * lab_num);
EntryData::LabelContainerType::const_iterator
lab_it = entry_data.get_labels().begin(), lab_end = entry_data.get_labels().end();
for(int i = 0; lab_it != lab_end; ++lab_it, ++i) {
tmpdbt[ i ].set_data( (void*)lab_it->c_str() );
tmpdbt[ i ].set_size( lab_it->size() );
skey->set_flags(DB_DBT_MULTIPLE | DB_DBT_APPMALLOC);
skey->set_data(tmpdbt);
skey->set_size(lab_num);
return 0;
//@Return Value: return non-zero at error
extern int database_setup()
const string DBEnvHome (DataDir + "DBEnv");
const string dbfile_bynam("dbfile_bynam");
const string dbfile_bylab("dbfile_bylab");
db_bylab.set_flags(DB_DUPSORT);
const u_int32_t env_flags = DB_CREATE | DB_INIT_MPOOL;
const u_int32_t db_flags = DB_CREATE;
rmkdir(DBEnvHome);
try
myEnv.open(DBEnvHome.c_str(), env_flags, 0);
db_bynam.open(NULL, dbfile_bynam.c_str(), NULL, DB_BTREE, db_flags, 0);
db_bylab.open(NULL, dbfile_bylab.c_str(), NULL, DB_BTREE, db_flags, 0);
db_bynam.associate(NULL, &db_bylab, generate_keys_for_db_bylab, 0);
} catch(DbException &e) {
cerr << "Err when open DBEnv or Db: " << e.what() << endl;
return -1;
} catch(std::exception& e) {
cerr << "Err when open DBEnv or Db: " << e.what() << endl;
return -1;
return 0;
int database_close()
try {
db_bylab.close(0);
db_bynam.close(0);
myEnv.close(0);
} catch(DbException &e) {
cerr << e.what();
return -1;
} catch(std::exception &e) {
cerr << e.what();
return -1;
return 0;
// 返回Dbt::put()的返回值
int store_entry_data(const EntryData& e, u_int32_t flags)
int res = 0;
try {
EntryData::DataBlock blk(e);
// data()返回的buf中存放的第一个字符串便是 e.get_name().
Dbt key ( (void*)blk.data(), strlen(blk.data()) + 1 );
Dbt data( (void*)blk.data(), blk.size() );
res = db_bynam.put(NULL, &key, &data, flags);
} catch (DbException& e) {
cerr << e.what() << endl;
throw; // 重新抛出.
return res;
// 返回 Db::get()的返回值, 调用成功时 EntryData* e的值才有意义
int get_entry_data
(const std::string& entry_name, EntryData* e, u_int32_t flags)
Dbt key( (void*)entry_name.c_str(), entry_name.size() + 1 );
Dbt data;
data.set_flags(DB_DBT_MALLOC);
int res = db_bynam.get(NULL, &key, &data, flags);
if(res == 0)
new (e) EntryData( data.get_data(), data.get_size() );
free( data.get_data() );
return res;
int rm_entry_data(const std::string& name)
Dbt key( (void*)name.c_str(), name.size() + 1 );
cout << "to remove: \'" << name << "\'" << endl;
int res = db_bynam.del(NULL, &key, 0);
return res;
EntryData::EntryData(const std::string& s, const char* labels_arr[]) : name(s)
{   // labels_arr 需要以 NULL 结尾.
for(const char** i = labels_arr; *i != NULL; i++)
labels.push_back(*i);
EntryData::EntryData(const void* mem_blk, const int len)
const char* buf = (const char*)mem_blk;
int consumed = 0; // 已经消耗的mem_blk的大小.
name = buf; // 第一串为 name
consumed += name.size() + 1;
for (string label = buf + consumed;
consumed < len;
consumed += label.size() + 1)
label = buf + consumed;
labels.push_back(label);
void EntryData::add_label(const string& new_label)
if(find(labels.begin(), labels.end(), new_label)
== labels.end())
labels.push_back(new_label);
void EntryData::rem_label(const string& to_rem)
LabelContainerType::iterator iter = find(labels.begin(), labels.end(), to_rem);
if(iter != labels.end())
labels.erase(iter);
void EntryData::show() const {
cout << "name: " << name << "; labels: ";
LabelContainerType::const_iterator it, end = labels.end();
for(it = labels.begin(); it != end; ++it)
cout << *it << " ";
cout << endl;
EntryData::DataBlock::DataBlock(const EntryData& data) :
data_size(0),
capacity(init_capacity),
buf_ptr(new SmartPtr(new char[init_capacity]))
pack_str(data.name);
for(EntryData::LabelContainerType::const_iterator \
i = data.labels.begin();
i != data.labels.end();
++i) { pack_str(*i); }
void EntryData::DataBlock::pack_str(const std::string& s)
int string_size = s.size() + 1; // to put sting in buf separately.
if(capacity >= data_size + string_size) {
memcpy(buf_ptr->buf + data_size, s.c_str(), string_size);
else {
capacity = (data_size + string_size)*2; // 分配尽可能大的空间.
buf_ptr->buf = (char*)realloc(buf_ptr->buf, capacity);
memcpy(buf_ptr->buf + data_size, s.c_str(), string_size);
data_size += string_size;
//////////// test_put.cc ///////////
#include <iostream>
#include <string>
#include <cstdlib>
#include "db_access.h"
using namespace std;
int main(int argc, char** argv)
if(argc < 2) { exit(EXIT_FAILURE); }
DBSetup setupup_mydb;
int res = 0;
EntryData ed(argv[1], (const char**)argv + 2);
res = store_entry_data(ed);
if(res != 0) {
     cerr << db_strerror(res) << endl;
     return res;
return 0;
// To Compile:
// $ g++ -ldb_cxx -lboost_regex -o test_put test_put.cc db_access.cc directory.cc
//////////// test_update.cc ///////////
#include <iostream>
#include <cstdlib>
#include <string>
#include <boost/program_options.hpp>
#include "db_access.h"
using namespace std;
namespace po = boost::program_options;
int main(int argc, char** argv)
if(argc < 2) { exit(EXIT_SUCCESS); }
DBSetup setupup_mydb;
int res = 0;
po::options_description cmdopts("Allowed options");
po::positional_options_description pos_opts;
cmdopts.add_options()
("entry", "Specify the entry that will be edited")
("addlabel,a", po::value< vector<string> >(),
"add a label for specified entry")
("removelabel,r", po::value< vector<string> >(),
"remove the label of specified entry")
pos_opts.add("entry", 1);
po::variables_map vm;
store( po::command_line_parser(argc, argv).
options(cmdopts).positional(pos_opts).run(), vm );
notify(vm);
EntryData entry_data;
if(vm.count("entry")) {
const string& entry_to_edit = vm["entry"].as<string>();
res = get_entry_data( entry_to_edit, &entry_data );
switch (res)
case 0:
break;
case DB_NOTFOUND:
cerr << "No entry named: \'"
<< entry_to_edit << "\'\n";
return res;
break;
default:
cerr << db_strerror(res) << endl;
return res;
} else {
cerr << "No entry specified\n";
exit(EXIT_FAILURE);
EntryData new_entry_data(entry_data);
typedef vector<string>::const_iterator VS_CI;
if(vm.count("addlabel")) {
const vector<string>& to_adds = vm["addlabel"].as< vector<string> >();
VS_CI end = to_adds.end();
for(VS_CI i = to_adds.begin(); i != end; ++i) {
new_entry_data.add_label(*i);
if(vm.count("removelabel")) {
const vector<string>& to_rems = vm["removelabel"].as< vector<string> >();
VS_CI end = to_rems.end();
for(VS_CI i = to_rems.begin(); i != end; ++i) {
new_entry_data.rem_label(*i);
cout << "Old data| ";
entry_data.show();
cout << "New data| ";
new_entry_data.show();
res = store_entry_data(new_entry_data, 0); // set flags to zero permitting Over Write
if(res != 0) {
cerr << db_strerror(res) << endl;
return res;
return 0;
// To Compile:
// $ g++ -ldb_cxx -lboost_regex -lboost_program_options -o test_update test_update.cc db_access.cc directory.cc

////////directory.h//////
#ifndef __DIRECTORY_H__
#define __DIRECTORY_H__
#include <string>
#include <string>
#include <sys/types.h>
using std::string;
class Path
public:
Path() {}
Path(const std::string&);
Path(const char* raw) { new (this) Path(string(raw)); }
Path upper() const;
void operator+= (const std::string&);
// convert to string (char*):
//operator std::string() const {return spath;}
operator const char*() const {return spath.c_str();}
const std::string& str() const {return spath;}
private:
std::string spath; // the real path
inline Path operator+(const Path& L, const string& R)
Path p(L);
p += R;
return p;
int rmkdir(const string& path, const mode_t mode = 0744, const int depth = -1);
#endif
///////directory.cc///////
#ifndef __DIRECTORY_H__
#define __DIRECTORY_H__
#include <string>
#include <string>
#include <sys/types.h>
using std::string;
class Path
public:
Path() {}
Path(const std::string&);
Path(const char* raw) { new (this) Path(string(raw)); }
Path upper() const;
void operator+= (const std::string&);
// convert to string (char*):
//operator std::string() const {return spath;}
operator const char*() const {return spath.c_str();}
const std::string& str() const {return spath;}
private:
std::string spath; // the real path
inline Path operator+(const Path& L, const string& R)
Path p(L);
p += R;
return p;
int rmkdir(const string& path, const mode_t mode = 0744, const int depth = -1);
#endif
//////////////////// All the code is above ////////////////////////////////
Use the under command
$ g++ -ldb_cxx -lboost_regex -o test_put test_put.cc db_access.cc directory.cc
to get a test program that can insert a record to database.
To insert a record, use the under command:
$ ./test_put ubuntu linux os
It will store an EntryData named 'ubuntu' and two labels('linux', 'os') to database.
Use the under command
$ g++ -ldb_cxx -lboost_regex -lboost_program_options -o test_update test_update.cc db_access.cc directory.cc
to get a test program that can update the existing records.
To update the record, use the under command:
$ ./test_update ubuntu -r linux -a canonical
It will update the with the key 'ubuntu', with the label 'linux' removed and a new
label 'canonical'.
Great thanks to you if you've read and understood my code!
I've said that the DB_SECONDARY_BAD exception is random. The same operation may cause
exception in one time and may goes well in another time.
As I've test below:
## Lines not started with '$' is the stdout or stderr.
$ ./test_put linux os linus
$ ./test_update linux -r os
Old data| name: linux; labels: os linus
New data| name: linux; labels: linus
$ ./test_update linux -r linus
Old data| name: linux; labels: linus
New data| name: linux; labels:
dbfile_bynam: DB_SECONDARY_BAD: Secondary index inconsistent with primary
Db::put: DB_SECONDARY_BAD: Secondary index inconsistent with primary
terminate called after throwing an instance of 'DbException'
what(): Db::put: DB_SECONDARY_BAD: Secondary index inconsistent with primary
已放弃
Look! I've received a DB_SECONDARY_BAD exception. But thus exception does not always
happen even under the same operation.
For the exception is random, you may have not the "luck" to get it during your test.
So let's insert a record by:
$ ./test_put t
and then give it a great number of labels:
$ for((i = 0; i != 100; ++i)); do ./test_update t -a "label_$i"; done
and then:
$ for((i = 0; i != 100; ++i)); do ./test_update t -r "label_$i"; done
Thus, the DB_SECONDARY_BAD exception is almost certain to happen.
I've been confused by the problem for times. I would appreciate if someone can solve
my problem.
Many thanks!
Wonder

Please fix the direct selection tool that you broke

When you create a curved path with at least four anchor points that is not a complete circuit, clicking on that path with the direct selection tool only selects a portion of the path, whereas before, it would select the entire path. This odd new behavior, whether intentional or not, is a result of the new Path Segment Reshaping functionality.
The problem is, it is very annoying to have only a portion of the path selected because it makes it look like the path is non-contiguous. (Selecting with the regular selection tool isn’t necessarily a solution if your paths are grouped, since it will always select the entire group, and not just the one path you’re interested in.)
This does not happen with closed paths, and it does not impede the Path Segment Reshaping functionality at all. Therefore, there is no reason why open paths shouldn’t/couldn’t behave the same way — the way they previously did before this update.

Thanks for thoroughly explaining the problem. I can reproduce the issue. I blamed it on improper screen redraw. I've noticed other screen redraw issues in 17.1.

The quick selection tool is freezing Photoshop CC.

Anyone else had this problem? Everything else seems to work fine but when I try to use the quick selection tool, Photoshop freezes and I have to shut it down. I can't find much online about this.
I'm on a Mac
Processor 2.3 GHz Intel Core i5
Memory 4 GB 1333 MHz DDR3
Graphics Intel HD Graphics 3000 384 MB
Software Mac OS X Lion 10.7.5 (11G63)

Does turning off »Use Graphics Processor« in the Performance Preferences and restarting Photoshop have any bearing on the issue?
What have you done for general trouble-shooting so far?
Photoshop: Basic Troubleshooting steps to fix most issues

Why is the "Quick Selection Tool" working so slowly? - Photoshop CC in Windows 7

Every time I try to use the Quick selection tool, it takes a REALLY long time to select. I had CS5 and it was super fast, even with large RAW files. Now with CC, it takes at least 20 minutes to select a person out of a photo.
I already tried "resetting" the tool - that did not work at all.
Please help!

I mentioned working on my laptop without GPU acceleration, and how much it slowed everything down, but Quick Select was still laggy after the driver updated and GPU acceleration restored. This is a reasonable laptop with i7, 16Gb and GTX680. Thankfully, I got my main system back yesterday, and Quick select is pretty much instant.
But there shouldn't be that much difference. The big box has six core running at 4.2Ghz (under load) 32GB and GTX570, so while it is certainly more powerful, the difference in performance in respect to Quick Select is not proportional. I've just tried reducing cache levels on the big box from the '6' it usually runs at right down to 2, but it still responds instantly even with large files. I have GPU set to Advanced, and tile size to 128 on both systems.
Another odd thing is that I only have 1GB vRAM with the GTX570, where the GTX680 has 4Gb of faster vRAM. But maybe Quick select is not a big user of GPU acceleration.
So no real help I am afraid. I have looked through the GPU FAQ, but nothing helpful there. OK, I have just found a more detailed article on GPU acceleration, and it mentions a lot of features, but not Quick Select, so it could be that GPU is irrelevant. The laptop is Windows 8.1 as opposed win 7 for the big box, if that makes a difference. Can you correlate anything between our systems? I hate to post this without any suggestions, but I'm stumped.
There are tricks to aid Quick select.
Make a copy of the layer, and apply Curves and/or Levels directly to the layer, and try to increase contrast between the subject and background. Use this layer to make the selection, then switch back to the normal layer to use the selection.
I don’t know if this will work as I have just thought of it. Copy the layer, and Free Transform it to a smaller size. It will be image dependant, but Quick Select is much faster with images below about 1500 pixels wide. Use Quick select on the smaller image layer, and copy the selection to a new layer. FT it back up to size, and it should fit. This would only be useful if you are going to use Refine Edge right after, and will have obvious limitations.
Make sure you report back if you find a solution.

Why can't I move artwork with the perspective selection tool?

I created a carpet and decorated it with symbols. When I tried to place it in the perspective grid with the perspective tool, it wouldn't move. I can move it fine with the selection tool and there's a bounding box but nothing happens when I use the perspective selection tool.
Need help. Thanks.

You have to make sure that one of the grids (Left, Right, Horizontal) is active.
Just check the widget that appears when you select the Perspective Grid Tool. You can click on those sides of the cube with the Perspective Grid or the Perspective Selection Tool to make one of them active. You can also press the key 1, 2 or 3 to make either of those grids active.
If you click on the circular portion outside the cube, none of the grids is active. Then you can't move the artwork with the Perspective Selection Tool. You can press the key 4 to make none of the grids active which is especially useful when you don't want your artwork to distort in perspective while still working with the Perspective Grid showing on the artboard.

Why won't the Quick Select tool select transparent canvas.

I remember being able to select anything on the canvas with my Quick Select tool in CS5.5 Photoshop Extended. Recently, making the switch to CC, the Quick Select tool will show my slection as I drag along the canvas, but once I release the mouse, the selection seems to be reduced to the visible pixels. I was intentionally trying to fill the transparent sections with my effects as well.
Mind you, the magic wand will select transparent pixels just fine, but it also adds unintentional sections which is irritating. I should probably also pint out that I already looked into the "lock transparence" option in the layers, but I did not activate anything of the sort.

I see how my question can be kind of vague, sorry about that.
I have an image with a transparent background and a layer with, as stated below, pixels missing. With the wand, when I select a section of the layer that has no pixels, it selects every transparent section of that layer within the canvases borders. Thing is, I only wish to select a particular transparent section without touching the existing pixels. My hands are not as gifted as I would like them to be when painting a mask unless I zoom in ten-fold for every inch of the image.
To clarify further, the Quick Select tool's marquee shows everything working as I would expect it to until I release the mouse button. Then, for a reason beyond me, the selection gets reduced to existing pixels in the layer only.

Can't nudge my edited Multi-Cam sequence forward with the Track Select Tool

Hello, Good People of this forum,
I can't move it forward using the Track Select Tool. I checks to make sure the mother tracks weren't locked and I can move that timeline fine.
Any suggestions greatly appreciated.
Thanks!
wsmith

I am having a similar issue. My system and FCP are latest updates.
I have a set of clips shot with one tripod camera for the full length, and what looks like one or two other "roving" cameras getting closeups and other angles, but start and top points (not runnign the entire interview). Effectively these are B roll with matching audio.
If I run Sync Clips, it makes a huge mess piling them all one atop another. The audio souds like a party, not a conversation with two people.
When I make a Multicam clip, FCP does a "pretty good job" but some short clips are WAY out of sync...
Then it becomes a puzzle to find where they go.
Is there a keyboard shortcut for monitoring the video of the track on which I have just clicked the clip it's on? the one Multiclip when I am done?
Also, ••• How do I close the Timeline back down to

ID CS 3.0.1 (838) crashes every time I use the Direct Selection Tool

We have recently installed an upgrade to InDesign CS for being able to open documents generated by newer ID versions, thus turning the InDesign version into CS 3.0.1 (838).
Since then, every time we start to use the Direct Selection Tool (white arrow) the program crashes.
As this is a relatively old upgrade (2005), I was hoping to find the solution on the Internet but had no success.
Does anyone know what should we do to solve this problem?

Yes, I did. Even though we're in Brazil, we prefer to use the softwares in their native language (english) in order to get eventual updates more quickly. This also applies to the operational environment (Windows XP Professional - SP3, with the most recent updates installed)

Does the frequency selection tool still exist in audition?

Similar Messages

Maybe you are looking for