VISA ERROR Problems

System:
Windows XP
Labview 6.0
Max 3.1.0.3021
NI Visa 3.1
Agilent I/O libray M.01.01.04 ( I do not install HP VISA)
Hardware:
NI GPIB-USB-B cable
Agilent 34970A
In Max I select NIVisa Tulip.dll, and I see there is this file at C:\VXIPNP\WINNT\....
About NI VISA, I have tried many versions, all work in the same way.
Now I do not know what to do. I am driven crazy by these kind of stupid work.
The attachment is the error message.
Attachments:
error message for the Visa.bmp ‏862 KB

This is a duplicate post that can be found here.
PPLUO, please only post your question in once, because it does not help to have multiple threads about the same problem. I believe Dennis has answered this question in the thread I linked above. If he hasn't you can continue to post there.
Shawn B.
National Instruments
Use NI products on Linux? Come join the NI Linux Users Community

Similar Messages

Visa error unless logged in as admin

I'm installing a LV program on several computers running Win7. It uses VISA to communicate with three separate instruments. If I'm logged in as admin everything runs perfectly but when anyone without admin rights logs in I keep getting VISA error "resources not found". This seems to be the two serial ports on a card, COM1 which is the on board port is working. I installed this on an identical computer yesterday and did not have this problem.
Solved!
Go to Solution.

When you are logged in as the other user, what do the serial ports show up as in Device Manager? What do they look like in MAX?
I wonder if there is a setting, possibly some sort of Windows Group Policy that is locking out serial ports for non-admins.
Is this a real serial port (with DB9 connector) or is this a USB-RS-232 converter which gives a virtual com port? Perhaps if group policy is to disable USB ports for non-admins, it is blocking the converter from working. Just speculating.

How can a I solve and GPIB/VISA compatibility problem?

My Labview (version 5.1 on a Macintosh) application talks to a variety of instruments over GPIB. In one mode it communicates with both 1) a LakeShore 340 temperature controler (LS340) using VISA-based drivers and 2) a Linear Research LR-700 AC resistance bridge using low-level GPIB functions. My application can query these instruments a couple of times per second, usually without trouble. However, periodically (about once an hour) the GPIB Read will cease to work with the LR700 or any of the other instruments on the same bus, returning error 6 (I/O operation aborted). GPIB Write still works fine. Querying the LS340 when the system is in this state produces the VISA error Hex 0xBFFF003C (Insufficient system reso
urces to perform necssary memory allocation). Querying the LS340 a second time is successful, and thereafter GPIB Reads are also successful.
I think somehow the GPIB and VISA protocols are interfering with each other. (Although the data dependency requires that the VISA Write/Read be complete before the GPIB Write/Read begins, I am not opening/closing the VISA session with every iteration. The VISA session is opened on the first iteration and stored in a shift register.) However, the maddening infrequency of this problem makes it very difficult to troubleshoot. Any suggestions?

Hi Chris,
One suggestion;
Write two seperate test routines that each use only one method or the other.
Test the H*&#$ out of each to attempt to determine if the issue is associated with the high level or the the low.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Sbrio9636 VISA Error -1073807202

Hello
I have a sbRIO9636 and the test instruments. I just want to connect sbRIO and Test instruments(with RS232).
I am trying to connect RS232 (9 pin) via serial ports..I also have Measurement & Automation Explorer (ver 5.1) to monitor and configure Serial/parallel connections.
The problem is that when I query, it looks like my device is not properly recognized. I only get time-out errors. VISA Error -1073807202. But when I connect the Test instruments directly to PC, NI Max shows COM 1 and can get the data from the test instrumnets. That means, I can get the data from PC , but I can't do the same with sbRIO9636.
How can I ensure that my device is properly recognized? Is my COM1 port activated at all? I can't see COM Port in NI Max for sbRIO9636.
thank you!
Solved!
Go to Solution.

Hey Kellydog
This is a kB what the VISA Error -1073807202 is.
http://digital.ni.com/public.nsf/allkb/10C6C0FBB8E7BD4486257850006CE8FF?OpenDocument
maybe this will fix your problem.
best regards,

