Login at Kodi Home

Diazz · (This post was last modified: 2012-03-01, 00:08 by Diazz.)

nvm

aaronb · 2012-03-01, 05:15

You can use 7zip to batch unrar all of them at the command line

**Sureguy** · 2012-03-01, 15:28

jmarshall Wrote:No need to unrar your movies as long as they're stored uncompressed. If you have movies stored in .rar compressed, then yes, unrar them.

The only problem with this is that you have to check each movie and show to see if it's compressed or not. If you're going to go to the trouble of doing that you might as well just automatically uncompress all new files to avoid the issue.

KeTonic · 2012-04-20, 02:38

There is plenty of good reasons beside "sharing" to keep it in a rar format.

Here is two good ones:
Filesize for old OS and HDD.
If the file gets corrupted, you only have to download a 48mb fil instead of a 4-8gb mkv fil.

(2012-03-01, 15:28)Sureguy Wrote: The only problem with this is that you have to check each movie and show to see if it's compressed or not. If you're going to go to the trouble of doing that you might as well just automatically uncompress all new files to avoid the issue.

No you don´t, i get 4 warnings when i go into my movie library about witch movies that are compressed. No need to manually check it.

d'Wooluf · 2012-04-20, 04:24

If you unrar them all (successfully), you'll at least know that the movies will probably play. It's a pain to find a corrupted archive half way through the movie.
Total Commander is one example of a program, that will unpack multiple archives. Highlight the first file in each archive set, Alt-F9 and you're set. You can do this on your 30-day evaluation copy.

flyingrat · 2012-10-10, 14:23

I think I found the root cause. It seem the scan file/directory function has a problem cooping with rar archives that are split like this:

Code:
File.part01.rar

File.part02.rar

File.part03.rar

Instead of more commonly:

Code:
File.rar

File.r01

File.r02

File.r03

**spiff** · 2012-10-10, 15:11

no, you didn't find anything....

that's just a consequence of the fact that stored archives are rar 2.5 (compatible), which uses the old naming format. compressed archives, however, are typically 3.0+ compatible, and that uses the new naming scheme.

flyingrat · (This post was last modified: 2012-10-11, 08:25 by flyingrat.)

(2012-10-10, 15:11)spiff Wrote: no, you didn't find anything....

that's just a consequence of the fact that stored archives are rar 2.5 (compatible), which uses the old naming format. compressed archives, however, are typically 3.0+ compatible, and that uses the new naming scheme.

Not quite, actually had some problems with some 2.9 archives too. Does the xbmc rar-libs only cope with vers 3+ and the new naming naming convention (in strict combination) thus what is the root cause and what can be done about it?

jmarshall · 2012-10-11, 08:33

You could read posts 2, 3, and 15 for a start, which explain exactly what the problem is: They're compressed rars, as opposed to stored rars.

flyingrat · 2012-10-11, 21:35

The was new to me. By design or due to old rar libs?

jmarshall · 2012-10-11, 22:45

It's been like that since 2004 or so, for obvious reasons: A stored rar you can "just" read the movie straight out of the container (with seeking and everything). A compressed rar has to be fully extracted first to a temporary location.

As said above several times over, compressing already highly compressed media is stupid. Storing highly compressed media in uncompressed rars is perfectly reasonable.

locoguano · 2012-10-12, 05:54

In windows you can use SCRU. It can be set to watch certain folders and you can create filters to tell it where to extract the files.

flyingrat · (This post was last modified: 2012-10-12, 12:51 by flyingrat.)

(2012-10-11, 22:45)jmarshall Wrote: It's been like that since 2004 or so, for obvious reasons: A stored rar you can "just" read the movie straight out of the container (with seeking and everything). A compressed rar has to be fully extracted first to a temporary location.

As said above several times over, compressing already highly compressed media is stupid. Storing highly compressed media in uncompressed rars is perfectly reasonable.

I do concur it's rather stupid to compress already compressed data streams. But it still happens quite often thus it would be nice if xbmc could deal with it. Technically it should be possible to randomly seek within a compressed rar archive (like rar2fs, WinArchiver, WinMount, etc) but I don't know if it's worth the effort to implement it.

But before anything else I think we should clarify the error message and also fix the annoying backgrund thead that constantly pop ups the "Need to unpack..." yes/no question. Picking "No" should stop any further scans to that file. The backgrund thread is started automatically when entering library mode when there are missing meta data.

**spiff** · 2012-10-12, 12:52

the entire point of the dialog is to nag you into fixing your shit.

flyingrat · (This post was last modified: 2012-10-12, 13:23 by flyingrat.)

(2012-10-12, 12:52)spiff Wrote: the entire point of the dialog is to nag you into fixing your shit.

What a wonderful and constructive point of view, I really love helpful people. Cheers with a great big hug and a kiss from me to you!