cheeserandyburg

Exactly my thoughts. Thanks again David.

That's what I'm wondering about. Is it safe to use third party ones? According to some google searches people were saying Roland told them "only use ours". But I hardly believe that. As a matter a fact I don't believe that at all.

I've had a R09HR for about 4-5 years now and just today the AC adapter (which has been sitting in the same position the whole time) stopped working. I can understand it breaking under wear and tear, but the thing is hardly ever moved, I just plug it in whenever I need to use it. Anyone have one of these PSU's go bad? $50 for a new one seems like a rip off, especially since its evident they are pure crap. Its a PSB-6U. Anyone ever use a third party power supply with these Roland products?

Thanks again Erik! If he (David) pops by this thread then he's welcome to share his experience. No biggie at the moment. Cheers

Thanks for the clarification. "FireWire connectors that support 400 Mbs operation." - Is what I have on the ULN2. Macbook Pro is the 17" and supports 800Mbs. I currently just use a 400 to 800 converter firewire cable (MH end) 400-800 (MBP end) I'm not very concerned about 400 vs 800 issue. The difference wouldn't be noticeable for me. I only record a max of 2 tracks at once at any given time. Besides the speed trade off (400 vs 800) - is there any wrong doing in going FW drive > Interface > Macbook ? Would be much more convenient, since I wouldn't have the Firewire HD in the middle of the chain. Plus, I would only need to turn on the drive when I'm working on music. If the drive is at the end of my chain I could just turn it on when working on projects in Logic and not daily use when I use the ULN2 (which is very frequent)

Even though I have over 270+GB of free disk space on my internal MBP drive, I'm thinking of moving all my projects onto an external drive for recording soon. Not having any issues recording to the internal drive for the past 3 years, but it would definitely loosen the load off the internal one for once. Maybe for the better! So with that being said... Whats the best way to do this? Will any 7200rpm drive do? USB? Firewire? Currently I back up all my stuff to an enclosed internal drive (7200RPM). So far so good. Should I get a Glyph firewire drive? ? with a separate power supply? Or one of those "bus powered" drives? I'm thinking a drive (within an enclosure with its own power supply) is much more reliable. The Macbook Pro has 1 x Firewire (currently being used by my interface) and 2 USB ports. Could I get away with recording to a USB drive? Or would it be advised that I connect a Firewire drive to the back of my Metric Halo and record to that? How do you guys do it? (for those using mobile recording rigs)

http://abletonlife.com/a-detailed-guide-to-dummy-clips-in-ableton-live

Any possibility you can record this and provide a sample?

That's it! Right after, "the". I can't wrap my head around the fact its analog. It doesn't sound analog in nature to me for some reason. I know they analyzed the file, used spectra foo, zoomed in, etc, but I still have some gut feeling its digital. The chain is; mic into either into channel 1 or channel 2 ULN2. Nothing else, nothing more. If I'm doing electric guitar, I'm going DI, either channel 1 or channel 2 and using the amp sims in Logic. An interesting thing about Logic and sound in general with this MBP-ULN2 setup is.... Occasional there is a "cut out". Very brief. For example if I'm working on a project (whether it be small or bigger in nature) the sound will cut out for a split second and come back. This never happens during recording, but I do run into it from time to time. Never tried recording using the digital source. It's always used with either input 1 or 2. Either a condenser, a shure Sm57, or DI electric guitar. I'm aware that you use the ULN-2 and never talked about issues, which is why this is so strange to me. I'm also the only person (in the internet community that I know of) that has to use the April, 1, 2010 driver version. The newer drivers were/are unbearable to work with for me (constant drop outs and issues) I think I may have to spend and waste some extra money on renting another interface or another ULN2 this year from the local music store and try to duplicate this issue. The problem is, it happens so randomly its hard to catch until listening to the mixes. Thanks for the advice.

HI David, During recording I AM using software monitoring. Not noticing any artifacts whatsoever. Yes. As soon as I'm done recording an acoustic track at times I'll notice something is off about it and then have to redo it. Other times I'll only notice it once I lay all the other instruments down. Sometimes I realize something is wrong during mixing. It jumps out like a glitch/artifact. I then have to then solo all the tracks in Logic and isolate the problem. More times then anything, its on vocal/acoustic. Another thing to mention is, this is only present when using the Interface. I've used my mic with other gear and never encountered it. So I know its not the mic. Here's an example from a older vocal track (2011) that had it occur: https://www.box.com/shared/0f4nguksj4 Happens 1.5 seconds in from the beginning. High freq, click/glitch. After contacting the guys at MH and letting them analyze that audio strip (in AIFF format), their words were "its not digital, definitely analog and happened at 13Khz."

