I guess I'm wondering how you route the audio back into your DAW. You don't seem to mention what software your are using as a DAW. 

I guess I didn't say in the original post - I'm trying to run the SE on a separate, single slave machine.  The DAW is Cubase, but the VE is running on a separate machine.  So I'm not running the DAW on the same machine as the VE.  It's all by itself on one beastly computer...

But the audio works fine - I can click on the keyboard in the VI and hear everything regardless of how much RAM I use.  And MIDI works as long as I stay under 3 GB of samples.

Thanks,

rgames

Update - I started trying random things to see what happens and it turns out that I can get one MIDI port to work if I hit the "Stop Engine" button and then hit the "Start Engine" button.  Unfortunately, I need four.

Furthermore, if I repeatedly stop and start, I switch between MIDI Port 1 and MIDI Port 3 working correctly.  MIDI Port 2 and 4 never work and 1 and 3 never work at the same time...

So the VE is definitely doing some screwey things - doesn't this seem to indicate that the problem is with the VE?

Looking forward to figuring this out,

rgames

You might want to contact RME to ask why having two instances of VE running should cause digital artifacts.  

Good advice - I hadn't pursued the mutliple-instance option to any large extent but if it works, I'll take it!  I've got a question on the RME forums and an e-mail to their support.

In the meantime, though, is there anybody actually running the full SE on a slave machine under XP64?  Multiple VE's or not - I just want to know what's working...

 Thanks,

rgames

@rgames said:

Good advice - I hadn't pursued the mutliple-instance option to any large extent but if it works, I'll take it!  I've got a question on the RME forums and an e-mail to their support.

In the meantime, though, is there anybody actually running the full SE on a slave machine under XP64?  Multiple VE's or not - I just want to know what's working...

 Thanks,

rgames

Sorry to hear you're still stuck Richard, depsite threads on here and ViC.  :( This seems daft in the extreme, it should be working. I'm not sure I can see why it works for me and not for you (XPP x64, RME HDSP cards, VE) but the only difference I can think of is I'm running the full cube, not SE...... dunno..... feel free to drop me a line if you want to have another go at thrashing this out.

Yeah - I got it to work ONCE with the E-Mu card and ONCE with the RME card but I have no idea why.  It seems that it does not work 99% of the time, but every now and then, the stars align...  Couldn't that indicate some type of memory addressing problem - sometimes certain sections get overwritten but every now and then the OS moves that chunk of code/data somewhere else?  Dunno - my code writing chops are pretty basic, so I'm just shooting in the dark here.

The main difference I recall between our setups was that you were using only two MIDI ports per slave machine - is that correct?  I'm using four.  And I'm using the SE, but that shouldn't make a difference.  So our memory use is different, and if it is a memory problem, it could be the difference that causes it not to work for me.  A lame explanation, but the only one I have right now.

Quick question, though - does your HDSP Mixer show up as a 32-bit process under XP64?  i.e. does it show *32 next to the process name in the task manager?

I'm doing the format/rebuild process once again today and adding drivers, software, etc. one-by-one to see what effect they have.

Thanks,

rgames

Update - I did a complete re-install and added the details to the original post.

Basically, nothing changed.  Sometimes the MIDI works and sometimes it doesn't.  I can stop and start the engine, change sound card settings, etc. and that seems to do something sometimes but, overall, it's just sort of random.  The audio always works, though...

rgames

OK - another update.  I bought a completely new motherboard to match the machine that VSL is using (ASUS P5W).

Still no change, though.

So now I've tried three different sound cards and two different motherboards.  I think it's safe to say it's not a hardware problem...

I'm really starting to wonder if it's not related to the Syncrosoft licensing software.  It is, after all 32 bit (so it might be subject to a 3 GB limit), and the only remaining difference between my machine and those of you who have responded is that we don't have the same licenses - I only have the SE.

I'd sill like to find out if anybody is actually running ONLY THE SE on a slave machine w/ 8 GB of RAM under XP64.  I know it's not supposed to matter from the standpoint of the VE, but I'm becoming more suspicious of the licenses...

