Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Rob Gardner]

You hit the nail on the head. A good system is the first requirement, but it will only be as good as the application sitting on top of it. I'll be keeping my old 1640 for use as a recording interface. Combined with Cubase 5 the latency is down to 2-3ms. Better than needed for almost anything I may do and certainly good enough to record and monitor without problems. The APB doesn't have firewire, but I won't miss it at all as this is not the boards primary function. Should I need a firewire interface I'll go to MOTU for the solution. I have owned there interfaces in the past and performance is similar if not as good. One less thing to go wrong with the board.

+1 on the 1640, I have the 1641 as my recording interface, scored it in brand new condition off of CL for 2 bills, can't say enough good things about it!

[Tim McCulloch]

I've been drooling over the manual for the new Midas Venice Firewire console for a while now, and have seen at least one positive review:

http://www.etnow.com/news/2011/4/first-tour-for-midas-digilogue-venicef-with-eliza-doolittle

I'm currently driving the 'old' Midas Venice 320 in my club and am already putting a bug in my boss's ear to upgrade at the end of the year (I know, no shame  ). Anyone here have any hands on with this desk?

It's a Behringer Venice with firewire, what's to know?

[Marsellus Fariss]

It's a Behringer Venice with firewire, what's to know?

 

You hit the nail on the head. A good system is the first requirement, but it will only be as good as the application sitting on top of it. I'll be keeping my old 1640 for use as a recording interface. Combined with Cubase 5 the latency is down to 2-3ms. Better than needed for almost anything I may do and certainly good enough to record and monitor without problems. The APB doesn't have firewire, but I won't miss it at all as this is not the boards primary function. Should I need a firewire interface I'll go to MOTU for the solution. I have owned there interfaces in the past and performance is similar if not as good. One less thing to go wrong with the board.

I promise if you measure your total round trip latency from input to output with something like CEntrance test utility you'll have at least 10ms latency. Probably a few ms more. Try it and you'll see why I'm unhappy with how the software companies leave you to figure out how to use the software they sold you for $1500.

Edit: I should say you should measure the round trip latency on the buffer settings you determine is the lowest you can run at and be stable with no pops and clicks. I can only achieve 14ms round trip and that's too long for most applications.

[Bob Leonard]

It's a Behringer Venice with firewire, what's to know?

 

You hit the nail on the head. A good system is the first requirement, but it will only be as good as the application sitting on top of it. I'll be keeping my old 1640 for use as a recording interface. Combined with Cubase 5 the latency is down to 2-3ms. Better than needed for almost anything I may do and certainly good enough to record and monitor without problems. The APB doesn't have firewire, but I won't miss it at all as this is not the boards primary function. Should I need a firewire interface I'll go to MOTU for the solution. I have owned there interfaces in the past and performance is similar if not as good. One less thing to go wrong with the board.

I promise if you measure your total round trip latency from input to output with something like CEntrance test utility you'll have at least 10ms latency. Probably a few ms more. Try it and you'll see why I'm unhappy with how the software companies leave you to figure out how to use the software they sold you for $1500.

Edit: I should say you should measure the round trip latency on the buffer settings you determine is the lowest you can run at and be stable with no pops and clicks. I can only achieve 14ms round trip and that's too long for most applications.

You shouldn't make promises you can't keep. I've done all the measurments from end to end many times while in search of the optimal configuration. In the end and after some hard work with the configuration and components, I've never clocked more than 6ms on a bad day. You might help your cause if you're able to use a 1394b adapter with your software, which you didn't name. I have to agree though, 14ms is not optimal.
 
http://www.lacie.com/products/product.htm?id=10334
 

[luis Markson]

I promise if you measure your total round trip latency from input to output with something like CEntrance test utility
[/quote]

I can't seem to find this software via the google...


oops... Stop looking..

Does anyone know of a latency test utility for mac?

[Marsellus Fariss]

[quote author=Bob Leonard
 
You shouldn't make promises you can't keep. I've done all the measurments from end to end many times while in search of the optimal configuration. In the end and after some hard work with the configuration and components, I've never clocked more than 6ms on a bad day. You might help your cause if you're able to use a 1394b adapter with your software, which you didn't name. I have to agree though, 14ms is not optimal.
 
http://www.lacie.com/products/product.htm?id=10334
[/quote]

Which interface/OS and PC are you using to get those numbers Bob? I've never gotten numbers that low with any interface!

[Bob Leonard]

Which interface/OS and PC are you using to get those numbers Bob? I've never gotten numbers that low with any interface!

Currently the OS is XP, the application is Cubase 5, the system I built myself, and the interface is an Adaptec 400 series. The drivers are the ASIO drivers from Mackie. The key to success here is the application. Cubase has tremedous support for virtualy any ASIO driver and managing the buffer size is the key to success. DO NOT use directX or programs that support directX only. If you do you're wasting your time. And of course, put as much memory into the system as is possible.

[Marsellus Fariss]

Currently the OS is XP, the application is Cubase 5, the system I built myself, and the interface is an Adaptec 400 series. The drivers are the ASIO drivers from Mackie. The key to success here is the application. Cubase has tremedous support for virtualy any ASIO driver and managing the buffer size is the key to success. DO NOT use directX or programs that support directX only. If you do you're wasting your time. And of course, put as much memory into the system as is possible.

So your rig is the Mackie 1640, a stout PC running XP, Adaptec 400 firewire card and Cubase as a host?

This is the best info I've found on doing this. I've posted several times in several forums about building a cheap but robust platform for this application and nobody's offered any advice. Thanks for that! If you say you can get the 1640's round trip down that low with a good host app I'll start looking for a Mackie interface! I wonder if the rest of their interfaces have as good of drivers?

[Bob Leonard]

Marsellus,
I was able to acheive pretty much the same performance using MOTU 24 channel interfaces as well. Again, the performance is derived from the applications capabilities in combination with the ASIO driver.

[ProSoundWeb Community]