Why do wav files work in background sound, but midi files don't?

[Geoffrey]

Using webpage properties in Publisher2000, wav files are audible by visitors
but mid files are not. Only I can hear them. While the tag <bgsound
src="xyz.wav> seems to work perfectly, <bgsound src="xyz.mid"> fails.

Perhaps, in the case of midi files they should be placed in a separate
folder on the site and called out by a link in the "Head" segment, i.e not
using webpage properties, but adding the <bgsound src="music/xyz.mid"
autostart> tag manually.

Does anyone know?

I'll try this anyway.

 

[David Bartosik]

IE may only support a wav file. You can probably google on the bgsound tag. I
myself don't follow media support because I don't use media.
Publisher does not expose the head section, all code fragments are in the
body.

 

[Geoffrey]

Thanks for your reply Dave,
I know Publisher puts code fragments in the body only; that's why I do a lot
of post scripting in the HTML document after Publisher has "saved as
webpage". I just run the HTML page and perform changes in the notepad file
and save. You know... when the page is running on the local browser, click on
"view", then click on "source" and add or amend script then "File save".

I.E. supports almost everything. I think my problem is possibly that a
script must be added to activate the CODEC that supports MIDI files. I'm
still searching for an answer.
--
SPQR

IE may only support a wav file. You can probably google on the bgsound tag. I
myself don't follow media support because I don't use media.
Publisher does not expose the head section, all code fragments are in the
body.
--
David Bartosik - [MSFT MVP]
http://www.publishermvps.com
http://www.davidbartosik.com

Using webpage properties in Publisher2000, wav files are audible by visitors
but mid files are not. Only I can hear them. While the tag <bgsound
src="xyz.wav> seems to work perfectly, <bgsound src="xyz.mid"> fails.

Perhaps, in the case of midi files they should be placed in a separate
folder on the site and called out by a link in the "Head" segment, i.e not
using webpage properties, but adding the <bgsound src="music/xyz.mid"
autostart> tag manually.

Does anyone know?

I'll try this anyway.

 

[DavidF]

Perhaps you could consider converting your file to a format that is
supported in Publisher. That way you won't have to edit your code every time
you make a change on that page, assuming that you ever do figure out how to
use a midi file.

And, FWIW, consider NOT using any background sound. I have read that as many
as 9 out of 10 people will not linger on a page with muzac in the
background. Why take the chance of alienating people once you actually get
them to your site?

DavidF

Thanks for your reply Dave,
I know Publisher puts code fragments in the body only; that's why I do a lot
of post scripting in the HTML document after Publisher has "saved as
webpage". I just run the HTML page and perform changes in the notepad file
and save. You know... when the page is running on the local browser, click on
"view", then click on "source" and add or amend script then "File save".

I.E. supports almost everything. I think my problem is possibly that a
script must be added to activate the CODEC that supports MIDI files. I'm
still searching for an answer.
--
SPQR

IE may only support a wav file. You can probably google on the bgsound tag. I
myself don't follow media support because I don't use media.
Publisher does not expose the head section, all code fragments are in the
body.
--
David Bartosik - [MSFT MVP]
http://www.publishermvps.com
http://www.davidbartosik.com

Using webpage properties in Publisher2000, wav files are audible by visitors
but mid files are not. Only I can hear them. While the tag <bgsound
src="xyz.wav> seems to work perfectly, <bgsound src="xyz.mid"> fails.

Perhaps, in the case of midi files they should be placed in a separate
folder on the site and called out by a link in the "Head" segment, i.e not
using webpage properties, but adding the <bgsound src="music/xyz.mid"
autostart> tag manually.

Does anyone know?

I'll try this anyway.

 

[Geoffrey]

Thanks for your advice DaveF.
1.- I use music because I'm testing a website I designed for a guy who runs
a Karaoke business. Music makes sense in this case.

2.- I finally figured what the problem is. The server hosting my test site
is not configured for MIME/x-MIDI !!! That's all the trouble was. Once the
pages are installed on a commercial server and the Service provider notified
that that Midi music is to be played, there'll be no problem.

Phewwww!!! what a relief. It was driving me mad for the last couple of days.
--
SPQR

Perhaps you could consider converting your file to a format that is
supported in Publisher. That way you won't have to edit your code every time
you make a change on that page, assuming that you ever do figure out how to
use a midi file.

