From: Florian J. <fl...@wi...> - 2013-06-02 21:55:20
|
Hi I found out that the wave editor offers various ways of manipulating audio data, such as fade-in, fade-out, copy'n'paste, normalize etc. However, I was not able to get this actually working. I selected some portions of audio, clicked the menu entry for "fade out", then a dialog told me that MusE was recalculating the peakfile. But there was no result. The wave just did not change. Is that normal? Am i doing something wrong? And, another thing: do we really need this functionality? IMHO, fade-in, -out and mute is unneeded because we can do this with wave controllers. normalizing, there might be a use for that. But frankly, MusE is not the right tool for editing audio, never was intended to be and probably never will be. We might want to integrate with an external editor like audacity for actual destructive audio operations? I'm asking because my audio stream changes make it hard for me to do operations on "a file". There is no file any more. There's just the result of the stretcher, and one can hardly manipulate that. Greetings flo |
From: Tim E. R. <ter...@ro...> - 2013-06-02 23:19:40
|
On June 2, 2013 11:55:12 PM Florian Jung wrote: > Hi > > I found out that the wave editor offers various ways of manipulating > audio data, such as fade-in, fade-out, copy'n'paste, normalize etc. Surprise, yep I just warned you in another post. > However, I was not able to get this actually working. I selected some > portions of audio, clicked the menu entry for "fade out", then a dialog > told me that MusE was recalculating the peakfile. But there was no > result. The wave just did not change. > > Is that normal? Am i doing something wrong? (I'll assume you're not doing anything complicated like using clones or using two wave parts sharing the same file. Simple tests for now.) Hm, odd, one other user reported the same thing a while ago and RJ and I tried it and it worked. It works here now. If the file in question is read-only (like say in /usr/share/sounds), what's supposed to happen is a dialog will ask to Copy On Write. Otherwise normally, as shown by your peak recalc message coming up, it's supposed to apply the function and that's it, display should update - if not try scrolling for update. And it won't edit FLAC or OGG files. Can you tell me more? Name/size of file, or other important info about project? > > > And, another thing: do we really need this functionality? IMHO, fade-in, > -out and mute is unneeded because we can do this with wave controllers. > > normalizing, there might be a use for that. > > But frankly, MusE is not the right tool for editing audio, never was > intended to be and probably never will be. Strongly disagree. MusE is an integrated Music Editor. Basic, if not advanced, wave editing functions are required. I use them all the time. The problem with controllers is the the information can be lost or modified, perhaps accidentally. Modifying the wave file makes it permanent. I want that. Then you can also transport that wave file elsewhere. Nobody wants to *have* to open another editor to do work, but if so desired... > We might want to integrate with an external editor like audacity for > actual destructive audio operations? ...Hello? "Edit -> Edit in External Editor". By default it is set to open 'sweep', a fine wave editor. I thought you knew about that. > I'm asking because my audio stream changes make it hard for me to do > operations on "a file". There is no file any more. There's just the > result of the stretcher, and one can hardly manipulate that. That's why I asked in the other post whether these other usages would still work. Which I imagine you've responded to by now... Tim. > > Greetings > flo > |
From: Florian J. <fl...@wi...> - 2013-06-02 23:34:31
|
Am 03.06.2013 01:19, schrieb Tim E. Real: > Can you tell me more? > Name/size of file, or other important info about project? 400MB wave file, /home/flo/hugetest.wav, no more info. It was just an empty project with that test file imported. > MusE is an integrated Music Editor. > Basic, if not advanced, wave editing functions are required. > I use them all the time. hm. Could you please give me a list of audio editing capabilities MusE currently offers? I'll need to find a way to do this with the audiostreams. I guess I will go with the editors displaying the *original* file, not processed by Rubberband, but instead "naively" stretched. If you increase tempo, and you would play what is displayed, this would increase pitch as well. > The problem with controllers is the the information can be lost > or modified, perhaps accidentally. > Modifying the wave file makes it permanent. I want that. > Then you can also transport that wave file elsewhere. who would want that if he has MusE ;)? > ...Hello? "Edit -> Edit in External Editor". > I thought you knew about that. i know; i was just wondering whether we might want to use solely that external editor for editing. please give me this list of audio editing capabilities, i'll need to think over that. Greetings flo |
From: Robert J. <spa...@gm...> - 2013-06-05 18:45:54
|
Good evening Florian, 2013/6/3 Florian Jung <fl...@wi...> > Am 03.06.2013 01:19, schrieb Tim E. Real: > > > Can you tell me more? > > Name/size of file, or other important info about project? > > 400MB wave file, /home/flo/hugetest.wav, no more info. It was just an > empty project with that test file imported. > > > > > MusE is an integrated Music Editor. > > Basic, if not advanced, wave editing functions are required. > > I use them all the time. > > I definitely must concur with that. Some editing capabilities, especially fades and normalization, are very useful to do without the hassle of using an external editor. > hm. Could you please give me a list of audio editing capabilities MusE > currently offers? I'll need to find a way to do this with the audiostreams. > > I guess I will go with the editors displaying the *original* file, not > processed by Rubberband, but instead "naively" stretched. If you > increase tempo, and you would play what is displayed, this would > increase pitch as well. > Yes, editing "what you hear" sounds complex (har har) and is likely not what you want. The functions I think are basically what you find in the function menu in the editor. Gain Mute Normalize Fade in Fade out Reverse >From a data point of view I think they are the same. You select a chunk in the editor, the chunk will be replaced by the processed chunk. There is a scheme for keeping undo of the edited wave also. This may be a problem too. Regards, Robert |
From: Florian J. <fl...@wi...> - 2013-06-05 20:26:30
|
Am 05.06.2013 20:45, schrieb Robert Jonsson: > Yes, editing "what you hear" sounds complex (har har) and is likely not > what you want. ... > From a data point of view I think they are the same. You select a chunk > in the editor, the chunk will be replaced by the processed chunk. > There is a scheme for keeping undo of the edited wave also. This may be > a problem too. > > > Regards, > Robert > Hi Robert, ah, thanks. Yeah, that looks pretty straightforward. I don't think this will become a problem with the AudioStreams. I just must add some conversion from XTicks into "frames of the audiofile", then change the audiofile, and then re-load the AudioStream. no worries :) Greetings flo |