Page 4 of 5

Posted: Sun Dec 09, 2007 2:09 am
by Phil Jeffers
Yeah, that makes sense...

Cheers, Phil J

Posted: Sun Dec 09, 2007 2:34 am
by Phil Jeffers
Mr_Clifford wrote:
tommymandel wrote: If you save the DP session as an OMF, and run Classic, you can use OMF Tool to translate and OMF file into a ProTools 4x session that later versions of PT will open.
Wow, I didn't know that one. Sure enough, I just installed Classic, downloaded OMF tool and I was able to convert a DP OMF file into a PT 4 session. For some reason the Pro Tools session crashed when I tried to open it, but I was able to get it working by creating a new PT7 session and importing all the tracks.

Thanks TommyMandel. Saves me buying DigiTranslator or DV Toolkit for the meantime.
OMF Tool will work right up to Pro Tools 6 I think (that is, PT's 4 & 5 - NOT 6) and OS 9. I'm amazed you can still download this app... Avid Free is no more... not sure about Pro Tools free...

Posted: Sun Dec 09, 2007 2:37 am
by Phil Jeffers
pcm wrote:Digitranslator is still available separately. You can buy it used on eBay for under $300. I have two copies, as I have two systems 100 miles apart. Everyone likes to make a big deal out of how Digi charges for what other companies give away for free. But it's not that simple. The import and export options are extensive, and it works every time. The OMF side of DP I find to be very iffy, as half the time I try to import stuff it simply doesn't come through. Or DP crashes. When it does work, DP reverts to 16-bit, and then I have to manually change it back to 24-bit. It feels like hobby software to me. And this is with files that always import into Final Cut Pro without issues. I'm a full-time professional, and I don't mind paying for tools that allow me to get on with my job. I've got work to get done!
I agree 100%...

MOTU: Please fix OMF import/export!

Posted: Sun Dec 09, 2007 2:41 am
by Phil Jeffers
tommymandel wrote:ah, i stand corrected, thanks. I didn't realize the 2408 did 24 bit - i guess when i had it, i was still doing things 16 bit at that time. well there goes my 24 bit multi-interface studio. . . for now anyway.
what i'd like would be a 24i/o. the ins and outs would mimic my departed ampex 2" machine...
Same - A 24i/o and a BRAND NEW 2408 Mk3...

Oh, and a V3HD...

Santa!?

:roll:

Posted: Sun Dec 09, 2007 2:52 pm
by Mr_Clifford
stiefelmusik wrote: Does it work with 24-bit sessions? I seem to remember trying this once and I could only translate 16-bit sessions.
To be honest I'm not totally sure. DP exports the OMF and associated audio files in 24bit. OMF tool says that the OMF is in 16 bit, but then the Pro Tools session references the 24bit files (possibly why the Pro Tools session was crashing when I tried to load it). By loading the tracks into a 24bit session, it was able to copy the files over - so unless it converts to 16bit then back to 24bit, I think it's maintaining the bit depth.
phil jeffers wrote:OMF Tool will work right up to Pro Tools 6 I think (that is, PT's 4 & 5 - NOT 6) and OS 9. I'm amazed you can still download this app... Avid Free is no more... not sure about Pro Tools free...
I haven't been able to find a version that saves to PT5, but that would be really handy if it exists. PT4 only supports mono audio tracks, so I have to create new stereo tracks and copy over once I'm in PT7.

Posted: Sun Dec 09, 2007 4:49 pm
by Don T
Hello,
If you are using 24 bit files do not embed the audio, reference the files only (in export OMF dialog - enforce digitranslator 2.0 compatability - export 24 bit files directly). That way you avoid all of the file mismatch errors. If you are using OMF tool/Digitranslator 1.0, you are stuck with 16 bit files. I had to experiment with the settings to get a good export / import between different DAW's like PT and Logic.
The college sprang for Digitranslator 2.x for use at the school only so I still have to go in, dang. I sold them on the import capabilities with the multimedia department and being able to interface with the NW Film school.

Now all I have to do is make it come true.

Re: CoreAudio: Digidesign finally gets it right!

Posted: Sat Dec 15, 2007 10:57 am
by leeahegg
[quote="stiefelmusik"]Well, it may have taken them a long time, but I believe Digidesign finally got it right with the CoreAudio driver that ships with the new PTLE 7.4! Finally I can use DP again as a solid frontend to my Digi002r without the flakiness that has plagued so many of their earlier drivers! And I can now proudly say I am happy using a Digi002r with DP instead of shamefully lurking in the darkness. Perhaps this latest driver can finally put to rest the endless bashing of PT LE gear for not playing nicely with other apps. I have tested this thing with DP, Reason, Live, and a hoard of other apps and so far not one single crash, glitch, belch, fart, you name it. Within DP I threw him a session full of heavy VIs from Arturia with the buffers set at 64 samples (!) and the playback was flawless.

I am very happy, indeed. Way to go Digi![/quote]

Mr. Stiefelmusik, it is good to heard that your system are able use DP with the Digi hardware successfully.

Actually, I'm planning to upgrade my audio interface from MBox (original) to 003 Factory before the due date of the exchange program. From my experience, I 'm not really happy to use the DP with my MBox. Because the Hardware buffer setting in Dp is extremely high (512 or 1024). After I saw your post, I have upgrade my "Coreaudio driver" form 7.3 to 7.4. ( I downloaded form digi web page) But It's seem doesn't work for me. The buffer size is still in 512 or 1024.

Can you or anyone can give me some suggestion on why it's doesn't work for me? because of the Mbox limitation?

I'm using DP 5.13, OSX 10.4.11, PT 7.3 cs1 and updated Digi Coreaudio Manager 7.4.

Re: CoreAudio: Digidesign finally gets it right!

Posted: Sat Dec 15, 2007 11:36 pm
by stiefelmusik
leeahegg wrote:
Can you or anyone can give me some suggestion on why it's doesn't work for me? because of the Mbox limitation?
Yes, that's correct. You cannot use buffer settings lower than 512 while running the original Mbox through Digi CoreAudio. Most unfortunate, I know... and it makes the Mbox useless for tracking VIs or for monitoring any real time effects during recording. This is due to a combination of USB 1.1 audio limitations and Digidesign's lazy CoreAudio drivers. Despite USB 1.1's bad rep regarding audio, low latency IS theoretically possible (I have an old emagic 2 6 USB audio interface which I mostly use now as a "glorified Sound Manager output" on my G4 tower, and the drivers for that device are highly efficient).

I also have an original Mbox, and when I upgraded to a Digi 002r I decided to keep my Mbox because, well, I like it, despite its limitations. First, those Focusrite preamps are sweet -- plus I like the portability. Since the discount you will receive by exchanging up to the 003 is minimal, you might want to consider hanging on to that Mbox as well. Once its limitations are understood -- and you have a better interface in your arsenal to turn to when you need it -- you might come to appreciate it more. It's a great little box for mixing!

Posted: Mon Dec 17, 2007 10:49 am
by leeahegg
Thank you for reply! Stiefelmusik!

Actually, I have try to use my MBox with Logic Pro 8. The Hardware buffer size can down to 64.....! It's lower than Protools (Lowest value is 256).
So, I start to think, DIgidesign hardware may not really work well with DP.

Have you try to upgrade your DP version to 5.13? And is it still work well with your digi 002r?

Anyway, two days left? (The due date of exchange program)

Are you saying that it's worth to save my MBox for the future?
Because of.........

THanks!

Posted: Mon Dec 17, 2007 11:49 am
by stiefelmusik
I'm still on DP 5.11 which, apart from the occasional unexplained volume surge when using virtual instruments, and a few other minor issues, is working very well for me with the Digi 002r and Digi CoreAudio 7.4. To be honest, I'm kinda scared to mess with my system right now because it's hasn't been this solid for me in a very long time. I probably won't update DP until I move to Leopard, or until a major revision comes out.

About the buffer sizes of the Mbox, the value being reported by Logic is inaccurate! Logic might let you select a buffer size of 64, but the Digi CoreAudio driver will stay fixed at 512 (or 1024) (switch over to the Digi CoreAudio Manager application to confirm). Sorry, mate!

Yes, I was saying that you might want to hang on to the Mbox, since the discount you will receive on the Digi 003 won't be that much, and I still find the original Mbox a useful addition to my studio -- but then, after realizing you can't use buffers lower than 512 with CoreAudio apps you might be ready to ditch that thing!

I don't know how things are where you live, but when I spoke to my Digidesign supplier here in Germany he implied there was some flexibility regarding the dates of the current upgrade offer -- in other words, the 20th of December was not written in stone... so you probably have more than just two days left. I'd ask about it first though!

Good luck with your decision.

Posted: Mon Dec 17, 2007 4:17 pm
by pcm
leeahegg wrote:Thank you for reply! Stiefelmusik!

Actually, I have try to use my MBox with Logic Pro 8. The Hardware buffer size can down to 64.....! It's lower than Protools (Lowest value is 256).
So, I start to think, DIgidesign hardware may not really work well with DP.

THanks!
What you are saying suggests an issues with how motu uses Coreaudio. We can all assume that Logic and Coreaudio are on the same page. So it stands to reason that if the mbox works at low buffers in Logic, but not in DP, that the issue is with DP's relationship to Coreaudio, and not Digi's hardware relationship to DP.

Posted: Mon Dec 17, 2007 10:27 pm
by stiefelmusik
pcm wrote:
leeahegg wrote:Thank you for reply! Stiefelmusik!

Actually, I have try to use my MBox with Logic Pro 8. The Hardware buffer size can down to 64.....! It's lower than Protools (Lowest value is 256).
So, I start to think, DIgidesign hardware may not really work well with DP.

THanks!
What you are saying suggests an issues with how motu uses Coreaudio. We can all assume that Logic and Coreaudio are on the same page. So it stands to reason that if the mbox works at low buffers in Logic, but not in DP, that the issue is with DP's relationship to Coreaudio, and not Digi's hardware relationship to DP.
I don't have Logic, so I can't confirm this, but the buffer size being reported in Logic is most certainly inaccurate! The original Mbox cannot be used with a buffer setting lower than 512 with CoreAudio (at least, not without using a third party driver like the one over at http://www.usb-audio.com/).

Posted: Wed Dec 19, 2007 12:23 pm
by leeahegg
Mr. stiefelmusik! Thank you for your reply and your useful information!

Finally, today, I joined the exchange program.
Actually, I 'm not really that wealthy, and I can save for the future plug-ins.

Anyway, when I got the 003, I'll share how DP is working in 003 to you all.

Anyway, Mr. PCM, I 'm not saying how good is logic...... and I 'm on your side. DP is my DAW is first priority, and I start every project in DP in the rarely beginning. SO, I really concern on how can make DP work better with DIGI or using the Digi Coreaudio manger as well. I come in peace! OK!

Posted: Wed Dec 19, 2007 6:05 pm
by lwilliam
I will have to give this a try. I haven't run DP since upgrading to PTLE 7.4. DP has not been playing nicely with my 002R for years.

really?

Posted: Wed Jan 02, 2008 8:37 pm
by KarlSutton
So I can see audio going to the 002R & it will record it & play it back, but for some reason I'm not hearing it as I record it. Any thoughts? I am daisy chaining it off of my 828mkII firwire. (attempting to get 16 inputs happening)