George

Photo station and Moments (DSM 6.2)

Recommended Posts

Question...

 

Does Photo station and the new Moments (6.2 beta at the moment) leave the photos you drop into folders where you dropped them (and leave original name in place), and simply build up a file name / tag index in the back ground.

 

Remember some MP3 systems in the pat on another platform actually moved the mp3's which messed things up badly.

 

looking at feature, with my more disk space and consolidating everything onto my new XPenology this is a package I'm keen on exploring,

 

G

Share this post


Link to post
Share on other sites

In Photo Station, pictures are left in the folders you have created. File names are not changed, as far as I know. At least not in the instance I have installed.

 

I recommend you use DSM account system if Photo Station will be used only by DSM users. Else use the Photo Station account system. Spend time configuring Photo Station properly. It can be tricky and not all that user friendly but when it works it works.

Share this post


Link to post
Share on other sites

I have a question as well about photo station.

I do have drive package so the folders are sync all over my PCs. I really love that feature of the synology. My quostion is can I link somehow photo station to the drive's pictures folder? I do not want to have same photos in two different applications. It will consume 2x of my storage.

Share this post


Link to post
Share on other sites
On 11/13/2018 at 2:15 PM, apejovic said:

Creating a team folder and put a symbolic link? Did you try that?

Hello apejovic,

I haven't tried that. But I did it now and it works. Thank you very much.

Edited by buozinis

Share this post


Link to post
Share on other sites

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.  

Share this post


Link to post
Share on other sites

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.

Edited by mcdull

Share this post


Link to post
Share on other sites
On 11/18/2018 at 8:29 PM, mcdull said:

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.

Thanks for the insight!  I haven't had any subjects detected except "children" ever, but I only got an Intel Xpenology this summer, and before that I was using an ARM Synology which didn't support subject detection.  So the timeline makes sense.

 

Anyway, I just downgraded my package to https://archive.synology.com/download/Package/spk/SynologyMoments/1.1.2-0511/ and am currently re-indexing, will update with my results!

 

Update: That did the trick!  I now have 28 categories and it's still indexing :)

Edited by cyberwitch

Share this post


Link to post
Share on other sites
9 hours ago, cyberwitch said:

Thanks for the insight!  I haven't had any subjects detected except "children" ever, but I only got an Intel Xpenology this summer, and before that I was using an ARM Synology which didn't support subject detection.  So the timeline makes sense.

 

Anyway, I just downgraded my package to https://archive.synology.com/download/Package/spk/SynologyMoments/1.1.2-0511/ and am currently re-indexing, will update with my results!

 

Update: That did the trick!  I now have 28 categories and it's still indexing :)

Could you share your computer, particularly the cpu info by running..

 

cat /proc/cpuinfo ?

 

Share this post


Link to post
Share on other sites
17 hours ago, mcdull said:

Could you share your computer, particularly the cpu info by running..

 

cat /proc/cpuinfo ?

 

Sure, it's an unmodified HP Proliant N54L with AMD Turion processor:

$ cat /proc/cpuinfo 
processor	: 0
vendor_id	: AuthenticAMD
cpu family	: 16
model		: 6
model name	: AMD Turion(tm) II Neo N54L Dual-Core Processor
stepping	: 3
cpu MHz		: 2200.000
cache size	: 1024 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
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 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow nopl pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt nodeid_msr hw_pstate npt lbrv svm_lock nrip_save
bogomips	: 4392.97
TLB size	: 1024 4K pages
clflush size	: 64
cache_alignment	: 64
address sizes	: 48 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate

processor	: 1
vendor_id	: AuthenticAMD
cpu family	: 16
model		: 6
model name	: AMD Turion(tm) II Neo N54L Dual-Core Processor
stepping	: 3
cpu MHz		: 2200.000
cache size	: 1024 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
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 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow nopl pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt nodeid_msr hw_pstate npt lbrv svm_lock nrip_save
bogomips	: 4392.97
TLB size	: 1024 4K pages
clflush size	: 64
cache_alignment	: 64
address sizes	: 48 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate

Hope this helps others!

Share this post


Link to post
Share on other sites
3 hours ago, cyberwitch said:

Sure, it's an unmodified HP Proliant N54L with AMD Turion processor:

Hope this helps others!

 

 

Make sense, the function is Intel specific.

Share this post


Link to post
Share on other sites

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. 

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now