Download issues (above 2GB?)

[DanH]

@Lindon hmmm, in 20 years of making music I've never encountered this, but you may be right. Running your OS drive close to capacity isn't a great idea

[Lindon]

@DanH take a look at this:

Attention Required! | Cloudflare

(www.scan.co.uk)

[DanH]

@Lindon Yep ran my last Mac Pro off one of those. Always left 10% clear

[d.healey]

Use a directory browser and ask the user where they want the samples installed to.

[DanH]

@d-healey well my idea was to install the link file in the main install so as to avoid people getting confused with multiple installers and the Hise system (which I'm desperately trying not to use)

[Lindon]

@DanH said in Download issues (above 2GB?):

@d-healey well my idea was to install the link file in the main install so as to avoid people getting confused with multiple installers and the Hise system (which I'm desperately trying not to use)

Why? Do you have experience that it doesnt work? I've had thousands of downloads and installs with little or no support calls on them. (well on the install process at least)

[d.healey]

@DanH Are you using expansions?

[d.healey]

@Lindon My experience has been similar. Provide good documentation and you'll get very few support issues regarding the installation procedure.

[DanH]

@d-healey @Lindon yeah people really hate the standard install, @Casey-Kolb came to the same conclusion too.

[d.healey]

@DanH We must sell to different people :p Are you using expansions?

[DanH]

@d-healey not yet but I will be at some stage

[d.healey]

@DanH Ok, my suggestion won't work then because I was thinking you were using expansions. You'll need to do it a little differently and download ch files instead of hr and add the link file manually (through scripting).

[DanH]

@d-healey can the user choose the sample location?

[d.healey]

@DanH Yeah, it's all exactly the same, user chooses the location you download the ch files to there and you create a link file that points to that location.

You can use the File API to create it. Something like this:

local fileName = "Link";

switch (Engine.getOS())
{
    case "LINUX":
        fileName += "Linux";
        break;
    
    case "WIN":
        fileName += "Windows";
        break;
    
    case "OSX":
        fileName += "OSX";
        break;
}

linkFile = linkDir.getChildFile(fileName);

FileSystem.browseForDirectory(FileSystem.Samples, function(dir)
{
   linkFile.writeString(dir.toString(0));
});

You'll need to figure out what the linkDir is using the FileSystem API, starting from the appData folder (in fact it might be the appData folder, I can't remember).

[DanH]

@d-healey

user chooses the location you download the ch files

Can the ch files be downloaded in a compressed format? And then uncompressed into the folder of choice? (I mean in a zip file to avoid downloading each ch file one at a time)

You'll need to figure out what the linkDir is using the FileSystem API, starting from the appData folder (in fact it might be the appData folder, I can't remember).

Do you mean where the link file is stored? Yes it's the appData folder

[d.healey]

@DanH

Can the ch files be downloaded in a compressed format? And then uncompressed into the folder of choice?

Not yet, but Christoph has indicated that he will be adding zip uncompression. For now you just have to download the ch files as they are - these are already compressed from wav.

Do you mean where the link file is stored?

Yes

[DanH]

@d-healey

For now you just have to download the ch files as they are

All 300

[d.healey]

@DanH You're doing something crazy again, I can feel it.

[DanH]

@d-healey It's fine as long as you're here to set me straight....

[d.healey]

@DanH Why 300 sample maps?