So I had a gig last night that had me using the Samsung Galaxy Note 10.1 to control Resolume via TouchOSC and Touch Bridge. Seemingly it was working fine until about midnight. Then Resolume started to not respond and I had to force quit about 20 times. This was running Resolume on my Mac Retina with only 2 layers and about 4 to 5 effects. It was barely using 10% of the processor and at most I was using 4 gigs of ram out of 16. Attached is the error report that was spit out after one of the crashes.
I would like to know where the point of failure was here, because I've never had Resolume lockup on this computer let alone 20 times in one night.
Samsung Galaxy Note 10.1
- Vjcheshire
- Posts: 69
- Joined: Fri Mar 11, 2011 09:42
- Location: Los Angeles
Re: Samsung Galaxy Note 10.1
Resolume is a 32 bit app, so 4 GB RAM usage is actually 1GB over the limit of what it can access.
I see a lot of threads dedicated to H264 decoding. Were you using H264 files?
I see a lot of threads dedicated to H264 decoding. Were you using H264 files?
- Vjcheshire
- Posts: 69
- Joined: Fri Mar 11, 2011 09:42
- Location: Los Angeles
Re: Samsung Galaxy Note 10.1
Sorry. I should specify more. The whole computer was using 4gb of ram. Resolume was only using around 250mb. I was only running 2 layers at a time, well within the ram limits. Also all of the footage was converted to the DXV codec.

Re: Samsung Galaxy Note 10.1
Can you still recreate this bug, with or without using TouchOSC or the Samsung?
- Vjcheshire
- Posts: 69
- Joined: Fri Mar 11, 2011 09:42
- Location: Los Angeles
Re: Samsung Galaxy Note 10.1
I haven't seen Resolume lock up at all on this computer.. so I don't think I can recreate this bug. It was solely when using the Samsung Galaxy Note 10.1 with TouchOSC for android and the Touch Bridge. When we stopped using the tablet, it worked just fine.
Sadly enough they took the tablet back so I cannot keep testing it.
Sadly enough they took the tablet back so I cannot keep testing it.
