@ tpmodding
hast du die switchHyperionSource angepasst ?
@ tpmodding
hast du die switchHyperionSource angepasst ?
OpenELEC mit automatisierter Ambilight Quellenumschaltung(Milhouse 31.10.15) #2? Schau mal ob du hier fündig wirst!
jap, alles wie immer...
glaub iwas spinnt beim CEC?
auch bekomme ich kein loop von video0 auf video1?
TPmodding,
diesen Fehler hatte ich vor langer Zeit mal. Schalte mal den TV komplett aus(stromlos). Reboote dann mal den rpi. Schalte ihn danach komplett aus. Starte nun den TV und danach den rpi.
Wenn das nichts bringt. Geh mal in folgende Datei:
und ändere:
nach
Jetzt ein
Welche Methode hat jetzt funktioniert?
.bismarck
hab so ne datei nicht? ...ich weiss nicht was bei mir abgeht hab auch bei den ganzen .tar's den überblick veroren ^^könntest du die neuste bzw stabilste neu verlinken? im thread sind mehrere und im startpost ist nen ganz anderer
Geh mal nach der Anleitung auf Seite eins vor und installiere auch alles von Seite eins!
.bismarck
hallo bismarck,
das hat sich nun geklärt, der fehler lag bei openelec selbst -> https://github.com/OpenELEC/OpenELEC.tv/issues/4725
tvdzwan hat gestern paar sachen gemerged, könntest du das in dein hyperion packet einbauen damit wir up2date sind und eventuell auch gleich den forwarder von redPanther? somit könntest du deinen video0 zu video1 loop sparen und den RPi entlassten
https://github.com/redPanther/hyp…_json_forwarder näheres hier
Danke für die Rückmeldung. Ich warte noch bis redPanther boblight-Clients weiterreichen kann.
.bismarck
Ich freue mich schon mal riesig drauf .
Hi,
OpenELEC 6.0.2 final ist raus, könntest Du davon vieleicht auch ein Image bauen?
Dann hätten wir ebenfalls den neuen Raspberry Pi 3 an Bord ...
Gruß Tom
Hallo,
bin jetzt von den 10mm LED Pixeln zu einem Stripe gewechselt.
Habe alles angeschlossen und nun sind die Farben falsch. Scheint so, als seien Grün und Blau genau vertauscht.
Habe schon probiert in der ~/hyperion/config/hyperion.config.json die colorOrder von rgb auf rbg zu stellen. Hab rebootet aber hat sich nichts geändert. Was könnte ich tun? muss man das an einer anderen Stelle einstellen?
Dann hast Du wahrscheinlich die falsche Datei geändert.
Die richtigen Dateien liegen normalerweise unter
/storage/.config/ambilight/
Die entsprechenden Dateien:
hyperion.config_KODI_ws2801.json
bzw.
hyperion.config_VIDEOGRABBER_ws2801.json
Je nachdem welche Config Du hast kann das suffix ws2801 auch anders lauten.
Schau mal nach was bei Dir drin ist.
Wenn Du einen Strip anderer Bauart benutzt, muss das suffix ggf. auch in der globalen Config Datei angepasst werden:
/storage/.kodi/addons/service.hyperion-switcher/ switchHyperionSource.conf
-->HYPERION_CONFIG="ws2801" --> "stk1160" usw...
So kannst Du mehrere *config.json Dateien haben, und bei Bedarf dann einfach wechseln
Ja sauber, vielen Dank, hat funktioniert
hatte dann nur nach genau der Datei gesucht und da hat er nur die gefunden die ich schon editiert hatte. aber klar, da war ja was mit mehreren configs.
Hi bismarck, sagmal laufen deine änderungen auch auf dem Rpi3? ist as nur "software"seitig gepatcht alles?
Guten Abend,
ich habe es jetzt endlich hinbekommen, (dank ihrer brillianten Anleitung) es teilweise in betrieb zu nehmen. Ich habe eine andere Anleitung genommen, um ein Ambilight zu erstellen, mit normalen LEDs Stripes. Ich habe jetzt 6 Transistoren, die einen zweigeteilten Strip ansteuern. Die Wlan Steuerung klappt super! Aber das Ambilight will nicht so ganz.
Ich habe in der Swichter Config-Datei zwei Einträge, undzwar für meine linke Seite des Fernsehers und die der rechten. Der Switcher startet nicht im Autostart.
Wenn ich alles manuell starte, klappt alles bis auf das ich kein Ambilight vom Kodi Signal bekomme. Ich benutze keinen USB-Grabber.
Config-Datei für Links
// Automatically generated configuration file for 'Hyperion daemon'
// Generated by: HyperCon (The Hyperion deamon configuration file builder)
// Created with HyperCon V1.00.1 (15.03.2016)
{
/// Device configuration contains the following fields:
/// * 'name' : The user friendly name of the device (only used for display purposes)
/// * 'type' : The type of the device or leds (known types for now are
/// -------------SPI---------------, APA102, WS2801, P9813, LPD6803, LPD8806, -------------PWM---------------, WS2812b, WS281x (no 12b), ------------OTHER-------------, PhilipsHUE, AtmoOrb, PiBlaster, ThinkerForge, UDP, SEDU, TPM2, USBASP-WS2801, USBASP-WS2812, ----------3rd PARTY------------, Adalight, AdalightAPA102, AmbiLed, Atmo, Lightberry, Lightpack, Multi-Lightpack, Paintpack, Test, None)
/// * [device type specific configuration]
/// * 'colorOrder' : The order of the color bytes ('rgb', 'rbg', 'bgr', etc.).
///
/// * 'Specific of Philips Hue:
/// * 'username' : The name of user registred on the Philips Hue Bridge
/// * 'switchOffOnBlack': Define if Hue light switch off when black is detected
/// * 'transitiontime' : Set the time of transition between color of Hue light
"device" :
{
"name" : "MyPi",
"type" : "piblaster",
"output" : "/dev/pi-blaster",
"assignment" : " r g b "
},
/// Color manipulation configuration used to tune the output colors to specific surroundings.
/// The configuration contains a list of color-transforms. Each transform contains the
/// following fields:
/// * 'id' : The unique identifier of the color transformation (eg 'device_1') /// * 'leds' : The indices (or index ranges) of the leds to which this color transform applies
/// (eg '0-5, 9, 11, 12-17'). The indices are zero based. /// * 'hsv' : The manipulation in the Hue-Saturation-Value color domain with the following
/// tuning parameters:
/// - 'saturationGain' The gain adjustement of the saturation
/// - 'valueGain' The gain adjustement of the value
/// * 'red'/'green'/'blue' : The manipulation in the Red-Green-Blue color domain with the
/// following tuning parameters for each channel:
/// - 'threshold' The minimum required input value for the channel to be on
/// (else zero)
/// - 'gamma' The gamma-curve correction factor
/// - 'blacklevel' The lowest possible value (when the channel is black)
/// - 'whitelevel' The highest possible value (when the channel is white)
///
/// Next to the list with color transforms there is also a smoothing option.
/// * 'smoothing' : Smoothing of the colors in the time-domain with the following tuning
/// parameters:
/// - 'type' The type of smoothing algorithm ('linear' or 'none')
/// - 'time_ms' The time constant for smoothing algorithm in milliseconds
/// - 'updateFrequency' The update frequency of the leds in Hz
/// - 'updateDelay' The delay of the output to leds (in periods of smoothing)
"color" :
{
"transform" :
[
{
"id" : "default",
"leds" : "*",
"hsv" :
{
"saturationGain" : 1.0000,
"valueGain" : 1.0000
},
"red" :
{
"threshold" : 0.0000,
"gamma" : 1.0000,
"blacklevel" : 0.0000,
"whitelevel" : 1.0000
},
"green" :
{
"threshold" : 0.0000,
"gamma" : 1.0000,
"blacklevel" : 0.0000,
"whitelevel" : 1.0000
},
"blue" :
{
"threshold" : 0.0000,
"gamma" : 1.0000,
"blacklevel" : 0.0000,
"whitelevel" : 1.0000
}
}
],
"smoothing" :
{
"type" : "linear",
"time_ms" : 300,
"updateFrequency" : 20.0000,
"updateDelay" : 0
}
},
/// The black border configuration, contains the following items:
/// * enable : true if the detector should be activated
/// * threshold : Value below which a pixel is regarded as black (value between 0.0 and 1.0)
/// * unknownFrameCnt : Number of frames without any detection before the border is set to 0 (default 600)
/// * borderFrameCnt : Number of frames before a consistent detected border gets set (default 50)
/// * maxInconsistentCnt : Number of inconsistent frames that are ignored before a new border gets a chance to proof consistency
/// * blurRemoveCnt : Number of pixels that get removed from the detected border to cut away blur (default 1)
/// * mode : Border detection mode (values=default,classic,osd)
"blackborderdetector" :
{
"enable" : true,
"threshold" : 0.11,
"unknownFrameCnt" : 600,
"borderFrameCnt" : 50,
"maxInconsistentCnt" : 10,
"blurRemoveCnt" : 1,
"mode" : "default"
},
/// The configuration of the effect engine, contains the following items:
/// * paths : An array with absolute location(s) of directories with effects
/// * color : Set static color after boot -> set effect to "" (empty) and input the values [R,G,B] and set duration_ms NOT to 0 (use 1) instead
/// * effect : The effect selected as 'boot sequence'
/// * duration_ms : The duration of the selected effect (0=endless)
/// * priority : The priority of the selected effect/static color (default=990) HINT: lower value result in HIGHER priority!
"effects" :
{
"paths" :
[
"/opt/hyperion/effects"
]
},
// "bootsequence" :
// {
// "color" : [0,0,0],
// "effect" : "Rainbow swirl fast",
// "duration_ms" : 3000,
// "priority" : 990
// },
/// The configuration of the Json/Proto forwarder. Forward messages to multiple instances of Hyperion on same and/or other hosts
/// 'proto' is mostly used for video streams and 'json' for effects
/// * proto : Proto server adress and port of your target. Syntax:[IP:PORT] -> ["127.0.0.1:19447"] or more instances to forward ["127.0.0.1:19447","192.168.0.24:19449"]
/// * json : Json server adress and port of your target. Syntax:[IP:PORT] -> ["127.0.0.1:19446"] or more instances to forward ["127.0.0.1:19446","192.168.0.24:19448"]
/// HINT: If you redirect to "127.0.0.1" (localhost) you could start a second hyperion with another device/led config!
/// Be sure your client(s) is/are listening on the configured ports. The second Hyperion (if used) also needs to be configured! (HyperCon -> External -> Json Server/Proto Server)
// "forwarder" :
// {
// "proto" : ["127.0.0.1:19447"],
// "json" : ["127.0.0.1:19446"]
// },
/// The configuration for the frame-grabber, contains the following items:
/// * width : The width of the grabbed frames [pixels]
/// * height : The height of the grabbed frames [pixels]
/// * frequency_Hz : The frequency of the frame grab [Hz]
/// * priority : The priority of the frame-gabber (Default=900) HINT: lower value result in HIGHER priority!
/// * ATTENTION : Power-of-Two resolution is not supported and leads to unexpected behaviour!
// "framegrabber" :
// {
// "width" : 80,
// "height" : 45,
// "frequency_Hz" : 10.0,
// "priority" : 900
// },
/// The configuration of the Kodi connection used to enable and disable the frame-grabber. Contains the following fields:
/// * xbmcAddress : The IP address of the Kodi-host
/// * xbmcTcpPort : The TCP-port of the Kodi-server
/// * grabVideo : Flag indicating that the frame-grabber is on(true) during video playback
/// * grabPictures : Flag indicating that the frame-grabber is on(true) during picture show
/// * grabAudio : Flag indicating that the frame-grabber is on(true) during audio playback
/// * grabMenu : Flag indicating that the frame-grabber is on(true) at the Kodi menu
/// * grabScreensaver : Flag indicating that the frame-grabber is on(true) when Kodi is on screensaver
/// * enable3DDetection : Flag indicating that the frame-grabber should switch to a 3D compatible modus if a 3D video is playing
"xbmcVideoChecker" :
{
"xbmcAddress" : "192.168.178.31",
"xbmcTcpPort" : 19444,
"grabVideo" : true,
"grabPictures" : true,
"grabAudio" : true,
"grabMenu" : true,
"grabScreensaver" : true,
"enable3DDetection" : true
},
/// The configuration of the Json server which enables the json remote interface
/// * port : Port at which the json server is started
"jsonServer" :
{
"port" : 19444
},
/// The configuration of the Proto server which enables the protobuffer remote interface
/// * port : Port at which the protobuffer server is started
"protoServer" :
{
"port" : 19445
},
/// The configuration of the boblight server which enables the boblight remote interface
/// * port : Port at which the boblight server is started
/// * priority: Priority of the boblight server (Default=900) HINT: lower value result in HIGHER priority!
// "boblightServer" :
// {
// "port" : 19333,
// "priority" : 900
// },
/// Configuration for the embedded V4L2 grabber
/// * device : V4L2 Device to use [default="/dev/video0"]
/// * input : V4L2 input to use [default=0]
/// * standard : Video standard (no-change/PAL/NTSC) [default="no-change"]
/// * width : V4L2 width to set [default=-1]
/// * height : V4L2 height to set [default=-1]
/// * frameDecimation : Frame decimation factor [default=2]
/// * sizeDecimation : Size decimation factor [default=8]
/// * priority : Hyperion priority channel [default=800]
/// * mode : 3D mode to use 2D/3DSBS/3DTAB (note: no autodetection) [default="2D"]
/// * cropLeft : Cropping from the left [default=0]
/// * cropRight : Cropping from the right [default=0]
/// * cropTop : Cropping from the top [default=0]
/// * cropBottom : Cropping from the bottom [default=0]
/// * redSignalThreshold : Signal threshold for the red channel between 0.0 and 1.0 [default=0.0]
/// * greenSignalThreshold : Signal threshold for the green channel between 0.0 and 1.0 [default=0.0]
/// * blueSignalThreshold : Signal threshold for the blue channel between 0.0 and 1.0 [default=0.0]
// "grabber-v4l2" :
// {
// "device" : "/dev/video0",
// "input" : 0,
// "standard" : "no-change",
// "width" : -1,
// "height" : -1,
// "frameDecimation" : 2,
// "sizeDecimation" : 8,
// "priority" : 800,
// "mode" : "2D",
// "cropLeft" : 0,
// "cropRight" : 0,
// "cropTop" : 0,
// "cropBottom" : 0,
// "redSignalThreshold" : 0.0,
// "greenSignalThreshold" : 0.0,
// "blueSignalThreshold" : 0.0
// },
/// The configuration for each individual led. This contains the specification of the area
/// averaged of an input image for each led to determine its color. Each item in the list
/// contains the following fields:
/// * index: The index of the led. This determines its location in the string of leds; zero
/// being the first led.
/// * hscan: The fractional part of the image along the horizontal used for the averaging
/// (minimum and maximum inclusive)
/// * vscan: The fractional part of the image along the vertical used for the averaging
/// (minimum and maximum inclusive)
"leds" :
[
{
"index" : 0,
"hscan" : { "minimum" : 0.0000, "maximum" : 0.0500 },
"vscan" : { "minimum" : 0.0000, "maximum" : 0.0800 }
},
{
"index" : 1,
"hscan" : { "minimum" : 0.0000, "maximum" : 0.0500 },
"vscan" : { "minimum" : 0.5000, "maximum" : 1.0000 }
},
{
"index" : 2,
"hscan" : { "minimum" : 0.0000, "maximum" : 0.0500 },
"vscan" : { "minimum" : 0.0000, "maximum" : 0.5000 }
}
],
"endOfJson" : "endOfJson"
}
Config-Datei Rechts
Alles anzeigen
// Automatically generated configuration file for 'Hyperion daemon'
// Generated by: HyperCon (The Hyperion deamon configuration file builder)
// Created with HyperCon V1.00.1 (15.03.2016)
{
/// Device configuration contains the following fields:
/// * 'name' : The user friendly name of the device (only used for display purposes)
/// * 'type' : The type of the device or leds (known types for now are
/// -------------SPI---------------, APA102, WS2801, P9813, LPD6803, LPD8806, -------------PWM---------------, WS2812b, WS281x (no 12b), ------------OTHER-------------, PhilipsHUE, AtmoOrb, PiBlaster, ThinkerForge, UDP, SEDU, TPM2, USBASP-WS2801, USBASP-WS2812, ----------3rd PARTY------------, Adalight, AdalightAPA102, AmbiLed, Atmo, Lightberry, Lightpack, Multi-Lightpack, Paintpack, Test, None)
/// * [device type specific configuration]
/// * 'colorOrder' : The order of the color bytes ('rgb', 'rbg', 'bgr', etc.).
///
/// * 'Specific of Philips Hue:
/// * 'username' : The name of user registred on the Philips Hue Bridge
/// * 'switchOffOnBlack': Define if Hue light switch off when black is detected
/// * 'transitiontime' : Set the time of transition between color of Hue light
"device" :
{
"name" : "MyPi",
"type" : "piblaster",
"output" : "/dev/pi-blaster",
"assignment" : "r g b"
},
/// Color manipulation configuration used to tune the output colors to specific surroundings.
/// The configuration contains a list of color-transforms. Each transform contains the
/// following fields:
/// * 'id' : The unique identifier of the color transformation (eg 'device_1') /// * 'leds' : The indices (or index ranges) of the leds to which this color transform applies
/// (eg '0-5, 9, 11, 12-17'). The indices are zero based. /// * 'hsv' : The manipulation in the Hue-Saturation-Value color domain with the following
/// tuning parameters:
/// - 'saturationGain' The gain adjustement of the saturation
/// - 'valueGain' The gain adjustement of the value
/// * 'red'/'green'/'blue' : The manipulation in the Red-Green-Blue color domain with the
/// following tuning parameters for each channel:
/// - 'threshold' The minimum required input value for the channel to be on
/// (else zero)
/// - 'gamma' The gamma-curve correction factor
/// - 'blacklevel' The lowest possible value (when the channel is black)
/// - 'whitelevel' The highest possible value (when the channel is white)
///
/// Next to the list with color transforms there is also a smoothing option.
/// * 'smoothing' : Smoothing of the colors in the time-domain with the following tuning
/// parameters:
/// - 'type' The type of smoothing algorithm ('linear' or 'none')
/// - 'time_ms' The time constant for smoothing algorithm in milliseconds
/// - 'updateFrequency' The update frequency of the leds in Hz
/// - 'updateDelay' The delay of the output to leds (in periods of smoothing)
"color" :
{
"transform" :
[
{
"id" : "default",
"leds" : "*",
"hsv" :
{
"saturationGain" : 1.0000,
"valueGain" : 1.0000
},
"red" :
{
"threshold" : 0.0000,
"gamma" : 1.0000,
"blacklevel" : 0.0000,
"whitelevel" : 1.0000
},
"green" :
{
"threshold" : 0.0000,
"gamma" : 1.0000,
"blacklevel" : 0.0000,
"whitelevel" : 1.0000
},
"blue" :
{
"threshold" : 0.0000,
"gamma" : 1.0000,
"blacklevel" : 0.0000,
"whitelevel" : 1.0000
}
}
],
"smoothing" :
{
"type" : "linear",
"time_ms" : 300,
"updateFrequency" : 20.0000,
"updateDelay" : 0
}
},
/// The black border configuration, contains the following items:
/// * enable : true if the detector should be activated
/// * threshold : Value below which a pixel is regarded as black (value between 0.0 and 1.0)
/// * unknownFrameCnt : Number of frames without any detection before the border is set to 0 (default 600)
/// * borderFrameCnt : Number of frames before a consistent detected border gets set (default 50)
/// * maxInconsistentCnt : Number of inconsistent frames that are ignored before a new border gets a chance to proof consistency
/// * blurRemoveCnt : Number of pixels that get removed from the detected border to cut away blur (default 1)
/// * mode : Border detection mode (values=default,classic,osd)
"blackborderdetector" :
{
"enable" : true,
"threshold" : 0.11,
"unknownFrameCnt" : 600,
"borderFrameCnt" : 50,
"maxInconsistentCnt" : 10,
"blurRemoveCnt" : 1,
"mode" : "default"
},
/// The configuration of the effect engine, contains the following items:
/// * paths : An array with absolute location(s) of directories with effects
/// * color : Set static color after boot -> set effect to "" (empty) and input the values [R,G,B] and set duration_ms NOT to 0 (use 1) instead
/// * effect : The effect selected as 'boot sequence'
/// * duration_ms : The duration of the selected effect (0=endless)
/// * priority : The priority of the selected effect/static color (default=990) HINT: lower value result in HIGHER priority!
"effects" :
{
"paths" :
[
"/opt/hyperion/effects"
]
},
// "bootsequence" :
// {
// "color" : [0,0,0],
// "effect" : "Rainbow swirl fast",
// "duration_ms" : 3000,
// "priority" : 990
// },
/// The configuration of the Json/Proto forwarder. Forward messages to multiple instances of Hyperion on same and/or other hosts
/// 'proto' is mostly used for video streams and 'json' for effects
/// * proto : Proto server adress and port of your target. Syntax:[IP:PORT] -> ["127.0.0.1:19447"] or more instances to forward ["127.0.0.1:19447","192.168.0.24:19449"]
/// * json : Json server adress and port of your target. Syntax:[IP:PORT] -> ["127.0.0.1:19446"] or more instances to forward ["127.0.0.1:19446","192.168.0.24:19448"]
/// HINT: If you redirect to "127.0.0.1" (localhost) you could start a second hyperion with another device/led config!
/// Be sure your client(s) is/are listening on the configured ports. The second Hyperion (if used) also needs to be configured! (HyperCon -> External -> Json Server/Proto Server)
// "forwarder" :
// {
// "proto" : ["127.0.0.1:19447"],
// "json" : ["127.0.0.1:19446"]
// },
/// The configuration for the frame-grabber, contains the following items:
/// * width : The width of the grabbed frames [pixels]
/// * height : The height of the grabbed frames [pixels]
/// * frequency_Hz : The frequency of the frame grab [Hz]
/// * priority : The priority of the frame-gabber (Default=900) HINT: lower value result in HIGHER priority!
/// * ATTENTION : Power-of-Two resolution is not supported and leads to unexpected behaviour!
// "framegrabber" :
// {
// "width" : 1080,
// "height" : 1090
// "frequency_Hz" : 10.0,
// "priority" : 100
// },
/// The configuration of the Kodi connection used to enable and disable the frame-grabber. Contains the following fields:
/// * xbmcAddress : The IP address of the Kodi-host
/// * xbmcTcpPort : The TCP-port of the Kodi-server
/// * grabVideo : Flag indicating that the frame-grabber is on(true) during video playback
/// * grabPictures : Flag indicating that the frame-grabber is on(true) during picture show
/// * grabAudio : Flag indicating that the frame-grabber is on(true) during audio playback
/// * grabMenu : Flag indicating that the frame-grabber is on(true) at the Kodi menu
/// * grabScreensaver : Flag indicating that the frame-grabber is on(true) when Kodi is on screensaver
/// * enable3DDetection : Flag indicating that the frame-grabber should switch to a 3D compatible modus if a 3D video is playing
"xbmcVideoChecker" :
{
"xbmcAddress" : "192.168.178.31",
"xbmcTcpPort" : 19444,
"grabVideo" : true,
"grabPictures" : true,
"grabAudio" : true,
"grabMenu" : true,
"grabScreensaver" : true,
"enable3DDetection" : true
},
/// The configuration of the Json server which enables the json remote interface
/// * port : Port at which the json server is started
"jsonServer" :
{
"port" : 19447
},
/// The configuration of the Proto server which enables the protobuffer remote interface
/// * port : Port at which the protobuffer server is started
"protoServer" :
{
"port" : 19449
},
/// The configuration of the boblight server which enables the boblight remote interface
/// * port : Port at which the boblight server is started
/// * priority: Priority of the boblight server (Default=900) HINT: lower value result in HIGHER priority!
// "boblightServer" :
// {
// "port" : 19333,
// "priority" : 900
// },
/// Configuration for the embedded V4L2 grabber
/// * device : V4L2 Device to use [default="/dev/video0"]
/// * input : V4L2 input to use [default=0]
/// * standard : Video standard (no-change/PAL/NTSC) [default="no-change"]
/// * width : V4L2 width to set [default=-1]
/// * height : V4L2 height to set [default=-1]
/// * frameDecimation : Frame decimation factor [default=2]
/// * sizeDecimation : Size decimation factor [default=8]
/// * priority : Hyperion priority channel [default=800]
/// * mode : 3D mode to use 2D/3DSBS/3DTAB (note: no autodetection) [default="2D"]
/// * cropLeft : Cropping from the left [default=0]
/// * cropRight : Cropping from the right [default=0]
/// * cropTop : Cropping from the top [default=0]
/// * cropBottom : Cropping from the bottom [default=0]
/// * redSignalThreshold : Signal threshold for the red channel between 0.0 and 1.0 [default=0.0]
/// * greenSignalThreshold : Signal threshold for the green channel between 0.0 and 1.0 [default=0.0]
/// * blueSignalThreshold : Signal threshold for the blue channel between 0.0 and 1.0 [default=0.0]
// "grabber-v4l2" :
// {
// "device" : "/dev/video0",
// "input" : 0,
// "standard" : "no-change",
// "width" : -1,
// "height" : -1,
// "frameDecimation" : 2,
// "sizeDecimation" : 8,
// "priority" : 800,
// "mode" : "2D",
// "cropLeft" : 0,
// "cropRight" : 0,
// "cropTop" : 0,
// "cropBottom" : 0,
// "redSignalThreshold" : 0.0,
// "greenSignalThreshold" : 0.0,
// "blueSignalThreshold" : 0.0
// },
/// The configuration for each individual led. This contains the specification of the area
/// averaged of an input image for each led to determine its color. Each item in the list
/// contains the following fields:
/// * index: The index of the led. This determines its location in the string of leds; zero
/// being the first led.
/// * hscan: The fractional part of the image along the horizontal used for the averaging
/// (minimum and maximum inclusive)
/// * vscan: The fractional part of the image along the vertical used for the averaging
/// (minimum and maximum inclusive)
"leds" :
[
{
"index" : 0,
"hscan" : { "minimum" : 0.9500, "maximum" : 1.0000 },
"vscan" : { "minimum" : 0.0000, "maximum" : 0.0800 }
},
{
"index" : 1,
"hscan" : { "minimum" : 0.9500, "maximum" : 1.0000 },
"vscan" : { "minimum" : 0.0000, "maximum" : 0.5000 }
},
{
"index" : 2,
"hscan" : { "minimum" : 0.9500, "maximum" : 1.0000 },
"vscan" : { "minimum" : 0.5000, "maximum" : 1.0000 }
}
],
"endOfJson" : "endOfJson"
}
Code vom Switcher
Alles anzeigen
# switchHyperionSource configurations file
#
##
#
NORM="PAL"
# hyperion configurations
HYPERION_CONFIG="Kodi left"
HYPERION_JSON="19446 19444"
# boblight/enigmalight (Enigma2 Receiver GUI)
WEBIFACE_IP=
REMOTE_CONTROL_COMMAND=
NORM="PAL"
# hyperion configurations
HYPERION_CONFIG="Kodi right"
HYPERION_JSON="19448 19450"
# boblight/enigmalight (Enigma2 Receiver GUI)
WEBIFACE_IP=
REMOTE_CONTROL_COMMAND=
Alles anzeigen
Ich weis langsam echt nicht mehr weiter, wo der Fehler liegen könnte. Außerdem muss ich immer erst die Left manuell starten, sonst habe ich bei Right einen XBMC Connection error (0).
Wenn jemand einen Tipp hat, einfach raus! Ich bin für jede Hilfe echt dankbar!
Mfg
TPmodding,
ja und folgendes Image(heute gebaut und ungetestet) müsste auf dem RPi3 laufen.
OpenELEC-RPi2.arm-8.0-devel-20160320133028-#0319-g0026734.tar
raspbastler,
ich kann mal per Teamviewer drüberschauen?
.bismarck
danke! wieder milhouse bild nutzen? oder das normale?
Ja klar habe das ganze System nochmal aufgesetzt!
Automatisch zusammengefügt:
Ab wann können sie denn?
TPmodding,
das Image aus meinem letzten Beitrag ist ein Milhouse-Build.
raspbastler,
Bis Mittwoch nur am Vormittag. Ab Donnerstag wäre der Nachmittag verfügbar. Zugangsdaten bitte per PM.
.bismarck
Okay ich werde es nochmal probieren, wenn ich es nicht schaffen sollte, melde ich mich bei Ihnen.
Danke schonmal
MFG
Nunja, was soll ich sagen, ich habe es nun endlich FAST hinbekommen, ich habe jetzt ein zweiseitiges Ambilight mit normalen 5050 Stripes. Dank nun 6 Transistoren die den Stripe schalten. Das Ambilight läuft sehr smooth ohne Ruckler und das auf einem Pi 1 B WOW:)! Mein größtest Problem ist, dass ich den Pi-Blaster nur in einer sehr alten Version besitze, deshalb könnte mir jmd. den Kompelierten Pi-Blaster zu verfügung stellen? Das wäre genial! Denn ich bekomme den sog. Pi-Blaster nicht in den Autostart. Und der Swichter glaube ich lädt nicht gleich alles in den Autostart?!? Ich gucke morgen nochmal, denn die Nacht bricht langsam an.
Danke schon mal im Voraus!
Mfg
Du hast noch kein Benutzerkonto auf unserer Seite? Registriere dich kostenlos und nimm an unserer Community teil!