07-28-2020, 11:28 AM
@moodenigo
@Dradder
I'm not in a position to test with such large source libraries nor is this post an endorsement of the change you propose, but you can make the change yourself with a single sqlite3 update statement.
Installing a new moOde release or making a new installation of an existing one? Just run the statement again.
Save the following code snippet into a file. let's call it update_max_output_buffer_size.sql, in user pi's home directory on your moOde player.
This is a single update statement which I split and indented for clarity. I followed it with an unnecessary select statement to print the contents of the entire table, just for confirmation.
To execute this on your moOde player from the command line:
As always, make a backup copy of the database file before you muck around with it.
Regards,
Kent
@Dradder
I'm not in a position to test with such large source libraries nor is this post an endorsement of the change you propose, but you can make the change yourself with a single sqlite3 update statement.
Installing a new moOde release or making a new installation of an existing one? Just run the statement again.
Save the following code snippet into a file. let's call it update_max_output_buffer_size.sql, in user pi's home directory on your moOde player.
Code:
/* make the change */
update cfg_mpd
set value=262144
where
param='max_output_buffer_size';
/* show the modified table */
select * from cfg_mpd;
This is a single update statement which I split and indented for clarity. I followed it with an unnecessary select statement to print the contents of the entire table, just for confirmation.
To execute this on your moOde player from the command line:
Code:
sqlite3 /var/local/www/db/moode-sqlite3.db < update_max_output_buffer_size.sql
As always, make a backup copy of the database file before you muck around with it.
Regards,
Kent