More > JRiver Media Center 23 for Linux
Problem importing large library
blgentry:
It definitely has nothing to do with library size. MC has users that have 500,000 or more files in their libraries.
You should try manually importing some of the files that have failed to import and see what happens.
I'm also stumped by this...
Brian.
madbrain:
--- Quote from: blgentry on October 02, 2017, 05:04:12 am ---It definitely has nothing to do with library size. MC has users that have 500,000 or more files in their libraries.
You should try manually importing some of the files that have failed to import and see what happens.
I'm also stumped by this...
Brian.
--- End quote ---
Well, I copied just the 12,225 MP3 files to a separate folder on the Odroid, created another library, and imported just that new folder in MC23 on Linux. All of the MP3 files imported successfully, and still showed up afterwards.
Most of the other 38k files are WMA.
I tried your suggestion. I went back to the original problematic after will import, with only 5003 files showing up.
I then imported a single folder of 28 WMA files that were missing.
The import succeeded. After I dismissed the import dialog, those files were still there, and the library size at the bottom was still 5031 files vs 5003 before.
So, somehow, things go bad when I import the entire tree, but are OK if I import a single folder. I have hundreds of folders with WMA files in them, though. It's not realistic to import them each one at a time. The GUI on the Odroid is abysmally slow, also, which makes all these attempts in MC very difficult. We are talking 4-5 seconds between clicks, easily.
I only want to use the box as a media server and nothing more.
As a file and network server, the box does great, it can stream 600 Mbit/s over Gigabit from a SATA NAS drive connected via USB 3.
blgentry:
Sounds like that thing is way underpowered. You might consider a "real" computer instead.
I use a Raspberry Pi 3 as one of my MC systems. But I don't import files into the Pi directly. Instead, what I do is this:
1. Copy all of my music files from my main MC installation to an external drive. Then I make a Library Backup and store the backup zip file on this same drive.
2. Mount this drive on the Pi on a specific path like /Volumes/my_drive_name . Then the Pi can see all of the files.
3. Using MC on the Pi, I restore the backup zip file that I previously stored on the external drive. Once that's done, MC sees entries for ALL of my music.
4. However, MC thinks all of that music is MISSING, because the file paths are wrong. It's still using the file paths from my main MC system. So, I select all files and use the Rename, Move, and Copy files tool in UPDATE mode. I use the Find & Replace template to change the file paths on all of these files to where they now reside on the external drive.
5. Once I verify that MC can see all of my files again, I rebuild thumbnails. This is necessary because on-the-fly thumbnail generation can crash MC on the Pi because it can run it out of memory. Pre-generating all of the thumbnails avoids this.
This procedure keeps me from ever having to import files. The real benefit is that ALL of my library fields are retained, exactly as I want them, from my main MC computer, to my MC on Pi.
I'm not sure if this procedure would work for you and your workflow, but you might give it a try and see.
Good luck.
Brian.
madbrain:
--- Quote from: blgentry on October 02, 2017, 07:24:56 am ---Sounds like that thing is way underpowered. You might consider a "real" computer instead.
I use a Raspberry Pi 3 as one of my MC systems. But I don't import files into the Pi directly. Instead, what I do is this:
1. Copy all of my music files from my main MC installation to an external drive. Then I make a Library Backup and store the backup zip file on this same drive.
2. Mount this drive on the Pi on a specific path like /Volumes/my_drive_name . Then the Pi can see all of the files.
3. Using MC on the Pi, I restore the backup zip file that I previously stored on the external drive. Once that's done, MC sees entries for ALL of my music.
4. However, MC thinks all of that music is MISSING, because the file paths are wrong. It's still using the file paths from my main MC system. So, I select all files and use the Rename, Move, and Copy files tool in UPDATE mode. I use the Find & Replace template to change the file paths on all of these files to where they now reside on the external drive.
5. Once I verify that MC can see all of my files again, I rebuild thumbnails. This is necessary because on-the-fly thumbnail generation can crash MC on the Pi because it can run it out of memory. Pre-generating all of the thumbnails avoids this.
This procedure keeps me from ever having to import files. The real benefit is that ALL of my library fields are retained, exactly as I want them, from my main MC computer, to my MC on Pi.
I'm not sure if this procedure would work for you and your workflow, but you might give it a try and see.
Good luck.
Brian.
--- End quote ---
I have a Raspberry Pi 3 also. The GUI is faster on the Pi. But the I/O on the Pi sucks, about 1/5th as fast as the XU4.
XU4 actually is great hardware and much better specs than the Pi3. It's the software that's the weak point due to support not being as good. It doesn't make much sense that the desktop would render so slowly over VNC, but it does. MC UI is faster on the Pi but not usable as a media server.
https://www.slant.co/versus/5727/15521/~odroid-xu4_vs_raspberry-pi-3-model-b
I do use an external SATA drive (actually, SATA drive in a USB 3.1 dock) with my XU4, but I'm using an EXT4 file system as I have found that NTFS was way too slow on the XU4 - the write speed goes down to 5MBytes/s , and makes the XU4 unusable as a file server. On the PI3, the network is the bottleneck, not the drive or filesystem.
I can't mount the EXT4 on my Windows machine .
I can however copy all the files over LAN, and it is fast enough that way. That is what I did.
Some of the files did not copy from NTFS to EXT4 over LAN because of file system differences - might be restrictions on some characters and depth of directories, not sure.
But 99% of the files did copy.
I will try your method, but I feel like local file import should work. The XU4 has plenty fast I/O and it takes <20 min to scan all 50k files, fairly reasonable. Problem is that they don't actually show up in the library afterwards.
blgentry:
Something is clearly wonky with your setup. I think MC is the least likely problem, but I could certainly be wrong. It might be MC's fault. I suspect your hardware because you say it is so slow. Again, I could be wrong.
What would really tell the story is if MC on a "real" Linux PC imported all of your files successfully. If that failed also, the MC for Linux would be a real suspect in this import problem.
BTW, this is a separate debate, but MC on the Pi works just fine as a media player. I control mine with EOS remote on Android and it does everything I want. Maybe you have some sort of different use case from me.
Brian.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version