Here Mike.  Just relax and have another glass...

my favorite shirt

Notice the socks.

Well, that's my ol thread yor talkin about I guess.  I just wanted to know both why my Control Bar wasn't showing what I thought it should and then...as things progressed... just what all the hub bub was about.  I'm still not sure I know anything more than I already did...or didn't.  I must say tho, that I did find Bub's test info quite illuminating and informative.  And other than the usual sides taking and name calling (which just washes over me like water off a ducks back) what was so all fired off-putting about it?

And then there were those of us who tried to  defuse derail the thread by commenting on the OPs hardware and how much we liked it and bought one just like it

In the loftier forums there seems to be a policy of finding the proper hammer for any nail that sticks up higher than the rest.

Everyone has their favorite hammer, and the nails must be level and organized.

I'm sure you cats from the deep south could find a more eloquent way of saying this. Up in the people's republic of Canukistan we would generally say that there's a bunch of hosers hangin' out in the X1 forum eh?

Beauty idea ampfixer.

yorolpal

Well, that's my ol thread yor talkin about I guess.  I just wanted to know both why my Control Bar wasn't showing what I thought it should and then...as things progressed... just what all the hub bub was about.  I'm still not sure I know anything more than I already did...or didn't.  I must say tho, that I did find Bub's test info quite illuminating and informative.  And other than the usual sides taking and name calling (which just washes over me like water off a ducks back) what was so all fired off-putting about it?

I was trying to help by mentioning the oddball thing I ran in to with Sonar being locked at 16bit which is kind of what it sounded like you were running in to. Where it got derailed was when I responded to a question about my setup. I should not have said it in the first place, and I should have ignored the other person when asked about it. I've been around here long enough to know better than to say anything anymore. Which leads me to ask myself a personal question, why even bother coming here anymore if you can't say anything without getting jumped and ridiculed for it?

I shouldn't have said anything other than the AUD.INI suggestion and I truly regret it olpal and offer up my sincerest apologies. How did you make out with your problem? Did you get it resolved I hope?

"The hard to understand stuff is never going to be understood because: "

Another hammer heard from.

Heck Bub, ol pal.  There's no need to apologize for hippin me to what I didn't know.  It's me that needs to thank you for the null test info!

bapu


Did this thread get moved upstairs?

Boy, that would something wouldn't it??  Wonder how you could actually get kicked upstairs?  I'm gonna work on that one.

yorolpal


As to whether my question got answered, I'd have to say yes...and pretty quickly.  Once I tried what couple folks suggested I got everything set right and showing up properly.  What I still don't know is why it shows up on the control bar but still shows up wrong (and can't be changed) in the audio dialog and why (and what the difference is) I had to go the "file" dialog to set it instead of the (greyed out) audio dialog. 

So pal, what you got it  finally set to , so I can try the same thing tonite ???

yorolpal


As to whether my question got answered, I'd have to say yes...and pretty quickly.  Once I tried what couple folks suggested I got everything set right and showing up properly.  What I still don't know is why it shows up on the control bar but still shows up wrong (and can't be changed) in the audio dialog and why (and what the difference is) I had to go the "file" dialog to set it instead of the (greyed out) audio dialog. 

This is an "upstairs" answer, but...

It's grayed out because that setting is determined by your audio drivers (at least under ASIO, I seem to recall it might be functional for the Windows driver types). 

The part in the status bar is the "record bit depth" which is subtly different from the "audio driver bit depth". But I can't think of a good reason why you would want them to be different, except maybe to set the record bit depth lower than the driver bit depth to save disk space and/or increase disk throughput.

Unfortunately CW neither documents clearly all of the audio options, nor puts the bit depth settings in the same place. 

Bub,

 FWIW, I am still a bit shocked. When someone made a pronouncement implying that the reason you state that you prefer 32 bit is that you were clipping the 24 bit, I thought for sure someone would point out the obvious.

  If you are clipping the ADC... it doesn't matter what bit depth you send out the digital pipe. Duh!
  So like, I don't know if you see it this way... but that diagnosis sort of sounds to me like an assumption that the operator doesn't know how to set a level OR recognize a clipped digital over.
  I'm not buying that... I figure you'd know if you clipped something. And just switching to 32 bit in SONAR didn't change what was going on at the place where clipping occurs. I figure you observed something, even if I don't think I know what it was. :-)



 Tip of the iceberg...


 best regards,
mike

mike_mccue

Bub,

FWIW, I am still a bit shocked. When someone made a pronouncement implying that the reason you state that you prefer 32 bit is that you were clipping the 24 bit, I thought for sure someone would point out the obvious.

If you are clipping the ADC... it doesn't matter what bit depth you send out the digital pipe. Duh!
So like, I don't know if you see it this way... but that diagnosis sort of sounds to me like an assumption that the operator doesn't know how to set a level OR recognize a clipped digital over.
I'm not buying that... I figure you'd know if you clipped something. And just switching to 32 bit in SONAR didn't change what was going on at the place where clipping occurs. I figure you observed something, even if I don't think I know what it was. :-)

Tip of the iceberg...

best regards,
mike

Yes, I saw it how you did Mike. I'm really starting to doubt the self proclaimed sincerity of some folks upstairs. There's one of two reasons someone would make the clipping comment ... 1. They have no clue. or 2. They are just trying to cause an argument.

This Fast Track Ultra has always corrupted my wav files. It did it in 8.0, 8.5~8.5.3, X1~X1b, in XP on a P4, and in XP and Windows 7 on my current i5. That's the main reason I got Sound Forge years ago was to fix the errors. You can see exactly what it does, it takes one sample and peaks it to 0db. I take it in to SF, zoom in, use the draw tool to smooth out that one sample, and it's fixed. It hasn't done that once since switching to 32bit. But if I have to get this tedious with my explanations on every thread to avoid being treated like a **** ... then it's just not worth it anymore. You know what I mean? I'm just tired of it.

It's too frustrating and I just give up. It is just not worth the aggravation anymore and I have too many other things to worry about besides some troll on the internet countering everything I saw even when he's wrong and knows it.

And I see the insanity continues. There's talk of sodomy now, but I assure you the admin will do nothing about it until I speak up for myself. Then somehow I'll be made out to be the bad guy.