MMM-AssistantMk2 problems when using electron-rebuild

[A Former User]

This post is deleted!

[A Former User]

@yep_dd
I didn’t make it configurable much. But you can modify ‘node_helper.js’ by yourself

var speaker = new Speaker({
channels: 1,
sampleRate: cfgInstance.conversation.audio.sampleRateOut,
});

You can add here ‘device:”hw:1,0”,”. I’ll fix them to be configurable next update.

[yep_DD]

@Sean

cool, works, thank you so much. Would you know where youtube audio is configured? Because that still uses the standard.

[A Former User]

@yep_dd I don’t know about that, sorry. :| I think you should adjust your mixer (alsa? or pulse?)

[yep_DD]

@Sean
correct, works. Modified /usr/share/alsa/alsa.conf for the default sound card and added a “record” for MMM-Hotkey so it wouldn’t use that as default: working just fine.

Just stuttering, the audio output as well as video. Let’s see why… when audio is played through the 3.5mm jack it works fine.

[yep_DD]

@Sean

what is your CPU usage when playing youtube videos and using the google assistent? I am using OpenGL for rendering… but videos and audio via HDMiIseems to stutter

[dvbit]

@yep_dd I am using rpi3b+ sound output via HDMI.no stutter.

[A Former User]

@dvbit Frankly I use mainly Asus Tinker Board. I couldn’t satisfied with performance of RPI3,
anyway, usually, with BT speaker, RPI3 has good enough sound. For video, I think non-HD youtube video can be played enough.

[dvbit]

@sean yes I saw your posts and realized it. Also had a look and thought about getting an asus but finally went for raspb3 for gpio support (at least in my readings it was saying it was suboptimal…)
I might give an AEON with atom (that I have) a ride if more power is needed.

PS: I went through the google sdk to understand current capabilities (especially in my language) and saw the output limitations you mentionned.
I could not find a list of supported features compared to smartphone assitant. do you have any pointer? tx

[A Former User]

@dvbit For screenOutput? At this moment, Nothing. It is experimental stage. Screenoutput is too tight binded with specific hw. By example, original search results of video is not playable. It is assumed to activate app on smartTv. I had to parse static html output to catch youtube Video Id.