INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: 'Something went wrong with playback'  (Read 7348 times)

deckman

  • Recent member
  • *
  • Posts: 19
'Something went wrong with playback'
« on: March 04, 2016, 04:41:42 pm »

Hi, I'm on a steep learning curve as I'm relatively new to MC21 and Linux (mint) but so far I have been pleased with both. There is however an issue that I would like some help with. I am running MC21 as trial to make sure it works OK with Linux mint (17.3) My music collection is stored in FLAC on a 3 TB WD red. (The OS runs off an SSD) I haven't tried all the functions but most stuff seams to work OK except that when I first start MC21 and try to play I get the following error message 'something went wrong with playback' The file could not be found. Check that the filename in the library matches the filename on disk' If I go to a music file and 'open with' jriver it plays fine and then I can play all the files in the library. I can close MC21 and open it and it will play fine until I restart the computer. Its like MC21 is forgetting what is in the library.  Is this a limitation of the trial version of MC21?

Thanks
Logged

bob

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 13817
Re: 'Something went wrong with playback'
« Reply #1 on: March 04, 2016, 04:43:50 pm »

Hi, I'm on a steep learning curve as I'm relatively new to MC21 and Linux (mint) but so far I have been pleased with both. There is however an issue that I would like some help with. I am running MC21 as trial to make sure it works OK with Linux mint (17.3) My music collection is stored in FLAC on a 3 TB WD red. (The OS runs off an SSD) I haven't tried all the functions but most stuff seams to work OK except that when I first start MC21 and try to play I get the following error message 'something went wrong with playback' The file could not be found. Check that the filename in the library matches the filename on disk' If I go to a music file and 'open with' jriver it plays fine and then I can play all the files in the library. I can close MC21 and open it and it will play fine until I restart the computer. Its like MC21 is forgetting what is in the library.  Is this a limitation of the trial version of MC21?

Thanks
There are no limitations in the trial version.
Are the drives that the files are on mounted locally on the Linux box or network/nas shares?
Logged

mwillems

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 5233
  • "Linux Merit Badge" Recipient
Re: 'Something went wrong with playback'
« Reply #2 on: March 05, 2016, 08:22:36 am »

Hi, I'm on a steep learning curve as I'm relatively new to MC21 and Linux (mint) but so far I have been pleased with both. There is however an issue that I would like some help with. I am running MC21 as trial to make sure it works OK with Linux mint (17.3) My music collection is stored in FLAC on a 3 TB WD red. (The OS runs off an SSD) I haven't tried all the functions but most stuff seams to work OK except that when I first start MC21 and try to play I get the following error message 'something went wrong with playback' The file could not be found. Check that the filename in the library matches the filename on disk' If I go to a music file and 'open with' jriver it plays fine and then I can play all the files in the library. I can close MC21 and open it and it will play fine until I restart the computer. Its like MC21 is forgetting what is in the library.  Is this a limitation of the trial version of MC21?

Thanks

It's likely that the OS is not mounting the WD Red on boot for some reason, and navigating to it in Nemo (the file manager) is mounting it (which is why JRiver can see it afterwards).  If that's the case, JRiver will not be the only program that will have this issue, so it's worth trying to work out your mount options to ensure the drive is being mounted correctly.

As bob asked, is it a local drive or a networked drive?  Is it encrypted?  Anything else special about it?  If it's just a normal internal drive with no special features, can you do the following:

Navigate to the music files using the file manager (to make sure the drive is mounted).  Then open a terminal and then post the output of the following commands so we can see them.

Code: [Select]
lsblk
Code: [Select]
cat /etc/fstab
Logged

deckman

  • Recent member
  • *
  • Posts: 19
Re: 'Something went wrong with playback'
« Reply #3 on: March 05, 2016, 11:18:50 am »

Thanks for the quick response. The machine is an old pc that was retired when the disk crashed. So I put in a small SSD and installed Linux mint. The plan is to build a ‘proper’ media centre but for now I’m using it as a test bed to what works best and learn Linux. I think you are right about mounting the disk, (not something I have had to do before) It is a 'local' disk that was added after the OS was installed and I recall that when I first ran MC21 I only had a few music files but they were on the SSD and I don’t recall this issue cropping up then. I have attached a screen shot from the terminal as requested.

Logged

mwillems

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 5233
  • "Linux Merit Badge" Recipient
Re: 'Something went wrong with playback'
« Reply #4 on: March 05, 2016, 02:18:59 pm »

Thanks for the quick response. The machine is an old pc that was retired when the disk crashed. So I put in a small SSD and installed Linux mint. The plan is to build a ‘proper’ media centre but for now I’m using it as a test bed to what works best and learn Linux. I think you are right about mounting the disk, (not something I have had to do before) It is a 'local' disk that was added after the OS was installed and I recall that when I first ran MC21 I only had a few music files but they were on the SSD and I don’t recall this issue cropping up then. I have attached a screen shot from the terminal as requested.

