Problem opening options in PSE 8

Just upgraded from Photoshop Elements 6 to 8. Installation was succesful and catalogue (13000 images) was transferred. I have opened Elements 8 this morning and all the images are there. I can move through them using the mouse. However all other options appear frozen - I cannot for example get the organise or fix or create functions to open. I can only close down I think via Ctrl Alt Dlete. Could you assist please?
Optional Information:
Computer OS: Windows XP
Browser: IE

Given what you have identified in other threads it could be an Acrobat issue but I'm also wondering if it is as simple as the link format.
Could the PDFs be added as baggage so that they form part of the CHM?
If that would not work, could you enter the path with the server address rather than the file prefix?
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

Similar Messages

There was a problem opening the catalog 'My Catalog' PSE 4.0

In the new PSE 4.0 I always get the message "There was a problem opening the catalog 'My Catalog'", then after pressing the start button again, the catalog starts. Is that the same error that was solved in Version 3.0 with the update 3.0.1.
That would be not very nice!!!! :(.
Fraenzchen

Have you done a catalogue recover?
File > catalogue > recover
Chris French

I am using PSE 9. I had no problem opening my Raw files from my Canon Rebel XT Now I have a Rebel 5ti and pse 9 won't reconize the Cr2 files

I am using PSE 9. I had no problem opening my Raw files from my Canon Rebel XT Now I have a Rebel 5ti and pse 9 won't reconize the Cr2 files

See this faq:
FAQ: Will Photoshop Elements work with my camera, or Why won't my raw files open?
That will explain why each new camera model uses its own raw format. (.CR2 does not indicate a format, only a Canon family of formats).
The first link tells you what version of camera raw is needed for your camera : https://helpx.adobe.com/creative-suite/kb/camera-raw-plug-supported-cameras.html
You need ACR 7.4
The second link tells you which ACR versions are supported by Elements versions Camera Raw-compatible Adobe applications
PSE9 supports version 6.5
Further down on that paper, you get links to download the free Adobe DNGconverter for Mac or Win.
This standalone software can batch convert a whole folder of raw files to the DNG raw file format that your present PSE9 can read.
Otherwise, you would have to upgrade to version 10 or later.

App.open options when opening a newer version photoshop file by an older version of photoshop, App.open options when opening a newer version photoshop file by an older version of photoshop

So, where I work, we have a script that handles all of our heavy lifting. This script is running on CS6, and all of the users are running CC 2014. Now when the CS6 machine opens a document with any type of vector object from CC 2014 it throws a dialog box asking if I want to flatten, cancel, or Keep layers. I do have DISPLAYDIALOGS.NO set at the top of this script.
I under stand scripting quite well, but I'm just not sure if there are app.open options to tell this to keep layers. Also, I'm pretty sure a try catch block will not work, becuase this dialog appears before the image is actually pixels on the screen.
When the script generates our web images I've tried to flatten the document right after its opened and I still see this dialog. Any help would be super appreciated.
Thank you!

app.open will encounter problems that you really have no control over so you get an annoying dialog that you can't do anything with. The one that caused me the most grief is when a script tries to open a corrupt jpg image. IMNSHO, app.open should throw an Exception if it can't open the file and DisplayDialogs.NO is set. That way you can log the filename and deal with it later.
Bottom line is that there is nothing you can do in JS. One thing I have done in the past was use a utility like AutoKey on Windows that looks for these dialogs and automatically responds to them so you can continue processing. I'm fairly certain there is something similar available for OS X.

Error message when publishing and problems opening output file

I have 5 projects linked together. When I publish one, I get a message that the files listed below are linked to the open project, and one or more of these projects may require exporting. I have tried to open these files and choose File | Export | Project to | but the options in the list (Flash 8 and Flash CS3) are both grayed out--on every one of these files. I'm publishing to Flash 9.
I didn't think much about this message until a few reviewers said they can't open the project, or when they do, they don't see my playbar on the skin.
One more thing--when an IT person was trying to help one reviewer open the output file, the IT person said "Oh, there's a problem with the code in line 25." I guess that's the html code? I'm not a programmer, but I can look at html code. What should I be seeing there in line 25?
Is their problem opening the output file(s) related to my message about possibly needing to export files? Why might they be having problems getting the output file to open?
Thanks for any insights you can provide!
SAM

Hi Sam
It depends on a number of things. Are you certain you uploaded all the files involved? If not, there will be problems.
The message about the linked files is quite simply advising you that you have links from that particular movie that will expect to find the files being linked to.
If a person isn't seeing playback controls and you have included them, it's likely you haven't provided the correct link for them to open and play the file. Typically you provide a link to the HTML page Captivate creates. As long as all the output files are in the same place on the server, you should be good to go.
Cheers... Rick
Click here for Adobe Authorized Captivate and RoboHelp HTML Training
Click here for the SorcerStone Blog
Click here for RoboHelp and Captivate eBooks

How to recover a file downloaded but not saved in firefox.(when downloading gave the open option instead of save)

Version: Firefox4Beta
OS: Windows7
Problem:
I was downloading a large RAR file from the internet.
While downloading the file i didn't selected the save option instead i gave open with(winrar) option. I have some other rar files to combine with this file. So after the completion of this partial downloaded rar file is not saved in my system.How can i recover it.
Thanks n regards,
Ponnukumar.S

hi,
Thanks for ur reply.
But i already searched the windows and looked for that file.. But its not anywhere to be found. See first while downloading i gave the open option instead of save. So after the completion of the download the file opened automatically in winRAR. I tried to extract that file then it gave me some error. After that i closed the winrar and searched for that file in windows with search option but its not seen anywhere.
Thanks n regards,
S.Ponnukumar

When downloading a file, "open" option does not appears, only "save" does

Before updating to 5.0, when downloading a file, I could select between "Open" and "save". Now I don't have the "Open" option. I need it because of my work and is a must have or it will take to much time to save and then opening them. In normal morning with "open" option took me like 30 minutes. Now it took me 1.5 hours and can't afford to loose that much time.

Start Firefox in [[Safe Mode|Safe Mode]] to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance).
*Do NOT click the Reset button on the Safe mode start window or otherwise make changes.
*https://support.mozilla.org/kb/Safe+Mode
A possible cause is that the server sends a wrong response header.
The server may not comply to RFC 5987 and sends a wrong Content-Disposition:attachment; filename header.
* https://developer.mozilla.org/en/Firefox_8_for_developers#Network

Problem opening Aperture in Mountain Lion

I'm running Aperture 3.3.2 and upgraded to Mountain Lion last night. Since the upgrade Aperture is hanging on the "Opening Aperture Library" window. I've repaired and rebuilt my library with all referenced files on externals attached. No help. I've also deletedt the "ProAppsSystemID" file and reentered my registration numbers and still had no success.
Oddly with the "Opening" window open Aperture's toolbar funcuions normally as if the program were open.
I have figured out a work around. I made a new, empty library. I can open Option-click and open Aperture and select that empty library. From that empty library I can then switch to my normal library and use it as normal. Upon closing Aperture however things go back to being locked up when I try to open it.
Anyone else seen this problem? I'm open for suggestions. Thanks.

MikeSwe wrote:
I used to launch a sparsebundle file to mount it on the desktop (in the form of a normal h.d. partition) and so reach to open the files directly from applications.
Don't do that; files in Time Machine backups are protected, and should not (usually cannot) be used directly with applications. The should be restored somewhere to be used.
Use the Time Machine browser (the "Star Wars" display) instead.
To see the backups for a different Mac, use the Browse Other Backup Disks option, per Time Machine - Frequently Asked Question #17/

Having problems opening images in photoshop cs2

Hi all. Im on a mac using cs2.(yes i will upgrade at some point) Anyways, Ive downloaded some photos from Stockexchange.com and have never had any problems opening up the files until now. It seems like Photoshop doesnt like them anymore. Ive done all the latest updates but it doent seem to work. I am on a mbp with 10.4.11. Any help would be appreciated as I cannot upgrade to cs4 until after the summer and all the OT shifts that come with it
chris

Ignoring the spam.............
What exactly is happening when you say you there are problems in opening images?
Have you tried cntrl + click on the the photo icon and then checking the options on "Open with..."
When you download the images do they have any kind of suffix eg .jpg or .tiff etc?

Cannot open the file because the open options are incorrect

