Hi
I've just spent a very, very frustrating day battling all kinds of issues with my studio, some of which I believe are Cubase bugs, possibly some hardware issues, but a couple which I can't solve, that affect VEPro - I'm hoping some network experts have seen these issues before and can help.
I have a system with a win7 DAW and two win7 slaves - all completely built from scratch, everything installed very carefully, and set up identically. Yet slave number 1 is behaving differently, on the network, from slave number 2. When exploring the network from the other machines it appears as both a PC and a media streaming device, even though media streaming is turned off on all three, Media Player has never been run, I don't have iTunes installed, nor anything else which might want to stream media, other than VEPro. I don't know whether it's a problem that it appears as both, but it does have issues with playback. When I use it as a slave there is a regular 'pulsing' (somewhere between a click and a pop, but constant at about 80bpm) in the audio that comes back. It's not related to the bpm of my Cubase project, nor the clock on my keyboard, nor anything else that transmits a MIDI beat - as far as I can tell. And I discovered today that it starts occurring when the machine appears in the 'Media Devices' list on the network. So long as it doesn't (and I still don't know what makes the difference) this pulsing doesn't happen.
Secondly I have audio dropouts in the streamed audio from both slaves. This varies from being an extreme problem to non-existent, and I also can't find a reason for it. It's not that there are dropouts ON the slaves, but in the capacity of the network to return the audio. This can happen when I'm only loading one instrument, and playing one note on the slaves,with only a single stereo output on VEPro, so it's not a capacity thing. So far no amount of fiddling with network settings seems to make any difference at all. I've tried it with JumboPackets on and off, Green Networking on and off, every possible combination of enabling collision management, etc, but it just doesn't stop. It's usually worst when the network has just been turned on, but sometimes it doesn't happen at all, and sometimes persists so long that I give up on doing any work. Anyone else having similar issues?
