Ooof! I'm out of cards on this one. It just doesn't make sense. Have you tried a brand new project with only a midi in and audio output to eliminate any possible conflicts (although I don't know why there would be any)?

This issue is on xite. Not the pci cards. And the answer is to change samplerate back and forth in scope to apply the edits/changes.

@ Gary. Do you seriously have it working on xite no problems?Has there been a fix? as via sonic core support (around 2013) it was confirmed that these (the mds8, step sequencers on synths like the sb404) bugs where known and should be fixed in the next release of scope on xite.

I just tried this and it works here as well, so I also tried assigning Gateway to dsp1 and that works as well. So I thought that it was worth trying SB404. When I assigned to dsp2 it doesn't work and I get an error notice saying that the Capacity limit of DSPs has been reached. If I then cancel that I get another error saying "The file you have attempted to load contains a configuration which does not match your hardware configuration", which I have not come across before. I then continue to get more errors about the capacity limit of DSPs.

However, I then tried loading SB404 on dsp1 and that works and allows SB404 Step Editor to respond to changes in real time.

So could this info be used by the coders at SC for them to look at those dsps and see if there is any relation to the Sequencer issues we have on XITE?

Who is online

Users browsing this forum: Google [Bot] and 2 guests

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum