recent posts recent posts - RSS

7/25/2017
Topic:
How to Uninstall in Windows 10

Andy Schmidt
Andy Schmidt
Administrator
Posts: 69
Andy Schmidt
Andy Schmidt
Administrator
Posts: 69
Topic: How to Uninstall in Windows 10
I can't delete Studioline in W10 at settings. Please help me to remove. How? Greetings René Gosens


You didn't specify what error message or other issue specifically prevented you from accessing the Windows 10 settings. The following screen shot shows how to initiate the uninstall in Windows 10:


edited by Andy Schmidt on 7/25/2017
edited by Andy Schmidt on 7/25/2017
6/26/2017
Topic:
Where to Store Images and StudioLine Data?

Andy Schmidt
Andy Schmidt
Administrator
Posts: 69
When I have a photo in my external photo folder I can catalogue it in StudioLine Photo.
What do I have to do when I edit the photo and store it in the same or other folder, using a new name for the edited photo (the original stays where it was)

If you edit a photo and save it back under the same name, then the pointer in the Image Archive will still be valid. You can use the context menu (right-click) on that one photo in the Image Archive to "Refresh" that "Original" (which, in reality, is no longer the original at all).


If, however, you instead create a new file under a different name and/or location, then that truly IS a DIFFERENT file. You would have to catalogue that one as a new file in StudioLine. (However, in StudioLine you'd be able to "drag" all the metadata (= descriptors) and/or any edits from the "old" image to "new" image, if you like)


If an external image NO LONGER is found at the "old" location (because that picture, or the entire folder, or the entire disk was moved), THEN StudioLine will prompt for the new location at some future time, when it needs to access the original file for any purpose.



My suggestion is that you do NOT use a scheme where you constantly move catalogued ("external") files to new Windows folders or rename them in Window - the chance of error is just too big. Moving files/folders should only be done on the very rare occasion when you change hardware/drives and/or you completely reorganize where your data is stored.
6/25/2017
Topic:
Where to Store Images and StudioLine Data?

Andy Schmidt
Andy Schmidt
Administrator
Posts: 69
But what is the best way to install the program and store my images?
I want to have the use of StudioLine Photo for searching, but to keep the possibility to open the photos in Photoshop and other applications, too.
So I'm considering installing the program on an external drive, have the Image Archive on that same drive, but to store my photos on an internal (or different external) drive (effectively duplicating the images in their own folder but also have them in the Image Archive). Perhaps this is not needed?

In general, the most important thing to plan is your backup strategy for your photos (= the entire “StudioLine Data” folder and subfolders). Wherever you place them, make sure you have the means to back up the content of that device on a regular basis.

Any recommendations would require for us to first have a good understanding YOUR workflow and what YOUR application for photos is. For now let me describe a generic scenario that would make sensible use of the features of StudioLine – and mention a few alternatives, just in case one sounds more like your workflow than others:

  • And event photographer comes back with hundreds of photos. He/she creates a new folder for those images, presets certain descriptive data such as copyright, event geo-location, event theme, etc. Then the photos are loaded into that folder.
    Next, any out-of-focus or other unusable photos are eliminated.

  • Some of the best or most relevant photos are ranked and undergo image edits/enhancements within StudioLine.

  • More specific descriptions are added to identify any objects/subjects.

  • A select series of images is exported for subsequent online publishing. An export “job” with reusable settings is used, that will automatically downsize the images for web usage, will convert them to high-compression (=small file size) JPEG and will add a logo watermark to protect your rights. You can choose to include some descriptor fields as text on the images; you can choose to reveal their geodata, etc.

  • In weeks to come, there might be requests from organizers or participants to acquire some of the photos. You could export those photos as originals and then spend time in PhotoShop to retouch them, remove blemishes, etc. before “selling” them.
  • On occasion there might be a request from one of several magazines that you've worked with in the past. They might have specific picture output requirements (as to file format, file size, no watermark, etc.) The various magazines could have distinct reusable Export jobs that satisfy the distinct requirements for each.

  • A few times a year you might be invited asked to present a slide show/talk. Again you could have a standard output job that prepares an ad-hoc selection of images in size, format and resolution for whatever projector device.

As far as working with images in PhotoShop, that depends on your typical work flow. If there is a small number of “top shots” that undergo extensive “post processing” work in PhotoShop after each “shoot”, then you could consider completing that work first, before ever loading that batch of photos into StudioLine for archival.

If, on the other hand, your typical work involves searching individual or groups of images in your archive sometime later, by whatever criteria, then it might make sense to take that selection of found images, possibly use the built-in abilities of StudioLine as much as possible to align and crop images, and then use the Export function to output those images in the file format and file size for the particular the production “job” to a work folder on Windows. From there you could still use PhotoShop as needed.

Keep in mind that any edits you do in StudioLine are fully reversible at any time, in full or in part, even years later – while edits you perform in other tools will be final. If technology advances in years to come, people sometimes regret having permanently altered the true original – or are confused by some other program having left numerous duplicates of pictures in various sizes, formats and states of edit – increasing the risk that the “wrong” one (the TRUE original) being accidentally deleted!

Yes, there is also the ability to add PhotoShop as a program shortcut to StudioLine, so that you can select images in StudioLine and then launch PhotoShop directly for a particular image. Saving the image in PhotoShop will then permanently update the underlying original photo – if that’s why you want.

As far as location of the StudioLine Data Folder – that’s mostly a matter of how BIG your archive is vs. the space on your available drives. Clearly, if your Windows workstation has a number of suitable internal drives, possible arranged in a RAID array to protect against single disk failure, with 70 or 80% of empty space to allow for a few years of growth – then there’s no reason to use external drives. By the time you run out of space, it might be time to replace the entire workstation.

On the other hand, if your disks are already 60 or 70% full, then you might be better suited with a set of (at least two) huge external drives – the second drive is used by an automated/scheduled Backup application!

The final consideration is whether to allow the Windows files to be “copied” into StudioLine or whether to use “catalogue” (but not copy) them:

  • If you use the “copy” option, then your originals will be maintained inside of the StudioLine Data folder – and once loaded, the source files can be deleted from your Windows folders to make room for more. The advantage is that all your originals are kept in the one StudioLine data folder and no external application will move files around where they might end up getting accidentally deleted years later from some arbitrary subfolder.
    But it also means, you’ll use the StudioLine workflow to “export” images for particular applications as needed.

  • If you do NOT use the “copy” option, then StudioLine will just remember the location of those original images on your Windows folders at the time of loading (and create a screen resolution “cache” version for previewing in StudioLine) – but it has no true best-resolution version of its own (it will always refer to the “external” original as needed). Your work with StudioLine itself will NOT be any different from the “copy” option, but only as long as the original files/folders are not moved, deleted, altered, renamed… in any way.
    This leaves the real potential actions you take in Windows with other applications will cause your data to go “out of synch” with StudioLine (although there IS the ability to “resynch” individual files or entire folders, after they were moved to a different parent folder or disk).

Fortunately, you can change your mind later – “external” images appear with a special status icon and can still be “copied” later – and, of course, “internal” (copied) images can be exported into regular Windows folders at any time…
6/21/2017
Topic:
"Backup" Options for StudioLine Basic

kemartin3
kemartin3
Posts: 2
Thanks for the reply Andy. Excellent insight.
6/20/2017
Topic:
"Backup" Options for StudioLine Basic

Andy Schmidt
Andy Schmidt
Administrator
Posts: 69
Dear Kevin,

Some sort of automated/scheduled Windows or third party backup strategy of the StudioLine Data folder is the most practical option. If ever there was any kind of catastrophic (hardware) loss, you would need to restore the StudioLine Data folder, in it's entirety, to some replacement disk and/or PC. This will recover not only the photos and metadata, but also settings and other information gathered up in StudioLine.

Using the StudioLine Export function is ideally suited when merging multiple StudioLine instances from different installations or computers, or as an "ad-hoc" backup of pictures and metadata. Since it cannot be scheduled automatically, it probably is not as useful as a regular backup. Also, the export will not preserve other settings, objects, etc. you may have created.
On the plus side, the export allows for selective restore and allows for the files to be used by other graphics applications. It could certainly come in handy as a supplement to a full folder backup.
edited by Andy Schmidt on 6/20/2017
6/20/2017
Topic:
"Backup" Options for StudioLine Basic

kemartin3
kemartin3
Posts: 2
Hi all. I just installed Basic on my PC. In the manual i see references to exporting pictures, but nothing about backups. To do a "backup" it would seem that I have three choices

1. Add the StudioLine data directory I specified during install to a Windows 10 library, and let Windows File History take backups.
2. With StudioLine not running, use native Windows commands to copy the SL data directory to another drive.
3. Use the SL export function against the highest level in the SL image archive tree ("\") and tell it to include "all subfolders of the folder '\'".

Is there another option I am not seeing? Is there a big "gotcha" for any of the above that I haven't realized? Thoughts on which is the best, most reliable option.

Thanks for your help.
Kevin
5/13/2017
Topic:
Dynamic menu uses wrong link

uligrepel
uligrepel
Posts: 3
Hi Andy, hi Jürgen,

thanks for the answers, and thanks for the emailed support as well. I was able to help myself even before entering this forum, since in my case there's just four JavaScript files involved that have to be fixed (four menues, one JavaScript file for each of them). I'd only have to take care that after changing a menu (and republishing it) I'd have to manually change default.htm into index.html again, that's why I said I wouldn't want to have to do that manually...

If you're creating a fix in the next version of StudioLine I'm just fine.

("Publishing to DVD (i.e. file) only" - the menus should work on the locally published preview as well as on a real server, where, as you point out correctly, it's the server's job to actually fix a URL from "www.whatever.com/pagename" first to "www.whatever.com/pagename/" (for "pagename" is a directory and not an existing to-be-delivered file), and then (internally only) fixing it to "www.whatever.com/pagename/default.htm" or whatever is configured to be the server's default filename. And "default.htm" is Microsoft's IS preferred name, while "index.html" is Apache's preferred name...)
5/12/2017
Topic:
Dynamic menu uses wrong link

Andy Schmidt
Andy Schmidt
Administrator
Posts: 69
Andy Schmidt
Andy Schmidt
Administrator
Posts: 69
Topic: Dynamic menu uses wrong link
This issue is specific to publishing the HTML pages to file (DVD) rather than through FTP. In this case, the name for the default document, "default.htm", carried over from the standard publishing profile for this project, instead of from the specific publishing profile.
As a temporary work-around one could temporarily change the setting of the standard publishing profile from "default.htm" to "index.html" prior to publishing the DVD.
Note: The "default document" name in a Publishing Profile is meant to match the setting on the target web server. It would be the job of the web server, to redirect a request for a non-specific HTTP URL (one lacking an explicit document name), to a fully qualified URL (which includes one of the default document names configured for that web site).
As is apparent, the concept of a "default document" doesn't apply with offline viewing, as no web server is involved. In this context, file system requests are always explicitly for a particular file, no matter the name (default.htm, index.html, or any other).

edited by Andy Schmidt on 5/12/2017
edited by Andy Schmidt on 5/12/2017
5/12/2017
Topic:
Is there a Command Line Argument To Exit?

Wayne Hewitt
Wayne Hewitt
Posts: 34
Good point Andy
5/12/2017
Topic:
Is there a Command Line Argument To Exit?

Andy Schmidt
Andy Schmidt
Administrator
Posts: 69
Hi Wayne,

a proper Windows backup application should be using VSS (Volume Shadow Copy Service) to handle open file backups. Rather than adding work-arounds to a Windows application (like StudioLine), the proper solution would be to use backup software that employs the features provided by the operating system.

Even if you were to devise some script that submits a "Close" to the StudioLine application window, there would always be the chance that some sort of "prompt" or other currently open modal window might get in way at times.
edited by Andy Schmidt on 5/12/2017
5/12/2017
Topic:
Is there a Command Line Argument To Exit?

Wayne Hewitt
Wayne Hewitt
Posts: 34
StudioLine Photo Classic 4:
My backup software runs in the middle of the night. If I happen to have left StudioLine open it will not properly back up the database. The backup software is fairly sophisticated and can issue Command Line commands. Is there a Command Line argument which would cause a running copy of StudioLine to Exit?

I am sure I could find a way to create a script which changes focus to the proper window (if it is open) and so to speak presses File Exit but I am hoping for a cleaner solution.
edited by wdhewitt on 5/12/2017
5/11/2017
Topic:
Dynamic menu uses wrong link

uligrepel
uligrepel
Posts: 3
Hi Jürgen,

the web site I'm working on is, for privacy reasons, actually not going to be published on the internet, it is meant for DVD distribution to about 100 people.

I added a new publishing profile, since I wanted a clean start in the publishing directory which I grabbed from the StudioLine directories to burn on the DVDs. So yes, every page was published. Actually, the pages themselves are just fine, just the generated JavaScript files for the menues were using the wrong default page name (default.htm instead of index.html) - otherwise I'd have had to manually update >300 individual files.

All original publishing profiles were specified as using "index.html" as well. 10 years ago the menus worked just fine as well.

And yes, the menu uses "link to page", not "link to URL".

When adding new entries to the menu I was asked whether I'd want to update the menues to the new technology which was faster. I said "yes". Maybe this caused the problem.

I also have to admit that I was not using the most current version of StudioLine - it was about 1.5 years old already. Didn't want to change a winning team when under time pressure for the DVD production... ;-). However, creating yet another fresh publishing profile and updating the menu and republishing everything didn't switch the generated dynamic menu JavaScript files from using "default.htm" when "index.html" would've been correct.

I'm going to send some screenshots and some files via email.

Greetings

Uli
5/10/2017
Topic:
Dynamic menu uses wrong link

Jürgen Wolz
Jürgen Wolz
Posts: 15
Hi,

We tested dynamic menues and were unable to reproduce the behaviour you reported.
On a page that has the problem, please right click the object to which the dynamic menu is attached, select "Dynamic Menu" / "Apply Dynamic Menu". For the menu, that will be displayed as "Applied dynamic menu", choose "Edit Menu".
Please select an affected menu item from the menu structure list and send us a screenshot to the support mail address: Support_D@studioline.net
Please do also check the link type: type "Link to page" will be refreshed to the profiles default document when the active publishing profile was updated, whereas type "Link to URL" is static and won't be updated by the system. Those will need manual updates in the Dynamic menu.
Please make also sure that the page with the incorrect link in the dynamic menu is also newly published.
In case the wrong link will not be corrected after updating the menu and publishing the page, please do send us the URL of the page that has the problem to above support email address, so we would be able to inspect.


Best Regards

H&M System Software GmbH
Jürgen Wolz
5/9/2017
Topic:
%%xxx%% Variables For Use in Descriptors

Andy Schmidt
Andy Schmidt
Administrator
Posts: 69
Hi Wayne,
Wayne Hewitt wrote:
name of the actual folder within the Image Archive

If you export a folder structure, then the name of each subfolder will be maintained in the exported folder structure.

Otherwise you could use "Descriptor Defaults" each time you create a new folder, to populate a certain user descriptor with a unique value for each folder. For already existing folders, you could globally assign all images in that folder that same user descriptor.

Best Regards,
Andy
5/9/2017
Topic:
SLStarter funktioniert nicht mehr

Jürgen Wolz
Jürgen Wolz
Posts: 15
Hallo,

bitte senden Sie uns die von StudioLine erzeugten Log-Dateien (als gezippte Datei) an die Support-Adresse: Support_D@studioline.net
Sie finden die letzten Log-Dateien (Dateien mit Dateierweiterung ".log") im StudioLine Datenverzeichnis, Unterverzeichnis \Log, z.B. c:\StudioLine Photo Classic 4\Log o.ä.
Alternativ können Log-Dateien auch in Verzeichnis C:\ProgramData\H&M System Software\StudioLine Photo Classic 4 gespeichert sein.
Falls Sie .dmp Dump Dateien finden sollten, senden Sie uns diese ebenfalls.



Bitte stellen Sie auch sicher, dass das neueste Update installiert ist. Laden Sie sicherheitshalber noch einmal das Installationsprogramm von der StudioLine Website und installieren Sie erneut: http://www.studioline.net/DE/download/download-photo-classic/default.htm

Mit freundlichen Grüßen

H&M System Software GmbH
Jürgen Wolz
5/8/2017
Topic:
SLStarter funktioniert nicht mehr

Bernd
Bernd
Posts: 1
Bei Aufruf von Studioline Photo Classic 4 (SLPhoto.exe) erscheint die Fehlermeldung "SLStarter funktioniert nicht mehr" mit der Option "Debuggen" und "Programm schließen.Das Programm wird beendet ohne Möglichkeit etwas auszuwählen oder aufzurufen. Was ist zu tun ?
5/8/2017
Topic:
Dynamic menu uses wrong link

uligrepel
uligrepel
Posts: 3
Hi,

long time, no hear... I've recently been working on a long time (i.e. 10 years old) statical web site project again, and I'm having trouble with dynamic menus: 10 years ago they just worked fine, now, probably after conversion to the new dynamic menu technique, they don't. The link is always referring to the page with the filename "default.htm", even though the publication profile (and the rendered page) is using the filename "index.html".

With Chrome, clicking on a menu link gives you the local equivalent of a 404 page, with Edge, you'll get a white page only.

Fixing the link from "default.htm" to "index.html" in the generated JavaScript files (e.g. slm_388.js) helps, however I'd prefer not having to do that manually ;-)
edited by uligrepel on 08.05.2017
5/5/2017
Topic:
DESCRIPTOR EXPORT

Andy Schmidt
Andy Schmidt
Administrator
Posts: 69
Andy Schmidt
Andy Schmidt
Administrator
Posts: 69
Topic: DESCRIPTOR EXPORT
Wayne Hewitt wrote:
unable to convince the Search and Replace to find any argument with a " (double quote) which I had used for 'Inch', or a - (hyphen).

I was able to search and replace for double quote and dash/hyphen without problems - filling out the screen below. Assuming you are using a recent version, I suggest you carefully inspect the screen right before clicking "OK" to be certain that the CORRECT Descriptor (still) appears in "Include" and "Search In" is correct:
Otherwise, you'll have to use the Service Request feature so that you can submit your diagnostic logs to our support team for inspection.

PS:Wayne Hewitt wrote:
I betray my age
Oh... if your earliest memories are MSDOS, then I have you beat by one complete generation of computing technology :-)
edited by Andy Schmidt on 5/5/2017
5/4/2017
Topic:
DESCRIPTOR EXPORT

Wayne Hewitt
Wayne Hewitt
Posts: 34
Andy
I betray my age smile
As a point of interest, Win10 seems to substitute an underscore for invalid characters.

While correcting the few invalid characters I had used I was unable to convince the Search and Replace to find any argument with a " (double quote) which I had used for 'Inch', or a - (hyphen). Is there a delimeter to tell this function that I am specifying the " or - as text?
5/4/2017
Topic:
DESCRIPTOR EXPORT

Andy Schmidt
Andy Schmidt
Administrator
Posts: 69
Andy Schmidt
Andy Schmidt
Administrator
Posts: 69
Topic: DESCRIPTOR EXPORT
Hi Wayne,

you definitely deserve extra credit for thinking out of the box. Of course, it requires someone with a bit of a technical mind, but more importantly, it assumes that the descriptors you are working with are almost strictly alphabetic. Many commonly used special characters that might appear in location or MANY corporate names (such as the Ampersand, or the Forward Slash in dates) would break your scheme. Double-quotes might even appear in names, such as:

Andrew "Stonewall" Jackson

or

Welcome to the "Big Apple"!

Here the list of special characters that would be rejected by Windows if you were to include them in your concatenated file names:
  • < (less than)
  • > (greater than)
  • : (colon)
  • " (double quote)
  • / (forward slash)
  • \ (backslash)
  • | (vertical bar or pipe)
  • ? (question mark)
  • * (asterisk)

Either way, thank for sharing this and I'm glad it happened to work out in your particular case. Maybe it can help another user with a similar limited dataset, but the content restrictions prevent it from being generally applicable.

Best Regards,
Andy




Powered by Jitbit Forum 8.3.8.0 © 2006-2013 Jitbit Software