I'm trying to iterate through a folder of images, open each one of them, duplicate them into another photoshop file and close the individual image. This code works great on a PC (Photoshop CS3), but when I run it on our macs (Photoshop CS3) I will receive the following error on random images. "Error: Cannot open the file because the open options are incorrect" Does anyone know how to solve this problem? I've read about possibly setting the OpenDocumentType but have not seen an example anywhere. This error will sometimes occur after loading in one image or sometimes after 20 images. Sometimes I run it on the same directory multiple times all with various points of error. Sometimes every images is loaded. Any help would be much appreciated. Sample code is below.
i //CODE BELOW
i //allows the user to select an folder full of images
b var inputFolder = Folder.selectDialog("Select a folder that contains the files you want added as layers.");
b var fileList = inputFolder.getFiles();
b var tempRef = app.open(tempName);
b for (var i = 0; i < fileList.length; i++)
b {
b var tempName = fileList[i];
b var tempStringName = fileList[i].toString();
i //used to check if the file in the directory does in fact contain the .png extension
b var reducedFileName = tempStringName.substring(tempStringName.lastIndexOf("/")+1);
b if(reducedFileName.substring((reducedFileName.length - 4),(reducedFileName.length)) != ".png" || reducedFileName.substring((reducedFileName.length - 4),(reducedFileName.length)) != ".PNG")
b {
i //setting reference to opened docuement PNG file
i //This seems to be the section throwing the error. Surrounding with Try Catch revealse the Error noted above
b var tempRef = app.open(tempName);
i //setting a tempName variable to the PNG file name
b var tempName = app.activeDocument.name;
i //setting reference to the active layer in the file
b var graphicLayer = app.activeDocument.activeLayer;
i //setting the PNG layer name to the PNG file
b tempRef.layers[0].name = tempName;
i //duplicating the image onto the opened Photoshop file
b tempRef.layers[0].duplicate(backRef);
i //closing the original PNG file without saving
b tempRef.close(SaveOptions.DONOTSAVECHANGES);
b }
b }

It looks as if the folder contains non Photoshop files, one way around the problem would be to change
var fileList = inputFolder.getFiles();
To specify the file types you want to process IE:
var fileList = inputFolder.getFiles(/\.(jpg|tif|psd|crw|cr2|nef|dcr|dc2|raw)$/i);

Problem opening a certain site properly

Hello, I have problem opening a certain site properly. I use firefox 4.0.1 and have tried pretty much everything that has already been suggested in other similar problems I found posted here but the site continues to look wrong. No images, blue letters, white background and all the links are displayed in a list on the left side of the page. I also tried to open it on IE but I get the same result. Could anyone help me?

That site works fine here with Firefox 4.
Clear the cache and the cookies from sites that cause problems.
"Clear the Cache":
* Tools > Options > Advanced > Network > Offline Storage (Cache): "Clear Now"
"Remove the Cookies" from sites causing problems:
* Tools > Options > Privacy > Cookies: "Show Cookies"
If you use extensions (Tools > Add-ons > Extension) like Adblock Plus or NoScript or Flash Block that can block content then make sure that such extensions aren't blocking content.
Start Firefox in [[Safe Mode]] to check if one of the extensions is causing the problem (switch to the DEFAULT theme: Firefox (Tools) > Add-ons > Appearance/Themes).
* Don't make any changes on the Safe mode start window.
* https://support.mozilla.com/kb/Safe+Mode
* https://support.mozilla.com/kb/Troubleshooting+extensions+and+themes

[CS3][JS] Open options

I'm dealing with a situation where Photoshop will not open a file using open() because of the error "Cannot open the file because the open options are incorrect". The problem arises because the files have no extension or the wrong extension! I cannot work out how to specifically tell Photoshop to open the file as a certain type. I know what type the files are (mostly TIFFS) before the open command runs.
Tried Action Manager but it did not provide any insight on how to force the open command to, for example, 'open as TIFF'. Any help would be much appreciated.

I was having a similar situation with the app.open command via javascript (.jsx). The script had been working fine but I started getting erratic behavior while doing minor edits. After closing the extendscript editor and restarting photoshop, the script began working as it should again. Using CS4 and PC.

N96 MMS problem (opening and deleting)

Hello people..
I came here through the Dutch Nokia website, so i hope my english is good enough to understand....
This is my problem:
this morning I recieved an MMS, and later on i send an MMS back. At that time, there was no problem opening the messages. (both in Inbox, and Send Items)
This afternoon i tried to make a back up of my phone, and after that, I tried to delete al my SMS and MMS. Only here came the problem.
I can delete every sms there is, but the both (2) MMS (in the Inbox and Outbox)
If I try to open them, they won't open, and if i try to delete them, i get the warning (now translated from dutch to english) "General: Already in use"
I checked everything, if there was some programs running, but there isn't, and i also tried to put the phone back to it's factory settings, but then they still won't open/delete.
I already got another MMS, and that one, i could open, en delete. So there is no problem with that one.
Hope that someone can help me?!?
kind regards Roger