I've been having this issue for some time now. I'll finish recording a bass track, guitar track, drums (midi) whatever else, and then I'll throw on vocals. I'll finish the tracking process and when I'm sitting down monitoring to what I have so far; whether it be through headphones or monitors, I'll notice high freq artifacts on the vocal track(s). Sometimes it'll happen on acoustic (guitar) tracks. I've had similar issues on plugging direct in (elec. guitar) in the past as well (Which were posted on here before. However, in those cases the freq artifact/sound was slightly different) Here's the puzzle. How come I'm hearing this POST recording and not DURING recording? I'd catch it if it was happening during, and I'm 100% sure it isn't happening during tracking. In addition, it happens completely randomly and its only noticable during monitoring post rec. I've so far tried looking into; 1) plosives, sibilance but that's not the issue here. 2) Buffer = not a problem 3) Duplicating the problem = can't What are the possibilities for this? Deep down I'm thinking two things, MH drivers (once again) or whatever data is getting recorded onto disk is somehow becoming corrupt along the way.

Thanks for the tips guys. Good food for thought. Technically speaking, I "could" track vocals even with the crop up of the "doubling" sound. But in order to get an authentic true vocal sound I'm better off sticking to direct monitoring from now on for vocals and micing in general. The only "real" use for software monitoring is when I'm using the amp sim, or a bunch of plug ins (ie. sculpting weird sounds and what not) and that's not too frequent. Plus with the ULN software I'm getting almost no latency. Big plus. Redlogic, thanks for that. I'm gonna try that out. I was waiting for someone to throw in "hardware" at some point in time and I was right! Edit Tried it like you suggested, works like a gem. I tried it both at 64 and at 1024. No difference as you stated. Even zoomed in on the audio wave to check the starting point. Usually there is a significant differences between those buffers, but with direct monitoring, nothing. This is good stuff. This really makes you think about using software monitoring in the first place, especially when everything is mic'd up . Thanks again guys.

I'm not sure if this'll make sense, but the ULN is always "off" in terms of "standalone" operation. For example. If I start up the computer and stick in a guitar cable DI, straight into either channel, crank up the gain, I don't hear anything. I see the input levels but If I want to hear that signal output (of me playing) I have to open some type of audio software (whether it be Quicktime, Logic, Garageband, etc) and activate input monitoring or record enable. Now, if I want to track using direct monitoring; using my unit in standalone mode, I then have to open up software that came with the ULN and open it, activating the ULN into standalone operation. Now that its activated I don't have to have software monitoring engaged or input monitoring turned on. It can simply work as a preamp at that point (with or without a computer) The problem with this ofcourse is the inability to use amp simulations (ie. Logic) without muting the specific channel within the software and then going back to logic and activating software monitoring. I understand how it works, I just don't get why it would double the signal (in certain circumstance) since I never run my unit in standalone. Funny enough, it comes and goes within the project and is only evident on specific projects. And it doesn't help whether I go down from 128 to 32 buffer. (usually i stay at 128) I'm thinking its something to do with plugins and CPU usage or something. Thats good to know. Now, what If I'd like to hear some reverb on my vocal track using direct monitoring when tracking??? (no software monitoring enabled, just my ULN) I've tried to figure this out, but I'm missing something. Also, buffer sizes wouldn't matter here as you say? I have the luxury of tracking at 64 or even 32 if I wanted too. But you say this doesn't make a difference when using direct monitoring, besides the obvious fact i'll be hearing the the signal of whatever I'm tracking over from Logic coming through my headphones. Thanks for the input!

Sure thing. I've removed all plug ins as a test too (in the project) and it didn't help. I'm wondering perhaps its a RAM issue, then again I think its just a bug, since it comes and goes. (and only happens in Logic) mixer

Hmmmmmm, that fixed it (for a short time), but interestingly enough....I didn't have anything else open, just Logic. (I'm running at 128 as well) In addition, something I noticed, If I uncheck it (Enabled checkbox) and do as you say. It fixes it. BUT, as soon as I play the project for a second/ or unclick "record enable" or "input monitoring" and then re-enable record/monitoring, its back there again. For some odd reason it gets activated by playing the project or unclicking and reclicking the monitor button/record enable. And funny enough its happening on a 13+ track project. I recall this happening to me in the past, but I had no idea what was going on, so I restarted from scratch and it may or may not of fixed it for that time being. I wonder, has Apple ever addressed this issue in a update? My guess is not. Kinda annoying to keep having to uncheck and recheck the Enabled box when it creeps out. Also, when using a buffer of 32, it was present, so its definitely one weirdo of a bug. Luckily it doesn't transfer into the final recorded file. Thanks for clearing that up.