#8

then it goes over and over with that failure

#9

Thanks! Hmm OK well that tells me something but not everything.

If you’re up for helping me track this down I’d love to see the results of the following:

#10

Hey Mark!
Just arrive from some days off… Will get into that right now and report back!

#11

Mark, sorry for taking this long. here the console log with your DEBUG version. Not too long, still having half of the grid operative

07/09/15 18:04:37,000 kernel[0]: AppleUSBFTDI: fInBufPool,kMaxInBufPool 8,64
07/09/15 18:04:37,000 kernel[0]: AppleUSBFTDI: Version number - 1.0.1b16, Input buffers 8, Output buffers 16
07/09/15 18:04:42,447 SystemUIServer[223]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
07/09/15 18:04:51,792 MIDIServer[391]: Bluetooth MIDI driver is starting …
07/09/15 18:04:51,794 MIDIServer[391]: Bluetooth MIDI driver finished starting.
07/09/15 18:04:52,990 Sequencer[389]: MIDI source: To Mark Eats Sequencer
07/09/15 18:04:52,990 Sequencer[389]: MIDI destination: From Mark Eats Sequencer
07/09/15 18:04:52,992 Sequencer[389]: OSC in port: 12234
07/09/15 18:04:52,992 Sequencer[389]: OSC out port: 12234
07/09/15 18:04:52,992 Sequencer[389]: OSC prefix: markeatsseq
07/09/15 18:04:52,993 Sequencer[389]: !sendOsc: <OSCMessage ‘/serialosc/list’-’(
“”,
“<OSCVal i 12234>”
)’>
07/09/15 18:04:52,994 Sequencer[389]: !sendOsc: <OSCMessage ‘/serialosc/notify’-’(
“”,
“<OSCVal i 12234>”
)’>
07/09/15 18:04:53,275 Sequencer[389]: OSC received /serialosc/device m0001714 monome 12814
07/09/15 18:04:53,276 Sequencer[389]: valueArray: (
“”,
“”,
“<OSCVal i 12814>”
)
07/09/15 18:04:53,276 Sequencer[389]: Auto-connecting…
07/09/15 18:04:53,276 Sequencer[389]: Connecting to grid controller…
07/09/15 18:04:53,276 Sequencer[389]: !sendOsc: <OSCMessage ‘/sys/host’, ‘’>
07/09/15 18:04:53,277 Sequencer[389]: !sendOsc: <OSCMessage ‘/sys/port’, ‘<OSCVal i 12234>’>
07/09/15 18:04:53,277 Sequencer[389]: !sendOsc: <OSCMessage ‘/sys/prefix’, ‘’>
07/09/15 18:04:53,277 Sequencer[389]: !sendOsc: <OSCMessage ‘/sys/info’, ‘<OSCVal i 12234>’>
07/09/15 18:04:53,277 Sequencer[389]: !sendOsc: <OSCMessage ‘/markeatsseq/tilt/set’-’(
“<OSCVal i 0>”,
“<OSCVal i 1>”
)’>
07/09/15 18:04:53,286 Sequencer[389]: OSC received /sys/host localhost
07/09/15 18:04:53,287 Sequencer[389]: value:
07/09/15 18:04:53,287 Sequencer[389]: OSC received /sys/host localhost
07/09/15 18:04:53,287 Sequencer[389]: value:
07/09/15 18:04:53,287 Sequencer[389]: OSC received /sys/port 12234
07/09/15 18:04:53,287 Sequencer[389]: value: <OSCVal i 12234>
07/09/15 18:04:53,287 Sequencer[389]: OSC received /sys/port 12234
07/09/15 18:04:53,288 Sequencer[389]: value: <OSCVal i 12234>
07/09/15 18:04:53,288 Sequencer[389]: OSC received /sys/prefix /markeatsseq
07/09/15 18:04:53,288 Sequencer[389]: value: <OSCVal s /markeatsseq>
07/09/15 18:04:53,288 Sequencer[389]: OSC received /sys/id m0001714
07/09/15 18:04:53,288 Sequencer[389]: value:
07/09/15 18:04:53,288 Sequencer[389]: OSC received /sys/size 0 0
07/09/15 18:04:53,288 Sequencer[389]: valueArray: (
“<OSCVal i 0>”,
“<OSCVal i 0>”
)
07/09/15 18:04:53,289 Sequencer[389]: WARNING: Monome returned size: 0x0 using 8x8 instead
07/09/15 18:04:53,289 Sequencer[389]: Connected to grid controller: m0001714 / Size: 8x8 / Type: 1 / Varibright: 1
07/09/15 18:04:53,291 Sequencer[389]: OSC received /sys/host localhost
07/09/15 18:04:53,292 Sequencer[389]: value:
07/09/15 18:04:53,292 Sequencer[389]: OSC received /sys/port 12234
07/09/15 18:04:53,292 Sequencer[389]: value: <OSCVal i 12234>
07/09/15 18:04:53,292 Sequencer[389]: OSC received /sys/prefix /markeatsseq
07/09/15 18:04:53,292 Sequencer[389]: value: <OSCVal s /markeatsseq>
07/09/15 18:04:53,292 Sequencer[389]: OSC received /sys/rotation 0
07/09/15 18:04:53,292 Sequencer[389]: value: <OSCVal i 0>
07/09/15 18:04:58,289 Sequencer[389]: Calibration of tilt sensor timed out
07/09/15 18:04:58,289 Sequencer[389]: No tilt calibration data received, assuming default values
07/09/15 18:04:58,289 Sequencer[389]: Calibrated tilt sensor to XCenter: 126 / YCenter: 126 / Range: 35 / DeadZone: 2
07/09/15 18:04:59,638 Sequencer[389]: OSC received /markeatsseq/grid/key 2 3 1
07/09/15 18:04:59,638 Sequencer[389]: valueArray: (
“<OSCVal i 2>”,
“<OSCVal i 3>”,
“<OSCVal i 1>”
)
07/09/15 18:04:59,712 Sequencer[389]: OSC received /markeatsseq/grid/key 2 3 0
07/09/15 18:04:59,712 Sequencer[389]: valueArray: (
“<OSCVal i 2>”,
“<OSCVal i 3>”,
“<OSCVal i 0>”
)

