S
SampleX
New member
Hi gang,
I'm a n00b here and signed up to be able to ask a question of the wise who, no doubt, already have the answers to my problems...
I've been put in charge of modernising a church 'recording' system with a view to preparing audio files for a website, most specifically I'm charged with simplifying the work flow for this effort.
We currently have a very simple, very adequate setup and in the past have recorded to now-obsolete audio cassettes. We also have a Pioneer CD Recorder (consumer, not computer) in the stack where previously we have been able to take a CD recording and then rip to computer, remove track breaks and then edit down and resample for the net.
I wanted to go even simpler than this, recording directly into the computer, but I've had some bizarre and unexpected results.
First week out was the weirdest, about four weeks back...
Our setup runs pretty much like this:
All instruments and Mic's go into a Mackie CFX12, and for PA we use SRM-450's. We were running a 'tape out' from the Mackie to a tape deck, then the tape out of the tape deck was run into the line in of the CD recorder and the CD Out of the CD recorder ran into the AUX channel on a standard stereo amp (Sony) for playback in our overflow/creche through normal stereo speakers. The system worked perfectly for years and the signal flow was as follows:
Mixer (Tape Out) --> Tape IN (Tape Out) --> CD IN (CD OUT) --> AMP
I just need to emphasise again, that while whoever set this up originally didn't follow the 'best practice' rules, this setup really worked and we had some pristine CD and - ahem - tape recordings of a genuine representation of the sound board mix.
Now, if I were redoing this, I would run the Tape Out of the Mackie to the AMP AUX IN, and then run outputs from TAPE 1 and TAPE 2 of the amp to the tape deck and the CD recorder respectively, so that the AMP gets the first signal and the two recording devices get the same signal independently of each other. In fact, in recent weeks we've tried using elements of this signal flow as we mess around with trying to get the computer in on the signal.
So... the weirdness begins as follows.
I decided to use my ever-present Samsung NC10 (Atom Netbook) as my primary recording device for portability's sake, so I installed both Adobe Audition and Sony Sound Forge, as well as Audacity and tested that they seemed to work even on this low-CPU computer, and everything appeared to be fine.
Since we were not going to be using the CD Recorder if the computer was going to work, what we did the first week was to simply bypass the CD Recorder and cut out the overflow feed, which we didn't need that week, and so the signal flow ran as follows:
MACKIE (Tape Out) --> Tape IN (Tape OUT) --> Samsung NC10 Audio IN
Emphasis is that the TAPE deck was still the first device to receive the signal, and would be passing a signal to the computer, not receiving one from it. I make this note because I SO did not expect what happened next...
The Mackie was connected via Cambridge Audio premium RCA (phono) cables to the tape, the tape via the same cable type to a 'Y' adaptor to convert a stereo phono pair (RCA) to a single stereo 3.5mm jack into the computer.
With the Samsung Audio IN (which I now know to be a 'MIC IN' jack) plugged in, the REC LEVEL on the tape deck suddenly went through the threshold and into nearly constant red (signal clipping) and adjusting the REC LEVEL on the tape deck didn't alter that. The signal into the computer also went similarly hot and but levels could be normalised by turning the REC LEVEL on the tape deck way down, even though this didn't make the slightest difference to the tape deck itself. If I unplugged the cable from the computer rec IN, the levels immediately went back to normal and the REC LEVEL had to be turned up to give the tape deck a workable signal. This was the same whether the audio software on the computer was Sony or Adobe or Audigy.
Further tests and attempts to verify that the right cables were plugged in the right places yielded the same results, and I concluded that there was some kind of issue with the computer port being a MIC IN rather than LINE IN which was somehow causing some kind of surge in gain or something, don't know the science behind 'why', but would love to...
Nonetheless, by forgetting about the recording on the tape (which would have had the levels blown out I presume), by reducing the REC LEVEL on the tape deck until the signal monitoring on the NC10 produced a consistent signal within acceptable peak ranges, the computer picked up a perfect recording of the message that morning, maybe a little less rich than the soundboard mix itself, but as near as anything I've ever heard, all directly into the MIC IN jack on the NC10, which probably doesn't actually have the best sound card in the world anyway.
Anyway, I decided to move on to plan B and I remembered that I owned a Griffin iMic which was originally purchased to allow an Apple iBook (sans audio ports) to be used to transfer audio tapes into the computer for editing, de-hiss and digital conversion. The principle of the iMic is essentially an analog/digital converter to USB and the device is compatible, allegedly, with the Windows XP running on the Samsung Netbook as well as Mac OS X.
So the next week I went to set up the recording equipped with the iMic which, after a bit of fiddling, the NC10 recognised and would receive a signal from. The iMic is switched into LINE IN mode rather than MIC, and appears to cause no clashes. I also concluded that in the absence of a power amp in the mix, the MAIN OUT on the Mackie was basically the same line output as the TAPE OUT, just using different cables (TSR instead of RCA), so I decided that since the 'MAIN OUT' was not needed since the PA system was running on self-powered SRM450's on the MAIN OUT XLR channels, I cable-converted the MAIN OUT's TSR's to RCA's into the AUX channel of the overflow amp, and then ran an RCA pair from TAPE 1 OUT on the overflow amp to REC IN on the CD Recorder. This, incidentally, works perfectly. I was then able to use the TAPE OUT from the Mackie via the Y adapter to the LINE IN on the Griffin iMic into the NC10 by USB.
The downside to this is that I haven't been able to set up live monitoring of the signal being recorded into the computer, so I've had no idea until now WHAT was being recorded. Nonetheless, for three weeks we've run this system, and sure enough not only does the CD record, and the overflow works, but the NC10 running EITHER Sony Sound Forge or Adobe Audition has been able to record single stereo tracks featuring the audio from the mix on the Mackie without any apparent issue. Audition simply records the track in 'real time', while Sound Forge gives me a 'monitoring' panel in which I can see signal levels on a live chart and in which they never 'red line' but seem to peak at about three quarters the available level, usually hovering around 50% on the meter. I noticed on the tracks as they were recording that I didn't have a big dramatic 'wave' to observe, but rather a very understated, seemingly muted, waveform, even when magnified significantly.
I started to wonder if I was getting a very low 'line' signal and would somehow need to boost amplitude in order to make it more listenable, but I couldn't specifically see any settings to let me do that 'live' or to preview it. Nonetheless, I thought it was simply something I could do later.
Until this week...
I came to sit down with the three audio files we had, and start to listen to them, edit them, work with them, and what I heard was simply horrible. It was very low indeed, even on headphones and the computer on full volume, and worse than that, it sounded hollow, stripped and like there was some kind of 'phase' fluctuating on the signal as even background ambient noise seemed to soar and then dip variously throughout the recording.
To be honest my first thought was 'is this what's been coming out of the mixer? is this what people hear? has someone 'dusted' the board and changed EQ settings? is this what we're recording?' and so I went down early today to find out.
What I safely concluded was that what the computer is receiving from the TAPE OUT on the Mixer via the iMic to USB is NOT what the mix from the Mackie actually sounds like live, nor is it what the Mixer is delivering via MAIN OUT (XLR) to the powered speakers, nor indeed is it what the Mixer is delivering via MAIN OUT (TSR) to the overflow amp and the CD recorder. In fact, it isn't even what the Mackie is delivering via TAPE OUT when the TAPE OUT connects directly to the overflow amp or even the CD Recorder.
The amp mix, the headphone monitoring on the Mackie, and the CD Recording made this morning all sound loud, clear, rich, and exactly what I would expect from my sound mix out of the Mackie.
In short, either the iMic is chuffing things up, or the computer is chuffing things up, or there's something I'm not doing/the equipment is all wrong.
Unless someone can tell me that the Atom powered NC10 is somehow so limited in power that it is the CPU in the machine which is injecting these problems, which I find hard to imagine because I've read on the 'net of other NC10 users using their pooter for digital audio recording in live situations, then I've got to go with either the iMic is unsuitable, or there's something else that I'm missing.
I remember in the 'old days' using a Digidesign AudioMedia 3 card and ProTools on a PowerMac to record from taped messages to computer hard disk, and because the Audiomedia 3 interface was a non-powered PCI card with RCA inputs we would have to run the tape RCA OUT into a Loom 4 channel 9v battery powered micromixer and then back out of the Loom into the Audiomedia 3 in order to boost the gain on the inputs so as to be able to give ProTools an adjustable gain level in order to set the input to just below the clipping threshold. I assumed that in the 'USB Analog/Digital Converter' days that signal was just signal and no such micro-mixer based gain'd input would be needed, especially as I'm currently unable to even undertake real-time monitoring of what the pooter is receiving. Is it this simple? Is that what I needed to do? That still doesn't account for why it isn't simply a low level signal that is recording, it doesn't account for the pinched, nasal, nasty-EQ phasey sound that I'm actually recording which sounds like robotic digital garbage.
Incidentally, today I ran both Sound Forge and Audacity recording on the iMic input simultaneously, and they both recorded the same crap, so the phenomenon is independent of the application. I did notice what appeared to be a live input gain setting on Audacity, which didn't discernibly alter either the quality of the signal, or for that matter have much influence on the level. The overflow amp system and the CD Recorder got perfect recordings
Is the NC10 the wrong machine?
Is the Griffin iMic the wrong external sound to USB adapter?
Am I missing a stage here?
The iMic has a setting to allow you to switch the input of the iMic from 'Line' to 'Mic', and I even tried setting it to 'Mic' instead of Line using the same TAPE OUT feed from the sound board to see if that yielded even a different recording, but it didn't make a noticeable difference.
The fact that the first recording we did sounded very good indeed using the plain old Mic IN on the Samsung but needed the TAPE REC LEVEL to be adjusted almost as if it were being activated like a volume/gain control reminds me of the faffing about with taking a signal from a tape deck into a micromixer and then into the Audiomedia 3 card on a Mac, but surely these external USB devices are designed to do away with that stage?
By default, all the recordings made so far (one good in a bad setup, and four bad in what appeared to be a good setup) have had the same 'default' settings in Sound Forge, using a sample rate of 44,100 Hz and a 16 bit-depth, stereo channel.
I'm sure that someone is going to tell me (and I can make clips of these different audio recordings if you want to message me, so you can hear what I'm talking about in terms of the difference between the 'good' recordings without the iMic, and the bad recordings with the iMic) that I'm an idiot, and that the answer is elementary, and it probably even has something to do with the theory behind what is a 'LINE' level signal and what is a MIC level signal, and what should be attenuated, and yada yada... I didn't go to sound engineering school... I know computers, and I know how to create music with instruments, and I even know a tiny bit (evidently) about how to do some rough mixing with the Mackie and get the sound levels right in our premises. This is just beating the stuffing out of me right now, so be gracious.
I'm sure its very easy to someone, and I'll probably go 'oh, what a doughnut...' but I'd love to know WHAT it is that I'm doing wrong, WHY it is wrong, and what to do next.
Is it as simple as the iMic being duff? Should I be using an M-Audio Transit? I can handle having to replace a piece of kit if and only if that's definately what it is... I wouldn't want to go out and buy 'better kit' because of someone's theory that the Griffin iMic is crap and should be binned, only to find that it makes no difference at all.
I also have, available to hand, a Mackie Spike Recording interface, which I could try. The reason I haven't started out with the Spike on this project is simply portability and convenience.
Can anyone please help me with this?
I've tried to give as full an account as I can, sorry if I bored you, but I'm sure that someone out there knows either from experience or because they have impeccable Digital Audio knowledge EXACTLY what this problem is and why...
Please help.
Thanks,
S.
I'm a n00b here and signed up to be able to ask a question of the wise who, no doubt, already have the answers to my problems...
I've been put in charge of modernising a church 'recording' system with a view to preparing audio files for a website, most specifically I'm charged with simplifying the work flow for this effort.
We currently have a very simple, very adequate setup and in the past have recorded to now-obsolete audio cassettes. We also have a Pioneer CD Recorder (consumer, not computer) in the stack where previously we have been able to take a CD recording and then rip to computer, remove track breaks and then edit down and resample for the net.
I wanted to go even simpler than this, recording directly into the computer, but I've had some bizarre and unexpected results.
First week out was the weirdest, about four weeks back...
Our setup runs pretty much like this:
All instruments and Mic's go into a Mackie CFX12, and for PA we use SRM-450's. We were running a 'tape out' from the Mackie to a tape deck, then the tape out of the tape deck was run into the line in of the CD recorder and the CD Out of the CD recorder ran into the AUX channel on a standard stereo amp (Sony) for playback in our overflow/creche through normal stereo speakers. The system worked perfectly for years and the signal flow was as follows:
Mixer (Tape Out) --> Tape IN (Tape Out) --> CD IN (CD OUT) --> AMP
I just need to emphasise again, that while whoever set this up originally didn't follow the 'best practice' rules, this setup really worked and we had some pristine CD and - ahem - tape recordings of a genuine representation of the sound board mix.
Now, if I were redoing this, I would run the Tape Out of the Mackie to the AMP AUX IN, and then run outputs from TAPE 1 and TAPE 2 of the amp to the tape deck and the CD recorder respectively, so that the AMP gets the first signal and the two recording devices get the same signal independently of each other. In fact, in recent weeks we've tried using elements of this signal flow as we mess around with trying to get the computer in on the signal.
So... the weirdness begins as follows.
I decided to use my ever-present Samsung NC10 (Atom Netbook) as my primary recording device for portability's sake, so I installed both Adobe Audition and Sony Sound Forge, as well as Audacity and tested that they seemed to work even on this low-CPU computer, and everything appeared to be fine.
Since we were not going to be using the CD Recorder if the computer was going to work, what we did the first week was to simply bypass the CD Recorder and cut out the overflow feed, which we didn't need that week, and so the signal flow ran as follows:
MACKIE (Tape Out) --> Tape IN (Tape OUT) --> Samsung NC10 Audio IN
Emphasis is that the TAPE deck was still the first device to receive the signal, and would be passing a signal to the computer, not receiving one from it. I make this note because I SO did not expect what happened next...
The Mackie was connected via Cambridge Audio premium RCA (phono) cables to the tape, the tape via the same cable type to a 'Y' adaptor to convert a stereo phono pair (RCA) to a single stereo 3.5mm jack into the computer.
With the Samsung Audio IN (which I now know to be a 'MIC IN' jack) plugged in, the REC LEVEL on the tape deck suddenly went through the threshold and into nearly constant red (signal clipping) and adjusting the REC LEVEL on the tape deck didn't alter that. The signal into the computer also went similarly hot and but levels could be normalised by turning the REC LEVEL on the tape deck way down, even though this didn't make the slightest difference to the tape deck itself. If I unplugged the cable from the computer rec IN, the levels immediately went back to normal and the REC LEVEL had to be turned up to give the tape deck a workable signal. This was the same whether the audio software on the computer was Sony or Adobe or Audigy.
Further tests and attempts to verify that the right cables were plugged in the right places yielded the same results, and I concluded that there was some kind of issue with the computer port being a MIC IN rather than LINE IN which was somehow causing some kind of surge in gain or something, don't know the science behind 'why', but would love to...
Nonetheless, by forgetting about the recording on the tape (which would have had the levels blown out I presume), by reducing the REC LEVEL on the tape deck until the signal monitoring on the NC10 produced a consistent signal within acceptable peak ranges, the computer picked up a perfect recording of the message that morning, maybe a little less rich than the soundboard mix itself, but as near as anything I've ever heard, all directly into the MIC IN jack on the NC10, which probably doesn't actually have the best sound card in the world anyway.
Anyway, I decided to move on to plan B and I remembered that I owned a Griffin iMic which was originally purchased to allow an Apple iBook (sans audio ports) to be used to transfer audio tapes into the computer for editing, de-hiss and digital conversion. The principle of the iMic is essentially an analog/digital converter to USB and the device is compatible, allegedly, with the Windows XP running on the Samsung Netbook as well as Mac OS X.
So the next week I went to set up the recording equipped with the iMic which, after a bit of fiddling, the NC10 recognised and would receive a signal from. The iMic is switched into LINE IN mode rather than MIC, and appears to cause no clashes. I also concluded that in the absence of a power amp in the mix, the MAIN OUT on the Mackie was basically the same line output as the TAPE OUT, just using different cables (TSR instead of RCA), so I decided that since the 'MAIN OUT' was not needed since the PA system was running on self-powered SRM450's on the MAIN OUT XLR channels, I cable-converted the MAIN OUT's TSR's to RCA's into the AUX channel of the overflow amp, and then ran an RCA pair from TAPE 1 OUT on the overflow amp to REC IN on the CD Recorder. This, incidentally, works perfectly. I was then able to use the TAPE OUT from the Mackie via the Y adapter to the LINE IN on the Griffin iMic into the NC10 by USB.
The downside to this is that I haven't been able to set up live monitoring of the signal being recorded into the computer, so I've had no idea until now WHAT was being recorded. Nonetheless, for three weeks we've run this system, and sure enough not only does the CD record, and the overflow works, but the NC10 running EITHER Sony Sound Forge or Adobe Audition has been able to record single stereo tracks featuring the audio from the mix on the Mackie without any apparent issue. Audition simply records the track in 'real time', while Sound Forge gives me a 'monitoring' panel in which I can see signal levels on a live chart and in which they never 'red line' but seem to peak at about three quarters the available level, usually hovering around 50% on the meter. I noticed on the tracks as they were recording that I didn't have a big dramatic 'wave' to observe, but rather a very understated, seemingly muted, waveform, even when magnified significantly.
I started to wonder if I was getting a very low 'line' signal and would somehow need to boost amplitude in order to make it more listenable, but I couldn't specifically see any settings to let me do that 'live' or to preview it. Nonetheless, I thought it was simply something I could do later.
Until this week...
I came to sit down with the three audio files we had, and start to listen to them, edit them, work with them, and what I heard was simply horrible. It was very low indeed, even on headphones and the computer on full volume, and worse than that, it sounded hollow, stripped and like there was some kind of 'phase' fluctuating on the signal as even background ambient noise seemed to soar and then dip variously throughout the recording.
To be honest my first thought was 'is this what's been coming out of the mixer? is this what people hear? has someone 'dusted' the board and changed EQ settings? is this what we're recording?' and so I went down early today to find out.
What I safely concluded was that what the computer is receiving from the TAPE OUT on the Mixer via the iMic to USB is NOT what the mix from the Mackie actually sounds like live, nor is it what the Mixer is delivering via MAIN OUT (XLR) to the powered speakers, nor indeed is it what the Mixer is delivering via MAIN OUT (TSR) to the overflow amp and the CD recorder. In fact, it isn't even what the Mackie is delivering via TAPE OUT when the TAPE OUT connects directly to the overflow amp or even the CD Recorder.
The amp mix, the headphone monitoring on the Mackie, and the CD Recording made this morning all sound loud, clear, rich, and exactly what I would expect from my sound mix out of the Mackie.
In short, either the iMic is chuffing things up, or the computer is chuffing things up, or there's something I'm not doing/the equipment is all wrong.
Unless someone can tell me that the Atom powered NC10 is somehow so limited in power that it is the CPU in the machine which is injecting these problems, which I find hard to imagine because I've read on the 'net of other NC10 users using their pooter for digital audio recording in live situations, then I've got to go with either the iMic is unsuitable, or there's something else that I'm missing.
I remember in the 'old days' using a Digidesign AudioMedia 3 card and ProTools on a PowerMac to record from taped messages to computer hard disk, and because the Audiomedia 3 interface was a non-powered PCI card with RCA inputs we would have to run the tape RCA OUT into a Loom 4 channel 9v battery powered micromixer and then back out of the Loom into the Audiomedia 3 in order to boost the gain on the inputs so as to be able to give ProTools an adjustable gain level in order to set the input to just below the clipping threshold. I assumed that in the 'USB Analog/Digital Converter' days that signal was just signal and no such micro-mixer based gain'd input would be needed, especially as I'm currently unable to even undertake real-time monitoring of what the pooter is receiving. Is it this simple? Is that what I needed to do? That still doesn't account for why it isn't simply a low level signal that is recording, it doesn't account for the pinched, nasal, nasty-EQ phasey sound that I'm actually recording which sounds like robotic digital garbage.
Incidentally, today I ran both Sound Forge and Audacity recording on the iMic input simultaneously, and they both recorded the same crap, so the phenomenon is independent of the application. I did notice what appeared to be a live input gain setting on Audacity, which didn't discernibly alter either the quality of the signal, or for that matter have much influence on the level. The overflow amp system and the CD Recorder got perfect recordings
Is the NC10 the wrong machine?
Is the Griffin iMic the wrong external sound to USB adapter?
Am I missing a stage here?
The iMic has a setting to allow you to switch the input of the iMic from 'Line' to 'Mic', and I even tried setting it to 'Mic' instead of Line using the same TAPE OUT feed from the sound board to see if that yielded even a different recording, but it didn't make a noticeable difference.
The fact that the first recording we did sounded very good indeed using the plain old Mic IN on the Samsung but needed the TAPE REC LEVEL to be adjusted almost as if it were being activated like a volume/gain control reminds me of the faffing about with taking a signal from a tape deck into a micromixer and then into the Audiomedia 3 card on a Mac, but surely these external USB devices are designed to do away with that stage?
By default, all the recordings made so far (one good in a bad setup, and four bad in what appeared to be a good setup) have had the same 'default' settings in Sound Forge, using a sample rate of 44,100 Hz and a 16 bit-depth, stereo channel.
I'm sure that someone is going to tell me (and I can make clips of these different audio recordings if you want to message me, so you can hear what I'm talking about in terms of the difference between the 'good' recordings without the iMic, and the bad recordings with the iMic) that I'm an idiot, and that the answer is elementary, and it probably even has something to do with the theory behind what is a 'LINE' level signal and what is a MIC level signal, and what should be attenuated, and yada yada... I didn't go to sound engineering school... I know computers, and I know how to create music with instruments, and I even know a tiny bit (evidently) about how to do some rough mixing with the Mackie and get the sound levels right in our premises. This is just beating the stuffing out of me right now, so be gracious.
I'm sure its very easy to someone, and I'll probably go 'oh, what a doughnut...' but I'd love to know WHAT it is that I'm doing wrong, WHY it is wrong, and what to do next.
Is it as simple as the iMic being duff? Should I be using an M-Audio Transit? I can handle having to replace a piece of kit if and only if that's definately what it is... I wouldn't want to go out and buy 'better kit' because of someone's theory that the Griffin iMic is crap and should be binned, only to find that it makes no difference at all.
I also have, available to hand, a Mackie Spike Recording interface, which I could try. The reason I haven't started out with the Spike on this project is simply portability and convenience.
Can anyone please help me with this?
I've tried to give as full an account as I can, sorry if I bored you, but I'm sure that someone out there knows either from experience or because they have impeccable Digital Audio knowledge EXACTLY what this problem is and why...
Please help.
Thanks,
S.