you said that the second MMS is still in your outbox, which means it hasn't been successfully sent yet.
try to delete the outbox MMS first. check its status if still on "sending", click options and choose defer sending.
try to delete, if not possible, try to move it to another folder like drafts before deleting from there.
i believe the inbox MMS can be deleted with no problems following deletion of the outbox one.
Fear not those who argue but those who dodge

After selecting "Never remember history," and "OK," re-opening options reveals it has reverted to "Use custom settings for history."

Problem occurs with all add-ons disabled, and in safe mode.

Thank you cor-el for your reply. To clarify for any other followers of this post: I found that if I first selected "Remember history" (apparently synonymous with "Default settings") and "OK," then reopened the Options pane and selected "Never remember history," it would stay selected. This seems like a bug to me however, since there is already a selection for single-session Private Browsing in the "Tools" pull-down menu, and it is simply not intuitive that a setting once selected would revert to any other setting simply because you re-opened "Options." This will result in many users who are not paying close attention using settings which they do not intend to use regarding their privacy. This is the sort of thing I expect from Microsoft or Adobe, but not from Mozilla.

MPD: ERROR: problems opening audio device

Since a day, maybe a little more, mpd is troubling me. When I use mpc, I get the error
ERROR: problems opening audio device
This is my mpd.conf
# An example configuration file for MPD
# See the mpd.conf man page for a more detailed description of each parameter.
# Files and directories #######################################################
# This setting controls the top directory which MPD will search to discover the
# available audio files and add them to the daemon's online database. This
# setting defaults to the XDG directory, otherwise the music directory will be
# be disabled and audio files will only be accepted over ipc socket (using
# file:// protocol) or streaming files over an accepted protocol.
music_directory "/home/adriaan/Music"
# This setting sets the MPD internal playlist directory. The purpose of this
# directory is storage for playlists created by MPD. The server will use
# playlist files not created by the server but only if they are in the MPD
# format. This setting defaults to playlist saving being disabled.
playlist_directory "/var/lib/mpd/playlists"
# This setting sets the location of the MPD database. This file is used to
# load the database at server start up and store the database while the
# server is not up. This setting defaults to disabled which will allow
# MPD to accept files over ipc socket (using file:// protocol) or streaming
# files over an accepted protocol.
db_file "/var/lib/mpd/mpd.db"
# These settings are the locations for the daemon log files for the daemon.
# These logs are great for troubleshooting, depending on your log_level
# settings.
# The special value "syslog" makes MPD use the local syslog daemon. This
# setting defaults to logging to syslog, otherwise logging is disabled.
log_file "/var/log/mpd/mpd.log"
# This setting sets the location of the file which stores the process ID
# for use of mpd --kill and some init scripts. This setting is disabled by
# default and the pid file will not be stored.
pid_file "/var/run/mpd/mpd.pid"
# This setting sets the location of the file which contains information about
# most variables to get MPD back into the same general shape it was in before
# it was brought down. This setting is disabled by default and the server
# state will be reset on server start up.
state_file "/var/lib/mpd/mpdstate"
# The location of the sticker database. This is a database which
# manages dynamic information attached to songs.
#sticker_file "~/.mpd/sticker.sql"
# General music daemon options ################################################
# This setting specifies the user that MPD will run as. MPD should never run as
# root and you may use this setting to make MPD change its user ID after
# initialization. This setting is disabled by default and MPD is run as the
# current user.
user "adriaan"
# This setting specifies the group that MPD will run as. If not specified
# primary group of user specified with "user" setting will be used (if set).
# This is useful if MPD needs to be a member of group such as "audio" to
# have permission to use sound card.
group "users"
# This setting sets the address for the daemon to listen on. Careful attention
# should be paid if this is assigned to anything other then the default, any.
# This setting can deny access to control of the daemon.
# For network
#bind_to_address "any"
# And for Unix Socket
#bind_to_address "~/.mpd/socket"
# This setting is the TCP port that is desired for the daemon to get assigned
# to.
#port "6600"
# This setting controls the type of information which is logged. Available
# setting arguments are "default", "secure" or "verbose". The "verbose" setting
# argument is recommended for troubleshooting, though can quickly stretch
# available resources on limited hardware storage.
#log_level "default"
# If you have a problem with your MP3s ending abruptly it is recommended that
# you set this argument to "no" to attempt to fix the problem. If this solves
# the problem, it is highly recommended to fix the MP3 files with vbrfix
# (available from <http://www.willwap.co.uk/Programs/vbrfix.php>), at which
# point gapless MP3 playback can be enabled.
#gapless_mp3_playback "yes"
# This setting enables MPD to create playlists in a format usable by other
# music players.
#save_absolute_paths_in_playlists "no"
# This setting defines a list of tag types that will be extracted during the
# audio file discovery process. Optionally, 'comment' can be added to this
# list.
#metadata_to_use "artist,album,title,track,name,genre,date,composer,performer,disc"
# This setting enables automatic update of MPD's database when files in
# music_directory are changed.
auto_update "yes"
# Limit the depth of the directories being watched, 0 means only watch
# the music directory itself. There is no limit by default.
#auto_update_depth "3"
# Symbolic link behavior ######################################################
# If this setting is set to "yes", MPD will discover audio files by following
# symbolic links outside of the configured music_directory.
#follow_outside_symlinks "yes"
# If this setting is set to "yes", MPD will discover audio files by following
# symbolic links inside of the configured music_directory.
#follow_inside_symlinks "yes"
# Zeroconf / Avahi Service Discovery ##########################################
# If this setting is set to "yes", service information will be published with
# Zeroconf / Avahi.
#zeroconf_enabled "yes"
# The argument to this setting will be the Zeroconf / Avahi unique name for
# this MPD server on the network.
#zeroconf_name "Music Player"
# Permissions #################################################################
# If this setting is set, MPD will require password authorization. The password
# can setting can be specified multiple times for different password profiles.
#password "password@read,add,control,admin"
# This setting specifies the permissions a user has who has not yet logged in.
#default_permissions "read,add,control,admin"
# Input #######################################################################
input {
plugin "curl"
# proxy "proxy.isp.com:8080"
# proxy_user "user"
# proxy_password "password"
# Audio Output ################################################################
# MPD supports various audio output types, as well as playing through multiple
# audio outputs at the same time, through multiple audio_output settings
# blocks. Setting this block is optional, though the server will only attempt
# autodetection for one sound card.
# See <http://mpd.wikia.com/wiki/Configuration#Audio_Outputs> for examples of
# other audio outputs.
# An example of an ALSA output:
audio_output {
type "alsa"
name "My ALSA Device"
device "hw:0,0" # optional
# format "44100:16:2" # optional
# mixer_type "hardware" # optional
# mixer_device "default" # optional
# mixer_control "PCM" # optional
# mixer_index "0" # optional
#audio_output {
# type "alsa"
# name "Sound Card"
# options "dev=dmixer"
# device "plug:dmix"
# An example of an OSS output:
#audio_output {
# type "oss"
# name "My OSS Device"
## device "/dev/dsp" # optional
## format "44100:16:2" # optional
## mixer_type "hardware" # optional
## mixer_device "/dev/mixer" # optional
## mixer_control "PCM" # optional
# An example of a shout output (for streaming to Icecast):
#audio_output {
# type "shout"
# encoding "ogg" # optional
# name "My Shout Stream"
# host "localhost"
# port "8000"
# mount "/mpd.ogg"
# password "hackme"
# quality "5.0"
# bitrate "128"
# format "44100:16:1"
## protocol "icecast2" # optional
## user "source" # optional
## description "My Stream Description" # optional
## genre "jazz" # optional
## public "no" # optional
## timeout "2" # optional
## mixer_type "software" # optional
# An example of a recorder output:
#audio_output {
# type "recorder"
# name "My recorder"
# encoder "vorbis" # optional, vorbis or lame
# path "/var/lib/mpd/recorder/mpd.ogg"
## quality "5.0" # do not define if bitrate is defined
# bitrate "128" # do not define if quality is defined
# format "44100:16:1"
# An example of a httpd output (built-in HTTP streaming server):
#audio_output {
# type "httpd"
# name "My HTTP Stream"
# encoder "vorbis" # optional, vorbis or lame
# port "8000"
# bind_to_address "0.0.0.0" # optional, IPv4 or IPv6
## quality "5.0" # do not define if bitrate is defined
# bitrate "128" # do not define if quality is defined
# format "44100:16:1"
# max_clients "0" # optional 0=no limit
# An example of a pulseaudio output (streaming to a remote pulseaudio server)
#audio_output {
# type "pulse"
# name "My Pulse Output"
## server "remote_server" # optional
## sink "remote_server_sink" # optional
## Example "pipe" output:
#audio_output {
# type "pipe"
# name "my pipe"
# command "aplay -f cd 2>/dev/null"
## Or if you're want to use AudioCompress
# command "AudioCompress -m | aplay -f cd 2>/dev/null"
## Or to send raw PCM stream through PCM:
# command "nc example.org 8765"
# format "44100:16:2"
## An example of a null output (for no audio output):
#audio_output {
# type "null"
# name "My Null Output"
# mixer_type "none" # optional
# This setting will change all decoded audio to be converted to the specified
# format before being passed to the audio outputs. By default, this setting is
# disabled.
#audio_output_format "44100:16:2"
# If MPD has been compiled with libsamplerate support, this setting specifies
# the sample rate converter to use. Possible values can be found in the
# mpd.conf man page or the libsamplerate documentation. By default, this is
# setting is disabled.
#samplerate_converter "Fastest Sinc Interpolator"
# Normalization automatic volume adjustments ##################################
# This setting specifies the type of ReplayGain to use. This setting can have
# the argument "off", "album" or "track". See <http://www.replaygain.org>
# for more details. This setting is off by default.
#replaygain "album"
# This setting sets the pre-amp used for files that have ReplayGain tags. By
# default this setting is disabled.
#replaygain_preamp "0"
# This setting enables on-the-fly normalization volume adjustment. This will
# result in the volume of all playing audio to be adjusted so the output has
# equal "loudness". This setting is disabled by default.
#volume_normalization "no"
# MPD Internal Buffering ######################################################
# This setting adjusts the size of internal decoded audio buffering. Changing
# this may have undesired effects. Don't change this if you don't know what you
# are doing.
#audio_buffer_size "2048"
# This setting controls the percentage of the buffer which is filled before
# beginning to play. Increasing this reduces the chance of audio file skipping,
# at the cost of increased time prior to audio playback.
#buffer_before_play "10%"
# Resource Limitations ########################################################
# These settings are various limitations to prevent MPD from using too many
# resources. Generally, these settings should be minimized to prevent security
# risks, depending on the operating resources.
#connection_timeout "60"
#max_connections "10"
#max_playlist_length "16384"
#max_command_list_size "2048"
#max_output_buffer_size "8192"
# Character Encoding ##########################################################
# If file or directory names do not display correctly for your locale then you
# may need to modify this setting.
filesystem_charset "UTF-8"
# This setting controls the encoding that ID3v1 tags should be converted from.
#id3v1_encoding "ISO-8859-1"
# SIDPlay decoder #############################################################
# songlength_database:
# Location of your songlengths file, as distributed with the HVSC.
# The sidplay plugin checks this for matching MD5 fingerprints.
# See http://www.c64.org/HVSC/DOCUMENTS/Songlengths.faq
# default_songlength:
# This is the default playing time in seconds for songs not in the
# songlength database, or in case you're not using a database.
# A value of 0 means play indefinitely.
# filter:
# Turns the SID filter emulation on or off.
#decoder {
# plugin "sidplay"
# songlength_database "/media/C64Music/DOCUMENTS/Songlengths.txt"
# default_songlength "120"
# filter "true"

milso wrote:
type "alsa"
name "equal"
device "default"
format "44100:16:2" # optional
mixer_device "default" # optional
mixer_control "PCM" # optional
mixer_index "0" # optional
I have mine set to plug:plugequal as I use an equalizer with alsa, but when I set it to default it works fine, try that.
That didn't work out.
Mr.Elendig wrote:Tell mpd to be more verbose. And check that mplayer -ao alsa whatever works.
Here's the output of mpd -v
listen: bind to '0.0.0.0:6600' failed: Address already in use (continuing anyway, because binding to '[::]:6600' succeeded)
path: path_set_fs_charset: fs charset is: UTF-8
database: reading DB
disabling the last.fm playlist plugin because account is not configured
daemon: opening pid file
daemon: daemonized!
daemon: writing pid file
Doesn't contain anything unusual.
EDIT: oh, and mplayer -ao alsa works fine.
Last edited by arthd (2011-02-09 15:14:09)

Problem opening options in PSE 8

Similar Messages

Maybe you are looking for