Posts by Marciano

Hello vpeter,

I've tried to install this addon with this build.

It's for odroid C2 64 bit kernel with 32 bit libs.

Installation went fine but httpd won´t start.

I you have some time can you pls make a build for this?

Thanks!

Quote from Luddi

Hello and thank you awiouy for this plugin.
I had similiar problems to HelpMeSpotify getting it to work with a USB soundcard. I'm on LE8, milhouse build from 10.02.2017 on a raspi 2 with a miniDSP 2x4HD.
'amixer' showed "amixer: Mixer attach default error: No such file or directory". The problem was that the soundcard was recognized as card 1 not card 0 and executing amixer without the specification of the device with the '-c 1' flag resulted in this error. I fixed this by making the USB device the default in /storage/.config/asound.conf :

Code

pcm.!default {
    type hw
    card m2x4HD
}
ctl.!default {
    type hw
    card m2x4HD
}

The name of the card is found out with 'aplay -L'. For me the output containes lines like this: "sysdefault:CARD=m2x4HD". So the card name is 'm2x4HD'.

Now I tested the connect server and worked out the correct parameters by starting it from the command line. The working command for me was

Code

./spotify-connect-web --key /storage/.kodi/userdata/addon_data/service.spotify-connect-web/spotify_appkey.key --playback_device sys
default:CARD=m2x4HD --mixer_device_index 0 --mixer 'miniDSP 2x4HD ' -u myusername -p mypassword

The name of the mixer is obtained by the output of 'amixer'. The other parameters were chosen like descriped in the projects repo.
By inspecting 'journalctl -u service.spotify-connect-web' I noticed that the passed name of the mixer 'miniDSP 2x4HD ' was truncated to 'miniDSP'. Also notice the trailing space in the name. Thanks miniDSP.... Spaces in names never bring any luck.
I followed the passing of the argument through the sources. The truncation happens at the calling of spotify-connect-web in bin/spotify-connect-web.start. Changing it in the following way made it work correctly:

Code

...
[ "$scw_b" == "-" ] && scw_b=""
[ "$scw_b" ] && scw_b="-b $scw_b"
#[ "$scw_m" ] && scw_m="-m $scw_m"
[ "$scw_p" ] && [ "$scw_u" ] && scw_p="-p $scw_p" && scw_u="-u $scw_u"


cd "$ADDON_DIR"
./spotify-connect-web $scw_b \
                      -c "$ADDON_HOME/credentials.json" \
                      -k "$ADDON_HOME/spotify_appkey.key" \
                      -m "$scw_m" \
                      -n "$HOSTNAME" \
                      -o "$scw_o" \
                      $scw_p \
                      $scw_u \
                      --mixer_device_index "$index"

Display More

I guess there is a more clever way to do this which preserves your check if $scw_m is specified. I don't need it for now. Maybe this is something for the next update.
Also the integration of the "--dbrange " option in the gui would be nice. Thanks.

I hope this helps people with the same issues.

Display More

How long does ot take to get a spotify app key?

I send a request a couple of days ago but still nothing...

Quote from Philos

Ah, thanks a lot! That's not a surprise, since most solutions end up with an Arduino. The second issue is software: Do you use Hyperion, and if yes, how did you install and configure it?

Yes i use hyperion from the LE repo.

You need a config file that you can create with hypercon.

You can download hypercon from the offical hyperion site.

Once you created a config file you have to copy you config to /storage/.kodi/userdata/addon_data/service.hyperion and reboot.

That's all good luck!

Quote from Philos

Well, how did you manage this? Did you connect the stripe directly to the C2 as shown in the wiki? Or did you use an additional Arduino?

Direct connection did not work for me and I could not find a workaround to do so. So how did you solve that?

I did it with an arduino

Quote from lrusak

don't do this.

copy the systemd service file, rename it, enable it, and start it

Code

cp /storage/.kodi/addons/service.hyperion/system.d/service.hyperion.service /storage/.config/system.d/service.hyperion2.service
nano /storage/.config/system.d/service.hyperion2.service

change the path to your second hyperion config

Code

systemctl enable service.hyperion2.service
systemctl start service.hyperion2.service

Thanks this works perfectly!

Cheers!

Hi Guys,

I'm running LibreELEC 7.1.1 on my odroid c2 with hyperion installed.

I have 2 hyperion.config.json that i want to start at boot, hyperion.config.json and hyperion.config2.json.
hyperion.config.json is for my ws2801 ledstripes and hyperion.config2.json is for my hue lamps.

I know it is possible to start 2 different config files.
From the commandline i can manually start hyperion.config2.json but i want this config to start after a reboot now only hyperion.config.json is start at boot.
How to achieve that?

And how many grabbers do i have to define in my hue config file cause after a couple of minutes my ledstripes and the hue lamps turn off.
After reboot and manually start hyperion.config2.json from commandline all is good for a couple of minutes.

These are my settings in hyperion.configs.json for my hue lamps:

// Automatically generated configuration file for 'Hyperion daemon'
// Generated by: HyperCon (The Hyperion deamon configuration file builder


{
    /// 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 'ws2801', 'ldp8806',
    ///                  'lpd6803', 'sedu', 'adalight', 'lightpack', 'test' and 'none')
    /// * 'output'     : The output specification depends on selected device. This can for example be the
    ///                  device specifier, device serial number, or the output file name
    /// * 'rate'       : The baudrate of the output to the device
    /// * 'colorOrder' : The order of the color bytes ('rgb', 'rbg', 'bgr', etc.).
    "device" :
    {
        "name"       : "MyOdroidC2",
        "type"       : "philipshue",
        "output"     : "192.168.178.195",
        "username"   : "username",
        "colorOrder" : "rgb",
        "switchOffOnBlack" : true,
        "lightIds"   : [15,17]
    },


    /// 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
    "color" :
{
"channelAdjustment" :
[
{
"id"   : "device2",
"leds" : "15,17",
"pureRed" :
{
"redChannel" : 58,
"greenChannel" : 0,
"blueChannel" : 0
},
"pureGreen" :
{
"redChannel" : 0,
"greenChannel" : 94,
"blueChannel" : 0
},
"pureBlue" :
{
"redChannel" : 0,
"greenChannel" : 0,
"blueChannel" : 15
}
}
],
"temperature" :
[
{
"id"   : "default",
"leds" : "*",
"correctionValues" :
{
"red" : 255,
"green" : 255,
"blue" : 255
}
}
],
"transform" :
[
{
"id"   : "default",
"leds" : "*",
"hsl" :
{
"saturationGain" : 1.2500,
"luminanceGain" : 1.1000,
"luminanceMinimum" : 1.0000
},
"red" :
{
"threshold" : 0.0000,
"gamma"     : 2.5000
},
"green" :
{
"threshold" : 0.0000,
"gamma"     : 2.5000
},
"blue" :
{
"threshold" : 0.0000,
"gamma"     : 2.5000
}
}
],
// SMOOTHING CONFIG
"smoothing" :
{
"type"            : "none",
"time_ms"         : 200,
"updateFrequency" : 30.0000,
"updateDelay"     : 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.1000 },
            "vscan" : { "minimum" : 0.0000, "maximum" : 1.0000 }
        },
        {
            "index" : 1,
            "hscan" : { "minimum" : 0.9000, "maximum" : 1.0000 },
            "vscan" : { "minimum" : 0.0000, "maximum" : 1.0000 }
        }
    ],


    /// 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)
    "blackborderdetector" :
    {
        "enable" : true,
        "threshold" : 0.01
    },


    /// The configuration of the effect engine, contains the following items:
    ///  * paths        : An array with absolute location(s) of directories with effects
    ///  * bootsequence : The effect selected as 'boot sequence'
    "effects" :
    {
        "paths" :
        [
            "/storage/.kodi/addons/service.hyperion/effects"
        ]
    },


    "bootsequence" :
    {
        "effect" : "Rainbow swirl fast",
        "duration_ms" : 4000
    },


    ///  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]


       "amlgrabber" : 
   {
      "width" : 64,
      "height" : 64,
      "frequency_Hz" : 5.0,
      "priority" : 799
   },










    /// The configuration of the XBMC connection used to enable and disable the frame-grabber. Contains the following fields:
    ///  * xbmcAddress       : The IP address of the XBMC-host
    ///  * xbmcTcpPort       : The TCP-port of the XBMC-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) in the XBMC menu
    ///  * grabScreensaver   : Flag indicating that the frame-grabber is on(true) when XBMC is on screensaver
    ///  * enable3DDetection : Flag indicating that the frame-grabber should switch to a 3D compatible modus if a 3D video is playing


       // KODI CHECK CONFIG
