Hi Hermann :) > Even just for such a small amount as of 1 or two sample steps. > 1/96000 s = 10 micro seconds. Of course you can't hear such as a timing > difference, but in the context I am working, you can hear it as a > colouring and unevenness in the way the spot supports the main micro. > I wouldn't call this effect minute or esoteric, it's quite blatant, > at least for trained ears, /and given the specific situation/ I > am working in.
Recording is different to PA work. We can't hear the Haas-Effect about 20ms as a second signal, but for a recording there will be extreme effects. Shifted phases will cause problems, not only when using computers. I guess the difference between two capacitors will be less than 10ms and if you are using a mic that is avoiding pass filters, at the minimum the capsule is a capacitor. If you are just doing a simple stereo recording with two mics, you would like to have a pair of mics, that is well-matched. If you have 2 percussive instruments with a fast attack and you play them "in unison" with a difference of less than 10ms, you will hear the delay. This isn't esoteric, but it is less relevant for people with consumer quality homerecording equipment or a less good feeling for grooves. > the way the prospective user feels and behaves. Something that is very easy to know, e.g. a virtual mixing console should be like a professional Neve, like a semi-professional Soundcraft and like a homerecording Behringer and all modern mixing consoles that are working that way. The difference between those 3 mixing consoles is the quality and nothing else. A sequencer should be near to the Atari's Cubase and all modern sequencers that are working that way. A HD recorder should be like a tape, while editing should be like MIDI for the Atari's Cubase, like all modern HD recorders that are working that way. New ideas and fine tuning are welcome, but this are the basics, because it fits to most needs. > Ralf, you describe a reasonable concrete usage situation. I take it that > you have checked the bulk of the available sequences for use in this > specific situation. > > Edit by using a grid or note editor C, Am, F, G. After that copy and > > paste it, until it has a length of 2 minutes. Do a loop range of some > > periods of C, Am, F, G, maybe 2 or 4 times. Let the loop range play > > and on a second MIDI track play for another instrument any white key > > on the manual, you can ride on C, Am, F, G by playing the white keys. > > Do this without recording for about 10 minutes, than record. Repeat > > this for the whole song, step by step and while doing that, change > > the soundfonts. > > And now, what is the problem? > > Ralf Mardorf schrieb: > > I can't do that with the most stable Linux I've got. Any Linux of > > mine can play MIDI files, but I can't produce with any of my Linux > > MIDI music myself. > > And this means...? > (a) all Seqs you tested behave unstable in this situation and crash? No. The sequencer I know, that might be interesting for me are Rosegarden, MusE and Qtractor. Rosegarden crashes when - playing MIDI events without recording - recording MIDI events - after recording audio tracks Also Fluid-DSSI, Qsynth, Qsampler and JACK will crash in this situations. MusE is totally broken. Qtractor might be fine, I only recorded 2 bars for drums, maybe it's not fine if I try to do more, but before I could go on, there was a problem with - Fluidsynth-DSSI. I can change one time the soundfont or choose another sound from the loaded soundfont, if I try to do it a second time it crashes. - Qsynth. I can use one engine, but it very often crashes when editing something, while Qsynth runs more than one engine. > (b) -or- you get latency problems when playing live? No serious problems for that. > (c) -or- the timings are unreliable and not exactly reproducible? There is MIDI jitter depending to the sequencer timing source and latency, I don't know how serious this is. It's okay for the moment. The problem still is, that working is impossible, because recording is impossible. > (d) -or- you have problems when coupling multiple apps in sync? I only need sync between audio and MIDI tracks, if a Linux studio in the box will work. Maybe MIDI jitter isn't a problem and as far as I can remember there wasn't a positive or negative delay for the starting point of audio recordings that reached 2 periods. There are problems for MTC. Rosegarden can be master for a Yamaha RX21, but not for the Atari ST. Ardour can be master for the Atari ST. Ardour can't be slave for the Atari ST. Because the Linux MIDI monitors don't show the bytes and a timer, I was thinking of programming a MIDI monitor myself. I'm able to do this, but maybe not for Linux, but at the moment MTC isn't interesting. MTC only will become interesting, when I have to chose between a Windows install as a workstation or a Linux HD recorder, Linux soft synth and effects in combination with an Atari ST. I tend to install Windows instead of using Linux and the Atari. > (e) -or- you have problems getting your audio hardware working? The TerraTec EWX 24/96, an Envy24 based 2 analogue IOs, is fine, resp. I can remember the sound was better when I tested Windows a long time ago, but that's not a disaster, following the JACK dev mailing list, I guess this might be the dithering, rounding problem. The Swissonic USB MIDI device, one input, one output is fine. On-board audio and HDMI are disabled by the BIOS and I removed the PCIe HDMI card. I remember I had troubles with my old mobo, were I tried to use MPU, gameport MIDI. My new mobo has no MIDI and I don't need HDMI at the moment. There's one drawback, I'm using an on-board ATI graphics with the VESA driver. The on-board graphics has access to the main memory, because it needs this as framebuffer. > And, further, apparently there is one breed of users which seem to be > quite fine, while you mention others (friends, complaints on forums) > which seem to experience similar fundamental problems. > > Any chance to identify a key difference between those two user groups? Maybe socket AM2 and on-board graphics aren't used by those who have stable MIDI applications, but I also know a Linux multimedia moderator who says, that he has got no trouble with sync, when using JACK transport, it should be 100% in sync in his studio. It's clear that he isn't able to hear it. It's impossible that he has JACK transport working without delay. He also told me, for multimedia is the need to use a 32-bit distro. As I've written, I don't know anybody living near to me, who has got no trouble with Linux audio, MIDI, I have to believe that there are people far away, that can use MIDI sequencers. There are people that are believable and they don't have an ASUS M2A-VM HDMI with a BE-2350 CPU, maybe they don't use a socket AM2 with a dual core CPU. > And, moreover, does anyone here know if the upstream developers are > aware of the problem. If not, do we have any chance of making them > aware -- I mean in a way they can't just put it off as being a strange > personal opinion? Maybe my tone isn't proper all the time, but I guess some developers know the problem I've got. But even if my tone is proper and the developers are interested to help, I can run all applications with the verbose option set, without getting helpful information. Because of the language barrier it's also not easy to know, if detailed information came over. Half OT: http://www.ichthyostega.de/cin3/ To think about a user interface for software like Cinelerra, is different to think about a user interface for a virtual audio mixing console. Okay, for an audio mixer there are questions like - if the whole mixer can't be displayed, is it better to have scroll bars or buttons to hide the EQ, the AUX sends etc.? Cinelerra is more complex, because it is a whole video studio. How is it most comfortable to have preview monitors etc.? Someone in the 64 Studio forums asked about what people need most, when editing a stand alone sound sampler and things like that, because he will program an editor. This is are smart questions, but for mixing consoles and sequencers the basics are well known. E.g. people said no to Notator and yes to Cubase, more people are fine with Cubase than with logic audio. Cheers, Ralf
signature.asc
Description: OpenPGP digital signature
_______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
