not able to record from busses makes DP6 useless !!

[nk_e]

But Shooshie, what would you think if your track levelmeter is working and you can hear the source, too - but your record is only silence AND other users have the same prob AND in 5.13 the same project records without a problem ?


It´s not that I want to make DP6 bad - no, it´s much more elgenat than 5 and has some very usefull new features. Also the DAE is working better than before - very nice. But that bus thing...very strange

Okay. Embarassing confession time.

I had a similar problem (not Protools environment though). Could hear it. Could see it. But couldn't record it. For the world.

It drove me insane.

Turns out it was something really really simple. A boneheaded oversight on my part.

I clicked a button, flicked a switch or something....and everything worked. It was embarassing.

I'm racking my brain to remember what I did. (That's how simple it was...so simple that after doing it I thought "well of course".)

But it was the situation you describe exactly (except for the protools part).

If I remember, I'll post.

Embarrassed but hope to be helpful.
GN

[tripit@earthlink.net]

Well, both Spirit and I have confirmed this bug as well. You can not record via a bus to another track. You can see and hear the audio as you are recording, but after the pass, the audio file is blank.

And yes MOTU really screwed up with this one. You would think that something so basic wouldn't have slipped through but it did. I can only assume that it most likely due to a serious lack of DP/DAE beta testers, if they even have any at all, which I'm inclined to think is the case at this point.

[tripit@earthlink.net]

You know, just because you found a bug doesn't make DP useless. That doesn't even make any sense.

It´s a matter of what kind of bug it is. If you´re not able to bring your mix to disk (either submix, nor bouncing), what do you call it then ?

User error?

It's not likely that MOTU left a gaping hole that big.

Shoosh

Well guess what, they did.

[nk_e]

It´s a matter of what kind of bug it is. If you´re not able to bring your mix to disk (either submix, nor bouncing), what do you call it then ?

User error?

It's not likely that MOTU left a gaping hole that big.

Shoosh

Well guess what, they did.

Well I'm pretty sure they didn't....

[tripit@earthlink.net]

User error?

It's not likely that MOTU left a gaping hole that big.

Shoosh

Well guess what, they did.

Well I'm pretty sure they didn't....

Then you would be wrong. Maybe you fire up your DAE and check if for us?.......

[spirit]

Yes, it's easy to blame MOTU prematurely. Maybe there is some new configuration required in DP 6- But there is not one DAE user saying recording from busses is working for them in DP6, and three users that it is not working. Not when busses are assigned as outputs, not at 44.1 or 96hz, not when sent from aux sends, not after trashing DP preferences.

It doesn't seem like it's MOTU bashing here- it's seems like the DAE user sentinment is that DP6.0 for DAE is very promising but has an important fundamental flaw. Useless would be correct unless, you never need an exportable mix of a project, or are ok with the inconvenience of mixing to an external machine or wiring an output back to an input in your digidesign interface. Actually it could force one to warm up mixes with an analogue limiter on every rough mix one makes- So maybe not useless- but severly impaired?

Details
Though recording through busses creates audio files with no audio (all zero), recording from VI outputs (i.e. motu ethno out 3/4 etc.) is working- if that helps anyone.

Ethno doesn't have the visual GUI weirdness's- but at least Ethno 1.0 does weird things like go dead until you click another window and back, and volume controls going up and down by themselves.
Were these known problems fixed in a later version Ethno- or is this a different manifestation of the plug in GUI bugs?

Sessions from previous versions sometimes crashing- but it is possible this is a digidesign plug-in compatilibity issue rather than a MOTU issue.

One of the joys of DP/DAE is that you have TWO applications to trouble shoot through for bugs sometimes.

[nk_e]

Well guess what, they did.

Well I'm pretty sure they didn't....

Then you would be wrong. Maybe you fire up your DAE and check if for us?.......

Point taken. I'm not a DAE user so will gently bow out...

[jayjo19]

Hi everyone,

We also have a problem with bussing at the studio, but different.
When we "fix" a vocal track and buss it out (via aux) to a new track (we dont merge because of fades and pitch correction causing clicks and pops), the resulted audio file is not accurate at all, meaning its either ahead or late compared to original audio, but not in a consistent way.

Some precisions : yes we bypassed all automation and plug ins before bussing to a new track.

If anyone has the same problem, or know what we re missing, or just want to complain about the bussing in DP6 please show up

[tripit@earthlink.net]

Hi everyone,

We also have a problem with bussing at the studio, but different.
When we "fix" a vocal track and buss it out (via aux) to a new track (we dont merge because of fades and pitch correction causing clicks and pops), the resulted audio file is not accurate at all, meaning its either ahead or late compared to original audio, but not in a consistent way.

Some precisions : yes we bypassed all automation and plug ins before bussing to a new track.

If anyone has the same problem, or know what we re missing, or just want to complain about the bussing in DP6 please show up

Are you sending out via an aux bus send (pre-fader) or are you routing the track (post fader) via bus to a new track?

[pcm]

Well guess what, they did.

Well I'm pretty sure they didn't....

Then you would be wrong. Maybe you fire up your DAE and check if for us?.......

I think it is about time that we get an official response from motu concerning this. That would be the professional thing to do.

Anyone here who runs in DAE mode knows full well that a thread like this on the DUC would result in someone from Digi piping in right quick.

I'm gonna sign off before I say what I really think [/url]

[tonwurm]

I use the freeze function only frequently, so I didn´t test it yet. But it is (at least with my system) like I supposed. Since freezing uses busses to work it has the same result - blank freeze files

[estudios.sdb]

Do you have input monitoring option on?

[tripit@earthlink.net]

Well I'm pretty sure they didn't....

Then you would be wrong. Maybe you fire up your DAE and check if for us?.......

I think it is about time that we get an official response from motu concerning this. That would be the professional thing to do.

Anyone here who runs in DAE mode knows full well that a thread like this on the DUC would result in someone from Digi piping in right quick.

I'm gonna sign off before I say what I really think [/url]

Yeah, I agree. I think I'm going to call MOTU today.

[Shooshie]

Any answers yet? I don't use DAE, but I was under the impression that they "greatly enhanced" DP's performance under Digi audio, so it would seem that there is some conflict taking place on the user level. That doesn't necessarily mean you're making a mistake, but it could be that there is a driver issue, or a plugin issue, or... who knows? It just seems very unlikely that MOTU would have let this thing out the door with that big a hole in it.

But this is your discussion; I'm not a DAE user, so I shouldn't even be commenting here. I'm only saying that I'm incredulous that such a mistake could be happening. Then again, I've seen some pretty big ones in the MAS side over the past few years. Giant ones. So yeah... I guess it's very possible. I wish for you all a good fix come DP 6.01.

Shooshie

[tripit@earthlink.net]

Any answers yet? I don't use DAE, but I was under the impression that they "greatly enhanced" DP's performance under Digi audio, so it would seem that there is some conflict taking place on the user level. That doesn't necessarily mean you're making a mistake, but it could be that there is a driver issue, or a plugin issue, or... who knows? It just seems very unlikely that MOTU would have let this thing out the door with that big a hole in it.

But this is your discussion; I'm not a DAE user, so I shouldn't even be commenting here. I'm only saying that I'm incredulous that such a mistake could be happening. Then again, I've seen some pretty big ones in the MAS side over the past few years. Giant ones. So yeah... I guess it's very possible. I wish for you all a good fix come DP 6.01.

Shooshie

Thanks Shooshie. Yeah, it's hard to believe, but it's there, plain as day.
DAE is kinda the red headed step child of MOTU/DP.