Go Back   Home > Forums > >

PC Based Computer music servers, crossovers, and equalization

CamillaDSP - Cross-platform IIR and FIR engine for crossovers, room correction etc.
CamillaDSP - Cross-platform IIR and FIR engine for crossovers, room correction etc.
Please consider donating to help us continue to serve you.

Ads on/off / Custom Title / More PMs / More album space / Advanced printing & mass image saving
Reply
 
Thread Tools
Old Yesterday, 08:45 PM   #2011
fluid is offline fluid  Australia
diyAudio Member
 
Join Date: Jan 2009
Quote:
Originally Posted by howabout View Post
Thank you for your quick reply, I've followed the recipe on minidsp page (example 1) correcting loudspeaker phase using rephase and importing that to minidsp 2x4 hd


rePhase FIR Tool
The MiniDSP 2x4HD is very tap limited being stuck at 96K and filters in the 20 to 100Hz area need a lot more taps for the filters to be anything other than very low resolution. It is quite hard to make a filter with significant pre-ringing due to low frequency phase shifts with that many taps, but it is easy to make a filter than ruins the response due to not matching the intended target properly.

Camilla would give you the ability to use more taps. Posting in the rephase thread might get you more help on what you are aiming to do and what is going wrong.
  Reply With Quote
Old Today, 07:58 PM   #2012
katariat is offline katariat  United States
diyAudio Member
 
Join Date: Nov 2014
@HenrikEnquist, here is the output i get when i put in the -v argument
Code:
2021-05-09 19:54:19.949 DEBUG camilladsp - Read config file Some("test_10_alsa.yml")
2021-05-09 19:54:20.041 DEBUG camillalib::biquad - a1=-1.5346539759579207 a2=0.5887907064808636 b0=0.7808611706096961 b1=-1.5617223412193921 b2=0.7808611706096961
2021-05-09 19:54:20.041 DEBUG camillalib::biquad - a1=-1.5346539759579207 a2=0.5887907064808636 b0=0.7808611706096961 b1=-1.5617223412193921 b2=0.7808611706096961
2021-05-09 19:54:20.041 DEBUG camillalib::biquad - a1=-1.948313741843362 a2=0.9489816091639206 b0=0.00016696683013967437 b1=0.00033393366027934874 b2=0.00016696683013967437
2021-05-09 19:54:20.041 DEBUG camillalib::biquad - a1=-1.948313741843362 a2=0.9489816091639206 b0=0.00016696683013967437 b1=0.00033393366027934874 b2=0.00016696683013967437
2021-05-09 19:54:20.041 DEBUG camillalib::biquad - a1=-1.5346539759579207 a2=0.5887907064808636 b0=0.7808611706096961 b1=-1.5617223412193921 b2=0.7808611706096961
2021-05-09 19:54:20.041 DEBUG camillalib::biquad - a1=-1.5346539759579207 a2=0.5887907064808636 b0=0.7808611706096961 b1=-1.5617223412193921 b2=0.7808611706096961
2021-05-09 19:54:20.041 DEBUG camilladsp - Config is valid
2021-05-09 19:54:20.041 DEBUG camilladsp - Wait for config
2021-05-09 19:54:20.042 DEBUG camilladsp - Config ready
2021-05-09 19:54:20.042 DEBUG camillalib::filters - Build new pipeline
2021-05-09 19:54:20.042 DEBUG camillalib::filters - Build from config
2021-05-09 19:54:20.042 DEBUG camillalib::biquad - a1=-1.5346539759579207 a2=0.5887907064808636 b0=0.7808611706096961 b1=-1.5617223412193921 b2=0.7808611706096961
2021-05-09 19:54:20.042 DEBUG camillalib::filters - Build from config
2021-05-09 19:54:20.043 DEBUG camillalib::biquad - a1=-1.5346539759579207 a2=0.5887907064808636 b0=0.7808611706096961 b1=-1.5617223412193921 b2=0.7808611706096961
2021-05-09 19:54:20.043 DEBUG camillalib::filters - Build from config
2021-05-09 19:54:20.043 DEBUG camillalib::biquad - a1=-1.948313741843362 a2=0.9489816091639206 b0=0.00016696683013967437 b1=0.00033393366027934874 b2=0.00016696683013967437
2021-05-09 19:54:20.043 DEBUG camillalib::filters - Build from config
2021-05-09 19:54:20.043 DEBUG camillalib::biquad - a1=-1.948313741843362 a2=0.9489816091639206 b0=0.00016696683013967437 b1=0.00033393366027934874 b2=0.00016696683013967437
2021-05-09 19:54:20.043 DEBUG camillalib::filters - Build from config
2021-05-09 19:54:20.043 DEBUG camillalib::biquad - a1=-1.5346539759579207 a2=0.5887907064808636 b0=0.7808611706096961 b1=-1.5617223412193921 b2=0.7808611706096961
2021-05-09 19:54:20.043 DEBUG camillalib::filters - Build from config
2021-05-09 19:54:20.043 DEBUG camillalib::biquad - a1=-1.5346539759579207 a2=0.5887907064808636 b0=0.7808611706096961 b1=-1.5617223412193921 b2=0.7808611706096961
2021-05-09 19:54:20.043 DEBUG camillalib::processing - build filters, waiting to start processing loop
2021-05-09 19:54:20.043 DEBUG camillalib::alsadevice - Buffer frames 2048
2021-05-09 19:54:20.051 DEBUG camillalib::alsadevice - Opening audio device "hw:Loopback,0,0" with parameters: HwParams { channels: Ok(2), rate: "Ok(48000) Hz", format: Ok(S16LE), access: Ok(RWInterleaved), period_size: "Ok(512) frames", buffer_size: "Ok(4096) frames" }, SwParams(avail_min: Ok(512) frames, start_threshold: Ok(0) frames, stop_threshold: Ok(4096) frames)
2021-05-09 19:54:20.051 DEBUG camillalib::alsadevice - Audio device "hw:Loopback,0,0" successfully opened
2021-05-09 19:54:20.061 DEBUG camilladsp - Capture thread ready to start
2021-05-09 19:54:20.062 DEBUG camillalib::alsadevice - Opening audio device "hw:S51" with parameters: HwParams { channels: Ok(6), rate: "Ok(48000) Hz", format: Ok(S16LE), access: Ok(RWInterleaved), period_size: "Ok(256) frames", buffer_size: "Ok(2048) frames" }, SwParams(avail_min: Ok(256) frames, start_threshold: Ok(768) frames, stop_threshold: Ok(2048) frames)
2021-05-09 19:54:20.062 DEBUG camillalib::alsadevice - Audio device "hw:S51" successfully opened
2021-05-09 19:54:20.062 DEBUG camilladsp - Playback thread ready to start
2021-05-09 19:54:20.062 DEBUG camilladsp - Both capture and playback ready, release barrier
2021-05-09 19:54:20.062 DEBUG camillalib::alsadevice - Starting captureloop
2021-05-09 19:54:20.062 DEBUG camillalib::alsadevice - Starting playback loop
2021-05-09 19:54:20.063 INFO camillalib::alsadevice - Capture device supports rate adjust
2021-05-09 19:54:20.089 INFO camillalib::alsadevice - Starting playback from Prepared state
  Reply With Quote
