[ddots-l] Re: firepod latency and performance
- From: "Phil Muir" <ddots@xxxxxxxxxxxx>
- To: <ddots-l@xxxxxxxxxxxxx>
- Date: Thu, 22 Nov 2007 07:38:30 -0000
Stacy, remember that when you alter the settings in your Sound cards control
panel to runt the wave
profiler again. You need to do that every time you alter a setting like that.
Regards, Phil Muir
P J Muir Productions
Music And Audio Production
URL:
www.philmuir.com/
Band website:
www.steelstringmusic.co.uk/
Band my Space Site:
www.myspace.com/steelstringmusic
----- Original Message -----
From: "Stacy Bleeks" <sbleeks@xxxxxxxxxxxx>
To: <ddots-l@xxxxxxxxxxxxx>
Sent: Thursday, November 22, 2007 4:39 AM
Subject: [ddots-l] Re: firepod latency and performance
> Hi Mike.
> Thanks very much for the offer. I will take you up on it. for now, I've
> been able to change the
> mms settings in the Firepod control panel up to 6 and then to 12, restarted
> but unfortunatley I
> still have the same results of audio stuttering. These audio cracks and pops
> etc. occur in the
> project where there is a lott going on as in audio and effects etc.
>
> Are you available this Sunday at some point?
>
> Thanks
> Stacy
>
> ----- Original Message -----
> From: "Mike C" <m_dsmusic@xxxxxxxxxxxx>
> To: <ddots-l@xxxxxxxxxxxxx>
> Sent: Wednesday, November 21, 2007 6:33 AM
> Subject: [ddots-l] Re: firepod latency and performance
>
>
>> Hi there stacy why don't you give me a call and I will definatly help you
>> troubleshoot your
>> firepod. In fact I have had no problems in getting the jaws cursor to
>> navigate the Presonus
>> control panel. -Or if you don't mind, I'll give you a call since I have
>> unlimited account to
>> long distance to skype.
>> ---- Original Message -----
>> From: "Phil Muir" <ddots@xxxxxxxxxxxx>
>> To: <ddots-l@xxxxxxxxxxxxx>
>> Sent: Wednesday, November 21, 2007 3:43 AM
>> Subject: [ddots-l] Re: firepod latency and performance
>>
>>
>>> Stacy wrote: I recall that the current driver is set at 3.1 mms but don't
>>> know what that
>>> means.
>>>
>>> Phil replied: it means that your latency slider is probably set too low.
>>> Try moving the driver
>>> setting to 5.8MS.
>>>
>>>
>>> Regards, Phil Muir
>>> P J Muir Productions
>>> Music And Audio Production
>>> URL:
>>> www.philmuir.com/
>>> Band website:
>>> www.steelstringmusic.co.uk/
>>> Band my Space Site:
>>> www.myspace.com/steelstringmusic
>>> ----- Original Message -----
>>> From: "Stacy Bleeks" <sbleeks@xxxxxxxxxxxx>
>>> To: <ddots-l@xxxxxxxxxxxxx>
>>> Sent: Tuesday, November 20, 2007 11:46 PM
>>> Subject: [ddots-l] firepod latency and performance
>>>
>>>
>>>> Hi Phil and all,
>>>>
>>>> I am using the Presonus Firepod. Even with the JAWS cursor the Firepod is
>>>> completely
>>>> innaccessible. I know that I've using 44/100 with number of buffers set
>>>> at 4 (16 is makximum
>>>> and setting more than 7 results in audio trouble) buffer size is set at 80
>>>> to 100% This needs
>>>> to be set at 12 to 20% for reasonable midi reaction using soft synths.
>>>>
>>>> I have no access to latency settings using either the JAWS or invisible
>>>> cursors let alone the
>>>> PC or virtual cursor.
>>>>
>>>> Everything seems to run pretty smoothly until I reach upwards of 24
>>>> tracks. Word around the
>>>> campfire is that with my system I should be getting way better performance
>>>> than this.
>>>>
>>>> I'll get somebody with a good pair of eyes over here aand see if we can't
>>>> find the "latency"
>>>> settings.
>>>>
>>>> I recall that the current driver is sett at 3.1 mms but don't know what
>>>> that means.
>>>>
>>>> Many thanks,
>>>> and
>>>> ** To leave the list, click on the immediately-following link:-
>>>> ** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
>>>> ** If this link doesn't work then send a message to:
>>>> ** ddots-l-request@xxxxxxxxxxxxx
>>>> ** and in the Subject line type
>>>> ** unsubscribe
>>>> ** For other list commands such as vacation mode, click on the
>>>> ** immediately-following link:-
>>>> ** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=faq]
>>>> ** or send a message, to ** ddots-l-request@xxxxxxxxxxxxx with the
>>>> Subject:- faq
>>>>
>>>
>>>
>>> ** To leave the list, click on the immediately-following link:-
>>> ** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
>>> ** If this link doesn't work then send a message to:
>>> ** ddots-l-request@xxxxxxxxxxxxx
>>> ** and in the Subject line type
>>> ** unsubscribe
>>> ** For other list commands such as vacation mode, click on the
>>> ** immediately-following link:-
>>> ** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=faq]
>>> ** or send a message, to ** ddots-l-request@xxxxxxxxxxxxx with the
>>> Subject:- faq
>>>
>>
>> ** To leave the list, click on the immediately-following link:-
>> ** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
>> ** If this link doesn't work then send a message to:
>> ** ddots-l-request@xxxxxxxxxxxxx
>> ** and in the Subject line type
>> ** unsubscribe
>> ** For other list commands such as vacation mode, click on the
>> ** immediately-following link:-
>> ** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=faq]
>> ** or send a message, to ** ddots-l-request@xxxxxxxxxxxxx with the Subject:-
>> faq
>
> ** To leave the list, click on the immediately-following link:-
> ** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
> ** If this link doesn't work then send a message to:
> ** ddots-l-request@xxxxxxxxxxxxx
> ** and in the Subject line type
> ** unsubscribe
> ** For other list commands such as vacation mode, click on the
> ** immediately-following link:-
> ** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=faq]
> ** or send a message, to ** ddots-l-request@xxxxxxxxxxxxx with the Subject:-
> faq
>
** To leave the list, click on the immediately-following link:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** ddots-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on the
** immediately-following link:-
** [mailto:ddots-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to
** ddots-l-request@xxxxxxxxxxxxx with the Subject:- faq
- Follow-Ups:
- [ddots-l] Re: firepod latency and performance
- From: Stacy Bleeks
- References:
- [ddots-l] firepod latency and performance
- From: Stacy Bleeks
- [ddots-l] Re: firepod latency and performance
- From: Phil Muir
- [ddots-l] Re: firepod latency and performance
- From: Mike C
- [ddots-l] Re: firepod latency and performance
- From: Stacy Bleeks
Other related posts:
- » [ddots-l] firepod latency and performance
- » [ddots-l] Re: firepod latency and performance
- » [ddots-l] Re: firepod latency and performance
- » [ddots-l] Re: firepod latency and performance
- » [ddots-l] Re: firepod latency and performance
- » [ddots-l] Re: firepod latency and performance
- » [ddots-l] Re: firepod latency and performance
- » [ddots-l] Re: firepod latency and performance
- » [ddots-l] Re: firepod latency and performance
- » [ddots-l] Re: firepod latency and performance
- » [ddots-l] Re: firepod latency and performance
- » [ddots-l] Re: firepod latency and performance
- » [ddots-l] Re: firepod latency and performance
- » [ddots-l] Re: firepod latency and performance
- » [ddots-l] Re: firepod latency and performance
- [ddots-l] Re: firepod latency and performance
- From: Stacy Bleeks
- [ddots-l] firepod latency and performance
- From: Stacy Bleeks
- [ddots-l] Re: firepod latency and performance
- From: Phil Muir
- [ddots-l] Re: firepod latency and performance
- From: Mike C
- [ddots-l] Re: firepod latency and performance
- From: Stacy Bleeks