This feature already worked in most of TV's then you set delay of bluetooth and set on multiple audio ouput...on my tv i see the step in 10ms...not so precisely but works fine for tv...since @frd__ made a lot of work for right clocking the source just putting usleep(param); send_to_dac(dac2); can make a trick.
IIUC you want to play both dacs in the same area. Then every variable millisecond makes a difference.
And if the track takes 10 minutes? Or an hour-long track made gapless from several tracks?
Clock synchronization/async issues are commonly faced in audio. Correct solutions are rather complex, and involve more than just trying to pause one stream against the other with usleep (which guarantees minimum delay, not maximum e.g. https://stackoverflow.com/a/8970637/15717902 ).
If you want to play, just use the alsa multi plugin for testing, but this is what the founder of alsa says: https://github.com/alsa-project/alsa-lib/issues/273#issuecomment-1268568415
Kernel driver can handle timings issues with better accuracy than usleep,,,many options to discuss.
What do you really want to accomplish? One dac for woofers, another for tweeters? Or something else?
@HenrikEnquist yes i think this usefull to try many configurations with ability to mix / to switch / to separate. At my setup first i'd try full range + tweeters and choose an lfe for sub..
@promisc : If you want to experiment, then IMO the custom-compiled and extremely cut-down (not even alsa plugins available) wtfplay does not seem to be the best platform. IMO a standard linux distribution would serve the purpose much better as all the tools are available there for you.
Good morning everyone,
I have a problem with the player and I would be very grateful to anyone who can help me.
On my old PC I used wtfplay with great satisfaction,
unfortunately now I can't run it on the new PC, composed of a b650 motherboard and a ryzen 7600 cpu.
Once loaded usb when I go to select the kernel it gives me this error
error: no such device: /vmlinuz.057.
error: file/vmlinuz.057' not found.
error: you need to load the kernel first.
Press any key to continue..
I'll start by saying that I tried the amda8 amdbd1 corei7-avx iso, disabled secure boot from the bios, switched the legacy - uefi modes but the error persists.
You want to tell me that the program is not compatible with the ryzen or the b650, I haven't found any info anywhere.
Thank you and greetings from Italy! Sorry for my English
I have a problem with the player and I would be very grateful to anyone who can help me.
On my old PC I used wtfplay with great satisfaction,
unfortunately now I can't run it on the new PC, composed of a b650 motherboard and a ryzen 7600 cpu.
Once loaded usb when I go to select the kernel it gives me this error
error: no such device: /vmlinuz.057.
error: file/vmlinuz.057' not found.
error: you need to load the kernel first.
Press any key to continue..
I'll start by saying that I tried the amda8 amdbd1 corei7-avx iso, disabled secure boot from the bios, switched the legacy - uefi modes but the error persists.
You want to tell me that the program is not compatible with the ryzen or the b650, I haven't found any info anywhere.
Thank you and greetings from Italy! Sorry for my English
Hi @Argentax,
The most up to date AMD computer that I have at my disposal is Lenovo X13 with Ryzen 6650U. I have just checked and wtfplay-live booted successfully in UEFI mode with Secure Boot disabled and Legacy Boot disabled.
Sadly, I have no access to a hardware with B650 chipset. What is the model of your motherboard exactly? I can check the BIOS documentation.
I understand that you are trying to boot in the Legacy mode. Have you tried booting in UEFI? If so, what is the result?
F
The most up to date AMD computer that I have at my disposal is Lenovo X13 with Ryzen 6650U. I have just checked and wtfplay-live booted successfully in UEFI mode with Secure Boot disabled and Legacy Boot disabled.
Sadly, I have no access to a hardware with B650 chipset. What is the model of your motherboard exactly? I can check the BIOS documentation.
I understand that you are trying to boot in the Legacy mode. Have you tried booting in UEFI? If so, what is the result?
F
Hi @Frd_,
first of all thanks for your interest!
my card is an msi b650 tomahawk.
I tried to set the bios in both Legacy and UEFI mode, but to give you a 100% sure answer give me time to get home and I'll try again tonight, I wouldn't want to have made some mistakes given my little experience with the various bios menus.
Finally I take this opportunity to ask you if the amda8 iso is the most suitable for ryzen 7600.
first of all thanks for your interest!
my card is an msi b650 tomahawk.
I tried to set the bios in both Legacy and UEFI mode, but to give you a 100% sure answer give me time to get home and I'll try again tonight, I wouldn't want to have made some mistakes given my little experience with the various bios menus.
Finally I take this opportunity to ask you if the amda8 iso is the most suitable for ryzen 7600.
guys I confirm that it works. I changed the bios to CSM mode. Now I'll proceed with the configuration but there shouldn't be any problems since I already have experience with the old PC. Thanks again Frd_
What is the actual cause of the error message 'no such device: /vmlinuz.057'? IIUC it's grub not finding the kernel image on the USB flash, but why is that? Apparently grub gets to start (so the bios boot layer does start grub), but grub cannot continue. Is it because incorrect grub is started (e.g. the legacy bios grub instead of the UEFI grub) and that grub is not configured correctly? The booting issues in modern PCs with legacy/UEFI never cease to amaze me.
Thanks!
Thanks!
Argentax, good stuff! I am happy to hear that you managed to boot the system.
phofman, there are actually two bootloaders: isolinux and grub. Grub is only used when booting in UEFI mode and it appears that this is the the case here. "you need to load the kernel first" comes from Grub. All Grub needs to boot is the access to EFI pairttion.
And this is when I am puzzled. Initially I thought that the firmware does not like the old DOS partition table, but it managed to load the bootloader from the DOS partition. Then the firmware decided not to expose DOS paritions to Grub? Does not make sense.
Then there is a question about the compatiblity mode (CSM). What does it do exactly?
To be honest this is not the first case of weird UEFI behaviour I am hearing about. I had a case when a PC refused to load the bootloader and was dropping straight to UEFI shell. When I executed the bootloader from manually from the shell, it was all file. Eventually I figured out what that was. The firmware was looking for the bootloader in the root directory of the EFI partition.
phofman, there are actually two bootloaders: isolinux and grub. Grub is only used when booting in UEFI mode and it appears that this is the the case here. "you need to load the kernel first" comes from Grub. All Grub needs to boot is the access to EFI pairttion.
And this is when I am puzzled. Initially I thought that the firmware does not like the old DOS partition table, but it managed to load the bootloader from the DOS partition. Then the firmware decided not to expose DOS paritions to Grub? Does not make sense.
Then there is a question about the compatiblity mode (CSM). What does it do exactly?
To be honest this is not the first case of weird UEFI behaviour I am hearing about. I had a case when a PC refused to load the bootloader and was dropping straight to UEFI shell. When I executed the bootloader from manually from the shell, it was all file. Eventually I figured out what that was. The firmware was looking for the bootloader in the root directory of the EFI partition.
Buongiorno a tutti,
Purtroppo, tra lavoro, famiglia e cane, ho poco tempo.
Comunque volevo informarti che, utilizzando il BIOS in modalità CSM, all'avvio il PC rileva la stessa USB due volte:
in UEFI arriva Flash generico (2a riga)
nel generico Flash Disk (5a riga)
Se si avvia la prima opzione, il PC si carica finché non viene scelto il kernel, dopodiché viene visualizzato l'errore descritto sopra.
Se invece si avvia la seconda opzione, il programma funziona quasi correttamente.
Ora ho scelto la ISO amdbd1, primo kernel (credo 53). Ho configurato subito alsamixer (se lo faccio dopo aver disabilitato le altre schede, il comando smette di funzionare).
Ho selezionato Xonar DX con F6, attivato il volume con M, eseguito wtfsetup in modalità DSD e impostato i valori. Infine, con fwtfcui, ho selezionato i file FLAC, che suonano benissimo.
Il problema è che, riavviando, le impostazioni non vengono salvate. Sbaglio qualcosa? Ricordo che con le versioni precedenti trovavo tutto esattamente come l'avevo impostato.
Edit Tonight I'll try to set up a partition with Rufus, I think that's why it doesn't save 🙂
Purtroppo, tra lavoro, famiglia e cane, ho poco tempo.
Comunque volevo informarti che, utilizzando il BIOS in modalità CSM, all'avvio il PC rileva la stessa USB due volte:
in UEFI arriva Flash generico (2a riga)
nel generico Flash Disk (5a riga)
Se si avvia la prima opzione, il PC si carica finché non viene scelto il kernel, dopodiché viene visualizzato l'errore descritto sopra.
Se invece si avvia la seconda opzione, il programma funziona quasi correttamente.
Ora ho scelto la ISO amdbd1, primo kernel (credo 53). Ho configurato subito alsamixer (se lo faccio dopo aver disabilitato le altre schede, il comando smette di funzionare).
Ho selezionato Xonar DX con F6, attivato il volume con M, eseguito wtfsetup in modalità DSD e impostato i valori. Infine, con fwtfcui, ho selezionato i file FLAC, che suonano benissimo.
Il problema è che, riavviando, le impostazioni non vengono salvate. Sbaglio qualcosa? Ricordo che con le versioni precedenti trovavo tutto esattamente come l'avevo impostato.
Edit Tonight I'll try to set up a partition with Rufus, I think that's why it doesn't save 🙂
Attachments
Last edited:
Good morning everyone, I'm about to become your worst nightmare, unfortunately even using the software recommended in the guide, Win32 Disk Image, the program does not want to know about saving the configuration and every reboot I have to reconfigure everything. I will try to use another memory even if it seems strange to me that the problem is that.
Has it ever happened to anyone? I used the amdbd1 version, I will keep you updated in case anyone has the same problem as me.
Has it ever happened to anyone? I used the amdbd1 version, I will keep you updated in case anyone has the same problem as me.