Visa Error in MAX for Compact RIO

Hi,
I have a compact rio I haven't used in a few months. In Labview 7.1 and since upgrading to 7.1.1, I can't
connect to the compact rio. In MAX, I can see the crio device. When I open up the device, I get a VISA error
under Devices and Interfaces . 0xBFFF00A7 (VI_ERROR_MACHINE_NAVAIL). I can't ftp or ping to the crio either.
I have NI-RIO 1.2.
I connected to the crio console ....
General Software STPC Embedded BIOS 2000 (tm) Revision 5.2
Copyright (C) 2003 General Software, Inc.
Copyright (C) 2004 National Instruments Corp.
NI cRIO-9002 Controller
00000589K Low Memory Passed
00064512K Ext Memory Passed
Wait.....
PCI Device Table.
Bus Dev Func VendID DevID Class Irq
00 0B 00 104A 0201 Host Bridge
00 0C 00 104A 0210 ISA Bridge
00 0D 00 104A 0229 IDE Controller 11
00 0E 00 104A 0230 Serial Bus 11
00 0F 00 104A 0238 Ethernet 11
00 18 00 1093 70F7 Unknown Device 11
00 1F 00 104A 0981 Ethernet 10
(C) 1996-2003 General Software, Inc.
STPC-5.2-01DE-EB2E
BIOS revision: 1.1.9 (08/10/04)
Firmware revision: 10.1.94
Booting LabVIEW RT from drive...
Fat16
Jumping to 07E0:0000
Checksum: 011BCEEB
LabVIEW RT Boot Loader
(C) Copyright 2002-2003 National Instruments Corporation
STE10/100A Ethernet found.
Initializing network... done. IP address is 152.50.232.157
--------------------- NI-Serial v2.5.4 for LabVIEW RT ---------------------
COM1 - | Built-In Serial Interface
Welcome to LabVIEW Real-Time 7.1
NI-VISA Server started successfully.

Hi, Raltieri,
I noticed from the text that you sent that your cRIO controller has LabVIEW RT 7.1. Since you upgraded your host computer to LabVIEW 7.1.1, you will also need to upgrade the LabVIEW image on your controller to the same version. Try reinstalling the LabVIEW RT component into the cRIO controller (in MAX, under Remote Systems, under your cRIO >> Software), and just make sure that you select 7.1.1 as the version to reinstall. Most likely that is the problem.
Please let me know if that doesn't help.
GValdes
National Instruments

Visa error handling in serial communication

Greetings,
I have a problem with the serial communication in my Labview program.
I have made an application that reads from serial port, searches for beggining characters, and later counts data after that beggining characters into variables in Labview program.
Everything work fine, but problem starts when I unplug the device from computer.
Program blocks and I could not do anything. Even Visa Close does not do anything.
I need to restart my computer to make my application works.
I made some indicators in subVi, and I see that when I unplug the device the error from READ VISA changes.
My question is: How to handle this event(error) to restart or unblock my serial device.
I am attaching a SubVi, that searches for starting characters " KBON,"
Best regards,
Chris
Attachments:
find_start.vi ‏12 KB

Hi Chris,
From the standpoint of VISA capabilities, you should be able to programmatically handle the desconection of the serial port. I am however not certain that your specific serial port hardware is OK with that.
As to how to handle disconnection using VISA:
I recommend using the "timeout" pin of the VISA Configure Serial Port VI
when the timeout is reached and no data is transferred, you will get a timeout error on the error wire.
You can then programmatically handle this error case in your code in a very similarly to this example.
I recommend experimenting to see what error codes your application throws, or alternatively you can use the VISA error codes documentation to create the case structures needed to hande these errors.
In all cases, you should close the VISA reference. Leaving the serial port rescource "open" in your operating system may be the reason why you need to restart your computer every time (as restarting will for sure free up the serial port rescource).
Best Regards,
T Simon
National Instruments
Applications Engineer
Certified LabVIEW Developer - Certified TestStand Architect