And, FWIW, consider NOT using any background sound. I have read that as many
as 9 out of 10 people will not linger on a page with muzac in the
background. Why take the chance of alienating people once you actually get
them to your site?

DavidF

Thanks for your reply Dave,
I know Publisher puts code fragments in the body only; that's why I do a lot
of post scripting in the HTML document after Publisher has "saved as
webpage". I just run the HTML page and perform changes in the notepad file
and save. You know... when the page is running on the local browser, click on
"view", then click on "source" and add or amend script then "File save".

I.E. supports almost everything. I think my problem is possibly that a
script must be added to activate the CODEC that supports MIDI files. I'm
still searching for an answer.
--
SPQR

IE may only support a wav file. You can probably google on the bgsound tag. I
myself don't follow media support because I don't use media.
Publisher does not expose the head section, all code fragments are in the
body.
--
David Bartosik - [MSFT MVP]
http://www.publishermvps.com
http://www.davidbartosik.com



:

Using webpage properties in Publisher2000, wav files are audible by visitors
but mid files are not. Only I can hear them. While the tag <bgsound
src="xyz.wav> seems to work perfectly, <bgsound src="xyz.mid"> fails.

Perhaps, in the case of midi files they should be placed in a separate
folder on the site and called out by a link in the "Head" segment, i.e not
using webpage properties, but adding the <bgsound src="music/xyz.mid"
autostart> tag manually.

Does anyone know?

I'll try this anyway.

 

[DavidF]

Geoffrey,

Thanks for the feedback...yes, I agree that in this case it does make sense.
Glad you figured it out.

DavidF

Thanks for your advice DaveF.
1.- I use music because I'm testing a website I designed for a guy who runs
a Karaoke business. Music makes sense in this case.

2.- I finally figured what the problem is. The server hosting my test site
is not configured for MIME/x-MIDI !!! That's all the trouble was. Once the
pages are installed on a commercial server and the Service provider notified
that that Midi music is to be played, there'll be no problem.

Phewwww!!! what a relief. It was driving me mad for the last couple of days.
--
SPQR

Perhaps you could consider converting your file to a format that is
supported in Publisher. That way you won't have to edit your code every time
you make a change on that page, assuming that you ever do figure out how to
use a midi file.

And, FWIW, consider NOT using any background sound. I have read that as many
as 9 out of 10 people will not linger on a page with muzac in the
background. Why take the chance of alienating people once you actually get
them to your site?

DavidF

Thanks for your reply Dave,
I know Publisher puts code fragments in the body only; that's why I do

a
lot

of post scripting in the HTML document after Publisher has "saved as
webpage". I just run the HTML page and perform changes in the notepad file
and save. You know... when the page is running on the local browser,

click
on

"view", then click on "source" and add or amend script then "File save".

I.E. supports almost everything. I think my problem is possibly that a
script must be added to activate the CODEC that supports MIDI files. I'm
still searching for an answer.
--
SPQR


:

IE may only support a wav file. You can probably google on the

bgsound
tag. I

myself don't follow media support because I don't use media.
Publisher does not expose the head section, all code fragments are

in
the

body.
--
David Bartosik - [MSFT MVP]
http://www.publishermvps.com
http://www.davidbartosik.com



:

Using webpage properties in Publisher2000, wav files are audible

by
visitors

but mid files are not. Only I can hear them. While the tag <bgsound
src="xyz.wav> seems to work perfectly, <bgsound src="xyz.mid"> fails.

Perhaps, in the case of midi files they should be placed in a separate
folder on the site and called out by a link in the "Head" segment,

i.e
not

using webpage properties, but adding the <bgsound src="music/xyz.mid"
autostart> tag manually.

Does anyone know?

I'll try this anyway.

 

[Geoffrey]

DaveF,

One final tip: post-scripting is not a problem if you keep the permanent
post-scripts in a Word file and copy and paste after every alteration to the
site.

It doesn't get any better ...hehehe.
Cheers
--
SPQR

Geoffrey,

Thanks for the feedback...yes, I agree that in this case it does make sense.
Glad you figured it out.

DavidF

Thanks for your advice DaveF.
1.- I use music because I'm testing a website I designed for a guy who runs
a Karaoke business. Music makes sense in this case.

2.- I finally figured what the problem is. The server hosting my test site
is not configured for MIME/x-MIDI !!! That's all the trouble was. Once the
pages are installed on a commercial server and the Service provider notified
that that Midi music is to be played, there'll be no problem.

Phewwww!!! what a relief. It was driving me mad for the last couple of days.
--
SPQR

Perhaps you could consider converting your file to a format that is
supported in Publisher. That way you won't have to edit your code every time
you make a change on that page, assuming that you ever do figure out how to
use a midi file.

And, FWIW, consider NOT using any background sound. I have read that as many
as 9 out of 10 people will not linger on a page with muzac in the
background. Why take the chance of alienating people once you actually get
them to your site?

DavidF

Thanks for your reply Dave,
I know Publisher puts code fragments in the body only; that's why I do a
lot
of post scripting in the HTML document after Publisher has "saved as
webpage". I just run the HTML page and perform changes in the notepad file
and save. You know... when the page is running on the local browser, click
on
"view", then click on "source" and add or amend script then "File save".

I.E. supports almost everything. I think my problem is possibly that a
script must be added to activate the CODEC that supports MIDI files. I'm
still searching for an answer.
--
SPQR


:

IE may only support a wav file. You can probably google on the bgsound
tag. I
myself don't follow media support because I don't use media.
Publisher does not expose the head section, all code fragments are in
the
body.
--
David Bartosik - [MSFT MVP]
http://www.publishermvps.com
http://www.davidbartosik.com



:

Using webpage properties in Publisher2000, wav files are audible by
visitors
but mid files are not. Only I can hear them. While the tag <bgsound
src="xyz.wav> seems to work perfectly, <bgsound src="xyz.mid"> fails.

Perhaps, in the case of midi files they should be placed in a separate
folder on the site and called out by a link in the "Head" segment, i.e
not
using webpage properties, but adding the <bgsound src="music/xyz.mid"
autostart> tag manually.

Does anyone know?

I'll try this anyway.

 

[DavidF]

Geoffrey,

Point taken, but I keep mine in notepad files. However, I generally have
researched alternatives, such as JavaScript, that I can use with the insert
HTML code fragment feature. I don't have to remember to make the edit when I
change the page, I tend to get lost when I am looking at the source code,
and I find it easier to edit from the code fragment box when I do want to
change something. And FWIW using Pub 2000 I have found that many of the free
JavaScripts that are available that say they must be in the head section
actually work by just inserting them into the body from the Pub file.
There's many ways to skin a cat they say, and I am certainly no
expert....cheers back at ya...DavidF

DaveF,

One final tip: post-scripting is not a problem if you keep the permanent
post-scripts in a Word file and copy and paste after every alteration to the
site.

It doesn't get any better ...hehehe.
Cheers
--
SPQR

Geoffrey,

Thanks for the feedback...yes, I agree that in this case it does make sense.
Glad you figured it out.

DavidF

Thanks for your advice DaveF.
1.- I use music because I'm testing a website I designed for a guy who runs
a Karaoke business. Music makes sense in this case.

2.- I finally figured what the problem is. The server hosting my test site
is not configured for MIME/x-MIDI !!! That's all the trouble was. Once the
pages are installed on a commercial server and the Service provider notified
that that Midi music is to be played, there'll be no problem.

Phewwww!!! what a relief. It was driving me mad for the last couple of days.
--
SPQR


:

Perhaps you could consider converting your file to a format that is
supported in Publisher. That way you won't have to edit your code

every
time

you make a change on that page, assuming that you ever do figure out

how
to

use a midi file.

And, FWIW, consider NOT using any background sound. I have read that

as
many

as 9 out of 10 people will not linger on a page with muzac in the
background. Why take the chance of alienating people once you

actually
get

them to your site?

DavidF

Thanks for your reply Dave,
I know Publisher puts code fragments in the body only; that's why

I do
a

lot
of post scripting in the HTML document after Publisher has "saved as
webpage". I just run the HTML page and perform changes in the

notepad
file

and save. You know... when the page is running on the local

browser,
click

on
"view", then click on "source" and add or amend script then "File save".

I.E. supports almost everything. I think my problem is possibly that a
script must be added to activate the CODEC that supports MIDI

