default templates?

[story]

Jerm,
Most audio progs (from Finale to DP4 to Peak...) seem to have an explicit default setup template (window displays and positions, color styles, mixer instrument definitions, default metronome/tempo/etc.) Metro6, on the other hand, seems to remember the display layout of the last saved file (and _not_ remember mixer settings, etc.)

I've found that I can get the effect I want very nicely by setting up for a project and saving, then LOCKing the Metro file. Now I can drag that file to the OSX dock, and click on it to get a really complete initial configuration. I can save various configurations in that way, and take my choice. And as long as it's finder-LOCKed, I can't accidentally overwrite it.
And "Save as..." create my actual project.

I think this (or an analogous) way of making setup templates should be in the documentation!

But...
[1] If I DO accidentally try to save, I get an ugly internal error message, apparently from the OSX file system code, rather than a polite and informative message from Metro6 itself.
[2] It would be nice if there were a "new template" or "new initial configuration" choice in Metro's File menu...perhaps as a submenu on New...

[Jerm]

Yes. I agree this would be nice. I will look into it.

[Scoot]

I require a template that installs the fastest current CPU available and brings me unlimited coffees.

Can ya manage that before xmas Jerm?


scoot

[Jerm]

In Metro version 6.1.0.5 if a file is locked (permissions Error) when opened, Metro will require a save as when saved. This fixes the problem described in this topic.

It would be nice to have (also) a save as template command which would simply save and then lock the saved file.

[Jerm]

Story,

If you do not fix your email address from story@well.com to one that is valid and receives mail by tomorrow I will be forced to delete you from this forum.

[story]

Seems like just the right solution!

(btw, I spent the last few days on DP4; Metro is already much better laid out than that; I was very familiar with Performer (1.0 through 6.03) and liked it a lot, but they've really messed up the user interface; DP's handling of stereo audio tracks and instrument plug-ins is _much_ worse than Metro's. There isn't even a single place one can go to open a window by type...some of them are in one menu, some in another. Ugly. I wish I'd saved the money for the expensive upgrade, and upgraded to the full version of Metro instead!)

((Sorry about the email bounces. I think the Well may have misconfigured their procmail last week. Also, I've added {sales,info}.sagantech.biz and admin@sagantech.com to the spam assassin whitelist on my account there, just in case that was it. --Lee))

[Jerm]

One more bounce like this and I will have to remove you:

From: Mail Delivery System <Mailer-Daemon@jose.farciert.net>
Date: Mon Nov 24, 2003 1:09:05 AM US/Eastern
To: admin@sagantech.com
Subject: Mail delivery failed: returning message to sender

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

story@well.com
SMTP error from remote mailer after RCPT TO:<story@well.com>:
host smtp.well.com [xxx.xx.xxx.x]: <story@well.com>... mail from server rejected - see <http://www.abuse.net/sbl.phtml?IP=64.191.10.22>

[Scoot]

That's interesting you posted that Jerm.

I get exactly the same message on my forum site from one person....and it's only started happening in the last few days.
When I email them directly it doesn't come back to me though....so the email address is valid.

I am assuming somewhere between my forum site and their email address is some kind of spam remover or block.

What I don't know is how to fix the problem.
Is it because the individual is emailing others through the forums email addresses?


scoot.

[Jerm]

Scoot,

No. I think this problem is due to the fact that other users on your particular server are using the server to spam. The only way the receiver can stop the abusive spam is to block all email from that particular server.

In order to stop this problem, the web hosting provider needs to stop the spammer and then contact the server with the block in place to have them remove it.

I think story's problem may be fixed because I did not get a error email when you posted yours. At least I hope so.