2

Everything about your signal chain sounds correct except for the mixer to the pc. It sounds like you want to use your mixer as an interface, in which case you'd want to use the USB to connect to your pc, not the speaker output. Once connected, you'll need software on the pc to be able to record. You could go the freeware route and get Audacity, but there ...


2

Hi Mikkal, It's curious that your meter wasn't clipping and you were still picking up the crackling. Perhaps you picked up some static discharge? May be helpful to look into VLF phenomena: http://en.wikipedia.org/wiki/Radio_atmospheric There is software to remove various levels of static and hiss. Waves Restoration plugins are fantastic.


2

Hi Mikkel, Not familiar with your particular microphone system, but I use the SD702 with different mics. However I tend to use a different rig for recording thunderstorms and know the problems caused by reasonably distant strikes let alone powerful close strikes. I would suggest you have two problems - Firstly your gain levels are set too high. EG: Today I ...


2

Make sure you are showing Auto-Created Regions in the Regions bin (option-command-K). If these are being hidden, they will not clear and will be considered part of your session.


2

Solution: Send a MIDI SysEx "reset all" message. What worked for me: Download MIDI-OX for Windows or KMidimon for Linux. I use Windows so these steps will continue with MIDI-OX. Start MIDI-OX. Go to Options->MIDI Devices. Select your MIDI input ("E-MU Xmidi1X1 Tab" for me). I actually selected Microsoft GS Wavetable Synth for my MIDI output, but I don't ...


1

At First, slhck's answer had solved my problem which is the same as yours (thanks slhck!), however, this was still not ideal, because I had to go in and change the sync source every time I turned my Saffire 56 on. After talking with Focusrite Support, I found a more permanent solution, which I will share with you: You need to remove your Audio MIDI Setup ...


1

Your symptoms describe a bad mic cable. None of your symptoms suggest that there is anything wrong with the mixer or its power supply.


1

it's Always a good idea to ground your equipment, audio-related or not, in your case, grounding your mixer probably gets rid of the hum, but also makes it safer to use (if for example the body (which I'm guessing is a conducting material) is being put under a current, it won't shock you because it'll redirect the power to the ground instead).


1

I'm pretty sure this is something related to the way you use Pro Tools. Make sure you do not have additional auxes and other outputs to the master channels, which are not active during bouncing. Make sure you have your master fader at 0 db when bouncing to disk (you should really not use that as a volume control, but instead control volume post output).


1

I have found out the problem, I will share this with anyone that may run into this in the future. It was a simple problem yet I could not notice it at first. The table I had my turntable on was vibrating from the speakers, thus causing the stylus to shake all over the record.


1

I have experienced the same issue, including just yesterday preparing for a live performance, and thought the unit was broken. Apparently based on your post, it is a bug in the 1x1 itself. To resolve the problem, unplugging the 1x1 and re-inserting it usually rectifies the issue. Very annoying... This effectively resets the unit.


1

Had the same problem with E-Mu MIDI 1x1, windows 7 64 bit. Disconnectng and reconnecting the MIDI USB solved the mystery delay. Thanks.


1

This exact thing is happening to me. I tried updating the drivers, but that didn't help. The only consistent feature that seems to take the lag away is to unplug the USB device, wait at least 10 seconds, then plug it back in. Once plugged in again, it works like a charm. Having the device plugged in during boot-up slows it down for some reason. I'm ...


1

One of the more common causes of this kind of problem is contamination from dirt or debris at the point where the exchangeable capsules and the mic body connect. One should be sure that the entire area is scrupulously clean. This is an extraordinarily high impedance part of the circuit, and a noisy leakage path can be caused by contamination that can't ...


1

If you can replace it as simply as others have mentioned its worth a try (if the manufacturer allows it). Some other things to try that I have found helpful with strange static issue. If you are using an interface that has its own power source but you are running it on USB/Firewire Power (usually can be done with smaller interfaces) try using the dedicated ...


1

If ever you post technical problems to a forum always include software version, system spec, OS, driver versions at the least. I'll presume you're running Windows. When a program uses an Asio driver it connects directly to the audio interface, bypassing Windows. So Asio can only be used by one piece of software - It's either Pro Tools or Windows not both of ...


1

Best bet is probably to do the above, trash preferences etc (the usual) and failing that ask on the AVID Pro Tools support forums as they're a more technical forum and less about sound design where as this is the opposite. They'll be able to get you sorted for definite i'm sure :) http://duc.avid.com/forumdisplay.php?s=f8813aed26a07f99959ff66a38d6cab6&f=...


1

There's a work-around; it's kind of a pain, but so's the latency... First, make a safety copy of all of your tracks as alternate playlists, so you can go back if need be. Then Option+Command-Click (or Alt+Control-Click) on the channel's vol/peak/delay display so you know how many ms the delay is. Then nudge your track forward in time by that number of ...


1

Aside from Shaun's good advice, you may also have a corrupted fade or file (I've seen all sorts). If clearing Prefs etc. doesn't work try these: First, try deleting the Fade Files for the session... PT will rebuild them. Corrupted Fade Files can cause all sorts of weirdness. Second, try a "Save Session Copy In" with all audio files. If there's a weird ...


Only top voted, non community-wiki answers of a minimum length are eligible