[haiku-bugs] Re: [Haiku] #1351: aliasing is heared with playback 44.1kHz files on 48kHz system sample rate

  • From: "stargatefan" <trac@xxxxxxxxxxxx>
  • Date: Sun, 10 Oct 2010 05:52:09 -0000

#1351: aliasing is heared with playback 44.1kHz files on 48kHz system sample 
rate
-----------------------------+----------------------------------------------
  Reporter:  nutela          |         Owner:  pulkomandy   
      Type:  bug             |        Status:  assigned     
  Priority:  normal          |     Milestone:  R1           
 Component:  Kits/Media Kit  |       Version:  R1/pre-alpha1
Resolution:                  |      Keywords:               
Blocked By:                  |   Has a Patch:  0            
  Platform:  x86             |      Blocking:               
-----------------------------+----------------------------------------------

Comment (by stargatefan):

 Replying to [comment:15 stippi]:
 > To stargatefan: The system works just fine in principle. Audio
 applications *can* do their own mixing and can have a single master
 output, if they so chose. Clockwerk and I think any other current
 BeOS/Haiku audio app is using such a setup today. There is nothing wrong
 with, and it's in fact required to have a global system mixer. And since
 sound cards have mostly one sound input, it's only logical to drive it in
 the highest frequency that the hardware allows (which is what Haiku
 currently does). Most movies use 48 kHz, most music is 44.1 kHz -- so what
 should one pick? In theory, the mixer could be improved to switch the
 audio hardware to the highest sampling rate of current mixer inputs. If
 there is only one input, use the sampling rate of that one. I don't think,
 however, that with a proper resampling implementation, it would make any
 practical difference. In fact it would just make the code more complicated
 and probably introduce audible hickups when there is already one mixer
 input playing and another one is added which causes a switch to a higher
 sampling rate.
 >
 > Really, fixing the resampling is all that needs to be done here.
 >


     Well in certain case resampling is the only option as hardware may
 only support one type of input and files are in another. no argument
 there. My concern is that mixer is really becoming more then it needs to
 be. whiles it great the I can watch 6 videos and listen to dozens of mp3's
 and or wav files all at the same time. Its not a very practical design for
 the end user.

    Try listening to 2 different songs as the same time. Its just not
 something the human brain would want to do.

   the ASIO model of mixer handling I think we would be a big improvement
 in many ways. alot of it is already in the mixer now for the most part.
 The overall design of ASIO looks to be based in some part on the Be mixer,
 which was great in its day.

    My thought is that to some degree mixer might be getting to complex.
 the application should have the job of file conversion or the mixer master
 output. pick a resolution " of one thats available in the hardware and end
 user selectable" and just go to that regardless of what comming in.

    but applications need to be able to acess that hardware " or have acess
 to it" down the road if DAW "digital audio workstations" are ever to take
 root in this OS. I sure hope they do. Would be a huge userbase gain for
 haiku.

    so your down to the WDM and ASIO rivalry to some degree when the
 internal API dictates a specific behavioor that the application developer
 may not want, nor the end user.

   BTW thats not a knock against the OS. It works great as it is now.

    My thought it. Pass the selection of sample rate to the application.
 this leaves the API open to DAW developers. also putting in a bootstrap
 type of mode for audio hardware control and IO blocking. Highly recomened.

-- 
Ticket URL: <http://dev.haiku-os.org/ticket/1351#comment:16>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.

Other related posts: