Can't use OSCP5 in landscape Orientation

Android Processing

snowcrash..

Can't use OSCP5 in landscape Orientation

in Android Processing • 2 years ago

Hello,

I developing an app that display a video when an osc message is received.

To display the video in fullscreen I put the orientation on landscape, the video is displayed using apwidgets.

I realized that in landscape orientation, osc message are still received and print in the console,

but any other code in the void oscEvent(OscMessage theOscMessage) is not effective any more...

Any solution ??

Here my code, you have to remove line 10 to make it works :

import oscP5.*;
import netP5.*;
OscP5 oscP5;
NetAddress myRemoteLocation;
void setup()
{
orientation(LANDSCAPE);
//OSC
oscP5 = new OscP5(this,12000);
myRemoteLocation = new NetAddress("127.0.0.1",12000);
}
void draw(){
}
void mousePressed() {
oscP5.send("/MessageToDevice",new Object[] {"GetCold"}, myRemoteLocation);
}
void oscEvent(OscMessage theOscMessage) {
/* print the address pattern and the typetag of the received OscMessage */
print("### received an osc message.");
print(" addrpattern: "+theOscMessage.addrPattern());
println(" typetag: "+theOscMessage.typetag());
background(random(255));
}

Replies(1)

metabog

Re: Can't use OSCP5 in landscape Orientation

2 years ago

I've had quite a few problems with the orientation function even crashing my apps. The issue is that calling orientation will (likely) completely restart your app, and a lot of subsystems like OSC don't like that (for example, it crashes SoundPool for me). What I would try is remove the call to orientation and instead change the manifest to force Landscape orientation, that way you don't have to call setup() and then call Orientation which essentially will call setup() again. I had one app where basically I stupidly wasted time making a kind of safeguard system to keep the app from reloading everything in memory twice when I called orientation to force landscape mode, when in fact the solution was a simple modification to the manifest. I may be completely wrong, though, but this is what I found doing some of my apps and experiments. Try adding this to the manifest file (the bolded part, you'll find where to put it) and remove the call to orientation...

<application android:icon="@drawable/icon" android:label="@string/app_name">
        <activity android:name=".Synth"
                  android:label="@string/app_name"
                  android:screenOrientation="landscape">
            <intent-filter>
                <action android:name="android.intent.action.MAIN" />
                <category android:name="android.intent.category.LAUNCHER" />
            </intent-filter>

Top Reply