My pleasure DG.
I'm afraid I've given up on the one-machine solution, although it's a totally worthy aim. I just always find that one system to be too heavily taxed to be totally reliable.
Good luck and all the best
Jules
194,099 users have contributed to 42,911 threads and 257,915 posts.
In the past 24 hours, we have 5 new thread(s), 19 new post(s) and 77 new user(s).
My pleasure DG.
I'm afraid I've given up on the one-machine solution, although it's a totally worthy aim. I just always find that one system to be too heavily taxed to be totally reliable.
Good luck and all the best
Jules
@Trailerman said:
My pleasure DG.
I'm afraid I've given up on the one-machine solution, although it's a totally worthy aim. I just always find that one system to be too heavily taxed to be totally reliable.
Fair enough. It's just that "one-machine" is my current workflow (with a 23GB template), and I don't want MIR to make things worse for me, rather than better.
DG
Hi Jules
I'm not sure why you mean "If you're monitoring directly, I'm not sure I understand why latency should be an issue for live players." ?
I plan to use a separate machine for MIR, but the latency issue is still in play here too as I see it - when I play on my main keyboard the midi goes though the main DAW then via MOL or similar to the MIR host's instrument, which then introduces an extra 1024 samples delay before sending the audiosignal back via eg. ADAT to the main DAW and finally to the speakers for me to hear. So there is at least 25 ms delay (more likely 35 ms) btw I press a key and I hear the sound playing.
But offcause having a bypass function will help a lot here - running 128 samples buffer instead while recording midi, and then raise the buffer when switching on the MIR functions.
Hi Bjarne
My statement related specifically to DG's comment about latency when working with live players, not when recording MIDI. If you're working with live musicians and have your host running on a separate system, then as long as the musicians are monitoring themselves 'direct' or via a low latency host buffer setting, MIR latency will not be an issue. In fact DG intends to run everything on one system, in which case it clearly IS an issue, because MIR and the host would share the same buffer settings.
I'll have to check into the bypass function, I wasn't aware of it, but have not been using MIR for the last few days. When I ran some stress tests I found 512 samples (sorry, I keep quoting buffers in ms, brain not working) not to be a problem, and that involved MOL, and it also invovled audio being routed back to Logic on a separate machine and then from Logic onto another separate machine running ProTools HD via lightpipe. 1024 could become probelmatic, no doubt.
I would have thought that on a well specified i7 machine you would get very good performance at 256 samples, indeed it may deliver close to the Xeon spec I use. The only reason I ended up with a Xeon machine is because of the price of 4GB Ram modules for the i7 config, because I wanted the system to have 24GB. When I compared specs, I could get the dual Xeon system for the same price as a 24GB i7 rig because of the savings on Ram cost.
Cheers
Jules
@Hamish said:
the guy recommending that you buy a good graphics card
harmish, it appears you _are_ rude ... though i don't know who *the guy* is i can assure you directX10, openGL 2.1 _is_ a system requirement - we had a hard time to get a slightly older directX9 card to work properly ... read through the posts (especially mine) and you will understand ... would you really like to throw your performance resources on the grafic?
christian
@cm said:
the 5520: we currently have one for testing, 24 GB RAM, overclocked to 2.9 GHz, not yet finetuned ... very impressive ... seems to be a tick less performant than the 5580 (3.2 GHz)
personally i'm still not sure what the most important part is - CPU speed, memory speed, number of calculation units, level2/level3 cache ... the amount of possible testing scenarios is pretty huge ... we will have to find out.
christian
Hi Christian
I suppose the memory bandwidth is increased also when overclocking the 5520 ?
I've noticed that the X and W types have 6.4Gb memory bus, while the E types "only" have 5.8Gb
Hamish - the easiest way to get some first-hand experience would be to download the demo version of Vienna MIR and try. Christian (cm) has already pointed out the needs of its GUI.
It seems that you don't own any VIs by now, but you could use its graphical features anyway.
We have made bad experiences when the graphic card doesn't adhere to some minimal standards.
... but of course the requirements are no the same as for full-fledged PC-games! 8-)