Open-source USB interface: Audio Widget - Page 183 - diyAudio
Go Back   Home > Forums > Source & Line > Digital Source

Digital Source Digital Players and Recorders: CD , SACD , Tape, Memory Card, etc.

Please consider donating to help us continue to serve you.

Ads on/off / Custom Title / More PMs / More album space / Advanced printing & mass image saving
Reply
 
Thread Tools Search this Thread
Old 17th September 2012, 06:39 AM   #1821
cviller is offline cviller  Denmark
diyAudio Member
 
cviller's Avatar
 
Join Date: Dec 2005
Location: Copenhagen
Blog Entries: 2
Quote:
Originally Posted by linuxworks View Post
windows used to force a default resample. that's no longer the case.

it was never the case with linux or alsa. the only time a resample was requested was when the output samplerate != input samplerate.

when I mpd over alsa and leave all options as defaults, I never get my 44.1 stuff upsampled to 48k. I have leds that show the actual output and I'd notice this
I have no idea about how it works on windows, but in Linux, major distributions still resample to 48k in order to be able to play 44.1 content together with 48k - it is done as part of the mixer. On mpd wiki, they do touch on the subject:
Tuning - Music Player Daemon Community Wiki

So if mpd is driving up cpu load, I would make sure the hw_params read what you are expecting.
  Reply With Quote
Old 17th September 2012, 04:49 PM   #1822
diyAudio Member
 
linuxworks's Avatar
 
Join Date: Jul 2008
Location: santa clara, CA
in all my life using linux, I have never seen any resampling that was not due to:

1) sound card reporting it does NOT support samplerate R
2) a forced manual over-ride setting
3) mixing playback of 2 or more mixed samplerate streams (mixer will have to sort this out)

absent of those 3, I am not convinced that any auto conversion happens. and again, when I look at the leds on my spdif meter, I never see a 48k light come on (ever!) when I play 44.1 music.

I would not worry much about samplerate conversion. its not the big problem on linux that it once was on windows.
__________________
My Photostream:http://www.flickr.com/photos/linux-works/
  Reply With Quote
Old 17th September 2012, 06:19 PM   #1823
diyAudio Member
 
linuxworks's Avatar
 
Join Date: Jul 2008
Location: santa clara, CA
just read the alsa link you posted.

I think you are confused. here's what it says:

Dmix resamples everything to 48khz. (see above url). You can force dmix to resample at 44.1khz, by setting (in /etc/asound.conf or ~/.asoundrc):

that's dmix. dmix is NOT required and is not mandatory for alsa to work.

I don't run dmix and most people don't, either.

more info:

NOTE: For ALSA 1.0.9rc2 and higher you don't need to setup dmix for analogue output. Dmix is enabled by default for soundcards which don't support hardware mixing. You still need to set it up for digital outputs.

Dmix - ALSA wiki

and for us, who use digital outputs, it does not sound like dmix is at all useful or even wanted. the AW certainly announces to linux that it supports all valid samplerates. unless you configure dmix, I don't think it will get in your way in the way you are saying.
__________________
My Photostream:http://www.flickr.com/photos/linux-works/
  Reply With Quote
Old 22nd September 2012, 03:04 PM   #1824
johnm is offline johnm  United Kingdom
diyAudio Member
 
johnm's Avatar
 
Join Date: Sep 2003
Location: Hampshire
Quote:
Originally Posted by alexlee188 View Post
Hi John,

1. Your firmware version is too old to work with the WidgetControl version in AWSetup.

2. My recommendation is for you to update your firmware (flash the firmware) to the latest experimental version (using the instructions for Win7):

audio-widget-ex-2012-08-13.elf - sdr-widget - Experimental audio firmware 2012-08-13 - Audio and Control Interface for Amateur Radio SDR and Audiophile USB-DAC - Google Project Hosting

3. Also, uninstall completely your version of AWSetup and removing the ASIO uac2 driver as well.

4. Install instead the latest experimental ASIO driver:

https://sites.google.com/site/nikkov...edirects=0&d=1

5. Follow the same instructions to install the latest experimental ASIO driver and then use the WidgetControl to set things up. DAC type should now be "generic" and Quriks "quirk_none".

Please do the above and post a screenshot of WidgetControl for me to verify that all are in order.

The latest "experimental" firmware and AWSetup (ASIO driver) has a number of improvements, including:

(a) Once setup, the audio-widget will work under Windows, Linux and OSX.

(b) Under Win7, you can set the audio-widget to uac1_audio (using WidgetControl) and the device will be enumerated as an "ordinary" sound card that you can use for system sound and all sound/music player programs. When you set the audio-widget to uac2_audio, you will be using Nikolay's ASIO uac2 driver and ONLY programs that support ASIO will play. E.g. Foobar2000 with (a separately downloaded and installed) ASIO plugin. JRiver also works. There may also be a plugin for Windows Media Player. However, you will NOT find the audio-widget listed by non-ASIO compatible software. Also Windows will not list it as a "sound" device.

The reason the latest firmware/Win uac2 driver are still "experimental" is that we are putting in more features, eg. HID controls, sampling rate indicater leds, etc., in preparation for future versions of the audio-widget.

Alex
Hi Alex.

Apologies for the delay in getting around to trying this out.

Have gone through the latest readme file, and followed it to the letter. Firmware flashed OK with no error messages. Uninstalled the original AWSetup drivers. Installed the AWlatestexperimental software instead.

In UAC1 mode, Window7 seems fine. However when switching to UAC2 (manually, on the rear of the DAC unit) the Widget Control now says 'device not found!'. When I switch back to UAC1 manually, all the information is in there and displayed correctly again. Obviously I have done something wrong somewhere, but I do not know what and it's driving me nuts. Again.

Here's a screenshot of my latest settings:
Attached Images
File Type: gif AW-screen.GIF (87.3 KB, 185 views)
File Type: gif devices.GIF (38.9 KB, 182 views)
File Type: gif devicenotfound.GIF (81.5 KB, 180 views)

Last edited by johnm; 22nd September 2012 at 03:16 PM.
  Reply With Quote
Old 22nd September 2012, 03:23 PM   #1825
johnm is offline johnm  United Kingdom
diyAudio Member
 
johnm's Avatar
 
Join Date: Sep 2003
Location: Hampshire
EDIT: DAC works (whew!) in UAC2 mode using Foobar2000 and ASIO, but just will not show up in Widget Control, unless set back to UAC1.

Is this how it should be?
  Reply With Quote
Old 22nd September 2012, 03:31 PM   #1826
diyAudio Member
 
Join Date: Apr 2011
The new Widget Control will work in both uac1 and uac2 modes. However, you need to remove the old libusb drivers.

The old widget control uses libusb drivers. The new experimental widget control uses libusbk drivers. You must be having your libusb drivers still installed, thus the libusbk driver cannot connect to the widget in uac2 mode (as the widget has already been captured by the libusb driver).

To completely remove old drivers:

Uninstall Hidden Devices, Drivers, and Services | a Tech-Recipes Tutorial

You need to remove all libusb drivers related to the widget.

This is (one of the) problems with Windows :-)

Alex
  Reply With Quote
Old 22nd September 2012, 03:32 PM   #1827
johnm is offline johnm  United Kingdom
diyAudio Member
 
johnm's Avatar
 
Join Date: Sep 2003
Location: Hampshire
Thanks for the super-speedy reply Alex - much appreciated

I did all that following the readme file, but perhaps I didn't remove it correctly - Will try again.

I'll do that now and report back...
  Reply With Quote
Old 22nd September 2012, 03:58 PM   #1828
johnm is offline johnm  United Kingdom
diyAudio Member
 
johnm's Avatar
 
Join Date: Sep 2003
Location: Hampshire
Looks fine to me:
Attached Images
File Type: gif drivers.GIF (153.7 KB, 173 views)
  Reply With Quote
Old 22nd September 2012, 04:00 PM   #1829
johnm is offline johnm  United Kingdom
diyAudio Member
 
johnm's Avatar
 
Join Date: Sep 2003
Location: Hampshire
Found these in the ATMEL driver section though - should I delete all these?
Attached Images
File Type: gif delete.GIF (29.3 KB, 172 views)
  Reply With Quote
Old 22nd September 2012, 04:21 PM   #1830
diyAudio Member
 
Join Date: Apr 2011
No. Not these Atmel ones. These are needed to flash firmware.

Did you click the view hidden drivers option etc. As described in the instructions?

Those drivers have Alex, Loftur in the driver descriptions.
  Reply With Quote

Reply


Hide this!Advertise here!
Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Async 192Khz USB - the SDR-Widget collaborative project SunRa PC Based 5 26th April 2011 06:38 PM
usb audio interface david12 Equipment & Tools 14 10th October 2010 02:58 AM
Cheap Audio Interface (USB?) to PC agm2003 Instruments and Amps 11 16th September 2007 07:48 AM
Open call for suggestions on Open Source DIY Audio Design gfergy Everything Else 1 15th April 2007 07:33 AM
USB Interface Perfect?- Computer Audio fmak Digital Source 3 4th December 2004 10:24 PM


New To Site? Need Help?

All times are GMT. The time now is 07:07 PM.


vBulletin Optimisation provided by vB Optimise (Pro) - vBulletin Mods & Addons Copyright © 2014 DragonByte Technologies Ltd.
Copyright 1999-2014 diyAudio

Content Relevant URLs by vBSEO 3.3.2