How can I solve a GPIB/VISA compatibility problem?

My Labview (version 5.1 on a Macintosh) application talks to a variety of instruments over GPIB. In one mode it communicates with both 1) a LakeShore 340 temperature controler (LS340) using VISA-based drivers and 2) a Linear Research LR-700 AC resistance bridge using low-level GPIB functions. My application can query these instruments a couple of times per second, usually without trouble. However, periodically (about once an hour) the GPIB Read will cease to work with the LR700 or any of the other instruments on the same bus, returning error 6 (I/O operation aborted). GPIB Write still works fine. Querying the LS340 when the system is in this state produces the VISA error Hex 0xBFFF003C (Insufficient system resource
s to perform necssary memory allocation). Querying the LS340 a second time is successful, and thereafter GPIB Reads are also successful.
I think somehow the GPIB and VISA protocols are interfering with each other. (Although the data dependency requires that the VISA Write/Read be complete before the GPIB Write/Read begins, I am not opening/closing the VISA session with every iteration. The VISA session is opened on the first iteration and stored in a shift register.) However, the maddening infrequency of this problem makes it very difficult to troubleshoot. Any suggestions?

Hi Dan,
I'm trying to follow your suggestion, but I can't get the VISA upgrade to function. I downloaded the NI-VISA 2.6 full development installer, which recommends uninstalling the prior version first. I couldn't find a good way to do this (the documentation is no help), so I ended up just reinstalling the entire Labview 5.1 without the VISA package. But even this approach (I tried several others) doesn't work - when I run VISA commands from within Labview after the VISA 2.6 install, I get 'unknown system error'. Any suggestions?
Chris

TestStand/LV VISA error

Hello Support,
I am encountering a VISA error while trying to Initialize a COM port using a LV-VI from Teststand. I have (3) GPIB devcies that Init properly, from the same VI. See attachments.
I am able to Init the COM port, after going into MAX and verifying VISA alias name, no actions made within MAX.
However, the problem comes back when I shutdown the system.
Dirk
Attachments:
VISA Flush COM Port error.jpg ‏315 KB
VISA Init COM Port error (VI-wiring Diagram).jpg ‏291 KB

Hello DAY-TE,
Looking at the VISA Init COM Port error wiring diagram it looks like you are initializing the port and then using VISA Open afterwards. The Initialize VI for your device should already be handling opening the resource. Check the documentation for the reset VI because resetting the device might not necessarily close the the resource so using the VISA Open would be redundant and therefore cause an error.
Ian M.
National Instruments

Intermittent VISA errors -10073807194 'connection for given session has been lost'

I am using a USB/Serial converter with FTDI chipset (VCP configured) to communicate with a serial device. There is an intermittent problem where the connection disappears, and the VISA error '10073807194' is generated. I have read carefully through the other threads related to this error, but still do not have a solution. Some background information on my set-up:
1) NI VISA 5.1.2
2) LV 2010
3) Windows 7 - 64 bit
Could windows be dropping the connection for the FTDI device when communication errors occur? Has anyone had this experience? We were previously using a prolific converter, and were encountering other communication errors where the read would timeout or only partial responses would be returned, but the VISA connection was not lost. I know the prolific converters can be problematic on 64 bit windows, so I was hoping the new converter would solve the problems.
I will post the code tomorrow, but I open the VISA session and configure the port on start up and close it when the application exits. I am using the bytes at port with the VISA read. However, the code I have has been running fine on two test machines in our office for several months. The above issues have been occuring at a customer's site overseas. We have not been able to reproduce the above problems here. There may be environmental factors at play (improper grounding, noise, etc.)
I should also mention that the original setup has this USB converter running through a hub, but the hub on their setup had to be removed due to reoccurring communication problems with this serial device, as well as other connected devices. We are going to get them to try installing a serial port on one of their PCs, and see if it eliminates the issue.
In the mean time any experience/help troubleshooting would really be appreciated. Thank you!!!
Zalusky

