[directmusic] Re: Problems copying dls instruments from one collection to another
- From: "Scott Morgan (Volt)" <a-smorg@xxxxxxxxxxxxx>
- To: <directmusic@xxxxxxxxxxxxx>
- Date: Mon, 4 Oct 2004 11:50:09 -0700
Yeah, identical GUIDs are definitely a problem. Sorry man, I feel your
pain.
-Scott Morgan
This message is "as is" and confers no rights whatsoever. (Umm, I don't
have the official disclaimer since I'm just now back at MS, but it goes
something like that :) )
-----Original Message-----
From: directmusic-bounce@xxxxxxxxxxxxx
[mailto:directmusic-bounce@xxxxxxxxxxxxx] On Behalf Of Jeff Gatlin
Sent: Monday, October 04, 2004 11:48 AM
To: directmusic@xxxxxxxxxxxxx
Subject: [directmusic] Re: Problems copying dls instruments from one
collection to another
The files in question were originally soundfonts. I used Awave to
convert
them to DLS 2+ (as Awave calls it).
I also tried saving them as DLS 2 (no plusses) with the same results.
For grins, I took a couple of instruments I created originally in
Producer
and tried the same copy and unfortunately, I get the same scrambled wave
assignment results. Sometimes it's just one wave, sometimes it's all of
them. I've even tried copying into a new project with the same results.
I've noticed that when I copy the instrument, it asks if I want to copy
the
waves used by this instrument. Naturally I answer yes since I need the
waves
in the new collection. I checked the GUIDs of the new waves compared to
the
originals and they are identical. I wonder if this is part of the
problem,
having two waves in seperate dls collections of the same project with
the
same GUIDs?
Of course, that doesn't lead to any reasonable work around. So far the
simplest thing is to compare each copied instrument with the old and
reassign each wave. Blah.
Jeff Gatlin
Simutronics Corp.
-----Original Message-----
From: directmusic-bounce@xxxxxxxxxxxxx
[mailto:directmusic-bounce@xxxxxxxxxxxxx]On Behalf Of Scott Morgan
(Volt)
Sent: Monday, October 04, 2004 12:11 PM
To: directmusic@xxxxxxxxxxxxx
Subject: [directmusic] Re: Problems copying dls instruments from one
collection to another
Ugh, I've run into that one before. If it doesn't mess up existing
sequences you can alter the GUIDs and patch numbers of the instruments
before copying them to the new DLS instrument. That way there's no
conflicts.
Somehow, I still remember having to go back and manually edit a bunch of
stuff :(
Here's a lamer answer: I do remember when playing with it, the order in
which you copy the instruments makes a difference in how scrambled
things get. Try a few different orders.
Wait, brain coming to life....Are you making these instruments outside
of Producer? I seem to remember my issue was with trying to combine
instruments I had converted from other formats in Awave. I think that's
why there wasn't a great solution, there was some kind of conflict
between the two programs.
-Scott Morgan
This message is "as is" and confers no rights whatsoever. (Umm, I don't
have the official disclaimer since I'm just now back at MS, but it goes
something like that :) )
-----Original Message-----
From: directmusic-bounce@xxxxxxxxxxxxx
[mailto:directmusic-bounce@xxxxxxxxxxxxx] On Behalf Of Jeff Gatlin
Sent: Monday, October 04, 2004 9:57 AM
To: directmusic@xxxxxxxxxxxxx
Subject: [directmusic] Problems copying dls instruments from one
collection to another
I am trying to take a number of dls instruments which have been saved as
individual dls files and combine them into a single dls collection. To
do so
I insert the dls files into a common project and create a new dls
collection
which will hold all the instruments.
After I copy a dls instrument from the inserted collection then paste it
into the new dls collection which has at least one other instrument in
it, I
find that the new copy of the instrument has several of its wave
assignments
scrambled, usually choosing the waves of one of the other instruments in
the
target collection.
Is there a work around or patch for this problem aside from manually
rebuilding each instrument from scratch?
Jeff Gatlin
Simutronics Corp.
-- Binary/unsupported file stripped by Ecartis --
-- Type: application/ms-tnef
-- File: winmail.dat
Other related posts:
