General StudioLine topics
Basic 4 hangs while loading.
|
bions Posts: 2
12/26/2019
|
In Windows 10 Pro fully up to date, Basic 4, on startup, pops up a message with a progress bar: Loading Image Information / 1 of 551 Files / 0% done. But it just sits there. The Windows Task Manager shows some CPU activity, but nothing seems to move it along. If I stop Basic 4 (click on the red X) the closing message appears, but that too hangs and the app never stops. The only way to stop it is to kill the job in the Task Manager. How can I get past this? Thank you.
|
|
|
0
link
|
|
Andy Schmidt Administrator Posts: 114
12/26/2019
|
Hi,
What's the context? Did this used to work in the past months - and it only started happening today? If so, what has changed in the operating system, hardware config, file/folders, external drives, etc. since it had last worked successfully?
Also, if this is an existing StudioLine Photo Basic installation, what's the specific StudioLine version number?
Or is this the first attempted usage after having downloaded the current version from our web site and installing that?
|
|
|
0
link
|
|
bions Posts: 2
12/27/2019
|
You can close this issue. I had been letting Basic 4 run for only 15 to 20 minutes. Just to see, I let it run overnight, and by morning it had finished. Apparently it takes a lot of time for certain operations. Anyway, I will now exercise more patience.
|
|
|
0
link
|
|
Andy Schmidt Administrator Posts: 114
12/27/2019
|
Thank you for reporting back.
Generally, loading a few hundred images should only take a few minutes; it's something users (incl. myself) do on a regular basis. So there may be other factors in play here - such as the speed and/or connection type to the device where those images were loading from, or whether something unique with these images, metadata, or their path caused StudioLine to wait for some error-handling, retries and timeouts to occur after each photo, etc. Another issued could be the speed and connectivity to the device/path hosting the "StudioLine Data" folder, where the database is kept.
If this were to be a persistent issue, contextual / environmental details and version information would be needed to zero in on whatever causes. StudioLine is also able to generate diagnostic log files, that would help us learn the specific I/O, database or other actions that are atypically slow in your case.
|
|
|
0
link
|