search

ohsewon / test

0 stars 0 forks source link

[GUI Tool] pipeviz is not compatible with tensor_* filters. #343

Open ohsewon opened 5 years ago

ohsewon commented 5 years ago

Issue by myungjoo-ham Thursday Jul 26, 2018 at 08:11 GMT Originally opened as https://github.sec.samsung.net/STAR/nnstreamer/issues/343

If we add tensorconverter (other tensor* filters are not tested) into a pipeviz ( https://github.com/virinext/pipeviz ) gstreamer pipeline, we soon get:

mzx@kohaku:/source/AutoDrv/pipeviz$ ./pipeviz  --gst-plugin-path ../NNStreamer/build/gst/tensor_converter/:../NNStreamer/build/gst/tensor_filter/:../NNStreamer/build/gst/tensor_decoder/
failed to get the current screen resources
QXcbConnection: XCB error: 170 (Unknown), sequence: 163, resource id: 90, major code: 146 (Unknown), minor code: 20
Segmentation fault (core dumped)
mzx@kohaku:/source/AutoDrv/pipeviz$
ohsewon commented 5 years ago

Comment by git-bot-sec Thursday Jul 26, 2018 at 08:11 GMT

:octocat: cibot: Thank you for posting issue #343. The person in charge will reply soon.

ohsewon commented 5 years ago

Comment by jinhyuck83-park Wednesday Aug 08, 2018 at 10:55 GMT

this segmentation fault is caused because there is no data GstTensor_Filter_Framework *fw in gst_tensor_filter_property_process function. in case of nnstreamer filter example(working), example app loads tensorflow-lite model, and use filter with tensorflow-lite but pipeviz, there is no steps to load which nnframework sub-plugin filter use . so I think there are two possible cadidates to use pipeviz with our nnstreamer.

case 1. Make own complete filter that loads specific nnstreamer data model. Pros : no need to modify pipeviz Cons: have to make every filters with every nnframework

case 2. Modify pipeviz that allows filter could load nnframework and load data model. Pros: no need to make every filters that suits for every specific nnframework(tensorflow, tensorflow-lite,caffe ...) Cons: need to modify pipeviz and don't know it would really works