Old Today, 08:30 PM   #2013
HenrikEnquist is offline HenrikEnquist  Sweden
diyAudio Member
 
Join Date: Apr 2016
Location: Lund
That log looks like it started up just fine. Then it has to continue and give more output while running, is it doing that?
__________________
CamillaDSP - cross platform dsp engine
Reporting an issue with CamillaDSP? Please attach the config file and the log from a run with "debug" log level.
  Reply With Quote
Old Today, 08:41 PM   #2014
katariat is offline katariat  United States
diyAudio Member
 
Join Date: Nov 2014
no, i dont see any additional activity on the screen for camilladsp. With the camailladsp running

i also tried few other things

a) ran a local wave file using VLC. In VLC, i could select the output to the loopback, no sound from the sound card
b) ran speaker-test to the loopback (-D hw:Loopback,0,0)...i could see it toggle through the 6 channels but no sound from the sound card

in both cases there was no additional log on the camilladsp terminal

i did run speakertest (-D hw:S51 -c 6) when camilladsp is not running and i do get sound toggling through the various channels
  Reply With Quote
Old Today, 08:57 PM   #2015
HenrikEnquist is offline HenrikEnquist  Sweden
diyAudio Member
 
Join Date: Apr 2016
Location: Lund
Ok, if there is no more output, then camilladsp is stuck waiting for something. So we need to figure out what it's waiting for and why.
Can you try that again with -vv?
Also, can you try putting another loopback as the playback device? That won't give you any sound, it's just to see if it gets stuck or not.
__________________
CamillaDSP - cross platform dsp engine
Reporting an issue with CamillaDSP? Please attach the config file and the log from a run with "debug" log level.
  Reply With Quote
Old Today, 09:17 PM   #2016
katariat is offline katariat  United States
diyAudio Member
 
Join Date: Nov 2014
is there a way i can pipe or send audio to the loopback to test if there is any sound coming out of the sound card. When i run the config file with -vv ....i can copy paste it but its a continuous flow of log output. As of now it seems that the config is up but i am not sure if i am able to send anything to it to process
  Reply With Quote
Old Today, 09:31 PM   #2017
HenrikEnquist is offline HenrikEnquist  Sweden
diyAudio Member
 
Join Date: Apr 2016
Location: Lund
Yes with -vv it quickly gets quite long, just let it run for some 10 seconds and save it to a text file. Then and attach that instead of pasting in the post.

Speaker-test should work fine for sending some sound to the loopback.
__________________
CamillaDSP - cross platform dsp engine
Reporting an issue with CamillaDSP? Please attach the config file and the log from a run with "debug" log level.
  Reply to this post

Reply


CamillaDSP - Cross-platform IIR and FIR engine for crossovers, room correction etc.Hide this!Advertise here!
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
The room correction or speaker correction? What can we do with dsp power now availabl Raimonds Full Range 233 28th January 2017 07:51 AM
Introducing OpenDRC, Open Digital Room Correction engine minidsp miniDSP 20 20th January 2016 05:37 PM
What the difference between dsp room correction eq and software correction erez1012 PC Based 0 10th March 2014 07:07 PM
Writing a Cross-Platform, Free Software Modeling Tool and TS-Parameter DB justinzane Software Tools 6 31st December 2013 06:55 AM
FS: DAC, room-correction, active crossovers, amp, speakers! taloyd Swap Meet 4 14th April 2009 03:16 PM


New To Site? Need Help?

All times are GMT. The time now is 10:01 PM.


Search Engine Optimisation provided by DragonByte SEO (Pro) - vBulletin Mods & Addons Copyright © 2021 DragonByte Technologies Ltd.
Resources saved on this page: MySQL 15.00%
vBulletin Optimisation provided by vB Optimise (Pro) - vBulletin Mods & Addons Copyright © 2021 DragonByte Technologies Ltd.
Copyright ©1999-2021 diyAudio
Wiki