|
Post by c0rtland on Feb 1, 2018 13:42:53 GMT -6
Been thinking about getting one of these as my master recorder. I have heard time and time again you shouldn't record into the same computer you are bouncing from. I can say it has caused me some issues so I'm willing to bite the bullet here. Besides an atr-102 I wonder if this is still the best option available.
|
|
|
Post by EmRR on Feb 1, 2018 13:48:22 GMT -6
I have heard time and time again you shouldn't record into the same computer you are bouncing from. I can say it has caused me some issues so I'm willing to bite the bullet here. Not sure what the problem is, not one I've had or been warned about.
|
|
|
Post by notneeson on Feb 1, 2018 13:51:54 GMT -6
I have heard time and time again you shouldn't record into the same computer you are bouncing from. I can say it has caused me some issues so I'm willing to bite the bullet here. Not sure what the problem is, not one I've had or been warned about. It’s standard operating procedure at most joints I’ve worked at, when not mixing to actual tape.
|
|
|
Post by EmRR on Feb 1, 2018 13:54:33 GMT -6
Not sure what the problem is, not one I've had or been warned about. It’s standard operating procedure at most joints I’ve worked at, when not mixing to actual tape. Not clear, what's standard operating procedure?
|
|
|
Post by c0rtland on Feb 1, 2018 13:55:23 GMT -6
Maybe it's just my conversion. 2 Mk1 symphony thunderbridge Mac Pro. I fight intermitant pops and clicks more often than I should. I h e tried running my audio files for projects/ and or the entire project folder on an external tb raid array and I get disk too slow errors constantly too. So I just end up using my system drive.
Both of these practices have been pointed at for my pop and click issue. By apogee and other engineers when troubleshooting.
|
|
|
Post by notneeson on Feb 1, 2018 13:55:58 GMT -6
It’s standard operating procedure at most joints I’ve worked at, when not mixing to actual tape. Not clear, what's standard operating procedure? Printing back to the protools rig. Sometimes through a fancy convertor.
|
|
|
Post by notneeson on Feb 1, 2018 13:56:37 GMT -6
Maybe it's just my conversion. 2 Mk1 symphony thunderbridge Mac Pro. I fight intermitant pops and clicks more often than I should. Buffer size issue?
|
|
|
Post by c0rtland on Feb 1, 2018 13:58:56 GMT -6
I print back through a burl bomber sometimes. Same thing. Buffer size doesn't cure what haunts me.
|
|
|
Post by notneeson on Feb 1, 2018 14:01:16 GMT -6
I print back through a burl bomber sometimes. Same thing. Buffer size doesn't cure what haunts me. Try the opposite of however you’re clocking the rig. E.g. make the Burl the master or vice verse depending on how you are doing it now.
|
|
|
Post by johneppstein on Feb 1, 2018 14:08:52 GMT -6
Maybe it's just my conversion. 2 Mk1 symphony thunderbridge Mac Pro. I fight intermitant pops and clicks more often than I should. I h e tried running my audio files for projects/ and or the entire project folder on an external tb raid array and I get disk too slow errors constantly too. So I just end up using my system drive. Both of these practices have been pointed at for my pop and click issue. By apogee and other engineers when troubleshooting. What kind of disks are in your array? Also, if I recall correctly (it's been some time since I messed around with RAID much) some types of RAID array are actually slower than the individual disks depending on the type of redundancy involved. Some Raid optimized for speed but some optimized for data security? I imagine somebody around here is more up to date than me.
|
|
|
Post by notneeson on Feb 1, 2018 14:18:57 GMT -6
Maybe it's just my conversion. 2 Mk1 symphony thunderbridge Mac Pro. I fight intermitant pops and clicks more often than I should. I h e tried running my audio files for projects/ and or the entire project folder on an external tb raid array and I get disk too slow errors constantly too. So I just end up using my system drive. Both of these practices have been pointed at for my pop and click issue. By apogee and other engineers when troubleshooting. What kind of disks are in your array? Also, if I recall correctly (it's been some time since I messed around with RAID much) some types of RAID array are actually slower than the individual disks depending on the type of redundancy involved. Some Raid optimized for speed but some optimized for data security? I imagine somebody around here is more up to date than me. I can mix from and print back to an external FW400 drive with no issues. Grab an $80 external and try it, system drive is less than ideal.
|
|
|
Post by c0rtland on Feb 1, 2018 14:29:46 GMT -6
Maybe it's just my conversion. 2 Mk1 symphony thunderbridge Mac Pro. I fight intermitant pops and clicks more often than I should. I h e tried running my audio files for projects/ and or the entire project folder on an external tb raid array and I get disk too slow errors constantly too. So I just end up using my system drive. Both of these practices have been pointed at for my pop and click issue. By apogee and other engineers when troubleshooting. What kind of disks are in your array? Also, if I recall correctly (it's been some time since I messed around with RAID much) some types of RAID array are actually slower than the individual disks depending on the type of redundancy involved. Some Raid optimized for speed but some optimized for data security? I imagine somebody around here is more up to date than me. 2 7200 rpm 2tb TB2 configured in raid0 (for speed)
|
|
|
Post by c0rtland on Feb 1, 2018 14:32:29 GMT -6
Thanks everyone. I will be attempting some trials this evening.
Also I'm in logic btw. My symphony's also give me loop sync errors sometimes and reset. Total fing disaster. I'm not gonna stop till I find the culprit.
|
|
|
Post by EmRR on Feb 1, 2018 15:01:40 GMT -6
I can't say I ever have this problem, unless it's an overall CPU strain that crashes everything. Good luck.
|
|
|
Post by kcatthedog on Feb 1, 2018 15:02:17 GMT -6
Something seems funny previously with my Apollo’s and nowcwith symphony mkii I print to my system drive without problem 2012 mbp i7, 16 gig, 2 internal ssds, also use logic.
|
|
|
Post by johneppstein on Feb 1, 2018 15:16:20 GMT -6
What kind of disks are in your array? Also, if I recall correctly (it's been some time since I messed around with RAID much) some types of RAID array are actually slower than the individual disks depending on the type of redundancy involved. Some Raid optimized for speed but some optimized for data security? I imagine somebody around here is more up to date than me. 2 7200 rpm 2tb TB2 configured in raid0 (for speed) Maybe your RAID card is glitchy? RAID 0 (Which isn't really RAID - no redundant backup) should not have speed problems. Or (and you should never discount the possibility of this, obvious as it might seem) a cabling or connector problem?
|
|
|
Post by notneeson on Feb 1, 2018 16:04:47 GMT -6
Worth repeating: pops and clicks are often clocking issues in my experience.
|
|
|
Post by Quint on Feb 1, 2018 19:14:09 GMT -6
This thread may lead to a solution for the issues you have going on. That being said, I generally like the idea of having a separate box for mixdown. One reason is, that it cuts out any mystery which may/could exist on the signal going back into your daw. You can seperately dial in your daw and standalone recorder each to their optimal or desired settings without having to worry about a "one size fits all" approach. I like the idea of separation of powers, so to speak.
As long as a standalone box like the Tascam is setup the way you want it, you know that the analog signal going into it is going to come out right. This also allows for easy sample rate and bit conversion to whatever you want without being locked into the sample rate and bit depth you have your daw set at.
I don't have a DA-3000 yet but I was planning on getting one in the next year or so. I'm also wanting to experiment with mixdown to dsd, which I hear the DA-3000 does a great job of for not that much money.
I guess I'm just saying that, even if you get your problems sorted out, the Tascam still might be a worthy purchase.
|
|
|
Post by jeremygillespie on Feb 1, 2018 21:30:11 GMT -6
I’ve always printed back into my session through a Lavry back in with AES. Never had a problem.
|
|
|
Post by c0rtland on Feb 1, 2018 22:18:20 GMT -6
So far so good on the pop click front. I switched my master clock to the burl from my symphony's. I still get the drop outs. Logic continues to play but my symphony's go blank on the meters, wait 4 secs then come back. Hmmm
|
|
|
Post by johneppstein on Feb 1, 2018 22:49:19 GMT -6
Worth repeating: pops and clicks are often clocking issues in my experience. Which is a good reason to be aware of your connections.
|
|
|
Post by johneppstein on Feb 1, 2018 22:55:08 GMT -6
This thread may lead to a solution for the issues you have going on. That being said, I generally like the idea of having a separate box for mixdown. One reason is, that it cuts out any mystery which may/could exist on the signal going back into your daw. You can seperately dial in your daw and standalone recorder each to their optimal or desired settings without having to worry about a "one size fits all" approach. I like the idea of separation of powers, so to speak. As long as a standalone box like the Tascam is setup the way you want it, you know that the analog signal going into it is going to come out right. This also allows for easy sample rate and bit conversion to whatever you want without being locked into the sample rate and bit depth you have your daw set at. I don't have a DA-3000 yet but I was planning on getting one in the next year or so. I'm also wanting to experiment with mixdown to dsd, which I hear the DA-3000 does a great job of for not that much money. I guess I'm just saying that, even if you get your problems sorted out, the Tascam still might be a worthy purchase. I've been interested in the Tascam box for some time now. Have not had a chance to use it but have heard some very complimentary things about it from experienced people who were all set to dismiss it before they tried it. I'm also very interested in DSD as an archival format.
|
|
ericn
Temp
Balance Engineer
Posts: 14,956
Member is Online
|
Post by ericn on Feb 1, 2018 23:04:52 GMT -6
This thread may lead to a solution for the issues you have going on. That being said, I generally like the idea of having a separate box for mixdown. One reason is, that it cuts out any mystery which may/could exist on the signal going back into your daw. You can seperately dial in your daw and standalone recorder each to their optimal or desired settings without having to worry about a "one size fits all" approach. I like the idea of separation of powers, so to speak. As long as a standalone box like the Tascam is setup the way you want it, you know that the analog signal going into it is going to come out right. This also allows for easy sample rate and bit conversion to whatever you want without being locked into the sample rate and bit depth you have your daw set at. I don't have a DA-3000 yet but I was planning on getting one in the next year or so. I'm also wanting to experiment with mixdown to dsd, which I hear the DA-3000 does a great job of for not that much money. I guess I'm just saying that, even if you get your problems sorted out, the Tascam still might be a worthy purchase. I've been interested in the Tascam box for some time now. Have not had a chance to use it but have heard some very complimentary things about it from experienced people who were all set to dismiss it before they tried it. I'm also very interested in DSD as an archival format. First Tascam product I can think of where Everybody's praise doesn't end with a "but...."! And that's saying something!
|
|
|
Post by mhbunch on Feb 1, 2018 23:43:22 GMT -6
Been thinking about getting one of these as my master recorder. I have heard time and time again you shouldn't record into the same computer you are bouncing from. I can say it has caused me some issues so I'm willing to bite the bullet here. Besides an atr-102 I wonder if this is still the best option available. One thing I’ve found with older gen Apogee (mk1 symphony etc) is that if you have iTunes or Spotify open while a session is up that is at 48, 88, or 96 the clock gets confused and there will be pops and glitches. Something to keep in mind. Seems to be fixed in current gen.
|
|
|
Post by kcatthedog on Feb 2, 2018 6:38:24 GMT -6
|
|