Windows "Encountere...
 
Share:
Notifications
Clear all

31 July 2020 - Comet Registration video tutorial using APP 1.083-beta1 released.

30 July 2020 - APP 1.083-beta1 has been released introducing Comet processing! This 1st beta has comet registration. The stable release will also include special comet integration modes.

9 July 2020 - New and updated video tutorial using APP 1.081: Complete LRGB Tutorial of NGC292, The Small Magellanic Cloud by Christian Sasse (iTelescope.net) and Mabula Haverkamp

2019 September: Astro Pixel Processor and iTelescope.net celebrate a new Partnership!

Windows "Encountered error in module FileDetailListUpdater"  

  RSS

(@gnagy1)
Hydrogen Atom Customer
Joined: 1 year ago
Posts: 2
March 4, 2020 20:33  

Hello. Section 1: Error trying to load light, dark, etc (RAW d810) files. Before the update, it worked fine.

bug

 


ReplyQuote
Topic Tags
(@mabula-admin)
Quasar Admin
Joined: 3 years ago
Posts: 2470
March 4, 2020 21:45  

Hi Grzegorz Nagy @gnagy1,

How are you loading these frames? Are they on an external drive?

I have 2 other customers with the same issue and one of them has confirmed now that he is loading the data from an external drive and his raws on that drive are now corrupt... so his drive is failing.

Feel free to send me a raw so I can test to make sure.

Upload them here:

https://ariesprodstor.astropixelprocessor.com:7001/

login and password : appuser

Make a folder with your name and let me know once uploaded.

Mabula


ReplyQuote
(@mabula-admin)
Quasar Admin
Joined: 3 years ago
Posts: 2470
March 5, 2020 23:21  
Posted by: @gnagy1

Hello. Section 1: Error trying to load light, dark, etc (RAW d810) files. Before the update, it worked fine.

bug

 

Hi  @gnagy1,

I think we have located the source of the problem 😉

The whole file path to your data, probably has a non-standard character like this for example:

E:\Daten\Privat\Bilder\01_Astrofotografie\Objekte\Elefantenrüsselnebel IC1396\20200304_Rothmannsthal_Canon600DaDeb_3_RedCat250mm\Lights_360\

On this file path, this bug is triggered, the reason is the umlaut on the u in "Elefantenrüsselnebel IC1396"

Can you share you filepath so we are 100% sure what we need to do to fix this properly?

Thanks in advance,

Mabula


ReplyQuote
 Henk
(@latour)
Molecular Cloud Customer
Joined: 3 years ago
Posts: 5
March 5, 2020 23:33  

Hallo Mabula,

I have a problem with loading Olympus ORF raw files from an Olympus E-3 camera into APP on a Windows 10 PC. Error message below. (APP 1.077)

I tried it on a Linux Mint box with APP 1.077 where I had no problems.

PC: Windows 10, 32GB, Intel Dual Hexacore, Nvidia graphics card.

 

Selection 031

Many thanks  and regards,

Henk


ReplyQuote
(@mabula-admin)
Quasar Admin
Joined: 3 years ago
Posts: 2470
March 5, 2020 23:35  

Hi Henk @latour,

Thank you for reporting this, I have merged your post, because it is a duplicate to another post with the same problem.

And I think we have located the problem, the problem will be a special character on the file path:

 

The whole file path to your data, probably has a non-standard character like this for example:

E:\Daten\Privat\Bilder\01_Astrofotografie\Objekte\Elefantenrüsselnebel IC1396\20200304_Rothmannsthal_Canon600DaDeb_3_RedCat250mm\Lights_360\

On this file path, this bug is triggered, the reason is the umlaut on the u in "Elefantenrüsselnebel IC1396"

Can you share you filepath so we are 100% sure what we need to do to fix this properly?

Henk, Can you share you filepath so we are 100% sure what we need to do to fix this properly?

Thanks,

Mabula


ReplyQuote
(@gnagy1)
Hydrogen Atom Customer
Joined: 1 year ago
Posts: 2
March 9, 2020 18:14  

Hello. Sorry for the late response. I am using M2 disk on pcie 3.0 x4 bus. Until now, there were no problems with reading or working on these files located on this disk. The previous version of the program is free of this error because I checked. After copying to the 3Tb internal disk, the program loads them correctly from this location. The M2 disk is error free and in excellent condition.I just uploaded the RAW files to the specified server.

EDIT : after copying the files to the internal 3 TB disk, the problem occurs at the moment, I do not understand why now it does not work since a few minutes ago I could. Disk status is excellent.

This post was modified 8 months ago 2 times by Grzegorz Nagy

ReplyQuote
(@vincent-mod)
Quasar Admin
Joined: 3 years ago
Posts: 2453
March 14, 2020 14:13  

Did you check if the filepath is indeed the possible issue? This will be addressed at least.


ReplyQuote
(@mabula-admin)
Quasar Admin
Joined: 3 years ago
Posts: 2470
March 18, 2020 21:21  
Posted by: @gnagy1

Hello. Sorry for the late response. I am using M2 disk on pcie 3.0 x4 bus. Until now, there were no problems with reading or working on these files located on this disk. The previous version of the program is free of this error because I checked. After copying to the 3Tb internal disk, the program loads them correctly from this location. The M2 disk is error free and in excellent condition.I just uploaded the RAW files to the specified server.

EDIT : after copying the files to the internal 3 TB disk, the problem occurs at the moment, I do not understand why now it does not work since a few minutes ago I could. Disk status is excellent.

 

Hallo Mabula,

I have a problem with loading Olympus ORF raw files from an Olympus E-3 camera into APP on a Windows 10 PC. Error message below. (APP 1.077)

I tried it on a Linux Mint box with APP 1.077 where I had no problems.

PC: Windows 10, 32GB, Intel Dual Hexacore, Nvidia graphics card.

Hi @gnagy1, @latour, & @vincent-mod,

The problem has been fixed.

In APP 1.077, loading CR2 & NEF frames is using LibRaw. APP 1.076 and before were using my own raw conversion code. So there is a difference there.

LibRaw code was not able to handle filepaths with non-standard characters like umlaut or chinese characters... My own code was able to process that. I had to fix the filepaths so LibRaw can now understand them correctly, so in APP 1.078 it should all work again.

Mabula


Share: