hi,
I'm a french composer, and I try to create an sp-midi file for nokia 3510 and communicator
I use beatnik since 2 years and I know that a mini Beatnik Audio Engine is in some nokia phones.
I'm waiting for Scalable Polyphony MIDI Specification and Device Profiles by MMa.
I try to create an sp-midi file. To do that , musician must embed at the top of the midifile a "mip "
code( in hexadecimal code )..This mip code allow to reduce or increase polyphony of a midifile
for 4-polyphony device or 8 or16- polyphony device....
This mip code is just a sys-ex message, in hexadecimal code.The hex is in the MMA's specification. Also in the spec. are the device ID's for upcoming phones.
Do you know :
How can I put the correct "'MIP" code in my sp-midi file ?
Have you in hexdecimal code thi mip code, with device ID's ?
How can I test a sp-midi file exept on a phone and beatnik editor?
can I test a file on a desktop nkia 3510 phone emulator?
thanks,
my website: www.kitmusica.com (flashsound api and beatnik)
try our beatnik mixer www.kitmusica.com/introbeat.htm (beatnik)
a sonified web site www.helentraiteur.com, by kitmusica (beatnik)
a sonified gypsy web site http://jeanluc.borla.free.fr/chico4/chico.htm (flashsound api)
All,
The following was recently published as a work item of the W3C RDFcore
working group. It is our hope that when the specification documents are
stabilized as W3C recommendations (hopefully, quite soon) we can move this
forward promptly for RFC publication.
If there's anything here likely to be problematic, we'd appreciate knowing
sooner rather than later.
#g
--
>A New Internet-Draft is available from the on-line Internet-Drafts
>directories.
>
>
> Title : application/rdf+xml Media Type Registration
> Author(s) : A. Swartz
> Filename : draft-swartz-rdfcore-rdfxml-mediatype-00.txt
> Pages :
> Date : 05-Apr-02
>
>This document describes a media type (application/rdf+xml) for use
>with the XML serialization of the Resource Description Framework
>(RDF). RDF is a language designed to support the Semantic Web, by
>facilitating resource description and data exchange on the Web. RDF
>provides common structures that can be used for interoperable data
>exchange and follows the World Wide Web Consortium (W3C) design
>principles of interoperability, evolution, and decentralization.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-swartz-rdfcore-rdfxml-mediatype-0…
>
>To remove yourself from the IETF Announcement list, send a message to
>ietf-announce-request with the word unsubscribe in the body of the message.
>
>Internet-Drafts are also available by anonymous FTP. Login with the username
>"anonymous" and a password of your e-mail address. After logging in,
>type "cd internet-drafts" and then
> "get draft-swartz-rdfcore-rdfxml-mediatype-00.txt".
>
>A list of Internet-Drafts directories can be found in
>http://www.ietf.org/shadow.html
>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>
>
>Internet-Drafts can also be obtained by e-mail.
>
>Send a message to:
> mailserv(a)ietf.org.
>In the body type:
> "FILE /internet-drafts/draft-swartz-rdfcore-rdfxml-mediatype-00.txt".
>
>NOTE: The mail server at ietf.org can return the document in
> MIME-encoded form by using the "mpack" utility. To use this
> feature, insert the command "ENCODING mime" before the "FILE"
> command. To decode the response(s), you will need "munpack" or
> a MIME-compliant mail reader. Different MIME-compliant mail readers
> exhibit different behavior, especially when dealing with
> "multipart" MIME messages (i.e. documents which have been split
> up into multiple messages), so check your local documentation on
> how to manipulate these messages.
>
>
>Below is the data which will enable a MIME compliant mail reader
>implementation to automatically retrieve the ASCII version of the
>Internet-Draft.
>Content-Type: text/plain
>Content-ID: <20020405150842.I-D(a)ietf.org>
>
>ENCODING mime
>FILE /internet-drafts/draft-swartz-rdfcore-rdfxml-mediatype-00.txt
>
><ftp://ftp.ietf.org/internet-drafts/draft-swartz-rdfcore-rdfxml-mediatype-00…>
-------------------
Graham Klyne
<GK(a)NineByNine.org>
Anders,
I am picking this up again - sorry for the long delay.
The optional parameter that you requested has been added to
the latest draft - see
http://www.ietf.org/internet-drafts/draft-hoschka-smil-media-type-09.txt
-Philipp
"Anders Nohlgren (EPL)" wrote:
>
> Philipp,
> couldn't there be an optional parameter to the SMIL MIME type (indicating e.g. profile) that could be used for content-negotiation purposes? I fully understand your arguments that such a parameter is not absolutely necessary, but in some cases it would be a useful feature. If you want to deliver an optimised SMIL file to the client you should be able to indicate the supported profile. The last sentence of clause 14.4.4 in the SMIL 2.0 recommendation (http://www.w3.org/TR/smil20/smil-basic.html#smilBasicNS-GuidePlayer) talks about processing the test attributes already on the server side. When doing so it would help to know the SMIL profile that the client supports. Providing this with the MIME type would be efficient I think.
>
> Best regards,
> Anders
>
> > -----Original Message-----
> > From: Philipp Hoschka [mailto:ph@w3.org]
> > Sent: 22 June 2001 19:45
> > To: Peter Stark (ECS)
> > Cc: ietf-types(a)iana.org; www-smil(a)w3.org
> > Subject: Re: please review: application/smil MIME type registration
> >
> >
> > Peter,
> >
> > I presume your use case is that a client should be able to
> > request a SMIL-basic document via content-negotiation ?
> > This is not the way SMIL basic works.
> >
> > All SMIL 2.0 documents are also SMIL basic documents
> > http://www.w3.org/TR/smil20/smil-basic.html#BaseGuideNS-BasicDoc
> >
> > However, SMIL basic user agents interpret only a well-defined
> > subset of the markup that may occur in a SMIL 2.0 docucment (see
> > clause 5. and 7. at
> > http://www.w3.org/TR/smil20/smil-basic.html#BaseGuideNS-BasicUserAgent
> >
> > To avoid an unsatisfactory user experience, an author can
> > 1) only use markup defined for SMIL basic
> > http://www.w3.org/TR/smil20/smil-basic.html#smilBasicNS-Basic
> > 2) write a "scalable document" that adapts gracefully depending
> > on whether it is played on a SMIL 2.0 or a SMIL basic user
> > agent:
> > http://www.w3.org/TR/smil20/smil-basic.html#smilBasicNS-GuideDoc
> >
> > The same approach can be applied to any profile, not just SMIL
> > basic, and there is thus no need to use the MIME type to distinguish
> > between profiles.
> >
> > -Philipp
> >
> > "Peter Stark (ECS)" a écrit :
> > >
> > > How does can it be used to distinguish between full SMIL
> > 2.0 and a profile such as SMIL Basic?
> > >
> > > PS
> > >
> > > > -----Original Message-----
> > > > From: Philipp Hoschka [mailto:ph@w3.org]
> > > > Sent: den 21 juni 2001 18:03
> > > > To: ietf-types(a)iana.org
> > > > Cc: www-smil(a)w3.org
> > > > Subject: please review: application/smil MIME type registration
> > > >
> > > >
> > > > We'd like to start the two-week review of
> > > >
> > > > http://search.ietf.org/internet-drafts/draft-hoschka-smil-medi
> > > > a-type-08.txt
> > > >
> > > > describing the registration of the application/smil MIME type for
> > > > SMIL 1.0 and SMIL 2.0.
> > > >
> > > > -Philipp Hoschka, W3C
> > > >
> >
