Re: [Lmuse-user] Problem with the new relative path feature for wav file

[Robert Jonsson <robert.jonsson@da...>]

Hi Linium

Tuesday 18 November 2003 03.10 skrev Linium:
> Hello,
>
> Is it possible to put wav files elsewhere than in the same directory of a
> muse song ? I like to put them in the waves folder that Muse has always
> been searching for, i finally adopted the idea (even though Muse doesn't
> record wav file in it).
> Right now if i save an old song with the version 6.2, the absolut paths are
> replaced by relative paths but the waves folder is not taken in account.
> So at the reload of the song Muse complain that it doesn't find the audio
> clips..
Hmmm... I thought I had taken care that paths would be preserved for old 
files... I'll have to check.

> The only solution seems to put the muse song file in the waves folder as
> well, but now i find an old Muse song with waves files in various folders.
>
> Argh :)
>
> Well i can move them.... but i prefer to ask.

Since the songs are only xml-textfiles it is quite safe to dive in and change 
the paths by hand in the file (i've done that occasionally with old songs), 
be sure to backup the songfile before you change anything though.

---

I would tend to agree that the change to relative paths is yet a half 
solution.
Though I'm not entirely sure how the 'waves' was handled before or how it 
should be handled.

Are you suggesting that muse should create a 'waves' directory under the 
current project-root ? That seems lika a pretty clean solution...

Or are you seeking to collect all wave files, for all songs, in the same 
folder? A global 'waves' directory.

I'd be happy for input.

/Robert



>
> Linium
>
>
>
> -------------------------------------------------------
> This SF. Net email is sponsored by: GoToMyPC
> GoToMyPC is the fast, easy and secure way to access your computer from
> any Web browser or wireless device. Click here to Try it Free!
> https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl
> _______________________________________________
> Lmuse-user mailing list
> Lmuse-user@...
> https://lists.sourceforge.net/lists/listinfo/lmuse-user

[Lmuse-user] Problem with the new relative path feature for wav file

[Linium <intent@ne...>]

Hello,

Is it possible to put wav files elsewhere than in the same directory of a muse 
song ? I like to put them in the waves folder that Muse has always been 
searching for, i finally adopted the idea (even though Muse doesn't record 
wav file in it).
Right now if i save an old song with the version 6.2, the absolut paths are 
replaced by relative paths but the waves folder is not taken in account.
So at the reload of the song Muse complain that it doesn't find the audio 
clips..
The only solution seems to put the muse song file in the waves folder as well, 
but now i find an old Muse song with waves files in various folders.

Argh :)

Well i can move them.... but i prefer to ask. 

Linium 

Re: [Lmuse-user] Problem with the new relative path feature for wav file

[Robert Jonsson <robert.jonsson@da...>]

Hi Linium

Tuesday 18 November 2003 03.10 skrev Linium:
> Hello,
>
> Is it possible to put wav files elsewhere than in the same directory of a
> muse song ? I like to put them in the waves folder that Muse has always
> been searching for, i finally adopted the idea (even though Muse doesn't
> record wav file in it).
> Right now if i save an old song with the version 6.2, the absolut paths are
> replaced by relative paths but the waves folder is not taken in account.
> So at the reload of the song Muse complain that it doesn't find the audio
> clips..
Hmmm... I thought I had taken care that paths would be preserved for old 
files... I'll have to check.

> The only solution seems to put the muse song file in the waves folder as
> well, but now i find an old Muse song with waves files in various folders.
>
> Argh :)
>
> Well i can move them.... but i prefer to ask.

Since the songs are only xml-textfiles it is quite safe to dive in and change 
the paths by hand in the file (i've done that occasionally with old songs), 
be sure to backup the songfile before you change anything though.

---

I would tend to agree that the change to relative paths is yet a half 
solution.
Though I'm not entirely sure how the 'waves' was handled before or how it 
should be handled.

Are you suggesting that muse should create a 'waves' directory under the 
current project-root ? That seems lika a pretty clean solution...

Or are you seeking to collect all wave files, for all songs, in the same 
folder? A global 'waves' directory.

I'd be happy for input.

/Robert



>
> Linium
>
>
>
> -------------------------------------------------------
> This SF. Net email is sponsored by: GoToMyPC
> GoToMyPC is the fast, easy and secure way to access your computer from
> any Web browser or wireless device. Click here to Try it Free!
> https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl
> _______________________________________________
> Lmuse-user mailing list
> Lmuse-user@...
> https://lists.sourceforge.net/lists/listinfo/lmuse-user

Re: [Lmuse-user] Problem with the new relative path feature for wav file

[Werner Schweer <ws@se...>]

On Tuesday 18 November 2003 10:43, Robert Jonsson wrote:
> Hi Linium
>
> Tuesday 18 November 2003 03.10 skrev Linium:
>
> > Hello,
> >
> > Is it possible to put wav files elsewhere than in the same directory of
> > a=0D muse song ? I like to put them in the waves folder that Muse has
> > always been searching for, i finally adopted the idea (even though Muse
> > doesn't record wav file in it).
> > Right now if i save an old song with the version 6.2, the absolut paths
> > are=0D replaced by relative paths but the waves folder is not taken in
> > account. So at the reload of the song Muse complain that it doesn't find
> > the audio clips..
>
> Hmmm... I thought I had taken care that paths would be preserved for old
> files... I'll have to check.
>
>
> > The only solution seems to put the muse song file in the waves folder as
> > well, but now i find an old Muse song with waves files in various
> > folders.
> > Argh :)
> >
> > Well i can move them.... but i prefer to ask.
>
>
> Since the songs are only xml-textfiles it is quite safe to dive in and
> change =0D the paths by hand in the file (i've done that occasionally with
> old songs), be sure to backup the songfile before you change anything
> though.
> ---
>
> I would tend to agree that the change to relative paths is yet a half
> solution.
> Though I'm not entirely sure how the 'waves' was handled before or how it
> should be handled.
>
> Are you suggesting that muse should create a 'waves' directory under the
> current project-root ? That seems lika a pretty clean solution...
>
> Or are you seeking to collect all wave files, for all songs, in the same
> folder? A global 'waves' directory.
>
> I'd be happy for input.

i want to suggest the following file layout:

      There are 3 areas files can reside:

      - system
            /usr/lib/muse     (architecture dependend file)
            /usr/share/muse   (architecture independend files)

            System files are not changeable by the user and can be viewed
            to contain the "factory presets" of MusE.

      - user
            ~/muse/
            Should contain common data for all users projects

      - project
            ./
            should contain all files of a project

The project directory is the directory of the *.med file.
If the project consists of more than the *.med file (i.e. is a wave project)
then i suggest creating a separate subdirectory for every project and
putting all project files into this directory. This makes backup easy and
should also allow for easily moving the project to other locations.

If the path of wave file referenced in a project is equal to the project
path (better: the project path is part of the wave path), then the wave
should be stored with a relative path to the project path.
In all other cases the wave path should be stored as an absolute path.

I'm not sure MusE should detect "user" files and store them relative to
"~/.".

MusE file dialog boxes should have 3 buttons on the left side to allow
selection of "system", "user" or "project" files.

This is only partly or incorrect implemented in MusE.

Regards,
Werner

Re: [Lmuse-user] Problem with the new relative path feature for wav file

[Linium <intent@ne...>]

On Mardi 18 Novembre 2003 11:35, Werner Schweer wrote:

> > Since the songs are only xml-textfiles it is quite safe to dive in and
> > change  the paths by hand in the file (i've done that occasionally with
> > old songs), be sure to backup the songfile before you change anything
> > though.

I tried to add "waves/" before the file name in the xml file, Muse finds the 
file but "save" removes it again.

> > I would tend to agree that the change to relative paths is yet a half
> > solution.
> > Though I'm not entirely sure how the 'waves' was handled before or how it
> > should be handled.

Before, the waves (and any) folder was not a problem. Wav files could be 
everywhere, expressed as absolut path in the xml file.

> > Are you suggesting that muse should create a 'waves' directory under the
> > current project-root ? That seems lika a pretty clean solution...

On a pratical viewpoint, it is better to put the wav files (and their .wca) in 
a folder when you work with several audio softwares. If you put all the files 
(patchs, text notes, etc...) at the same level, it gets crowded rapidly. 

Ardour allows you to import wavs and they are copied in a subdir "sounds" as 
well. External sound files are stored with absolut path.

>       - project
>             ./
>             should contain all files of a project
>
> The project directory is the directory of the *.med file.
> If the project consists of more than the *.med file (i.e. is a wave
> project) then i suggest creating a separate subdirectory for every project
> and putting all project files into this directory. This makes backup easy
> and should also allow for easily moving the project to other locations.
>
> If the path of wave file referenced in a project is equal to the project
> path (better: the project path is part of the wave path), then the wave
> should be stored with a relative path to the project path.
> In all other cases the wave path should be stored as an absolute path.

Yes, it translates as: every wavs in the same dir or sub-directories than the 
muse project is stored with relative path, isn't it ? It should be the good 
behavior, i think..

Linium