|
2015-05-16 05:09
|
import.png (38,158 bytes) |
|
|
mmh. I wonder if this is related to the (incomplete) Chinese translation and/or windows UTF-16 filenames. Import works here. Could you please try if it works with a file that has a simple ASCII filename? eg. "test.wav" (maybe on a USB stick "D:\test.wav" So that it does not have "C:\some\Chinese\characters\filename" If that does not help Menu > Edit > Preferences > GUI > Disable Translations re-start ardour, it'll come up in English. |
|
|
Hmm.I notice that any path with blanket character or non-ASCII character will not be recongized by Ardour for Windows. It is a pretty simple problem, I think solve it will not take too much time---After my college entrance exam, I will try to solve it if there are still not solve by others:) As for the bad Chinese translation, in my view, some sentence is too ....rude. For example "Are you sure?" translate to Chinese just like "What the F**K you want to do?" So I want to re-translate it into more proper Chinese after my college entrance~ |
|
|
Added, if LADSPA PATH or LV2 path(in enviroment var) has blanket or non-ASCII character, it will not work too.... PS:I don't know why Ardour 's PianoRoll don't display velocity in strip but in color. To draw multiple note 's velocity is not convient as Qtractor or Cubase.....If I add this function, will the patch accept by the Ardour Team? |
|
|
Thanks for tracking this down. I'll check whitespace later when I'm close to a win7 box. (on Linux and OSX there are no problems with space). As for velocity entry: check out http://manual.ardour.org/editing-and-arranging/edit-midi/step-entry/ (right click on the record-enable of a midi-track). Midi-notes are certainly color-coded by velocity. |
|
|
I mean to display each note 's velocity in strips. Just like most MIDI Editor does. The velocity is display under the note strip. And long strip shows hi velocity, short strip shows low velocity....That.is what I am talking about |
|
|
Velocity display just like this: http://qtractor.sourceforge.net/image/qtractor-screenshot3.png |
|
|
Ah a velocity track. different issue: http://tracker.ardour.org/view.php?id=5608 |
|
|
Importing an audio file with a space in the filename works fine here as long as all the characters are ASCII only on windows 7. I tried with an audio file that I renamed ??.aif and that did indeed fail to import. I believe the first problem is that in SndFileSource::get_soundfile_info the filename needs to be converted from utf-8 to the encoding of the current locale using Glib::locale_from_utf8() so that sf_open can open the file. So I tried that but unfortunately on this system Glib::locale_from_utf8() throws a conversion error for every file with a non-ASCII filename. I'm not sure why at this stage. |
|
|
The filename I use was not "??.aif" I took an existing audio file and renamed it and used a filename from libs/pbd/test/i18n_test and it failed to import |
|
|
I guess we should find a way to run those tests... Since we cross-compile windows binaries the actual system which produces the binaries is not a windows system. With some effort It would possible to automatically run the tests using wine (and xvfb), but then again the underlying filesystem is still ext3/4 and wine maps the path (using winepath). it's not the real thing. |
|
|
Believed fixed in Mixbus (Commit #34605a43). If working now, needs to get backported to Ardour. |
|
|
There's no commit 34605a43 in mixbus git, did you push it? |
- Anonymous
