Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correct operation requires a device running at 700MHz + #63

Open
xross opened this issue Jul 30, 2024 · 2 comments
Open

Correct operation requires a device running at 700MHz + #63

xross opened this issue Jul 30, 2024 · 2 comments

Comments

@xross
Copy link
Contributor

xross commented Jul 30, 2024

Likely relates to

if (frame == AWE_BLOCK_SIZE) { // TODO: this may not fit between samples

@ed-xmos
Copy link
Contributor

ed-xmos commented Aug 1, 2024

I tested play_basic 3 thread and, if you set the design to bypass, audio streams without interruption even down to 500MHz. This suggests that the lib_Awe data path is not the issue. I think it is more related to CPU loading for the DSP involved with the standard example.

It is still worth profiling the above code however.

@ed-xmos
Copy link
Contributor

ed-xmos commented Aug 1, 2024

I have profiled the code and the call to data_to_and_from_awe(output_data, input_data, c_children); for a three thread system with block_size=32 is about 112 ticks or about 1.12 microseconds. Given we have 20.8 microseconds to play with per frame I don't think this function is causing any issues
Note: I tried 5 thread and got similar numbers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants