Hi Folks,
this is my first post on this forum though I used to be Mr Apocalypse on the original mackie forum many many moons ago. My workplace has a D8b V3(166mhz I think) 32mb ram with opt8 cards going via lightpipe to an Rme 52/96 in a carillon audio pc running cubase 6.
Last year I had occasion to look at cubase statistics for a file I had recorded with the d8b and noticed it said 16bit as the resolution(we were running cubase 4 at the time), i took some example files home and checked the statistics on a copy of sx2 which I had - they came up 24bit, so I thought panic over it's a bug with cubase. This year both myself and the studio upgraded to cubase 6 and i'm still getting 16 bit as the resolution of any files recorded with the d8b. I've analysed what's going out of the desk with stillwell audio's bitter bitscope, the top 16bits look normal, but the bottom 8 bits look like copies of a single bit though when i make a noise in the channel's mic this block of bits is increased and breaks down, but reaches the width of the bitscope which bitter's helpfile says is an indication of something being wrong. So technically there are 24bits being used cos the last 8bits are there, but there is something wrong/abnormal with them.
Now I know what you're thinking did I install the 16/24 patch that fixes the old vs 16bit output problem, well yes I did - years ago though as we were using an HDR24/96 i had no way of testing that it worked (our v3 is showing build 224 by the way). A horrible thought is that I've been recording in 16bit for the last 10 years.
So I'm still testing things - I've blown up the files in cubase and added 40db and compared them visually to known 24bit files - the mackie audio is definitely coming out 16bit. Of course cubase is writing them as 24bit files, so I tried reconverting the mackie files to 16bit proper and phase cancelling with the original _ a lot of noise is present in the cancelled out sum and distortion in the loud passages, noise is aprox -103db I have amplified it and blown it up this noise is 16bit stepped with the odd very miniscule 24bit sized ripple - this is the wierd blocking that i'm seeing in the lower 8 bits in bitter, but just viewd as a waveform
. I tried turning the mic down to minimum while watching bitter and could never get the 16th bit to switch off, even if I turned down the d8b digital trim to anything other than off. the only thing that will switch the 16th bit off is turning down the level to tape, interestingly you have to turn it down very far before cubase will acknowledge anything other that 16bit - I think I had to turn it down about 15bd's or so just to get a supposedly 20bit file (which makes me think that the old work around for the 16bit issue was an illusion as all it did was decrease the stepping in an already 16bit file). Also I've sent a known 24bit signal from cubase through the tape in 3 off the desk and routed to tape on channel one and It definitely comes back into cubase as a 24bit file. I've tried switching compression, eq gate on a off - no difference. The only time I can get the analogue going in to become 24bit going out is when I switch on the uv, bit it's only the uv that would appear to be operating at 24bit (or have some bits down there) and I don't want to be compressing uv afterwards . If this were the old fashioned analogue world I'd had said that the problem lies somewhere at the input (AD), but of course It would be that simple lol.
I need to fix this, or replace the desk. I realise that neither myself nor any other clients (including a number of successful musicians and producers) have noticed that there was a problem, but now that I know there is a problem it would be dishonest to pretend otherwise and professionally that is not an option. It's an old desk, true, but as it's not mine I'm not sure whether a replacement can be bought and how long that would take (the replacement certainly has to do less that the d8b started out doing - I only use it for ad da conversion and cue mixes - all my mixing in done inside cubase).
Does anyone else have/had the same problem
- is everyone else certain that they don't??????
Would upgrading to V5 fix this or is it possibly something else.
Help please!!!
thanks for reading
Mark