|
Replies:
15
-
Pages:
2
[
1
2
| Next
]
-
Last Post:
22 Nov 24, 10:01
Last Post By: davidekholm
|
Threads:
[
Previous
|
Next
]
|
|
Posts:
72
Registered:
16-Apr-2008
|
|
|
|
Updates, every time I have to go into jalbum.ini
Posted:
10 Aug 22, 15:31
|
|
|
|
Every time I update jalbum I need to go into jalbum.ini to update the virtual machine parameters.
And every time I forget that ...
This is what I use now
Virtual Machine Parameters=-Xms256M -Xmx8000M ...
I have plenty of RAM (32 GB) , and without increasing this format the default I get Out of Java heap errors on large albums (some photos I work with are many large file panorama's).
Is there a better way to preserve these settings?
Hans
|
|
|
Posts:
3,922
Registered:
18-Oct-2002
|
|
|
|
Re: Updates, every time I have to go into jalbum.ini
Posted:
10 Aug 22, 16:02
in response to: hanso
|
|
|
|
Unfortunately not (Installer design, not ours), but I've bumped these memory settings to 8000M for upcoming versions now.
|
|
|
Posts:
8,222
Registered:
31-Jan-2006
|
|
|
|
Re: Updates, every time I have to go into jalbum.ini
Posted:
10 Aug 22, 16:05
in response to: davidekholm
|
|
|
Unfortunately not (Installer design, not ours), but I've bumped these memory settings to 8000M for upcoming versions now.
Will that cause problems for users who have only 8GB of RAM to start with?
ETA: I think I've already answered my own question - I bumped the value beyond the RAM my PC has, and it seems to be fine. |
|
|
Posts:
3,922
Registered:
18-Oct-2002
|
|
|
|
Re: Updates, every time I have to go into jalbum.ini
Posted:
10 Aug 22, 16:19
in response to: JeffTucker
|
|
|
Unfortunately not (Installer design, not ours), but I've bumped these memory settings to 8000M for upcoming versions now.
Will that cause problems for users who have only 8GB of RAM to start with?
No, it's a max setting not a min setting. The historical reason for not going higher is that we also want to catch memory leaks early. Bumping up the max value may hide such leaks, but as image sizes increase, so does the need to bump the max setting.
ETA: I think I've already answered my own question - I bumped the value beyond the RAM my PC has, and it seems to be fine.
Edited by: davidekholm on 10 Aug 2022, 16:19 |
|
|
Posts:
8,222
Registered:
31-Jan-2006
|
|
|
|
Re: Updates, every time I have to go into jalbum.ini
Posted:
10 Aug 22, 16:20
in response to: davidekholm
|
|
|
|
I have some dim recollection of a time when setting it too high would prevent the VM from launching. Probably back in the Pleistocene Era.
|
|
|
Posts:
3,922
Registered:
18-Oct-2002
|
|
|
|
Re: Updates, every time I have to go into jalbum.ini
Posted:
10 Aug 22, 16:20
in response to: JeffTucker
|
|
|
I have some dim recollection of a time when setting it too high would prevent the VM from launching. Probably back in the Pleistocene Era.
Yes, that was also one historical reason for being conservative with the max setting. |
|
|
Posts:
177
Registered:
18-Jun-2010
|
|
|
|
Re: Updates, every time I have to go into jalbum.ini
Posted:
17 Nov 24, 12:53
in response to: hanso
|
|
|
I'm reviving this old thread because I sometimes need to run two instances of jAlbum in parallel (see also this thread ). So, for that, I modify jalbum.ini and at the next update, my modifications are erased 
Wouldn't it be possible to have in the config directory a partial jalbum.ini containing only customized entries, that would take precedence over the jalbum.ini in the installation directory? In my case, something like:
[Application]
Single Instance=no
By doing it this way, user modifications such as Single Instance or JVM settings would be preserved when an update occurs 
I am a former Java developer, I used the Properties class that allowed to read/write .ini files and that had a fallback mechanism to use default entries. Isn't it possible to implement an equivalent in the jAlbum code? |
|
|
Posts:
3,922
Registered:
18-Oct-2002
|
|
|
|
Re: Updates, every time I have to go into jalbum.ini
Posted:
17 Nov 24, 16:44
in response to: phil44
|
|
|
|
I can look into whether there is a way. This mechanism is managed by the launcher code, which isn't java and isn't developed by us. It's developed by AdvancedInstaller.com
|
|
|
Posts:
824
Registered:
13-Apr-2006
|
|
|
|
Re: Updates, every time I have to go into jalbum.ini
Posted:
17 Nov 24, 19:10
in response to: phil44
|
|
|
I'm reviving this old thread because I sometimes need to run two instances of jAlbum in parallel (see also this thread ). So, for that, I modify jalbum.ini and at the next update, my modifications are erased
I copy that. This is one of the other most bad things about jAlbum. I don't know any other application which erases settings during an update or even reinstall.
Cheers, Markus |
|
|
Posts:
3,955
Registered:
4-Aug-2006
|
|
|
|
Re: Updates, every time I have to go into jalbum.ini
Posted:
17 Nov 24, 21:23
in response to: MarkusD
|
|
|
|
I'm probably missing something but since the original thread in 2017 jAlbum can now make albums in background mode. Doesn't that solve the original problem?
|
|
|
Posts:
177
Registered:
18-Jun-2010
|
|
|
|
Re: Updates, every time I have to go into jalbum.ini
Posted:
18 Nov 24, 10:36
in response to: RobM
|
|
|
I'm probably missing something but since the original thread in 2017 jAlbum can now make albums in background mode. Doesn't that solve the original problem?
It's not a problem about albums making. For this, I think that increasing the memory and the number of threads is more efficient than using two instances of jAlbum.
What I need to do is to compare and/or modify 2 albums (or 2 different versions of an album), with a complex tree structure. If it was just about the hierarchy of folders or image files, it could have been done with two explorer windows side-by-side, but to manage metadata (titles, comments, etc.), there is nothing better than two jAlbum windows open simultaneously side-by-side |
|
|
Posts:
3,955
Registered:
4-Aug-2006
|
|
|
|
Re: Updates, every time I have to go into jalbum.ini
Posted:
18 Nov 24, 11:54
in response to: phil44
|
|
|
I'm probably missing something but since the original thread in 2017 jAlbum can now make albums in background mode. Doesn't that solve the original problem?
It's not a problem about albums making. For this, I think that increasing the memory and the number of threads is more efficient than using two instances of jAlbum.
What I need to do is to compare and/or modify 2 albums (or 2 different versions of an album), with a complex tree structure. If it was just about the hierarchy of folders or image files, it could have been done with two explorer windows side-by-side, but to manage metadata (titles, comments, etc.), there is nothing better than two jAlbum windows open simultaneously side-by-side
It sounds very laborious, wouldn’t it be easier to make a text file with the contents of each project and then compare the text files for differences. An external tool should be able to create the files. |
|
|
Posts:
177
Registered:
18-Jun-2010
|
|
|
|
Re: Updates, every time I have to go into jalbum.ini
Posted:
18 Nov 24, 19:40
in response to: RobM
|
|
|
I'm probably missing something but since the original thread in 2017 jAlbum can now make albums in background mode. Doesn't that solve the original problem?
It's not a problem about albums making. For this, I think that increasing the memory and the number of threads is more efficient than using two instances of jAlbum.
What I need to do is to compare and/or modify 2 albums (or 2 different versions of an album), with a complex tree structure. If it was just about the hierarchy of folders or image files, it could have been done with two explorer windows side-by-side, but to manage metadata (titles, comments, etc.), there is nothing better than two jAlbum windows open simultaneously side-by-side
It sounds very laborious, wouldn’t it be easier to make a text file with the contents of each project and then compare the text files for differences. An external tool should be able to create the files.
It's not all that laborious. I agree that an external tool could compare two projects and give the differences, probably in text form. But what to do with that? Inspect each difference and go to the appropriate project to move an image from one directory to another, copy an image with its title and comment from one project to another, or copy the comment of an image to another project???
For me, it is more convenient and efficient to have two instances of jAlbum side-by-side. I find image comparisons more intuitive visually, rather than deciphering a list of file differences. That's just my opinion |
|
|
Posts:
824
Registered:
13-Apr-2006
|
|
|
|
Re: Updates, every time I have to go into jalbum.ini
Posted:
18 Nov 24, 19:50
in response to: phil44
|
|
|
It's not all that laborious. ...
I totally agree with that. Running two instances of JA makes some things much easier. Comparing (with „WinMerge“) two (or even three) text-files (.jap files for example), is of course another way to compare different settings of different projects. But it is not so easy to find out what all these variable names are good for. Cheers, Markus |
|
|
Posts:
177
Registered:
18-Jun-2010
|
|
|
|
Re: Updates, every time I have to go into jalbum.ini
Posted:
21 Nov 24, 11:00
in response to: davidekholm
|
|
|
I can look into whether there is a way. This mechanism is managed by the launcher code, which isn't java and isn't developed by us. It's developed by AdvancedInstaller.com
Technical stuff: I don't know their product, but I have anyway found this page on StackOverflow, particularly the 2nd paragraph, which might be relevant to solve this problem. I hope this can help... |
|
|
|
Legend
|
|
Forum admins
|
|
Helpful Answer
|
|
Correct Answer
|
|
