My SX Projects hangs on reload if I have DS-404 in them

Official support for: muon-software.com
RELATED
PRODUCTS

Post

Hello,

I've had the 404 for awhile but just now got around to trying to play with it. I patched to 1.11. I have SX 1.06. Basically any project I try to load a 404 into will not reload once I close it. The SX interface will just totally lock up as soon as the interface loads. If I rename the DS404.dll and load that project then it will load fine with the DS404 not found message.

Post

LOL, ok I went back and created a project with nothing but a 404 track. It loaded fine. Then I went back to the project where it wouldn't load and now it loads fine. I have no idea what changed but at least for the moment I'm good to go.

Post

I have no idea what changed but at least for the moment I'm good to go.
Look to see if there is anything in cubasesx.log (in your cubase sx directory) with a crash against DS404.dll - that would help us track down if there was actually a problem with DS404 at all.

Regards
Dave

Post

Ok, I've played with this a few days and I still have the prob. I can make it happen consistantly now. No, there is no entry in the log file at all. Not even the lock up of Cubase SX. I'm pretty sure its an SX issue but maybe you have some ideas. Here is the break down of what order I can do things in.

I created a test project that only has 1 track with 1 instance of DS-404. If I open that project from a shortcut it will hang. If I open SX and then open the project it will open.

My other projects hang no matter which way I open them, unless I open SX, open the test project, close the test project and then open the project I want to work on.

This is goofy, but if you have any ideas I would be all ears.

Post

So it only crashes when you try to launch the project from a short cut without opening SX first? I'll try your recipe and see if I can make it hang too. Are you running SX on OSX or Windows?

Regards
Dave

Post

Windows XP Pro. Delta 1010. SX 1.06 UAD-1 Midisport 4x4

My last post was a little confusing. Let me see if I can clarify. It always hangs if I launch from a shortcut.

But, an existing project with lots of tracks and FX and such always hangs even if I launch SX first unless I launch the DS404 single track project, close that project without closing SX and then open the larger project from the File Open dialog. If I follow those steps then the larger project will load. I have a boat load of VSTs, I'm wondering if its not getting a chance to load properly. I plan on working on this again tonight. I'll remove all VST from the vstplugins directory, put the DS404 as the plugin, do all the load tests and then start adding them VST back in and see if I can recreate the problem. Heck, it could be a specific combo of VST that is causing the prob, or could be rogue VST that makes it seem like DS404 is the prob. I'll do my best to narrow it down.

Hope that makes sense (of course it doesn't :lol: ) Anyhow, I appreciate you looking into it. Its probably some driver or VST combination thats causing the probs.

Post

It always hangs if I launch from a shortcut.
I've not been able to reproduce this problem. I've got a project using CM101, SR202 and 7 tracks of DS404. I can launch it any which way I like and no problems.

How did you get on with isolating just DS404 in the vstplugins folder?

Dave

Post

sorry, got caught up in some honeydos and didn't get to it till last night. It's some combination of VSTs for sure. When I stripped down the plugins directory everything works fine. I believe, but haven't absolutely proved it yet, that it is FM7 in conjunction with 404 that is causing the prob. But, right when I thought I had that figured out, I loaded a project with both FM7 and DS404 and it worked. So, still working on it.

Post

got caught up in some honeydos
As in "honey can you do this" and "honey can you do that"? happens to me all the time :roll:

Post

Muon Software Ltd wrote:
got caught up in some honeydos
As in "honey can you do this" and "honey can you do that"? happens to me all the time :roll:
Them's the exact kind I was referin to 8), only at this point in life I rarely get the "can you" part.

Post

I hardly ever get the "honey" bit myself :cry:

Post

ok, see if this makes any sense at all. On further review it is probably not FM7 itself. I believe the problem is that I had installed FM7 several times over time. Demo, original, patches..... I should add that the project that would not load is the only one in which I had both an invalid plug listed in the DirectX list loaded as a VSTi (should have been loading the dll version) and the DS-404.


Turns out every single entry for the DirectX entries were still there. This is also true for Pro52 and B4. It is also true for TC Native stuff that I un-installed over a year ago when I got UAD-1. Stuff like the plugs that came with Vegas from my 1010 card bundle. I uninstalled that stuff almost as soon as it hit my HD. But all the entries are still there and SX has them listed in the plugins list. I never look in the DirectX page of the plugins menu. I had zillions of entries for software that has been uninstalled for ages. So, into regedit I went. Weeeeeeeeeeeeeeeeeeeee!!! I removed all the offending entries that should have been removed by the un-install programs. Now my DX plugin page is clean except for the proper ones.

Ok, so my DX Plugin page was a mess in SX. Here is my question. Is it possible that an invalid port assignments was getting handed to DS404 during the init stage if an invalid plug was loaded first? I'm not real clear on exactly what is being done to the plugs as they initialize.

So anyhow, now that it is all clean it seems to be working. I'll let you know if I it happens again. But, I'm pretty sure something in that messed plugin list was causing the prob.

Post

geez, I shouldn't do something else while I'm trying to write an explanation.

It should read that there were multiple entries for each VSTi.

FM7 Demo
FM7 blah blah
FM7 blah blah etc.....

so there was more than one entry for every DirectX instrument plus a boat load of plugs that are not even installed on my system anymore.

Post

no response? Any other info you need?
If you have to ask, you can't afford the answer

Post

So anyhow, now that it is all clean it seems to be working. I'll let you know if I it happens again. But, I'm pretty sure something in that messed plugin list was causing the prob.
From your post before I sort of thought that the problem had gone away. Do you still have problems?

Regards
Dave

Locked

Return to “Muon Software”