Anybody have thoughts on what to try next?

Thanks,

rgames

Hi Christian,

Yes, I have tried the hardware MIDI and it does not work, either.  Well, actually, it works every now and then, just like MOL.  I have two 4x4 hardware MIDI boxes on order but I'm not hopeful that it will solve the problem.

How are you able to run a full template on just 32 MIDI channels?  I need at least four ports to cover all the instruments I'm using...

I'm really starting to believe that it has something to do with the licenses - the only responses I've seen so far have been from people running the Cube.  I still have not heard from anyone who is running ONLY THE SE this way...

Thanks,

rgames

@rgames said:

Update - I did a complete re-install and added the details to the original post.

Basically, nothing changed.  Sometimes the MIDI works and sometimes it doesn't.  I can stop and start the engine, change sound card settings, etc. and that seems to do something sometimes but, overall, it's just sort of random.  The audio always works, though...

rgames

rgames,

My other two posts explain a bit more. But I'm now having similar behavior. I was able to get the VE to respond to Midi once I pressed teh Stop Engine Key, but only the one time. It hasn't worked since. Funny thing is, as of now, my other slave (which is an exact duplicate except for the motherboard) is not behaving this way. I've loaded build 2781 on it and 6.5 gigs of RAM (all Chamber and Solo Strings) and it seems to be ok so far.

By the way, my slave machines are a bit different from yours, so the difference may help in eleminating some guesses:

Gigabyte motherboard

8 GB RAM

Frontier Wavecenter PCI Card (2 midi inputs/1 ADAT out/1 ADAT in)

Midisport 4x4 midi interface

Sonar 7

Mahlon

@Mahlon said:

By the way, my slave machines are a bit different from yours, so the difference may help in eleminating some guesses:

Gigabyte motherboard

8 GB RAM

Frontier Wavecenter PCI Card (2 midi inputs/1 ADAT out/1 ADAT in)

Midisport 4x4 midi interface

Sonar 7

Mahlon

Mahlon - I'm sorry to hear that you're having the same problem but I am at least relieved to hear of someone else repeating it :).

I don't think the hardware has anything to do with it (I've tried a lot of different hardware and it all behaves the same with the same set of samples).

So you have one machine that works: it has the solo/chamber strings.  What are you running on the other machine that is having MIDI problems?  And here's a test you might do: swap the samples between the two machines and see if the problem follows the machine or the samples.

Oh yeah - how many MIDI ports are you using on the two machines?  Is the functional machine using fewer MIDI ports? 

Hopefully VSL will chime in with some suggestions soon...!!! 

rgames

DG,

The midisport 4x4 is on the DAW main computer, which is running XP32 and Sonar. The (2) slaves are running XP64 with the Wavecenter PCI cards receiving the midi in. Now, there might be a problem with the Wavecenter 64 bit drivers and midi, not sure. I couldn't work on it anymore last night, but this evening I will try some scenarios to see if either I can reproduce what happened or chalk it up to user error somewhere.

rgames,

Each slave computer has 2 midi ports which come in through the Wavecenter PCI cards. Both ports on each computer are enabled in VE, but I'm only using 1 port on each computer (Port 1 IN) at the moment.

On the machine (Computer VSL01) which has worked correctly so far:

App Strings ,L1 and (L2 in demo mode)

Chamber Strings, L1 and (L2 in demo mode)

Solo Strings, L1 and L2

Harp L1, and L2

On the machine (Computer VSL02) which gave me the glitch last night:

 Brass 1, L1 and L2

Woodwinds 1, L1 and L2

I will try your suggestion of switching the sounds tonight if I have time. So far, it's only happened with the one VE Project file which runs about 6.5 gigs on Computer VSL02. I tried reloading the matrices individually to make a new project file, and as of bedtime last night, MIDI was working on that project file. But I didn't have time to reload that file in one 'go' -- but I will tonight.

Thanks,
Mahlon

Well, rgames,

After several hours, I'm making some headway in finding at least a little consistency. VE definitely stops receiving midi. Whenever I load more than 13 channels in a standalone VE and save this as a project, the project won't re-open with midi working correctly. In fact VE is not recognizingn any midi at all when I open a project that has 14 channels with a matrix in each. If I have 13 channels loaded and save this as a project, it re-opens and works fine with midi. This has been consistent and is why my other slave hasn't displayed the problem -- because it's only had 10 channels loaded at most. IWhen I loaded 14 channels into it, the midi stopped working upon re-opening the saved project. Incidentally, if I don't save the project file, I can load up to 16 channels and everything works ok. It's just once I save the file, and re-open it that the midi stops. So, I guess I will contact tech support with this info and see if there something weird going on.

 Below (if you want to read it) is a bit of stream of consiousness writing I did while experimenting. It may help explain in more detail about my setup and what I did. I'm going to bed now.... my hard drives have had a time of it tonight...and so have I.

Mahlon

1. I have a 5.7 GB VE project file with 15 midi channels, one matrix loaded into each. This project file will load into VE but midi doesn't seem to be working. Midi is leaving Sonar 7 and going out the DAW's midisport 4x4 and then to the slave machine. But VE does not pick up any midi! (incidentally, I can play the patches from the VE keyboard by mouse-clicking, so I know my audio is OK)

2. However, if instead, I start from a clean slate (nothing loaded and full RAM in VE), I can individually load the same matrices as above into VE by hand, and the midi DOES work correctly. It's just once I save it as a project midi won't work. But this hasn't been true for all projects -- smaller projects with less midi channels load ok.

3. So, to experiment, I've decided to load the individual matrices one at a time, AND SAVE a new project file after each additional matrix. In other words, I load my matrix Flute 01, then save the project as Project Flute 01, reboot the computer, start VE, then reload the saved Project Flute 01. If all goes well, I add another matrix (say, Oboe 01), save both matrices as a new project (Project Flute 01 Oboe 01), reboot, start VE and reload Project Flute 01 Oboe 01, then add another matrix, save, etc. etc.

...you can imagine how long this is taking once several instruments are loaded..... keep imagining....I'm loading up midi channel 13 right now, and so far so good (even on such an unlucky number)....

Ok. It broke on midi channel 14. After saving the 14th matrix, and then reloading that Project (with 14 midi channels), the midi stopped responding. Now, I'm thinking that why my other machine may be working fine is because I have only 10 midi channels loaded. hmmm.......just confirmed, the other slave loses midi connectivity at channel 14 loaded.....

Yes - I've had the same behavior: I can load up a number of channels on-by-one and they seem to work sometimes but then won't work at all when I re-load the saved project.

I now recall that I went down a similar path many weeks ago when I first started debugging this problem.  But I got sidetracked into trying to match VSL's hardware setup... I guess it's time to revisit it.

I'm willing to bet all your MIDI channels will work so long as your total sample usage stays below 3 GB.  That's my experience.  I can get all MIDI ports/channels to work as long as I stay under the 3 GB limit.

So maybe it's a combination of the 3 GB limit and the total number of channels being used.

But it doesn't seem possible - I've seen posts from people using 7+ GB of samples.  Surely they must be using more than 13 MIDI channels, right?

I'll do some more testing today and see what I can come up with.

rgames

I'll try loading under 3 gigs in 14 or more channels tonight.

Mahlon

Perhaps if someone else who has a xp64 system with 8 GB ram could also test this.

Try loading more than 3 GB of samples into 13 midi channels in VE. Then save the file as a project and re-open it. See if Midi is being received. It should be. Then load one more matrix into channel 14 to make 14 midi channels and save this as a new project file. Re-load this file and see if the midi is being received.

Thanks if anyone has time to do this. That way I would know whether or not to start looking at my Wavecenter PCI card's midi as a culprit. (but since rgames is using different midi in devices and getting somewhat similar problems, I don't think right now that it's the midi/audio card).

Mahlon