1 Topic by glparke

  • glparke
  • Member
  • Offline
  • Registered: 2012-10-25
  • Posts: 47

Topic: Control Frame Rate - 30 works, 10 and compile fails

I have a file with 3 Nion's. When I change the control frame rate update from 30 to 10, it will not compile. When I change it back to 30, it compiles fine. What is the correlation between Control FPS rate and DSP / Memory usage? I have stereo wav players in this project. about 4 of them.
Attached is a pic at the 10 fps control frame rate. The 30fps is fine.

Post's attachments

Attachment icon 10fps control rate.PNG 26.17 kb, 573 downloads since 2017-04-24 

2 Reply by JoshM

  • JoshM
  • JoshM
  • Owner of BJM Unlimited and Happy Hour
  • Offline
  • From: Philadelphia, MS
  • Registered: 2007-08-13
  • Posts: 1,498

Re: Control Frame Rate - 30 works, 10 and compile fails

To what DSP's are your Wave Players assigned?

I'll bet if you look at the details, you will see that the wave players require significantly more memory resources at the lower frame rate. Why? I don't know, they just do. It may have something to do with them needing to store three times more information between operations or something like that. Can you reduce the number of wave players by one? Try just using three and assign one to each DSP chip.

Thanks!
Josh

Josh Millward
BJM Unlimited
Happy Hour

JoshM's Website

3 Reply by Graham

  • Graham
  • Administrator
  • Offline
  • Registered: 2008-05-02
  • Posts: 8

Re: Control Frame Rate - 30 works, 10 and compile fails

The wav players have to buffer a frames worth of audio data so the audio buffers are 3 times bigger at 10fps than 30fps.

4 Reply by Fergy

  • Fergy
  • MM Tech Support
  • Offline
  • From: The Home Office--Meridian
  • Registered: 2007-08-15
  • Posts: 338

Re: Control Frame Rate - 30 works, 10 and compile fails

Though this is long ago and the project is probably completed, I thought I would add to our response.

From the JPG you attached, DSP 201 and 203 have available Block 1 Memory, so you could "hand-place" (right click on an audio device and look for device placement) on the player on 201 or 203.  I would start with one player and see how the report changes.  The XDAB probably be setup different to get the audio back on the needed NioNode.

Also, it is not a 10 or 30 solution, you could try 20 and see what happens.

I would bet you could try locking the player to a different NIONs and change the Frame Rate to 15 will get you the best of both worlds.

Make it intuitive, never leave them guessing.