#12

Hi just wanted to say thanks for trying that and I will definitely dive into it soon, just a little busy atm :slight_smile:

At first glance I think I may have to quiz you a little more to track this done but I want to try a few things my side first.

#13

No problem :slight_smile: at your disposal

#14

OK so I know this is several months later but if you do still have time I’d still be interested in tracking this one down!

I put together a simple test app:
http://www.markeats.com/sequencer/old-versions/monome-connection-test-001.zip

Can you try:

  • Plug in the grid
  • Open the test app
  • Choose the monome from the dropdown
  • Hold a key on the monome for a second and you should see a test pattern across the whole grid (or not)
  • Let me know what you see, and copy and paste the log it produces in it’s window back here.

Thanks!

#15

Of course! will report back tomorrow :slight_smile:

#16

I’ve had the same problem as OP but didn’t chime in – happy to help testing!

[2016-12-30 19:05:20] Raw OSC: <OSCMessage ‘/serialosc/device’-’(
“”,
“<OSCVal s monome 128>”,
“<OSCVal i 18294>”
)’>
[2016-12-30 19:05:29] Selected OSC out address 127.0.0.1
[2016-12-30 19:05:29] Selected OSC out port 18294
[2016-12-30 19:05:29] Trying to connect…
[2016-12-30 19:05:29] Raw OSC: <OSCMessage ‘/sys/port’, ‘<OSCVal i 12234>’>
[2016-12-30 19:05:29] Raw OSC: <OSCMessage ‘/sys/prefix’, ‘<OSCVal s /markeatsseq>’>
[2016-12-30 19:05:29] Raw OSC: <OSCMessage ‘/sys/id’, ‘’>
[2016-12-30 19:05:29] Raw OSC: <OSCMessage ‘/sys/size’-’(
“<OSCVal i 16>”,
“<OSCVal i 8>”
)’>
[2016-12-30 19:05:29] Grid size set to 16x8
[2016-12-30 19:05:29] Connected OK to monome!
[2016-12-30 19:05:29] Raw OSC: <OSCMessage ‘/sys/host’, ‘’>
[2016-12-30 19:05:29] Raw OSC: <OSCMessage ‘/sys/port’, ‘<OSCVal i 12234>’>
[2016-12-30 19:05:29] Raw OSC: <OSCMessage ‘/sys/prefix’, ‘<OSCVal s /markeatsseq>’>
[2016-12-30 19:05:29] Raw OSC: <OSCMessage ‘/sys/size’-’(
“<OSCVal i 16>”,
“<OSCVal i 8>”
)’>
[2016-12-30 19:05:29] Grid size set to 16x8
[2016-12-30 19:05:29] Connected OK to monome!
[2016-12-30 19:05:29] Raw OSC: <OSCMessage ‘/sys/rotation’, ‘<OSCVal i 0>’>
[2016-12-30 19:05:34] Raw OSC: <OSCMessage ‘/markeatsseq/grid/key’-’(
“<OSCVal i 0>”,
“<OSCVal i 3>”,
“<OSCVal i 1>”
)’>
[2016-12-30 19:05:37] Raw OSC: <OSCMessage ‘/markeatsseq/grid/key’-’(
“<OSCVal i 0>”,
“<OSCVal i 3>”,
“<OSCVal i 0>”
)’>

#17

(I saw the pattern across the whole 128).

#18

Ah it looks like the stuff in quotes is getting removed by the forum software… could you try formatting it as code like this:

[2015-12-31 13:37:07] Raw OSC: <OSCMessage '/serialosc/device'-'(
    "<OSCVal s m0000871>",
    "<OSCVal s monome 256>",
    "<OSCVal i 13792>"
)'>

Although if it’s detecting the size OK then it’s probably not needed :slight_smile:

#19

Hi @damianschwartz just wondered if you’d had a chance to try this?

#20

Hello Mark
Sorry for taking so long, i was in Argentina for a month visiting my family, came back last week but it’s taking me a lot to put up with everything, will try that tonight and will post results here :slight_smile:

#21

Having this issue as well. Test app shows pattern on one half of the grid.
Using the 2015 128.

A snippet of what was produced in the connection test app:

[2016-02-19 19:16:02] Raw OSC: <OSCMessage '/serialosc/device'-'( "<OSCVal s m1000275>", "<OSCVal s monome i2c>", "<OSCVal i 13461>" )'> [2016-02-19 19:16:02] Raw OSC: <OSCMessage '/serialosc/device'-'( "<OSCVal s m1000275>", "<OSCVal s monome i2c>", "<OSCVal i 13461>" )'> [2016-02-19 19:16:15] Selected OSC out address 127.0.0.1 [2016-02-19 19:16:15] Selected OSC out port 13461 [2016-02-19 19:16:15] Trying to connect... [2016-02-19 19:16:15] Raw OSC: <OSCMessage '/sys/port', '<OSCVal i 12234>'> [2016-02-19 19:16:15] Raw OSC: <OSCMessage '/sys/prefix', '<OSCVal s /markeatsseq>'> [2016-02-19 19:16:15] Raw OSC: <OSCMessage '/sys/id', '<OSCVal s m1000275>'> [2016-02-19 19:16:15] Raw OSC: <OSCMessage '/sys/size'-'( "<OSCVal i 0>", "<OSCVal i 0>" )'> [2016-02-19 19:16:15] Width is 0, using default of 8 [2016-02-19 19:16:15] Height is 0, using default of 8 [2016-02-19 19:16:15] Grid size set to 8x8 [2016-02-19 19:16:15] Connected OK to monome! [2016-02-19 19:16:15] Raw OSC: <OSCMessage '/sys/host', '<OSCVal s localhost>'> [2016-02-19 19:16:15] Raw OSC: <OSCMessage '/sys/port', '<OSCVal i 12234>'> [2016-02-19 19:16:15] Raw OSC: <OSCMessage '/sys/prefix', '<OSCVal s /markeatsseq>'> [2016-02-19 19:16:15] Raw OSC: <OSCMessage '/sys/rotation', '<OSCVal i 0>'> [2016-02-19 19:16:19] Raw OSC: <OSCMessage '/markeatsseq/grid/key'-'( "<OSCVal i 0>", "<OSCVal i 3>", "<OSCVal i 1>" )'> [2016-02-19 19:16:20] Raw OSC: <OSCMessage '/markeatsseq/grid/key'-'( "<OSCVal i 0>", "<OSCVal i 3>", "<OSCVal i 0>" )'> [2016-02-19 19:16:20] Raw OSC: <OSCMessage '/markeatsseq/grid/key'-'( "<OSCVal i 9>", "<OSCVal i 5>", "<OSCVal i 1>" )'> [2016-02-19 19:16:21] Raw OSC: <OSCMessage '/markeatsseq/grid/key'-'( "<OSCVal i 9>", "<OSCVal i 5>", "<OSCVal i 0>" )'>

#22

Think this is actually a serialosc bug (have mentioned it to tehn already). New Sequencer build has a work-around though, give it a go and see if it works for you guys.

#23

First I must say that I love this app. It’s the first app for monomer grid that I could understand and actually predict in less than 5 minutes (I’m new to this grid thing…), however, I have a problem:
When I have a sequence running my grids buttons sometimes stop working. The leds are still updated and the midi signal is just fine. It’s just that it doesn’t respond to pushes. After a couple of seconds it gets responsive again. I haven’t yet found a pattern how to trigger this behaviour. Any tips for debugging?
I’m using 1.0 (20 beta) with a gs 64.

#24

hmm not heard of that before. a few starter questions:

  • what version of serialosc are you using?
  • have you double checked this doesn’t happen with other monome apps?
  • is the desktop UI, or the computer in general, unresponsive when this happens?
#25

I don’t know which version of serialOSC. All I know is that I have only installed the package from the grid getting started page. The one that also includes the sum app.
The sum app works fine. I have also played around with processing and have not experienced any problems.
The system works fine during hiccups. I use some software synths and they continue to play midi from the sequencer via an IAC driver. I’ve also sent the sequence to my Korg SQ-1 used as usb-cv and usb-midi interface.
My initial thought was that the communication line was filled with tilt-data but then I got the same problem when I try to hold the device still. (I don’t even know if the tilt is working).
I will do some more testing tonight and see if I can find a common parameter.

#26

I was mainly wondering if you could click things in the desktop app, if the UI is responsive not just the MIDI is sending.
You can try disabling tilt in the preferences.
And I think this is the latest serialosc: https://github.com/monome/serialosc/releases/tag/v1.4
Another thing to mess around with is USB hub vs direct to computer.

#27

That is the most recent version of serialosc. I believe the version that comes with monome_sum is v1.2. Good idea to go ahead and update.

1 Like