Peer Control problems

[Grids]

Hey guys I am having problems with peer control....

I can't access the assignments section...it just does nothing when I click....

I am using nubuzz - the newest version from about 1 month ago....I have windows 7


Any ideas?

[snowglobe]

register envelope.ocx

[Grids]

Sorry how do I do this?

[snowglobe]

Sorry how do I do this?

Possibly the easiest route is to download and run the old fixkit.

• cancel when it asks you if you want to open the help file
  agree to the terms
  setup -> check boxes : extract Stygmate's envelope.ocx & register envelope.ocx
  run

[hofmeister]

I encounter the same problem and the Fixkit thing didn't help. Now what?

Thanks in advance,

Hofmeister

[snowglobe]

I encounter the same problem and the Fixkit thing didn't help. Now what?

If you have registered envelope.ocx and are still having issues with not seeing the Assignments window, the only thing I can think of is:

you might not have the version of PeerCtrl that works in Buzz08/New Buzz/not-old-Buzz?
maybe you have the right version, but it's not in the Gens folder?

[hofmeister]

Thanks for reaction, I'll take a look again to be sure. The new Peer LFO works great, that's kinda strange...

[hofmeister]

Okay, peer state and peer ctrl are in Generators folder like they should. I'm working on a 64bit system and peer ctrl and state are 32bit? that shouldn't be a problem does it? Peer LFO has a 64bit version, that one works.

I still run old buzz on the same system as well, could that be interfering somehow with the hew one?

Not a big problem but it's quite odd though, when loading old tracks, made with old buzz, into new buzz CPU blows up to 100%, anyone familiar with this error?

Greets,

Hofmeister

[thOke]

I still run old buzz on the same system as well, could that be interfering somehow with the hew one?

I am running old and new Buzz from the same directory on a 64-bit system, too. That shouldn't be a problem.

There must be a subfolder called PeerCtrl in the generators folder with additional files.
They are included in the zip of version 1.5 on buzzmachines:
http://www.buzzmachines.com/machineinfo.php?id=805

Version 1.6 for new Buzz is here (main DLL only):
http://sourceforge.net/projects/btdsys/files/

[hofmeister]

There must be a subfolder called PeerCtrl in the generators folder with additional files.
They are included in the zip of version 1.5 on buzzmachines:
http://www.buzzmachines.com/machineinfo.php?id=805

Okay, thank you for responding. I have created that folder. So it should work now. But it doesn't.

Version 1.6 for new Buzz is here (main DLL only):
http://sourceforge.net/projects/btdsys/files/

I've done this as well. Still a white screen with no machines. PeerLFO works well. PeerState and PeerCtrl don't.

[IXix]

I'm glad to hear that PeerLFO x64 works okay.

For state and ctrl, I can only suggest running dependency walker (http://www.dependencywalker.com/) on them and see what it says.

[hofmeister]

Here we go:

Dependency Walker on Peer State file:

Error: At least one module has an unresolved import due to a missing export function in an implicitly dependent module.
Error: Modules with different CPU types were found.
Warning: At least one delay-load dependency module was not found.
Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module.

Dependency Walker on Peer Control file:

Error: At least one required implicit or forwarded dependency was not found.
Error: At least one module has an unresolved import due to a missing export function in an implicitly dependent module.
Error: Modules with different CPU types were found.
Warning: At least one delay-load dependency module was not found.
Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module.

[IXix]

It should tell you exactly what's missing, although it may mention some things that don't actually matter. My guess would be a visual studio runtime dll or some similar thing. I can't remember if you can save/export the dependency report but if you can, we might be able to determine what you need.

[hofmeister]

I'm on it!

[hofmeister]

Peer Control errors opening files

MSVCR80.DLL
API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
API-MS-WIN-SHCORE-SCALING-L1-1-1.DLL
DCOMP.DLL
IESHIMS.DLL


Peer State errors opening files

API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
API-MS-WIN-SHCORE-SCALING-L1-1-1.DLL
DCOMP.DLL
IESHIMS.DLL

[IXix]

MSVCR80.DLL

That's a biggie. As I understand it, it used to be a system file but is no longer distributed as part of a Windows installation. I'm guessing that you need the x86 version for the x86 machines so you could try installing this...
http://www.microsoft.com/en-us/download ... px?id=3387

If that installs okay, see if it fixes the machines. If not, run depends.exe on them again.

I know from past experience that IESHIMS.DLL (and DCOMP.DLL I think) is not necessary. I don't know about the API-MS-WIN- ones. Those may be a different problem.

[hofmeister]

I ran the utility. Peer stil doesn't work. Dependancy walker detects the same errors as before. Thanks a lot so far, coming back tomorrow, good night!

[IXix]

I ran the utility. Peer stil doesn't work. Dependancy walker detects the same errors as before.

Ah well. If you can find the MSVCR80.DLL it installed, you could try popping that in the Buzz program folder or maybe in the generators folder. I'm pretty much guessing as I have no experience of running Buzz on a 64bit machine.

[IXix]

I haven't really looked at the PeerCtrl code much as it's a complicated beast but I have built it in the past. Firing up Buzz just now and trying PeerCtrl, I found my build suffers the same "crash when you open a dialog" problem that I hit with PeerADSR, so I rebuilt it using the same fix (thanks again Oskari) and it opens up okay now. I think there's a good chance that it will work for you too, although it may not...

BTDSys PeerCtrl (x86 dll only, static MFC) - 2014.04.08

[IXix]

Done the same with PeerState...
BTDSys PeerState (x86 dll only, static MFC) - 2014.04.08

Note that I haven't actually tested either of these new builds, other than loading them up and seeing whether they crash when I open a dialog. Also, I forgot to mention (because I forgot I'd done it) that the new PeerCtrl build has been converted to use PeerLib2 and incorporates some other improvements of my own. It should be backward compatible with the previous version but I haven't tested it. It's the main dll only because I haven't tackled the extra plugins yet and so I don't know if those will work or not (I'm not optimistic). I haven't released it before because I wanted to have the full package.

The new PeerState is just a straight rebuild using the newer compiler so it's 100% the same machine, just newer.