Re: Regarding the demo shown at CES 2019

[developers-linux@xxxxxxxxxxxxx]

Hi Ohiwa-san

Thanks for the response.

>In this case, if you are going to participate in the AMM held next month.
>How about telling there?
I understand.
I will ask about it at the AMM held next month.

Regarding the demo(demo3) exhibited at CES2019, will it be exhibited at 
the AMM held next month too?

Regards,
Kikugawa

>Hi Kikugawa-san,
>
>I'm sorry for reply late.
>
>In this case, if you are going to participate in the AMM held next month.
>How about telling there?
>
>BR,
>Toshikazu Oiwa
>
>-----Original Message-----
>From: developers-linux@xxxxxxxxxxxxx [mailto:developers-linux@xxxxxxxxxxxxx] 
>Sent: Tuesday, February 12, 2019 9:43 AM
>To: "wenlong zheng(鄭 文龍)"; 大岩　敏和/TOSHIKAZU OHIWA
>Cc: automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
>Subject: Re:  Regarding the demo shown at CES 2019
>
>Hi Zheng-san,Ohiwa-san
>
>>→Based on server-static.js, just change video_path to pipe file.
>Regarding the above, we have investigated it in details.
>The below is the details. Please tell us what you think about our questions.
>
>■For server-static.js
>We have specified pipe(/storage/video_stream_pipe) as video_path of server-
>static.js, but
>the following error showed up.
>
>[Error details]
>　Error: throttle rate must be a positive number
>　　at new ThrottleGroup (/storage/h264-live-player/node_modules/stream-
>throttle/src/throttle.js:54:15)
>　　at new Throttle (/storage/h264-live-player/node_modules/stream-throttle/
>src/throttle.js:14:17)
>　　at StaticFeed.get_feed (/storage/h264-live-player/lib/static.js:30:34)
>　　at StaticFeed.start_feed (/storage/h264-live-player/lib/_server.js:32:27)
>　　at WebSocket.<anonymous> (/storage/h264-live-player/lib/_server.js:74:14)
>　　at emitTwo (events.js:106:13)
>　　at WebSocket.emit (events.js:194:7)
>　　at Receiver.ontext (/storage/h264-live-player/node_modules/ws/lib/
>WebSocket.js:816:10)
>　　at /storage/h264-live-player/node_modules/ws/lib/Receiver.js:477:18
>　　at /storage/h264-live-player/node_modules/ws/lib/Receiver.js:361:7
>
>[Location of the error]
>　●filename: h264-live-player\lib\static.js
>　　get_feed() {
>　　　var source = this.options.video_path; // source = /storage/
>video_stream_pipe
>
>　　　//throttle for "real time simulation"
>　　　var sourceThrottleRate = Math.floor(fs.statSync(source)['size'] / this.
>options.video_duration);
>　　　console.log("Generate a throttle rate of %s kBps", Math.floor
>(sourceThrottleRate/1024));
>　　　
>　　　var readStream = fs.createReadStream(source);
>　　　readStream = readStream.pipe(new Throttle({rate: sourceThrottleRate})); 
>★ Error!!
>　　　
>　　　console.log("Generate a static feed from ", source);
>　　　return readStream;
>　　}
>
>We have investigated the error by inserting the logging and found that 
>sourceThrottleRate becomes 0 since fs.statSync(source)['size'] became 0. 
>Then this leads to the error.The file size of video_stream_pipe becomes 0.
>
>If it is a specific file (ex. XXX.mp4), the sourceThrottleRate can be 
>calculated by dividing the play time.
>If pipe is specified, we don't think we can get the correct value, and we 
>think this leads to the phenomenon.
>
> [Question 1]
> 　For this phenomenon, how did you resolve it ?
>
> [Question 2]
> 　What value did you specify for sourceThrottleRate ?
>
> [Question 3]
> 　What value did you specify for VideoStreamingParamter setting(*1) of SDL 
>sent from smartphone apps ?
>
> 　(※1) The implementation example
> 　　　　private VideoStreamingParameters mVideoStreamingParameters = new 
>VideoStreamingParameters();
> 　　　　....
> 　　　　....
> 　　　　　mVideoStreamingParameters.setBitrate(512000);
> 　　　　　mVideoStreamingParameters.setDisplayDensity(240);
> 　　　　　mVideoStreamingParameters.setFrameRate(30);
> 　　　　　mVideoStreamingParameters.setInterval(5);
> 　　　　　mVideoStreamingParameters.setFormat(new VideoStreamingFormat
>(VideoStreamingCodec.H264, VideoStreamingProtocol.RAW));
> 　　　　　ImageResolution iImageResolution = new ImageResolution();
> 　　　　　iImageResolution.setResolutionHeight(1920);
> 　　　　　iImageResolution.setResolutionWidth(1080);
> 　　　　　mVideoStreamingParameters.setResolution(iImageResolution);
> 　　　　　
> 　　　　　proxy.startRemoteDisplayStream(getApplicationContext(), 
>TestSDLPresentation.class, mVideoStreamingParameters, false);
> 　　　　....
>　　　　
> [Question 4]
> 　>For the No.2,
> 　>It is using the navigation image from the smartphone by using SDL.
>  
>   Does that mean it is streaming the navigation image sent from smartphone ?
>   What kinds of navi apps did you use in the smartphone ?
>   (Is it open to the public?)
>
> 　Also, regarding the demo at CES 2019, which version of AGL was used for 
>its development ?
>
>Regards,
>Kikugawa
>
>>Hi Kikugawa-san
>>
>> > 　1. Is this done based on the sample code of server-tcp.js ?
>> > 　　 * https://github.com/131/h264-live-player/blob/master/server-tcp.js
>>→Based on server-static.js, just change video_path to pipe file.
>>
>> > 　2. The decode of H.264 is performed inside javascript of 
>>h264-live-player.
>> >       Does that mean it does not use anything like FFmpeg or GStreamer ?
>>→No, It doesn't use ffmpeg or gstreamer. Use boardway like this.
>>   https://github.com/mbebenita/Broadway
>>
>>BR,
>>Zheng
>>
>>On 2019/02/07 16:04, developers-linux@xxxxxxxxxxxxx wrote:
>>> Hi Ohiwa-san
>>> 
>>> I have additional questions.
>>> I'm afraid of asking these kinds of basic questions,
>>> but that is because I don't have much experience with h264-live-player and 
>>> JavaScript.
>>> 
>>> <List of questions>
>>> 　1. Is this done based on the sample code of server-tcp.js ?
>>> 　　 * https://github.com/131/h264-live-player/blob/master/server-tcp.js
>>> 
>>> 　2. The decode of H.264 is performed inside javascript of h264-live-
>>> player.
>>>       Does that mean it does not use anything like FFmpeg or GStreamer ?
>>> 
>>> Regards,
>>> Kikugawa
>>> 
>>>> Hi Ohiwa-san
>>>>
>>>> Thanks for the response.
>>>>
>>>>> This demo uses HTML5 instead of Qt and draws with chromium.
>>>>> Current SDL core on AGL cannot use Qt lib.
>>>>>
>>>>> The video stream output from SDL core is raw H.264 and cannot be played
>>>>> as it is.
>>>>> In this demo, h264-live-player decodes raw H.264 and Javascript's
>>>>> Canvas draws on chromium as PoC.
>>>>
>>>> Thank you for providing various information.
>>>> I will try.
>>>> If I have further questions, I will ask again.
>>>>
>>>> Thank you very much.
>>>>
>>>> Regards,
>>>> Kikugawa
>>>>
>>>>> Hi Kikugawa-san,
>>>>>
>>>>>> For the No.2,
>>>>>> It is using the navigation image from the smartphone by using SDL.
>>>>>> Could you tell me how you achieve it ?
>>>>>
>>>>> This demo uses HTML5 instead of Qt and draws with chromium.
>>>>> Current SDL core on AGL cannot use Qt lib.
>>>>>
>>>>> The video stream output from SDL core is raw H.264 and cannot be played 
>>>>> as
>>>>> it
>>>>> is.
>>>>> In this demo, h264-live-player decodes raw H.264 and Javascript's Canvas
>>>>> draws on chromium as PoC.
>>>>>
>>>>> We cannot post the SDL cord of the demo
>>>>> because we use some binary codes by the demo of this SDL.
>>>>> We're going to post other cords of demo 3.
>>>>>
>>>>> BR,
>>>>> Oiwa
>>>>>
>>>>> -----Original Message-----
>>>>> From: developers-linux@xxxxxxxxxxxxx [mailto:developers-linux@brison-inc.
>>>>> jp]
>>>>> Sent: Tuesday, February 05, 2019 8:46 AM
>>>>> To: 大岩　敏和/TOSHIKAZU OHIWA; automotive-discussions@lists.
>>>>> linuxfoundation.
>>>>> org
>>>>> Subject: RE:  Regarding the demo shown at CES 2019
>>>>>
>>>>> Hello Ohiwa-san,Walt-san,
>>>>>
>>>>> Thanks for the response.
>>>>>
>>>>>> For the No.1,
>>>>>> as Walt-san said, only a few can be posted.
>>>>>> Currently posting in order.
>>>>>
>>>>>> That is a picture of Demo 3. The source code is not available for that 
>>>>>> demo
>>>>>> yet. Some of it has been posted in gerrit. Hopefully one of the demo 3
>>>>>> developers can chime in.
>>>>> I understand.
>>>>>
>>>>>> For the No.2,
>>>>>> It is using the navigation image from the smartphone by using SDL.
>>>>> Could you tell me how you achieve it ?
>>>>>
>>>>> We are currently trying to achieve the video streaming of the navigation
>>>>> image(h.264) written in pipe from SDL core by using WebEngineView(+
>>>>> Gstreamer) and QMediaPlayer of Qt.
>>>>>
>>>>> For the above demo, is it implemented by Qt ?
>>>>> Or is it using something other than Qt ( for instance WaylandSink ) ?
>>>>>
>>>>> ※The R-Car M3 is used in the demo machine.
>>>>>
>>>>>> By the way,
>>>>>> I've seen an article where your company is runnig SDL in AGL.
>>>>>> Are you still continuing now?
>>>>> Yes, we are still doing various things.
>>>>>
>>>>> Regards,
>>>>> Kikugawa
>>>>>
>>>>>> Hello kikugawa-san,
>>>>>>
>>>>>> I reply to your questions.
>>>>>>
>>>>>> For the No.1,
>>>>>> as Walt-san said, only a few can be posted.
>>>>>> Currently posting in order.
>>>>>>
>>>>>> For the No.2,
>>>>>> It is using the navigation image from the smartphone by using SDL.
>>>>>>
>>>>>> By the way,
>>>>>> I've seen an article where your company is runnig SDL in AGL.
>>>>>> Are you still continuing now?
>>>>>>
>>>>>> BR,
>>>>>> Toshikazu Oiwa
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: automotive-discussions-bounces@xxxxxxxxxxxxxxxxxxxxxxxxx [mailto:
>>>>>> automotive-discussions-bounces@xxxxxxxxxxxxxxxxxxxxxxxxx] On Behalf Of
>>>>>> developers-linux@xxxxxxxxxxxxx
>>>>>> Sent: Friday, February 01, 2019 8:18 PM
>>>>>> To: automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
>>>>>> Subject:  Regarding the demo shown at CES 2019
>>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> I'd like to know the details about the demo that was exibited at CES 
>>>>>> 2019(*
>>>>>> 1)
>>>>>> ?
>>>>>> (*1)http://monoist.atmarkit.co.jp/mn/articles/1901/16/news070.html
>>>>>>
>>>>>> I have the following questions. Could you send me the answers for them
>>>>>>  ?
>>>>>>
>>>>>> 1. Is the source of the demo at CES 2019 opened to the public ?
>>>>>>    If it is not yet opened, do you have the plan to make it open to the
>>>>>> public ?
>>>>>>
>>>>>> 2. There is the picture(the 4th) that the navigation and the music 
>>>>>> screen
>>>>>> (Spotify) are both displayed.
>>>>>>    For the navigation image, is it using the navigation image from the
>>>>>> smartphone by using SDL ?
>>>>>>    Or the navigation image is displayed by using Mapbox ?
>>>>>>
>>>>>> Regards,
>>>>>> kikugawa
>>>>>> _______________________________________________
>>>>>> automotive-discussions mailing list
>>>>>> automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
>>>>>> https://lists.linuxfoundation.org/mailman/listinfo/automotive-
>>>>>> discussions
>>> _______________________________________________
>>> automotive-discussions mailing list
>>> automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
>>> https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions
>>> 
_______________________________________________
automotive-discussions mailing list
automotive-discussions@xxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linuxfoundation.org/mailman/listinfo/automotive-discussions