Re: [Audacity-devel] P2 Crash in Unicode Release on Windows (only?) importing or exporting...
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
From: LRN <lr...@gm...> - 2009-03-08 12:04:45
|
Leland wrote: > LRN wrote: > >> Leland wrote: >> >>> ExportFFmpeg -> crash >>> ImportFFmpeg -> crash >>> >>> And there is no global or simple fix. If we want to support Unicode >>> filenames in the above features, then each one will have to be looked at >>> and handled differently. >>> >>> >>> >> It is possible to fix that for ffmpeg specifically by implementing >> utf8-aware file uri protocol. >> >> > Would that be difficult? I'll stay away from ffmpeg or leave it until > last if you want to give it a go. > > What I've been finding (so far) is that most libraries have a way to > pass a "FILE *" handle and that works just fine since a wxFFile can > handle the Unicode name just fine since it uses Windows API calls > instead of fopen(). > That wouldn't help with FFmpeg, because it has very elaborate URI handling mechanism (by the way, it means that with FFmpeg we can import the network URIs), i'm sure it does not support importing from bare file descriptor. Just committed the fix. By the way, this is very common issue. Media Player Classic, for example, refuses to play files that have Greek letters in filename. |