SourceForge has been redesigned. Learn more.
Close

#176 Gain function damages audio recordings

closed
Audio (19)
5
2009-07-21
2008-03-30
No

Hello good people from the muse team.

Today I will talk about the muse bug that frightens me the most. This one is MAJOR, although luckiky it shows up very rarely. (but it did today :) )

Here it is:
In audio edition window, when I use the gain function, sometimes the audio recording is severely messed up. Either, the part I was working on is silenced, or it becomes a mess of the same recording truncated in random.

The bad thing is that this damage is directly done into the audio file of the recording, and so the undo function does not work at all. The recording is lost forever (one of my song still have a bad sequel of that bug :) ).

The only workaround I found was to make a daily backup of all my files... :)

It is hard to say how to provoke it. I saw it about 4 or 5 times, and it was always after lots of audio recordings. I guess there is a link. (I use gain function a lot usually)

Background:
I am a regular muse user since last summer. I am using Muse 0.9 on ubuntu 7.10 32bit, on an AMDx2

Discussion

  • terminator356

    terminator356 - 2008-03-31

    Logged In: YES
    user_id=606684
    Originator: NO

    You have just learned how Muse edits audio files in place. :-(
    Unfortunately, Muse's handling of audio file editing is basically written in stone.
    It is too late and too complex to change this now.
    Ironically, I recently added some code to the Muse 0.9.x CVS (development) branch,
    which warns the user upon the very first attempt at wave editing. It warns:
    "Warning! Muse currently operates directly on the sound file."
    "Undo is supported, but NOT after an exit, WITH OR WITHOUT A SAVE!"
    "If you are stuck, try deleting the associated .wca file and reloading."
    But I disabled it, fearing that users would be 'annoyed' by the warning.
    But I will enable it now. I absolutely want users (especially new ones) to
    see this warning! It will appear in the next release.
    The new Muse version '2' may have better support for this.
    I am not sure, it appears to use sound 'clips', which may help.
    I would have to ask Werner if this is true. Tim.

     
  • terminator356

    terminator356 - 2008-03-31
    • assigned_to: nobody --> terminator356
     
  • cargobidibulle

    cargobidibulle - 2008-04-02

    Logged In: YES
    user_id=1998518
    Originator: YES

    Thanks Tim.

    A warning is already something, but one problem is that since update from version 0.9pre2 to 0.9, the "edit in external audio editor" function is no longer working. I used to edit audio with audacity, but today although "audacity" is still set in setting page, the audacity window just does not open up. (Sometime I work directly on audio recordings, opening them from audacity. But it is unconvenient for large number of recordings.)

    This is one of the two regressions I noticed from 0.9pre2 to 0.9. For the other one I will submit separated bug report.

    Thomas

     
  • terminator356

    terminator356 - 2008-04-02

    Logged In: YES
    user_id=606684
    Originator: NO

    You must first select part of the wave, then
    'open in external editor'.

     
  • cargobidibulle

    cargobidibulle - 2008-04-02

    Logged In: YES
    user_id=1998518
    Originator: YES

    Thanks for your support Tim.

    Well, I hate to sound overly pessimistic but :) , I retried and it did not work again.

    I include a screenshot.

    Cheers

    T.
    File Added: Capture.png

     
  • cargobidibulle

    cargobidibulle - 2008-04-02

    screen shot of external editor function bug

     
  • terminator356

    terminator356 - 2008-04-05

    Logged In: YES
    user_id=606684
    Originator: NO

    I tried it with gnome-sound-recorder. It worked.
    Your screen shot seems OK, but are you sure
    'audacity' is the real name of the executable and
    that it is on the path (seen by muse)?
    Perhaps it is a permission or ownership problem.
    As far as I know, the Muse coding related to the
    external editor has not changed in recent memory.
    If you are into building muse yourself, try the latest
    CVS version, or wait a while because a new
    official release of 'Muse number one' should be out
    sometime (hopefully) soon...

     
  • cargobidibulle

    cargobidibulle - 2008-04-05

    Logged In: YES
    user_id=1998518
    Originator: YES

    Hello Tim,

    Well, of course I can not guaranty that I have no environment setting problem, or that it is muse who is causing the problem.

    But What I can say is that in a terminal, "audacity" command with the exact same spelling launches audacity editor without problem. This works whatever the directory I am in, and with standard user permissions. It also works when I add the name of audio file to open like "audacity song.mp3".

    Anyway, I will follow updates, as I am pretty Muse dependent these days. :)

    Cheers

    T.

     
  • cargobidibulle

    cargobidibulle - 2008-04-28

    Logged In: YES
    user_id=1998518
    Originator: YES

    After recompiling to last CVS, I can open audacity from Muse. So, this was only a compilation problem. Sorry for that.

    One thing about compilation of CVS (which I am new to): After make command, it was requested a password for su command. However ubuntu user like me do not have su account by default and it leads to make error. I had to create a su account, and it worked.

    T.

     
  • cargobidibulle

    cargobidibulle - 2008-04-29

    Logged In: YES
    user_id=1998518
    Originator: YES

    Going back to the original bug of this report (the fact that audio events are sometimes messed up without apparent reason), I have to to add that this is not specific to the gain function.

    Today I have a similar problem when editing in audacity:
    - I open an audio event with the audio editor and then with audacity. fine
    - I do my audio treatment in audacity. fine
    - I save the result as wav in the directory /tmp_musewav. fine
    - I close audacity
    - then Muse seems to read the modified audio file, but then the audio is suddenly messep up in the audio edit window

    The good thing is I can undo in this case (assuming I notice it)

    The bad thing is, once the bug appear on an audio event it will happen again if I retry to edit the same event.

    T.

     
  • Robert Jonsson

    Robert Jonsson - 2009-07-06

    If you are still using MusE and this happens, please let us know.
    Setting this to pending since we've not been able to reproduce (bug will auto close in some weeks)

    ... also, I see that you are on a dual core system. There is a known issue (clicks in the audio) with MusE and dual core systems fixed by starting muse with 'taskset -c 1 muse'

     
  • Robert Jonsson

    Robert Jonsson - 2009-07-06
    • status: open --> pending
     
  • SourceForge Robot

    • status: pending --> closed
     
  • SourceForge Robot

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).