Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[lucian.jp]

>>> BUG : Unable to save file in Media Editor

Step to reproduce :
Open Tools > Advanced tools > Media Editor ...
Open any audio file or create a new one
Click File > Save OR File > Save As OR File > Save Selection
Select any file format
When click save you receive this error :
---------------------------
Media Editor
---------------------------
Attempted an unsupported operation.
---------------------------
OK   
---------------------------

Thx

[MusicHawk]

Before seeing this post, I just used Media Editor in 13.0.115, and had no problem.

I found an MP3 track in my collection, an ancient vinyl rip, with very low audio. It was beyond the range of Replay Gain to fix dynamically.

So for a quick fix I opened the MP3 in Media Editor using the same steps in the bug report. I normalized the track, then resaved as MP3 VBR-Extreme. No problems.


Side comment: Unless I'm missing an option, I wish Media Editor could smoothly handle in-place editing of a track. It should recognize that I might want to save the edited track back to the original location and name and format. Instead, it defaulted to somewhere on a different drive and a different media file type. It took some clicking to get back to where the file lives, give it the correct original name, and switch to saving in the original MP3 format.

I realize sometimes the opposite is desired: new name, new location, maybe new format. But a huge advantage of MC having an editor is quick fixes (trimming talk from the front of a live recording track, for instance) and in this situation it would be wonderful to have MC understand the notion of editing the track in-place.

(I do my main vinyl ripping, restoration and editing using Sony Sound Forge.)

[lucian.jp]

So for a quick fix I opened the MP3 in Media Editor using the same steps in the bug report. I normalized the track, then resaved as MP3 VBR-Extreme. No problems.

Then it's maybe related to my computer setup :
Windows Server 2008 R2 build 7000 X64

The file I opened was on a network share and I was trying to save on the desktop

My user is administrator but the UAC is still activated --->For testing purpose of Windows Server R2

I tried it more than once and it's still doesn't work.

[Matt]

Then it's maybe related to my computer setup :
Windows Server 2008 R2 build 7000 X64

The file I opened was on a network share and I was trying to save on the desktop

My user is administrator but the UAC is still activated --->For testing purpose of Windows Server R2

I tried it more than once and it's still doesn't work.

Try saving as WAV.

Or if you're saving with an encoder, use that encoder once in Media Center and see if it makes a difference.

[lucian.jp]

Try saving as WAV.

Or if you're saving with an encoder, use that encoder once in Media Center and see if it makes a difference.

I have tried every formats, crash on every.

[JimH]

Does the location exist?  Is there space available?

[lucian.jp]

Space is available and yes the location exist, it`s the desktop.

Using Process Monitor, here is what I got for information :

10:09:03.2574324 PM   Media Editor.exe   3592   RegQueryKey   HKLM   SUCCESS   Query: HandleTags, HandleTags: 0x0
10:09:03.2574675 PM   Media Editor.exe   3592   RegOpenKey   HKLM\Software\Microsoft\Windows NT\CurrentVersion\FontSubstitutes   SUCCESS   Desired Access: Read
10:09:03.2575053 PM   Media Editor.exe   3592   RegSetInfoKey   HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes   SUCCESS   KeySetInformationClass: KeySetHandleTagsInformation, Length: 0
10:09:03.2575278 PM   Media Editor.exe   3592   RegQueryValue   HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes\Segoe UI   NAME NOT FOUND   Length: 144
10:09:03.2575581 PM   Media Editor.exe   3592   RegCloseKey   HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes   SUCCESS   

It retries 3 times those operations before showing the error popup.

I see in the stack that there is alot of access to wow64 dlls around the crash.



Hope it helps

[lucian.jp]

It's still happening with 124.

Here is a screencast of my experience : http://screencast.com/t/t6fN15ya

[lucian.jp]

I did my best to describe my problem, but it seems my request as been ignored. Is it because I do not give enough details? Can I do something else to help fix this problem?

[Alex B]

I have no idea of a possible cause (it works for me on XP), but does the problem exist only on your "Server 2008" PC? Have you tested it on Vista or XP?

[lucian.jp]

Vista work fine

[elpadre31]

I'm under Vista and i have the same error with MC13 but it works fine with MC12 on the same computer.

Congratulations for your software !

[Matt]

Thanks for the video.  I was able to reproduce the problem here.  Look for a fix in a coming build.