Marbles_00 wrote:P3rvB3ar,
What's the PervClient?
Its crude debugging tool which allows commandline access to pervhub running on local machine.
When my crash occurs, it's when I go to adjust the volume control, if I click on the arrows or bars I can get it to crash kXd.
Double check your registers on .ini files. Also if it would happen just on arrows it could be caused bu the fact that kXd wont check that value is valid. This is know bug. And u could try that far fetched idea i was having, that it could be scalt nov 28 bug... notice though that in scalt case those were dummy fades... what u could try would be dummy registers... it might be that u would actually have to take idea so far that u would add dummy stereo mixers to your DSP... but as i said this is just very far fetched quess... there could be lot of other reasons... i would start by double checking those ini files.
EDIT: and actually seeing scalts registers pretty much shutdown my theory. cause he is having separate register names on different cards, and he dont have that problem with volume... question though is if he is using firstname or callsign of device when calling those... what im trying to say marbles, is if u r using firstname pervhub will send command to both kXd instances and since there is no register alias like that on other one and no safeguard in place (also know bug) it will crash. So i think what u should do is make sure that bars and arrows are actually using kXd instances alias name instead of first name, but scalt can prolly say is this right? do alias names work properly and so on...
For me, what I've noticed, and I'm going to have to play with it some more, but Pervhub doesn't crash until I try and close the current hub down (to restart after making changes).
this is nothing to worry about... its happening to me too... im pretty sure its because when perhub is bringing whole infrastructure down it will try to close already closed TCP-connection and that causes error. ill just need to add little more intelligent shutdown procedure... or rather one more error handler
to clean things up properly... this though has never been very high on priority.