--- En date de : Mar 1.9.09, [email protected] 
<[email protected]> a écrit :

De: [email protected] 
<[email protected]>
Objet: 64studio-users Digest, Vol 28, Issue 1
À: [email protected]
Date: Mardi 1 Septembre 2009, 12h00

Send 64studio-users mailing list submissions to
    [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
    http://lists.64studio.com/mailman/listinfo/64studio-users
or, via email, send a message with subject or body 'help' to
    [email protected]

You can reach the person managing the list at
    [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of 64studio-users digest..."


Today's Topics:

   1. Re: machine reboot (Ralf Mardorf)
   2. Re: Re : 64studio-users Digest, Vol 27, Issue 26 (Ralf Mardorf)
   3. Re: Linux Sampler delays (Ralf Mardorf)
   4. Re: Linux Sampler delays (Quentin Harley)
   5. Re: Linux Sampler delays (Ralf Mardorf)


----------------------------------------------------------------------

Message: 1
Date: Tue, 01 Sep 2009 09:47:43 +0200
From: Ralf Mardorf <[email protected]>
Subject: Re: [64studio-users] machine reboot
To: fred <[email protected]>
Cc: 64 Studio users list <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8; format=flowed

Gustin Johnson wrote:
> You should look at /var/log/messages and /var/log/syslog, the .0 files
> are older (look at the time stamps).

I thought the .0 files are for the second last time, while the files 
without .0 are for the actual boot, but I was wrong, Gustin is right.

Btw. for Suse you can enable a system restore function, but IMO it is 
very flaky. Dunno if Debian and Ubuntu do have a system restore too. The 
system restore for a widespread Non-Linux OS most times is fine, anyway 
I do agree with Gustin, backups are important for any platform, but OT: 
some other platforms need to haul out the big guns for a backup. I guess 
not every OS will have all the important stuff stored by files, that 
easily can be archived by running tar.

I also agree that the overheating of the CPU isn't off the hook.

"sometimes I just launch the session, select a track, double click on 
its insert, move any cursor in the insert settings popup, and then 
reboot come"

If this happens after a reboot because of overheating, the CPU still 
might be to hot, but if this happens when starting a session while the 
CPU is cold, than the overheating probably is from the hook.


------------------------------

Message: 2
Date: Tue, 01 Sep 2009 10:00:04 +0200
From: Ralf Mardorf <[email protected]>
Subject: Re: [64studio-users] Re : 64studio-users Digest, Vol 27,
    Issue 26
To: frederic rech <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

frederic rech wrote:
> Hi list,
>
> Cool to see an entire issue just for your lil' problem !
>
> As you can see in http://www.64studio.com/node/1289,
>
> this will be fixed. Don't know if I'm supposed to mark somewhere 
> "resolved" ?
>
> Thanks a lot men, even shots in the dark were good tries ;o))
> Fred
>

Don't fear to use several WM/DE in the future, actually for my 3.0-beta3 
I'm running GNOME, e17 and KDE4, IIRC Gustin at least is using GNOME and 
KDE4. I'm not using Ardour and I've got MIDI jitter, but I guess Ardour 
would be fine too and the jitter is because of hardware issues and not 
because of using several WM/DE ;). IIRC I had trouble when I used 
Fluxbox and GNOME for another 64 Studio version, when I run the Nautilus 
file browser by Fluxbox.


That's a known bug Ralf, (or is it a feature ?)) if you run "nautilus" in 
fluxbox you break the fluxbox config
Prefer to run "nautilus --no-desktop -browser" and it's ok...


------------------------------

Message: 3
Date: Tue, 01 Sep 2009 11:18:14 +0200
From: Ralf Mardorf <[email protected]>
Subject: Re: [64studio-users] Linux Sampler delays
To: [email protected]
Cc: 64 Studio Users <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Note: Please reply to the list too. At the list there're people having 
much more knowledge than I've got.

Hi Paul :)

    * Have you used other GIG files too, but this particular piano sound?
    * You are sure that you don't use an effect, e.g. a delay?

Pardon, I guess this is something you know yourself, it's just that I 
want to except that the GIG is bad or an effect was disregard.

    * Which version on what architecture of 64 Studio do you run? I
      guess because of your hardware the architecture is amd64, but some
      people prefer to run x86 even on 64-bit. Do you run 2.1 or
      3.0-beta3? I don't know if anybody used QSampler with 3.0-beta3
      ;). I didn't use it and I only will make a test, if you are using
      3.0-beta3 too, because I'm a little bit lazy ;). For 2.1
      QSamplers's latency was fine on my machine and I never heard that
      your trouble occurred by someone else. It might be an issue for
      3.0-beta3. Dunno.
    * Did you changed anything for your plain vanilla, OOB installation?

Do you know QSynth, resp. fluidsynth-dssi? 1. QSampler should work, we 
should try to figure out what the problem is, but  2. if you need to 
finish a song, you might like to use a "soundfont" instead of a GIG?! 
Quasi as a band aid.

Best,
Ralf

[email protected] wrote:
>
> Ralf,
>
> Thanks for the response.
>
> The delay only occurs for LinuxSampler? Have you searched the web for
> "latency linuxsampler"? Do you use the GUI front-end QSampler?
>
> *I believe so, I can hear the delay when layering midi out to one of 
> my outboard devices and the linux sampler together. there is a clear 
> delay in the sampler side.*
>
> *Yes and can't find anything that addresses the problem. It does not 
> seem to be a generally reported issue. *
>
> *I use the GUI front end. I don't know any other way to use LS.*
>
>
> I wonder about 300 - 400 msec. Even if you set up JACK to 4096
> Frames/Period, 3 Periods/Buffer and a sample rate of 44100 Hz the
> latency should be < 300 msec and then the delay for Aeolus should be the
> same.
>
> *The number is an estimate - given mostly to make clear that the delay 
> is significant. Not sure about delay to Aeolus -  there is a certain 
> natural delay in the pipe organ anyway. The problem manifests when 
> playing a piano in LS - the delay is then obvious.*
>
> What are your JACK settings? Do you get any messages if you run QSampler
> in a terminal?
>
> *Don't know ... i have not changed JACK from defaults - that seems to 
> work fine. I will have another look but assume that because the delay 
> is in LS but not in the outboard midi which is also through JACK - 
> JACK is not the problem.*
>
> *I take it that this is not a 'known problem'?*
>
> Thanks again for any hints
>
> Regards
>
> Paul



------------------------------

Message: 4
Date: Tue, 01 Sep 2009 11:34:47 +0200
From: Quentin Harley <[email protected]>
Subject: Re: [64studio-users] Linux Sampler delays
To: Ralf Mardorf <[email protected]>
Cc: [email protected], 64 Studio Users
    <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Ralf Mardorf wrote:
> I don't know if anybody used QSampler with 3.0-beta3

I do.  3.0-beta3 on 64bit

I do not have any latency or jitter problems at all (not audible anyway)

PS: I mainly use Jack midi connections...  Try using Jack midi in qsampler.




------------------------------

Message: 5
Date: Tue, 01 Sep 2009 11:46:29 +0200
From: Ralf Mardorf <[email protected]>
Subject: Re: [64studio-users] Linux Sampler delays
To: Quentin Harley <[email protected]>
Cc: 64 Studio Users <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Quentin Harley wrote:
> Try using Jack midi in qsampler.

*OT for Paul*: I didn't know that Qsampler is able to use JACK MIDI.

*Might be very, very important for Paul*: I don't know what version of 
JACK is up to date for 2.1. When I used 2.1 the MIDI tab for QjackCtl 
was the common ALSA MIDI and there was no JACK MIDI available. For 
newbies this might cause some confusion.

The old QjackCtl was using JACK for audio (with a defined frontend, e.g. 
-d alsa, but MIDI always was ALSA MIDI, there was no JACK MIDI. Today we 
have ALSA MIDI, still the common MIDI and JACK MIDI, underutilised.



------------------------------

_______________________________________________
64studio-users mailing list
[email protected]
http://lists.64studio.com/mailman/listinfo/64studio-users


End of 64studio-users Digest, Vol 28, Issue 1
*********************************************



      
_______________________________________________
64studio-users mailing list
[email protected]
http://lists.64studio.com/mailman/listinfo/64studio-users

Reply via email to