"xbmcVideoChecker" : 
{
"xbmcAddress" : "192.168.178.20",
"xbmcTcpPort" : 9090,
"grabVideo" : true,
"grabPictures" : true,
"grabAudio" : true,
"grabMenu" : true,
"grabPause" : true,
"grabScreensaver" : true,
"enable3DDetection" : false
},


    /// The configuration of the Json server which enables the json remote interface
    ///  * port : Port at which the json server is started
    "jsonServer" :
    {
        "port" : 19446
    },


    /// The configuration of the Proto server which enables the protobuffer remote interface
    ///  * port : Port at which the protobuffer server is started
    "protoServer" :
    {
        "port" : 19447
    },


    /// The configuration of the boblight server which enables the boblight remote interface
    ///  * port : Port at which the boblight server is started
//     "boblightServer" :
//     {
//         "port" : 19333
//     },


    "endOfJson" : "endOfJson"
}

Quote from wrxtasy

Actually the answer should be YES, smooth 23.976fps video playback is still a WIP for all AML LE Kodi Krypton platforms.
You still get the ~41 second video frame upset playing 23.976fps video at a refresh rate of 24Hz. (No Sync playback to display)

Best bet is to turn off Kodi dynamic Refresh switching all together for the time being and use a Kodi GUI of 1080p60Hz if this glitch upsets you.

Sync Playback to display has to disable Passthrough Audio because Audio has to be converted to PCM and then sped up or slowed down to match the fps of the source video content. You will notice this at the start of video playback sometimes when the Pitch of the Audio changes up/down as A/V Sync does its thing.

Thanks for clarify wrxtasy!

I hope i the next alpha build this bug will be fixed.

Do maybe now progress is of this bug?

Quote from DaVu

No.

Get us a full debug log.

Be sure, that your TV switches to 24p as well. If the TV isn't 24p capable then there won't be no switch and you will get stuttering playback.

Also get us some screenshots from your video settings and from the video settings the OSD provides.

To what setting is your deinterlace option set? Make sure it's set to "auto" if you play locally stored movie files. deinterlace should only be used for Live-TV.

I will get you a full debug log and screenshots from my video settings tomorrow i just at home from work.

My TV is capable of switching to 24p and my deinterlace option is off and greyed in videos settings while playing video i just can't select to "auto".

In videoplayer accelaration settings i've set

mpeg2 --> always
mp4 --> always
h264 --always

Thanks

Quote from DaVu

Wrong.

That has nothing to do with 24p playback. Therefore you should enable the "change refreshrate to match video" setting. "Sync Playback to display" is needed if the audio is not in sync with the video. So those settings aren't related to each other.
[hr]

Yes. And I guess there will never be. Because the audio has to be synced to the video as well. That's kind of a default setting. So there's no ac3 for Live-TV.

There was a forum thread at forum.kodi.tv where fernetmenta mentioned this. But I can't find it at the moment.

Thanks for the info.

But i have "change refreshrate to match video" enabled and i have a stuttering playing 24p videos.

Is this still a WIP?

Thanks!

Quote from lrusak

that is working as intended.

You cannot have passthrough when "sync playback to display" is enabled.

How about 23.976 smooth play back when sync playback to display disabled?
It is stuttering when disabled.

Hi,

I'm using the newsest build v7.90.009 alpha on my odroid C2 and when i select sync playback to display videoplayer use not passtrough but i only get multichannel.
When playin a movie with DTS HD MA i get multichannel.
What are the right settings to get passthrough with sync playback to display on?
If i not select sync playback to display i videoplayback is stuttering..And with Live TV i only get multichannel even when sync playback to display is off
Is ac3 5.1 with Live TV still WIP?

Thanks guys!

About Amazon Prime on odroid C2 more info Here

Quote from danmed

Thank you for replying..

Do you know if it was OK in any of the releases for the Odroid C2? If i can downgrade.. run the tool and then upgrade again i'd be happy for now..

Don't know for sure but i tought none of them was ok to run the tool.

I have the same.

In the previous build the same issue.

Quote from lrusak

some yes

Cab you tell me wich build is working cause the latest build kodi is crashing.

Are the builds for odroid C2 working to play games?

I found this somewhere but didn't try it.

Maybe is this what your looking for i think it is Jarvis.

Quote from awiouy

Thank you for confirming MDB post-processing works (with the preview release, right?)

selectserie and matchserie in mdb.config.xml are the defaults provided with WebGrab+Plus.
I do not know what the right settings are.

Maybe someone on this thread can help you out.
Otherwise, you will certainly find help on the WebGrab+Plus forum, or at the WebGrab+Plus configurator thread.

Sorry didn't try the preview release yet i wil try this tomorrow.
If i update to the new preview release do i have to copy the mdb file again to the mdb folder?

I will check the webgrab+Plus forum thanks!