That confirms my suspicion.  For purposes of Linux learning I'll explain some theory instead of just telling you what to do:

lsblk lists the block devices (typically disk drives) on your system.  You can see that you have three block devices:

1) sda: The "sd" originally stood for SCSI device, but the category also includes SATA devices now (IDE drives and removable media have different prefixes).  This drive has three partitions on it, each denoted by adding a number after the "sda" (although the swap is curiously numbered "5", did the drive previously have more partitions?).  In any case you can see that the partition sda1 is mounted at "/" which means it's the root partition.  So I'm assuming that's your SSD.

2) sdb: This is your second SCSI/SATA drive and based on the size I'm assuming it's your WD Red.  It has one partition (sdb1) that is mounted under /media.  /media or /run are where linux systems mount transient or removable media (like cd roms or external hard drives).  The fact that it's mounted there (using a long random looking mount point) is a strong hint that the partition is being auto-mounted when accessed by the file manager rather than mounted at boot.

3) sr0 usually refers to a CD-ROM drive.  You'll note that it's mounted under /media.

So with that in hand we can have a look at the fstab, which stands for Filesystem Table and is where the OS looks to find instructions on how and where to mount drives at boot.  You can see that there are only three lines that aren't commented out: it's only auto-mounting the root partition, the swap partition, and a floppy disk drive (that doesn't appear to be connected to the system anymore based on the lsblk?).  

That confirms that sdb1 isn't being mounted at boot.  So you need to add a line to your fstab file to mount sdb1.  The entries are structured as six entries separated by spaces or tabs (any number of spaces is the same as one space, so it's important there aren't spaces within the entries).
Code: [Select]
/device/to/be/mounted    /place/to/mount/it    filesystemtype  options  dump   pass

The device to be mounted can be expressed either as a filesystem location (e.g. /dev/sdb1)or a universal unique identifier (UUID).  Looking at your fstab, your root partition is being mounted by UUID instead of filesystem location if you want to see what a UUID looks like.  UUIDs are "safer" as the block device ordering is not guaranteed to be stable across reboots (but usually is), with the result that sometimes what is sda today may be sdb tomorrow.  If you experience that, you'll need to use UUID's in your fstab.  The blkid command will tell you the UUIDs of all your block devices (but typically needs to be run as root or with sudo).

However, for most systems the block device ordering is stable enough unless you're adding or removing disks, so filepath works just fine. So we'll start with that because it's easier. Assuming your WD Red is formatted ext4 like your root partition you'd want to add a line like this to your fstab:
Code: [Select]
/dev/sdb1    /home/mh/data   ext4  rw,defaults  0  0

You would need to make a directory called "data" in your user's home directory (/home/mh) first for this to work.  You'll also need to edit the fstab as a privileged user (i.e. use sudo).  Ask if you need any tips. If you find that your wd red is not consistently sdb, you'll need to use a UUID for the first entry instead.

More info here: https://wiki.archlinux.org/index.php/fstab

Hope this helps!



Logged

deckman

  • Recent member
  • *
  • Posts: 19
Re: 'Something went wrong with playback'
« Reply #5 on: March 05, 2016, 03:59:05 pm »

Many thanks, that make sense, I really appreciate you taking the time to explain this. I think I formatted the disk for NTFS but will take some time over the next few days to fully understand. For now, I’m just relieved to know what the issue is and that it is fixable.  I have some more hardware mods to do and I want to see if I can get my CD ripping software, DB poweramp to run in wine. (Then I think I will be fully cured of Microsoft.) At some point I will do a complete clean install of mint, more for the experience than necessity, When I do this if I have root and swap on the SSD then home on the WD red I assume this would be a more 'elegant' solution? (I understand there are advantages to having home on a separate partition when it come to updating.)
Logged

mwillems

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 5233
  • "Linux Merit Badge" Recipient
Re: 'Something went wrong with playback'
« Reply #6 on: March 05, 2016, 06:25:07 pm »

Many thanks, that make sense, I really appreciate you taking the time to explain this. I think I formatted the disk for NTFS but will take some time over the next few days to fully understand.

Ntfs disks can be a little tricky on Linux, but most of the bugs have been ironed out in recent years.  If it's an ntfs disk just substitute "ntfs" for "ext4" in the fstab entry.

Quote
For now, I’m just relieved to know what the issue is and that it is fixable.  I have some more hardware mods to do and I want to see if I can get my CD ripping software, DB poweramp to run in wine. (Then I think I will be fully cured of Microsoft.)

If you figure out how to do this, do let me know; I've had no success running dBpoweramp in wine and would love to know that it's still possible.  Meanwhile, I use soundjuicer on Linux when I'm not in front of a windows box: it pulls from musicbrains database and does (to my knowledge) secure ripping (but not accurate rip obviously as that's proprietary).  Sooner or later JRiver for linux might support ripping as well, but that's still a little ways off as I understand it.

