search

monome / monome_sum

max for live & max 6.1 routing & patch management system for grids (+arcs?)
33 stars 6 forks source link

[windows] serialosc looses connection #67

Closed SorenAndreasen closed 10 years ago

SorenAndreasen commented 10 years ago

it seems, quite randomly (or i can't see the patterns) that serialosc will just quit at some point.

i base this upon grids suddenly not showing up in the serialosc object anmore (tested in sum and monome_test). also serialosc doesn't show up as an active process.

tehn commented 10 years ago

be specific.

it just drops out while running? you sleep the computer and wake it up then it's gone? you quit a program then load another and it doesn't come up? when do you notice it going away?

On Tue, Apr 8, 2014 at 5:24 PM, SorenAndreasen notifications@github.comwrote:

it seems, quite randomly (or i can't see the patterns) that serialosc will just quit at some point.

i base this upon grids suddenly not showing up in the serialosc object anmore (tested in sum and monome_test). also serialosc doesn't show up as an active process.

Reply to this email directly or view it on GitHubhttps://github.com/monome/llllllll/issues/67 .

SorenAndreasen commented 10 years ago

it doesn't drop out while running no. it happens between connecting and disconnecting the grid and restarting monome sum. i'm going back and forth between yours and my pc to test several things, so for now i'm just observing that this is an issue.

i will try and be aware of details the next time it happens

trentgill commented 10 years ago

this is probably a serialosc issue, not monome_sum -> so while it’s important it’s not really on topic for now??

On Apr 8, 2014, at 5:40 PM, SorenAndreasen notifications@github.com wrote:

it doesn't drop out while running no. it happens between connecting and disconnecting the grid and restarting monome sum. i'm going back and forth between yours and my pc to test several things, so for now i'm just observing that this is an issue.

i will try and be aware of details the next time it happens

— Reply to this email directly or view it on GitHub.

trentgill commented 10 years ago

closing this because it's probably a serialosc server issue