I've recently started using the stm 2448 mixer in my projects and wanted to use the board id feature on the mixer. I found that when I assigned board 1 and board 2 I was getting unexpected dsp overloads with even very light projects. I looked into my cset.ini file and found a few problems...
firstly I have board0 with id 1 and board1 with id 0. Surely I need to assign an id for the third board, no?
[Host-config] shows Numboards=1. Should this not be 3?
And comming back to the stm 2448, there isn't any way of assigning board0, so how should I assign my first and then second board?
[board0]
boardid=1
[board1]
boardid=0
also found this if this helps
[host-config]
Numboards=1
board0=host
Many thanks
3 boards only 2 board id's?
boardid
Hi,
Just put on your cset.ini:
[board0]
boardid=0
[board1]
boardid=1
[board2]
boardid=2
If that configuration gives you dsp reload warnings etc change the sequnce of the cards in the above.
like 1,0,2 or 2,1,0
Whatever works.
Hope this helps.
Regards,
DIMITRIOS
Just put on your cset.ini:
[board0]
boardid=0
[board1]
boardid=1
[board2]
boardid=2
If that configuration gives you dsp reload warnings etc change the sequnce of the cards in the above.
like 1,0,2 or 2,1,0
Whatever works.
Hope this helps.
Regards,
DIMITRIOS
-
irrelevance
Board0=1 this is the scope pro and thats where I thought it's optimum setting was, at 0 position?
with the other two pulsars I'm not to bothered which order they asume
soi with the stm2448 if I selet board id as 1 am I selecting board0=1 or board1=0?
Astro regarding the numboards thing, thats what I would have expected? However the correct amount of dsp is registered 15+6+6
with the other two pulsars I'm not to bothered which order they asume
soi with the stm2448 if I selet board id as 1 am I selecting board0=1 or board1=0?
Astro regarding the numboards thing, thats what I would have expected? However the correct amount of dsp is registered 15+6+6
cset.ini
Hi,
I have played around with these settings fro many times so Iknow what I am saying
and I mean what I say 
The number 3 did not make any difference to me at all.
You have to put all three boards so scope knows which to seefirst and thereafter.
It is very important if you wanna avoid the dsp warning messages.
It can solve all these matters.
It is not what you waana see as master card but what wanna see Scope and your motherboard.
Play around with the sequence as I said and you will find the appropraitte series.
Regards,
Dimitrios
I have played around with these settings fro many times so Iknow what I am saying
and I mean what I say The number 3 did not make any difference to me at all.
You have to put all three boards so scope knows which to seefirst and thereafter.
It is very important if you wanna avoid the dsp warning messages.
It can solve all these matters.
It is not what you waana see as master card but what wanna see Scope and your motherboard.
Play around with the sequence as I said and you will find the appropraitte series.
Regards,
Dimitrios
-
irrelevance
Ok I just found an explanation in my installation guide After dusting off the pages I found some text on page97 onwards that explains the boardid situation.
I'll just post the main points from the text, in my own words.
1.It is recommended that the card with the most dsp's is treated as the first or main card in the system (knew I read it somewhere). In particular with scope pro card as mixers are distributed among dsp and if changed could result in phase issues.
2.
[board0]
boardid=1
[board1]
boardid=0
is an example of a system setupp which uses two second generation cards with the scope pro as first card.
3.
When a system includes a mix of first and second generation products then the entry
[HW]
Numboards=
should equal the number of cards installed.
After dusting off the pages I found some text on page97 onwards that explains the boardid situation. I'll just post the main points from the text, in my own words.
1.It is recommended that the card with the most dsp's is treated as the first or main card in the system (knew I read it somewhere). In particular with scope pro card as mixers are distributed among dsp and if changed could result in phase issues.
2.
[board0]
boardid=1
[board1]
boardid=0
is an example of a system setupp which uses two second generation cards with the scope pro as first card.
3.
When a system includes a mix of first and second generation products then the entry
[HW]
Numboards=
should equal the number of cards installed.
-
TimingLess
- Posts: 77
- Joined: Thu May 15, 2003 4:00 pm
- Location: DubbleU-Upper-Valley "Germany"
Hi Guys,
I just bought a LUNA II card, which is now together with a Pulsar 1 and Pulsar 1 SRB on my MOBO.
I have the same problems and I fooled around with the settings in the CSET.INI. But still strange behavior when you switch the board ID`s in the 24/48 mixer. DSP OVERLOAD. "No more STDM connections between Board 0 and Board 2"
Moreover I could not manage to use ASIO2 Modules. I don't care that much about. ASIO 1 is still OK for. But still .... strange ???
I found an old post, where is said, the if you have aux effects in the Mixer, they all try to stay on the first board. So its better to exclude the effects out of the mixer. I did'nt try that but I will in the evening and let you know.
Anyhow my question is:
How do I know, which board has which ID?
Regards
D.
I just bought a LUNA II card, which is now together with a Pulsar 1 and Pulsar 1 SRB on my MOBO.
I have the same problems and I fooled around with the settings in the CSET.INI. But still strange behavior when you switch the board ID`s in the 24/48 mixer. DSP OVERLOAD. "No more STDM connections between Board 0 and Board 2"
Moreover I could not manage to use ASIO2 Modules. I don't care that much about. ASIO 1 is still OK for. But still .... strange ???
I found an old post, where is said, the if you have aux effects in the Mixer, they all try to stay on the first board. So its better to exclude the effects out of the mixer. I did'nt try that but I will in the evening and let you know.
Anyhow my question is:
How do I know, which board has which ID?
Regards
D.
-
irrelevance
How many stdm cables have you got running between the boards?
You can find the board numbers on the samplerate settings page. I found with the creamware recommended settings that my scope pro was numbered 2 while pulsar2 was 2 and srb[2]
[board0]
boardid=1
[board1]
boardid=0
With musurgio recommended settings my scope card is now 1 with pulsar2 at 2 and srb[2]
[board0]
boardid=0
[board1]
boardid=1
[board2]
boardid=2
You can find the board numbers on the samplerate settings page. I found with the creamware recommended settings that my scope pro was numbered 2 while pulsar2 was 2 and srb[2]
[board0]
boardid=1
[board1]
boardid=0
With musurgio recommended settings my scope card is now 1 with pulsar2 at 2 and srb[2]
[board0]
boardid=0
[board1]
boardid=1
[board2]
boardid=2
-
TimingLess
- Posts: 77
- Joined: Thu May 15, 2003 4:00 pm
- Location: DubbleU-Upper-Valley "Germany"
Thanks for input.
I check that in the evening. Never looked for that there.
Anyhow I fooled around yesterday and I was not able to use other
ASIO MODULES then ASIO SOURCE AND ASIO DEST.
That works now and I can make music - but sometimes I wish to have more then 32 channel going out LOGIC to SFP!!!
All other ASIO 1 or ASIO 2 Modules did'nt work with LOGIC 5.51 or only 1 Stereo signal was transferred between SFP and LOGIC.
I keep trying and let you know if I was succesful or not.
DT
I check that in the evening. Never looked for that there.
Anyhow I fooled around yesterday and I was not able to use other
ASIO MODULES then ASIO SOURCE AND ASIO DEST.
That works now and I can make music - but sometimes I wish to have more then 32 channel going out LOGIC to SFP!!!
All other ASIO 1 or ASIO 2 Modules did'nt work with LOGIC 5.51 or only 1 Stereo signal was transferred between SFP and LOGIC.
I keep trying and let you know if I was succesful or not.
DT
all asio modules do work with logic.
remember that the asio modules and sequencer midi modules must be in place with the proper number of channels before opening logic for logic to configure itself properly.
you must reset the driver in logic every time you change the driver. in fact, to reduce the probability of a freeze, you should close logic before changing the type of asio module or the number of channels on those modules. of course you must use the proper asio dest for the source you choose.
there are asio64 modules. those give 64i/o and they definitely work with logic.
remember that the asio modules and sequencer midi modules must be in place with the proper number of channels before opening logic for logic to configure itself properly.
you must reset the driver in logic every time you change the driver. in fact, to reduce the probability of a freeze, you should close logic before changing the type of asio module or the number of channels on those modules. of course you must use the proper asio dest for the source you choose.
there are asio64 modules. those give 64i/o and they definitely work with logic.
-
TimingLess
- Posts: 77
- Joined: Thu May 15, 2003 4:00 pm
- Location: DubbleU-Upper-Valley "Germany"
Thanks for reply Gary!
Yes I tried that all but unfortunately it does not work properly.
I arranged several times a project with asio 64 mod. that worked.
(Even so I had to reload logic and sfp several times)
But everytime I open it again, it does not work.
I assume that there is something wrong with PSU or something else.
But good to know that it must work.!!!!!!!
thanks
D.
Yes I tried that all but unfortunately it does not work properly.
I arranged several times a project with asio 64 mod. that worked.
(Even so I had to reload logic and sfp several times)
But everytime I open it again, it does not work.
I assume that there is something wrong with PSU or something else.
But good to know that it must work.!!!!!!!
thanks
D.