On February 26, 2011 07:04:06 am Florian Jung wrote:
> Tim E. Real schrieb:
> > On February 25, 2011 07:38:44 am Florian Jung wrote:
> >> Hi,
> >> i am using MusE 1.1 on a debian lenny system, using jack for audio and
> >> midi in- and output;
> >> how can i tell muse to "echo" incoming midi events (from a master
> >> keyboard) to the device which should play them? i managed to set muse up
> >> so that i can record onto that track; if i rewind and play then, the
> >> notes are sent to the appropriate device. but how can i make muse send
> >> them while recordig and even when not recording (when i'm trying out how
> >> it sounds, for example)?
> > That's the job of the 'echo' button (now called 'midi thru' in the latest
> > SVN version) in the midi track info panel.
> > It should be on by default. Try again, it should be working.
> > Recommend to try latest SVN version for latest and greatest features.
> > Let us know if it still doesn't work.
> >> my setup is as follows:
> >> jack-keyboard is my "master-keyboard" (has a jack-midi-source)
> >> muse has a jack-midi-sink which is connected to jack-keyboard
> >> muse also has a softsynth, which is the device i want to echo the events
> >> to
> >> my midi track i created is assigned to the softsynth, and on the left
> >> side, under "input routing (iR)", i selected all channels of my
> >> jack-keyboard-input. i also played with the "echo" button, but it has no
> >> effect :(
> > If your input routing is correct, the little red 'input detect' LED
> > should flash when you play the KB. If not, something is wrong.
> > Tim.
> >> I'd be glad if anyone could help me there :)
> >> flo
> i have solved the problem already: i had jack running for two days at
> that time, and it seems like jack_nframes_t is bigger than a normal int
> (or only unsigned?). the problem was, that, when recording, the time of
> the midi event which MusE calculated was negative (due to an int
> overflow). restarting jack (i.e., setting the time to zero again) has
> solved this;
Ah, I see. I have known that this type of problem would come up
with long running-time set-ups.
This might be a very difficult problem to fix.
The entire app uses 32-bit ints or unsigned ints for frames and ticks,
and all calculations and operations are based on that.
Let's see, at 44100 samples per second, after two days that's
7,620,480,000 which is more than the 4,294,967,296 that an
unsigned can handle.
> maybe you either want to fix the use of the too-small data type, or at
> least print an error message which suggests a possible solution ;)?
> uhm, and i have a general question to that mailing list ;) (i'm new to
> mailing lists in general)
> should i always full-quote? should i put my new text on the top or on
> the bottom?
Not terribly important, a personal choice really, sometimes I quote the
whole thing, sometimes I snip for clarity if the quote is getting very long,
sometimes I write on top, sometimes on bottom, sometimes I quote
and reply to each section.
As long as the intended idea or response is put forth, I suppose.
We're not that terribly formal here at MusE. :)