files.
I'm

still searching for an answer.
--
SPQR


:

IE may only support a wav file. You can probably google on the bgsound
tag. I
myself don't follow media support because I don't use media.
Publisher does not expose the head section, all code fragments

are
in

the
body.
--
David Bartosik - [MSFT MVP]
http://www.publishermvps.com
http://www.davidbartosik.com



:

Using webpage properties in Publisher2000, wav files are

audible
by

visitors
but mid files are not. Only I can hear them. While the tag <bgsound
src="xyz.wav> seems to work perfectly, <bgsound src="xyz.mid"> fails.

Perhaps, in the case of midi files they should be placed in a separate
folder on the site and called out by a link in the "Head"

segment,
i.e

not
using webpage properties, but adding the <bgsound src="music/xyz.mid"
autostart> tag manually.

Does anyone know?

I'll try this anyway.

 

[Geoffrey]

Good on you DavidF,

"many of the free

JavaScripts that are available that say they must be in the head section
actually work by just inserting them into the body"

Crikey, now here's something I've never tried. But thanks for the tip, mate,
I shall have a go at it.
Thanks
--
SPQR

Geoffrey,

Point taken, but I keep mine in notepad files. However, I generally have
researched alternatives, such as JavaScript, that I can use with the insert
HTML code fragment feature. I don't have to remember to make the edit when I
change the page, I tend to get lost when I am looking at the source code,
and I find it easier to edit from the code fragment box when I do want to
change something. And FWIW using Pub 2000 I have found that many of the free
JavaScripts that are available that say they must be in the head section
actually work by just inserting them into the body from the Pub file.
There's many ways to skin a cat they say, and I am certainly no
expert....cheers back at ya...DavidF

DaveF,

One final tip: post-scripting is not a problem if you keep the permanent
post-scripts in a Word file and copy and paste after every alteration to the
site.

It doesn't get any better ...hehehe.
Cheers
--
SPQR

Geoffrey,

Thanks for the feedback...yes, I agree that in this case it does make sense.
Glad you figured it out.

DavidF

Thanks for your advice DaveF.
1.- I use music because I'm testing a website I designed for a guy who
runs
a Karaoke business. Music makes sense in this case.

2.- I finally figured what the problem is. The server hosting my test site
is not configured for MIME/x-MIDI !!! That's all the trouble was. Once the
pages are installed on a commercial server and the Service provider
notified
that that Midi music is to be played, there'll be no problem.

Phewwww!!! what a relief. It was driving me mad for the last couple of
days.
--
SPQR


:

Perhaps you could consider converting your file to a format that is
supported in Publisher. That way you won't have to edit your code every
time
you make a change on that page, assuming that you ever do figure out how
to
use a midi file.

And, FWIW, consider NOT using any background sound. I have read that as
many
as 9 out of 10 people will not linger on a page with muzac in the
background. Why take the chance of alienating people once you actually
get
them to your site?

DavidF

Thanks for your reply Dave,
I know Publisher puts code fragments in the body only; that's why I do
a
lot
of post scripting in the HTML document after Publisher has "saved as
webpage". I just run the HTML page and perform changes in the notepad
file
and save. You know... when the page is running on the local browser,
click
on
"view", then click on "source" and add or amend script then "File
save".

I.E. supports almost everything. I think my problem is possibly that a
script must be added to activate the CODEC that supports MIDI files.
I'm
still searching for an answer.
--
SPQR


:

IE may only support a wav file. You can probably google on the
bgsound
tag. I
myself don't follow media support because I don't use media.
Publisher does not expose the head section, all code fragments are
in
the
body.
--
David Bartosik - [MSFT MVP]
http://www.publishermvps.com
http://www.davidbartosik.com



:

Using webpage properties in Publisher2000, wav files are audible
by
visitors
but mid files are not. Only I can hear them. While the tag
<bgsound
src="xyz.wav> seems to work perfectly, <bgsound src="xyz.mid">
fails.

Perhaps, in the case of midi files they should be placed in a
separate
folder on the site and called out by a link in the "Head" segment,
i.e
not
using webpage properties, but adding the <bgsound
src="music/xyz.mid"
autostart> tag manually.

Does anyone know?

I'll try this anyway.