Testing V3.
Henrik, I have converted some v2 configs to v3 and they work fine. However I have a config that is causing me grief. I tried converting it in full but when in the "pipeline" tab and I add a mixer I get a blank screen.
So, I have zipped up the config and coeffs directories and offer these to you as real world test data from the great unwashed user land down under.
The config that is causing trouble is "DAC8X Streamer In 2 flat 6K-Horn out.yml" that I have converted to "V3 DAC8X Streamer in 2 Flat 6 K-Horn out.yml". CamillaDSP is running on a RPi 5.
Henrik, I have converted some v2 configs to v3 and they work fine. However I have a config that is causing me grief. I tried converting it in full but when in the "pipeline" tab and I add a mixer I get a blank screen.
So, I have zipped up the config and coeffs directories and offer these to you as real world test data from the great unwashed user land down under.
The config that is causing trouble is "DAC8X Streamer In 2 flat 6K-Horn out.yml" that I have converted to "V3 DAC8X Streamer in 2 Flat 6 K-Horn out.yml". CamillaDSP is running on a RPi 5.
Thanks for the feedback!
No there is no "mm" unit for the delay, yet at least. I have it on my list of possible future new features.
@Wirrunna I'm playing around with your files but I have not been able to reproduce the problem. Can you try to trigger it with the browser console open? There could be some useful error message. Also check the logs from the backend. You will likely see something there with "KeyError: 'ramp_time'". Just ignore that one. I have fixed it but it should not be able to cause the issue you describe.
Henrik, thank you for testing.
Using a laptop and Chrome browser makes the problem happen.
I altered my procedure for conversion to save the config immediately following the import and before accessing the pipeline tab. Checking shows that the config was actually created and saved, but accessing the pipeline tab brings up the blank screen, reload brings back the previously viewed config. Loading the newly created config works fine.
The log file screen is attached as two jpgs.
If I use the RPi 5 running CamillaDSP with HDMI 10.1" attached screen, USB keyboard/mouse and Chromium browser, GUI 127.0.0.1:5005/gui/index.html
1. in Files tab click "New blank config"
2. in Files tab click "Import config"
3. Select "DAC8X_2Flat_6KHorn.yml", tick all sections and click import
4. Confirm import was successful and close selection dialog
5. Enter name for new config and save as "V3 Test import DAC8X 2flat 6Khorn.yml"
the config is saved and going to the Pipeline tab works
So, I should have tested further, the import works and by saving then reloading the new config into the GUI the pipeline can be accessed.
There is still the "Additional properties are not allowed ('channel' was unexpected)" message in the pipeline and the filters being allocated to "all" channels rather than the channel that the original was in. The 'channel' unexpected message is easily fixed by editing the .yml file and deleting the "channel:" line and then selecting the correct channel for the filters in the pipeline gui.
Using a laptop and Chrome browser makes the problem happen.
I altered my procedure for conversion to save the config immediately following the import and before accessing the pipeline tab. Checking shows that the config was actually created and saved, but accessing the pipeline tab brings up the blank screen, reload brings back the previously viewed config. Loading the newly created config works fine.
The log file screen is attached as two jpgs.
If I use the RPi 5 running CamillaDSP with HDMI 10.1" attached screen, USB keyboard/mouse and Chromium browser, GUI 127.0.0.1:5005/gui/index.html
1. in Files tab click "New blank config"
2. in Files tab click "Import config"
3. Select "DAC8X_2Flat_6KHorn.yml", tick all sections and click import
4. Confirm import was successful and close selection dialog
5. Enter name for new config and save as "V3 Test import DAC8X 2flat 6Khorn.yml"
the config is saved and going to the Pipeline tab works
So, I should have tested further, the import works and by saving then reloading the new config into the GUI the pipeline can be accessed.
There is still the "Additional properties are not allowed ('channel' was unexpected)" message in the pipeline and the filters being allocated to "all" channels rather than the channel that the original was in. The 'channel' unexpected message is easily fixed by editing the .yml file and deleting the "channel:" line and then selecting the correct channel for the filters in the pipeline gui.
Attachments
Ok that channel message is odd. Can you also check the browser JavaScript console?
https://balsamiq.com/support/faqs/browserconsole/
Open the console, then follow the steps to get the blank page, and see if there are any errors in the console.
https://balsamiq.com/support/faqs/browserconsole/
Open the console, then follow the steps to get the blank page, and see if there are any errors in the console.
Henrik, here are the errors, but this is a distraction. Somewhere we should document the procedure to convert a V1 or V2 config to V3 -
1. in Files tab click "New blank config"
2. in Files tab click "Import config"
3. Select the .yml config to be converted, tick the wanted sections and click import
4. Confirm import was successful and close selection dialog
5. Enter name for new config and save.
6. Load the converted config into the GUI and check the pipeline steps and modify and save if necessary.
In my view the only problem is the cosmetic one of the conversion leaving the "channel: n" line in the config that results in the "Additional properties are not allowed ('channel' was unexpected)" message.
Attachments
Never mind, I managed to trigger the problem myself. New gui version (hopefully) soon!
That's a relief, I was going mad trying to get the browser JavaScript console. It is only a nuisance if you haven't saved a converted config before you go to the pipeline tab.
The pipeline plot in V3 - I do like the popup information when the mouse pointer is hovered over a step, made me go back to the Filters tab and fill in the description info for those with none. Pics show a plot with individual filters collapsed into a filter step, then when mouse pointer is hovered over a step the popup info shows the steps.
Attachments
When one use REW to generate PEQs they get the same name + a digit - perhaps grouping all PEQs in one pipeline symbol if starting with the same characters?
//
//
TNT , First pic below is the group of REW generated PEQs, second pic is the pipeline plot showing all the individual PEQs, then in my post above yours, the pic titled config Plot is the Pipeline plot after clicking the "Collapse individual filters into filter steps" icon. The last pic "Config plot showing info" shows as a popup the individual filters.
So Henrik is doing what you are suggesting.
Attachments
New gui here: https://github.com/HEnquist/camillagui-backend/releases/tag/v3.0.0-beta.3
The main problem was that old configs were not being migrated if you clicked the existing files in the lower part of the import dialog. The migration was only done if you clicked the "CamillaDSP config" button in the "Upload new config file" part on the top. So clicking an existing file just imported it in the old format. That is fixed now so that migration always happens.
I also added some improvements to the table, to let it show more information about the config files. It doesn't allow loading old files directly any more, and invalid files cannot be selected as the active file. I hope these changes will avoid a lot of errors and make the file listing easier to use.
The main problem was that old configs were not being migrated if you clicked the existing files in the lower part of the import dialog. The migration was only done if you clicked the "CamillaDSP config" button in the "Upload new config file" part on the top. So clicking an existing file just imported it in the old format. That is fixed now so that migration always happens.
I also added some improvements to the table, to let it show more information about the config files. It doesn't allow loading old files directly any more, and invalid files cannot be selected as the active file. I hope these changes will avoid a lot of errors and make the file listing easier to use.
Henrik, Just tried beta 3 converting a V2 config and it worked perfectly. A converted config is playing now, the pipeline conversion worked this time.
The Valid and Version columns in the Files tab are a good enhancement, as is the ability to zoom the plot with the mouse wheel.
The Valid and Version columns in the Files tab are a good enhancement, as is the ability to zoom the plot with the mouse wheel.
Attachments
Last edited:
I am running the next30 with the beta 3 gui on raspberry pi with bookworm desktop installed. Can't seem to be able to add a mixer to the pipeline using the + in the pipeline tab. Clicking on the + adds a pipeline step which defaults to a filter, when I change the filter to mixer the screen blanks and the gui is no longer responsive. Seem to be getting the same behaviour on firefox and edge. I tried with beta 2 and getting the same. I am able to manually add a mixer to the pipeline by editing the yml file.
I have not managed to reproduce this on my end. Do you have any mixers defined? Could you try doing it once with the javascript console open? There should be some error message, most likely something about an unhandled exception. See https://www.diyaudio.com/community/...overs-room-correction-etc.349818/post-7813084
I can confirm this.
Edit: in Chrome browser.
First pic is when + adds step, second pic is when you select mixer
Attachments
Last edited:
Thanks! Found the problem 🙂
https://github.com/HEnquist/camillagui-backend/releases/tag/v3.0.0-beta.4
https://github.com/HEnquist/camillagui-backend/releases/tag/v3.0.0-beta.4
