mcdull
-
Posts
252 -
Joined
-
Last visited
-
Days Won
4
Everything posted by mcdull
-
If that is the case, it is not a CPU generation problem. And how you set up your box? using Esxi or bare metal?
-
My Bad. The latest version still able to recognize faces. Just that it will not show up until finish the entire database. Subject recognition is still the same as before, only Child being recognized. Photo assistant never returns a result, but it will suggest similar pictures.
-
I cannot edit the previous reply. I found some resources that documented the similar technology being used. http://hyd23.rssing.com/chan-12487997/all_p164.html
-
I have a little bit more detail. In moments version 1.1.2-0511, everything was fine. Face, subject, place, etc. In moments version from 1.2.0-0638, facial recognization and place works fine. In moments version 1.3.0-0691, only place works. I looked in the package file, and suspect the following change may account for the difference. in 1.3.0 Under package\models\concept\detector, there are 5 files. cpu_model.bin cpu_model.xml gpu_model.bin gpu_model.xml model.pb cpu_model.??? were introduced in 1.2.0-0638 (so may explain the break of subject recognition) gpu_model.??? were introduced in 1.3.0-0691 (or 1-2 version earlier that may explain the break of facial detection) My xpenology box is builted under ESXi with E3-1275v2 (sandy bridge), thus, there is NO intel GPU visible to the DSM. However, I have no clue on the xml. Hope there are experts that can help to force software calculation. cpu_model.xml gpu_model.xml
-
After update to Moment 1.3, my box cannot even recognize all faces and subject. Only location. Mine is sandy bridge (E3-1275 v2), hope there are workarounds.
-
Make sense, the function is Intel specific.
-
You will need to ssh to the synology. No root is required.
-
This is what I got from cpuinfo processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 58 model name : Intel(R) Xeon(R) CPU E3-1275 V2 @ 3.50GHz stepping : 9 microcode : 0x20 cpu MHz : 3491.367 cache size : 8192 KB fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx rdtscp lm constant_tsc arch_perfmon nopl xtopology nonstop_tsc pni pclmulqdq ssse3 cx16 pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm arat spec_ctrl ibpb_support fsgsbase tsc_adjust smep bogomips : 7018.21 clflush size : 64 cache_alignment : 64 address sizes : 43 bits physical, 48 bits virtual power management:
-
Can you share your result of the following? cat /proc/cpuinfo Synology DS3615xs should not use E5-2630 specific instruction. When comparing the difference between E3-1275v2 and i3 4130 used in the original Synology DS3615xs, only AVX2 is missing, and AVX2 is missing in the E5 2630v2 as well. The other difference is the Integrated Video, but under ESXi environment, it should not matter if no passthrough action being taken.
-
Could you share your computer, particularly the cpu info by running.. cat /proc/cpuinfo ?
-
Yes, I did fresh install moments and start a completely new vm as 3617xs. Both have the same behavior. It is too weird that a single tag works. "Child" subject always works but not others. I will try FreeBSD v11 x64 again. EDIT: okay.. tested with FreeBSD profile still no go. I even pass through the CPU intel display to the vm.
-
Thanks. I have no clue on it. The 2630v2 and 1275v2 seems to be the same generation of CPU. My mements tagging works until the May 2018 update of the moments app, which introduced a new Intel engine for speeding up the process. Would you also share what kind of VM profile (OS Type) you have set up? I have tried Linux (Other) 64bit and Other OS 64 bit.
-
Are you testing the Moments in ESXi 6.7? Have you passthrough any Display to the vm?
-
Mine will not tag subject "other than" Children. Facial recognition and geotagging works.
-
me 2 having the same issue. My E3 1200v2 cpu would not boot the 918 image with network. I am running 3615 fine but the moments app does not behave correctly because lacking of Intel CV feature in ESXi. I am trying to switch to another image to see if it will fix this one.
-
I have an issue with my set up and synology moments update 1.2.0-0638. In that particular update, the following function being implemented. "Integrated Intel Computer Vision SDK to facilitate image recognition performance on Synology NAS that has Intel processors from x15 series onwards." Since this release, the Synology moments failed to recognize any subjects except "child" category. I suspect that the Intel Computer Vision SDK is not functioning properly in my environment. My DSM is running under ESXi with DS3615xs loader and having E3 1200v2 class of CPU which should be equivalent to the one in DS3615xs. Can you share if you can successfully classify "NEW" photo with latest moments and share your configuration, please?
-
It seems to me that the issue is related to the following update. Version: 1.2.0-0638 (2018-05-24) Integrated Intel Computer Vision SDK to facilitate image recognition performance on Synology NAS that has Intel processors from x15 series onwards. I guess that the synology were not given access to cpu's intel graphic card and thus the SDK does not work at all.
-
Sorry for being sidetracked. I have a problem with Moments. It used to be working good, but in recent month the moments stop classifying photos. I realise the most updated photo being tagged are back in May 2018 (photo taken date). Then I clear the moment db and reindex everything, turns out it only tag one single photo (as child). I have tested to add some more child photo and moments do tag them successfully, but not other categories. Face recognition do work as expected. I am not sure if it is a loader problem or synology problem. Thank you. I am using 1.03b loader and DSM 6.2.1-23824 Update 1 under ESXi 6.7.
-
Hello, My set up is an ESXi with 1.02b firmware. I fleshly install the 6.1.2 and did multiple update. Now I am having an issue that everytime I start the VM (Syno) in will go to recovery mode with different IP. If I click recover and reboot, it will boot fine with my pre-defined IP. The booting virtual disk is set to dependent mode. Any hint?
-
I have done 2 updates on my ESXi box. Both required fresh install. i.e. I need to manually format the first 2 partitions in the data disks and it will then allow me to install the new pat files. Or else the recovery process will kill the DSM. But it is weird that the DSM stop working in around 3 days. Is there anything I can check if I managed to get back to the DSM screen or SSH console? There are some chances that I can get it connected and then the instances will be stable. But new connection cannot be made.
-
Did you lost DSM access at 24/48 hr etc, after boot with this image? I have currently facing this issue. And I need to force reboot everytime to get the box connected again.
-
Some more information (Sorry that I cannot re-edit the original post) ulimit is "unlimited" /volume1/web/17wo$ netstat -ant | awk '{print $6}' | sort | uniq -c | sort -n 1 CLOSE_WAIT 1 Foreign 1 LAST_ACK 1 established) 6 FIN_WAIT1 25 TIME_WAIT 67 LISTEN 144 ESTABLISHED 146 SYN_SENT Connections seems to be very normal.
-
Are there any new time bomb triggered in the 1.02b release? I have been using the loader with the 6.2 on an ESXi box. It will usually runs fine for days and I started to lost contact of the DSM. the port 5000 no longer responses, and I cannot even ssh to the port 22 with putty. But I am quite sure it is not the network blockout as I had a putty connection to the ssh service of the DSM for days and it will continue to work. I also found that the ports (ssh) were occasionally opened. Once I got connected, it will stay connected. I was wonder if I had reached the connection limit of the synology box because of the download station (BT). But the netstat show only a few hundreds connection which should be far from the limit. Edit: More, it responses to ping correctly. Any hint? Thanks.
-
No, you cannot. You need to re-format the volume for a different file system
-
update always result in recovery mode. Need clean install everytime.