On Tuesday 12 Dec 2006 21:07, D. Michael McIntyre wrote: > Seems a little odd when the help goes away after I press shift.
The help is supposed to say what you can do in the current state, so if all it says is "Hold Shift to avoid snapping to grid" (or whatever the wording is) and you hold Shift, it should go empty. Is that all that's happening? I'm still not certain about the wording -- I may go over it again. It's surprisingly hard to get it all complete and accurate, never mind as friendly as possible given the restrictions on length and readability. (Unlike the status bar in Inkscape, which truncates long texts, KDE's status bar resizes itself and the whole application window to fit if you put a long text in it. I think that's silly, but it seems to be what we have.) > Having the help crawling constantly side to side as the notes change widths > (C3 C#3 D3) is rather annoying. You use quite a big font, don't you? Apart from moving the note descriptions to the right end (which I didn't try, but thought would seem wrong), the only way I could think of to stop the context help bopping about like that was to set minimum widths on the note description labels. I did that, but I guess they're not big enough. Again, the problem is we can't make everything too big because it would prevent the use of small matrix windows. Try giving it a tweak if you like (the sizes are just hardcoded in MatrixView somewhere). > > there's a velocity inspection/setting menu; > > Total blank trying to figure out what you're talking about here. Between the Grid size and Quantize menus in the matrix toolbar there is now a Velocity menu. This shows you the velocity of the currently selected note, or the mean velocity of the selected group. Or you can select some notes, dial a velocity and choose Adjust -> Set Current Velocity (or whatever). > [timestretching] > Um. Let's see. Interesting. I hope the change isn't permanent on disk > somehow. It doesn't touch the original audio file, no. Note that stretching and squashing MIDI segments is nothing new -- we've had that for ages (although you couldn't do it just by Ctrl-dragging as you can now). What's new is doing it for audio segments too. > I'm thinking you should go whole hog with the status bar tooltip thingies > and explain about the stretching and whatnot in the main window too. Er, I thought I had? > (And why does the status bar in the notation view always say 0%? It's done > that for years, and it looks incredibly stupid.) Agreed. > Tried to drop an mp3 onto the canvas from my desktop. > > "Can't add dropped file. Bad audio file > path /home/silvan/Desktop/dungeon.wav.mp3" > > This is universal for .mp3 .ogg .au files tried from various random > locations. > > Likewise if I try to add a non .wav file manually in the audio file > manager. Sounds like your rosegarden-audiofile-importer is reporting itself as not working. Try rosegarden-audiofile-importer -t || echo Not working or rosegarden-audiofile-importer -l to list the supported file extensions (none == busted), or run it with sh -x. And make sure it's in the path or whatever and executable of course. Also see below. > 1) Why did we we decide to hide the audio file manager? I had to spend > half an hour looking for the damn thing the other day. The icon > disappeared, and I had no idea which menu it was on. The icon's still there for me. Some problem in your rosegardenui.rc? A Subversion conflict maybe? It's at Segments -> Manage Files Associated with Audio Segments, but I have to say I think it should probably just be Manage Audio. (We changed it from Manage Audio Files or Manage Audio Segments or something because that text wasn't strictly accurate, but I think maybe Manage Audio is fuzzy enough to get away with?) > 2) The file open dialog in the audio file manager doesn't want to look for > anything but .wav files. > > It doesn't appear that any resampling is taking place when I import a file > recorded at the wrong rate. Both of these also suggest the importer simply isn't being used at all, which should happen if it fails the configuration test on startup. > This project I'm slinging things > into at random was originally recorded at 48, and I've got a warning about > that in the file manager I want to do a popup on startup if you've changed the JACK sample rate since the last time you saved a project that you had imported audio files into. But I haven't got around to it yet. > I do have oggdec, flac, and sndfile-convert. Do you have a resampler? "sox" would do. You need at least one resampler. The script supports the three most likely candidates: sndfile-resample (which comes from the libsamplerate examples rather than the sndfile programs, and thus irritatingly is not in a Debian package as far as I know), sox, and ssrc. ssrc (http://shibatch.sourceforge.net/ -- the download on that page builds very easily on Linux) is the fastest of these, though it only supports the common samplerates. As far as I can tell from unreliable sources on the Internet, ssrc is thought to be marginally "better quality" than libsamplerate and libsamplerate is "better quality" than sox polyphase. But I'd be surprised if you can hear any difference among the three of them. Chris ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