Well, I saw your Kudos to this post
Using "Bytes at port" on the FTDI driver can be very problematic and is the likely culprit for the behavior change. If there is any way to use a term char with the serial protocol change this.
The FTDI driver does have control of the buffer size and latency timer. Read through the documentation in this link. At the very least your polling rate for "Bytes at port" should be greater than the latency timer setting if the expected transfer is less than the buffer size. (shorten the timer )
Jeff

I am currently using Lightroom 5.6 and operating on a Mac with OSX Ver 10.9.5. I am receiving an error problem when doing the following - I am exporting selected photos from a particular Catalogue saved on Drive 1 to a folder created on another Drive whe

Hi, I am having a little trouble with exporting images to another drive and Catalogue and need some help if anyone can give me some advice
I am currently using Lightroom 5.6 and operating on a Mac with OSX Ver 10.9.5.
I am receiving an error problem when doing the following -
I am exporting selected photos from a particular Catalogue saved on Drive 1 to a folder created on another Drive where a Lightroom Catalogue has been created. In this Catalogue I have arranged for the images once exported to be moved to a different folder - I used the Auto Import process under the File dialogue box.
When processing the Export I receive an error message for each of the images being exported indicating the following -
Heading Import Results
Some import operations were not performed
Could not move a file to requested location. (1)
then a description of the image with file name
Box Save As Box OK
If I click the OK button to each image I can then go to the other Catalogue and all images are then transferred to the file as required.
To click the OK button each time is time consuming, possibly I have missed an action or maybe you can advise an alternative method to save the time in actioning this process.
Thanks if you can can help out.

Thank You, but this is a gong show. Why is something that is so important to us all so very, very difficult to do?

Error "Problem occured locking WS object" while activating Proxy

Hi All,
I have move an Inbout proxy to a different Client(QA system) and in QA system that proxy shows incative.
When i tried to activate that proxy/service in Sproxy, getting error "Problem occured locking WS object".
Proxy was active in development system and was working fine without any error.
Please provide some help, what need to be done to fix this issue
Thanks
Harshit

Hi Harshit,
Try with the following steps in sequence:
1. Re-genarate the proxy in Development - Create a New Transport Reuest.
2. Transport the Proxy from PI Dev to PI OA
3. Confirm the Proxy in PI QA and then, transport the re-generated Request from ECC Dev to ECC QA.
Regards,
Pranav.

Error "Problem building schema" while invoking external webservice

Hi,
I have following problem:
I created 2 BPEL processes.
One of these processes should be called from the other as a partnerlink.
When I create the partnerlink, pointing to the deployed wsdl, I get following error "Problem building schema" when I try to access the input variable that was created by the invoke activity.
I have tried a lot of things but keep on getting this error.
When I create a new, empty BPEL process, and do exactly the same it does work!
any help would be greatly appreciated.....

Hi,
I have given this URL 'http://ws.cdyne.com/WeatherWS/Weather.asmx?WSDL'.
Now it is showing the following error
Exception occured in library handler.Not implemented.
Exception of class CX_SIDL_INTERNAL_ERROR
Please have a look into it
Regards,
Dhana

When trying to test my serial port instrument I receive Visa error 1073807346, which means that they is not enough information for Visa to access or resource does not exist.

The error I am getting is on Visa open.

I found couple of knowledge base (KB) entries that talk about Visa error 1073807346. The best way to find knowledge bases (KB) is to goto ni.com >> Support >> Advanced Search (option 3) >> type in the keywords in the box "1073807346", you will get them.
Also refer, http://www.ni.com/support/labview/visa/default.htm. Hope this helps.

I'm a character error problem in firefox. How can I solve.

I'm a character error problem in firefox. How can I solve.

Hello haruntt, please be a little more specific about the issue. In order to better assist you with your issue please provide us with a screenshot. If you need help to create a screenshot, please see [[How do I create a screenshot of my problem?]]
Once you've done this, attach the saved screenshot file to your forum post by clicking the '''Browse...''' button below the ''Post your reply'' box. This will help us to visualize the problem.
Thank you!

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)

VISA ERROR Problems

Similar Messages

Maybe you are looking for