Quote
At some point I will do a complete clean install of mint, more for the experience than necessity, When I do this if I have root and swap on the SSD then home on the WD red I assume this would be a more 'elegant' solution? (I understand there are advantages to having home on a separate partition when it come to updating.)

For sure there can be advantages to having a separate home partition, especially with distros like Mint where you reinstall once or twice a year.  Personally, I keep my data segregated in directories under home because a lot of user configuration winds up in the root of home and I want to be able to blow away all my configuration easily while keeping my data.  But your proposed plan is a good one, especially if you're planning to stick with Mint.. 

Once you've spent some more time with Linux and are more comfortable on the command line, I'd highly recommend having a look at Arch.  Definitely not for beginners (a much steeper learning curve), but you learn a lot and never have to reinstall because it's a rolling release.  But one step at a time  ;)
Logged

Awesome Donkey

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 7768
  • Autumn shade...
Re: 'Something went wrong with playback'
« Reply #7 on: March 05, 2016, 10:22:34 pm »

Does Mint not include the GUI-based Disks like Ubuntu does? Makes mounting volumes much, much easier.
Logged
I don't work for JRiver... I help keep the forums safe from "male enhancements" and other sources of sketchy pharmaceuticals.

Windows 11 24H2 Update 64-bit + Ubuntu 24.10 Oracular Oriole 64-bit | Windows 11 24H2 Update 64-bit (Intel N305 Fanless NUC 16GB RAM/500GB M.2 NVMe SSD)
JRiver Media Center 33 (Windows + Linux) | iFi ZEN DAC 3 | JBL 306P MkII Studio Monitors | Audio-Technica ATH-M50x Headphones

mwillems

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 5233
  • "Linux Merit Badge" Recipient
Re: 'Something went wrong with playback'
« Reply #8 on: March 05, 2016, 11:23:39 pm »

Does Mint not include the GUI-based Disks like Ubuntu does? Makes mounting volumes much, much easier.

It may; I don't run Mint/Ubuntu at all so I can't speak to that.  It probably does since the file manager is automounting the drive for him.  But it only mounts it when he navigates to it, not automatically at boot. Editing the fstab is a reliable way of permanently changing the mount on boot options.  Most GUI mounters I've interacted don't reliably remount things at boot, but if Disks will do that, it may well be easier and OP should investigate it.  

In any case learning about the fstab is useful for 'nix users sooner or later; eventually he may want to socket mount a networked drive on boot or something which is trivial in the fstab, but not so easy from any GUI utility I've ever seen.
Logged

deckman

  • Recent member
  • *
  • Posts: 19
Re: 'Something went wrong with playback'
« Reply #9 on: March 08, 2016, 01:30:15 pm »

Thank you all for your help. After a few attempts the drive now mounts at start and jriver seams to be playing everything OK. I have tried dbpoweramp in wine but with limited success as dbpoweramp does not recognise there is a CD drive and I have not been able to fix this. I did have some success with ‘Morituri’  (http://cd-rw.org/t/make-perfect-audio-cd-rips-using-morituri-linux/24) but it is painfully slow compared to dbpoweramp so the search for an ‘accurate rip on Linux goes on. Over the last few weeks I have installed loads of stuff, played with the terminal, changed all the settings I could find and despite my ‘irresponsible’ behaviour I have yet to ‘break Linux mint. MC21 has also remained stable and works well with Gizmo on the android tab.

So now I know what I want and how I’m going to configure it all I can wipe all the drives, start again with a clean install and purchase MC21.

Thanks again for all your help. :)
Logged

mwillems

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 5233
  • "Linux Merit Badge" Recipient
Re: 'Something went wrong with playback'
« Reply #10 on: March 08, 2016, 02:21:42 pm »

Thank you all for your help. After a few attempts the drive now mounts at start and jriver seams to be playing everything OK. I have tried dbpoweramp in wine but with limited success as dbpoweramp does not recognise there is a CD drive and I have not been able to fix this. I did have some success with ‘Morituri’  (http://cd-rw.org/t/make-perfect-audio-cd-rips-using-morituri-linux/24) but it is painfully slow compared to dbpoweramp so the search for an ‘accurate rip on Linux goes on.0

You might have trouble finding an accurate rip solution as it relies on a proprietary database.  Secure rip is what morituri (and JRiver on Windows) do, which involves re-reading the disc to ensure one is getting the same reading each time.  It takes at least twice as long as accurate rip for that reason (longer if it has trouble reading the disk as it will try re-reading until it gets a "clean" read).

Quote
Over the last few weeks I have installed loads of stuff, played with the terminal, changed all the settings I could find and despite my ‘irresponsible’ behaviour I have yet to ‘break Linux mint. MC21 has also remained stable and works well with Gizmo on the android tab.

So now I know what I want and how I’m going to configure it all I can wipe all the drives, start again with a clean install and purchase MC21.

Thanks again for all your help. :)

My pleasure! Linux is much more fun when you dig around under the hood and break things.  Happy Hunting!
Logged
Pages: [1]   Go Up