[ddots-l] Re: ProjectMix

  • From: "Tim Burgess" <tim@xxxxxxxxxxxxx>
  • To: <ddots-l@xxxxxxxxxxxxx>
  • Date: Wed, 19 Apr 2006 09:23:10 +0100

Hi,

Setting up the EQ gain was one of those aux button page functions.  I had no
problems with the MIDI on the unit I tried, so suspect that Gudrun may have
a fault on hers.  I didn't try the scrubbing because I'm using Sonar and I
know it's rubbish anyway. 

The nearest I've found to a credible alternative for my needs is a Tascam
US2400 and the new Saffire 28 IO, but this works out at about half as much
again price-wise.  I think the Project Mix is a great bit of kit that just
misses the mark by a fraction..

Cheers.

Tim
-----Original Message-----
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Gordon Kent
Sent: 19 April 2006 03:19
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: ProjectMix

Well, I noticed a couple of other things too.  The scrubbing doesn't work
really, not nearly as well as it does with the frontier transport.  And in
all of the alt configurations, I nefver saw where you could adjust the gain
of the four bans of eq.  And of course there is the problem with the midi
input.  It didn't work when I tried installing Gudrun's on my laptop either.

It was as if some buffer was getting overloaded, and we were using a good
Kurzwiel keyboard with it.  I did get the feeling that the mic pre's were
quite good, and you could get the latency down really low.
Gord
----- Original Message -----
From: "Tim Burgess" <tim@xxxxxxxxxxxxx>
To: <ddots-l@xxxxxxxxxxxxx>
Sent: Tuesday, April 18, 2006 5:41 PM
Subject: [ddots-l] Re: ProjectMix


> Hi,
>
> I really liked the Project Mix that I had on evaluation.  The only 
> drawback that I found (and it was enough for me to not keep it), was 
> the way that the Aux buttons worked - one press of Aux 1 would set up 
> the rotary encoders on the channel strips to do one thing.  A second 
> press got them to do something else and so on.  Others may not find 
> this to be a problem but I found that I lost track very quickly as to 
> how the encoders were configured.  A real shame as, if the firmware 
> were written differently, M-Audio could have achieved the same result 
> without using nested "pages" of setup by using
> Shift+Aux1, Alt+Aux1, Shift+Alt+Aux1, etc..  The shift and alt keys 
> Shift+exist
> on
> the unit - I'll be raising this with my M-Audio rep to see if it's 
> possible
> to get the change into a future release.
>
> Cheers.
>
> Tim
> -----Original Message-----
> From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] 
> On
> Behalf Of Gordon Kent
> Sent: 18 April 2006 22:24
> To: ddots-l@xxxxxxxxxxxxx
> Subject: [ddots-l] Re: ProjectMix
>
> Mike:
> I worked with Gudrun's project mix i/o last week and my initial impression
> was that the project i/o software is quite accessible and could be 
> scripted.
> I certainly didn't explore it in home row or anything like that because I
> was in the middle of training Gudrun, but I've certainly seen a lot worse.
> Gord
>
> ----- Original Message ----- 
> From: Mike C <mailto:m_dsmusic@xxxxxxxxxxxx>
> To: ddots-l@xxxxxxxxxxxxxxxx
> Sent: Tuesday, April 18, 2006 7:18 PM
> Subject: [ddots-l] ProjectMix
>
> Hi guys and gals on list.  I know that Lew also has a Project Mix,
> my question is as follows
> 1. How were you able to update the Project Mix to the latest
> Firmware?
> and 2. In your opinion is the control panel on the porject Mix
> scriptable?
> I've been trying to fidle arround with reclassifying the windows,
> and trying to use the homerow feature to try and find my Window but Jaws
> reports that the Child window, nor the parrent Window can not be found.  I
> just finished taking the script writing course in St. Peter's Burg, and of
> course at this time I'm no experct, so that's why I'm seeking advice.
> Let me know.
>
>
>
> ** To leave the list, click on the immediately-following link:-
> ** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
> ** If this link doesn't work then send a message to:
> ** ddots-l-request@xxxxxxxxxxxxx
> ** and in the Subject line type
> ** unsubscribe
> ** For other list commands such as vacation mode, click on the
> ** immediately-following link:-
> ** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=faq]
> ** or send a message, to
> ** ddots-l-request@xxxxxxxxxxxxx with the Subject:- faq
>
> 
** To leave the list, click on the immediately-following link:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** ddots-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on the
** immediately-following link:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to 
** ddots-l-request@xxxxxxxxxxxxx with the Subject:- faq


** To leave the list, click on the immediately-following link:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** ddots-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on the
** immediately-following link:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to 
** ddots-l-request@xxxxxxxxxxxxx with the Subject:- faq

Other related posts: