Eselter (guest) 03 Jun 2017 00:36
in discussion General discussion / ReScene » WinRAR pack (2.00 - 5.40)
Recent Forum Posts
Eselter (guest) 03 Jun 2017 00:36
in discussion General discussion / ReScene » WinRAR pack (2.00 - 5.40)
I received this email on May 11:
# name,organisation,country,email,comment
ReScene Feedback,,,ten.rrssrs.enoyreverofsitsopsihtenon|diassa#ten.rrssrs.enoyreverofsitsopsihtenon|diassa,"I Have python 34 installed so ReScene works with XP.
Two PC Python is not on a PC connected to the internet. How to get the source so can be built or used with Python 34.
At the very top of the Downloads page is a link: Download repository. Go to https://bitbucket.org/Gfy/pyrescene/downloads/ and click the link there because it can get outdated.
A year between builds is a lifetime. And it is nearly a year already since last release.
Depends on all the issues that were fixed. It takes some time for me to figure it out each time too. Run from source if you want the latest and greatest.
It would be helpful if you could allow us to download the source from Bitbucket as an archive. That we can feed to Python (show us how) so we can keep up to date.
It's provided by Bitbucket. Have a look at http://rescene.wikidot.com/pyrescene-installation but it includes more than you need.
Or better make more often releases such as at least once a month or sooner for major bugs found.
I won't include email since this is the same for anyone that doesn't want to mess there internet pc with source code stuff and terminals whatever to get source code.
If Bitbucket was Github there wouldn't be an issue since can download from Github source in an archive.
I think Bitbucket is user friendlier.
Hope this helps you understand that not everyone uses ReScene as you would. So able to help us keep up to date with you. After all how can code survive if people are not using the latest build so able to report problems they have noticed so making this code better for all.
The reason for everyone is the reason I don't include email here because this feedback is for everyone not just me alone.
A simple GUI for internet pc woud help to get all files related to any release on srrdb. Input release name and it downloads to folder we have set in the GUI options. This will save time having not to visit srrdb, searching each release we need and downloading individually each file for the release."
You only need to download the .srr fiie. Files will be extracted upon reconstruction or when you do srr.exe -x file.srr to extract them.
My priorities are the historical aspects first: the collection of meta data, the core components. Others have written tools, so check out http://rescene.wikidot.com/downloads
in discussion General discussion / ReScene » CRC mismatch in one of the recreated RARs (Dark.Souls.III.The.Ringed.City.Update.v1.14-CODEX)
I don't think your CPU matters here, the mt option tells rar to use N threads which it should regardless of actual cpu cores.
Even a single core cpu can run multiple threads it's just slower but the output should be the same.
I quote Gfy from this link I posted above:
-mt is a rar.exe switch to force the amount of threads it must use. By default it uses the amount of cores * 2. (due to hyperthreading)
Normally it starts with 1 and goes up automatically, but certain values can provide false positives: while correct early on, it'll fail later.
And about this:
Anyway if your bad r03 file is wrong in the same place as the one I got you can just use a hex editor and change the affected bytes as mentioned in my other post.
Yes it's wrong in the same 5 bytes as yours (I've eventually downloaded the scene release RAR files as well). And, I know I could fix them with a hex editor (thanks anyway).
Someone (guest) 17 May 2017 22:17
in discussion General discussion / ReScene » CRC mismatch in one of the recreated RARs (Dark.Souls.III.The.Ringed.City.Update.v1.14-CODEX)
I don't think your CPU matters here, the mt option tells rar to use N threads which it should regardless of actual cpu cores.
Even a single core cpu can run multiple threads it's just slower but the output should be the same.
Anyway if your bad r03 file is wrong in the same place as the one I got you can just use a hex editor and change the affected bytes as mentioned in my other post.
in discussion General discussion / ReScene » CRC mismatch in one of the recreated RARs (Dark.Souls.III.The.Ringed.City.Update.v1.14-CODEX)
(thanks for trying to help and for confirming)
I've posted above that only with "—mt-set 8" it completed.
This must be because my CPU is an i7, 4 cores x 2 (due to hyperthreading).
With 1, 2, 4, 16 and 32 it would crash with "Unexpected Error: Still not fine :(.".
With 6, 10, 12, 24 it wouldn't find a matching RAR executable.
Also, using 5x RAR executables older than 5.40, didn't help.
Someone (guest) 16 May 2017 21:25
in discussion General discussion / ReScene » CRC mismatch in one of the recreated RARs (Dark.Souls.III.The.Ringed.City.Update.v1.14-CODEX)
Just tried it and couldn't rebuild it, I also get a bad r03 and it only differs in five bytes according to fc
fc /B good_DB2FC440.r03 bad_385555B4.r03
Vergleichen der Dateien good_DB2FC440.r03 und BAD_385555B4.R03
00E47A22: 9C 9D
00E47A23: 3E B0
00E47A24: FD 9E
00E47A25: EC ED
00E47A26: 4F 1F
Someone (guest) 16 May 2017 20:59
in discussion General discussion / ReScene » CRC mismatch in one of the recreated RARs (Dark.Souls.III.The.Ringed.City.Update.v1.14-CODEX)
try larger mt settings (e.g. 10, 12 or 16), sometimes you get some bad parts if the mt setting is not correct
make sure you only have one rar version in your rar directory
also trying an older rar version this may help sometimes although I didn't see this with rar5xx yet
in discussion General discussion / ReScene » CRC mismatch in one of the recreated RARs (Dark.Souls.III.The.Ringed.City.Update.v1.14-CODEX)
Thank you for replying.
in discussion General discussion / ReScene » CRC mismatch in one of the recreated RARs (Dark.Souls.III.The.Ringed.City.Update.v1.14-CODEX)
1. Issues with compressed files is always a pyReScene issue.
2. Only moderators can confirm .srr files. It's done in batch mostly by checking the release names, uploader,…
in discussion General discussion / ReScene » CRC mismatch in one of the recreated RARs (Dark.Souls.III.The.Ringed.City.Update.v1.14-CODEX)
Update:
Based on the sticky and this thread
I downloaded the latest version of pyReScene via https://bitbucket.org/Gfy/pyrescene/get/default.zip ,
installed latest Python 3.61 x64
and then tried:
c:\Gfy-pyrescene-cb6f9b1b2d26\bin\windows\pysrr Dark.Souls.III.The.Ringed.City.Update.v1.14-CODEX.srr -z C:\pyReScene-0.6.1-w32\_test -t temp --mt-set 8
i.e. with "—mt-set 8" it completed ok (without any errors, as seen below) -all other values would either lead to crash, or it wouldn't find a matching RAR executable).-
but, unfortunately, when I checked the recreated RAR files against the .sfv file,
the "codex-dark.souls.iii.the.ringed.city.update.v1.14.r03" file has wrong CRC (all others are ok).
1. Could one please check this? Is it a pyReScene issue or the .srr file is wrong?
2. The .srr file page (https://www.srrdb.com/release/details/Dark.Souls.III.The.Ringed.City.Update.v1.14-CODEX)
shows "This file is unconfirmed" (with an "X" button to its right ).
I have registered to srrdb.com.
Which members can "confirm" an .srr file?
How is it done? By clicking the "X" button?
PS. For reference, my initial decompressed files all match with the CRC hashes posted in https://www.srrdb.com/release/details/Dark.Souls.III.The.Ringed.City.Update.v1.14-CODEX
in discussion General discussion / ReScene » CRC mismatch in one of the recreated RARs (Dark.Souls.III.The.Ringed.City.Update.v1.14-CODEX)
I want to recreate "Dark.Souls.III.The.Ringed.City.Update.v1.14-CODEX"
The .srr is from the db: https://www.srrdb.com/release/details/Dark.Souls.III.The.Ringed.City.Update.v1.14-CODEX
Initially I tried pyReScene-0.6.1-w32 in win10 x64
but I got "Unexpected Error: Still not fine :(." (see below)
I've checked issue #46, and based on a comment there,
I tried removing the executables 5.40, 5.31, 5.30… down to 4.20 from inside the '_test' folder (in which I have all RAR executables from v2.0 to v5.40), one at a time,
but without success:
in discussion General discussion / ReScene » Force method2 for compressed rars?
No, you'll have to edit the code.
Someone (guest) 05 May 2017 18:25
in discussion General discussion / ReScene » Force method2 for compressed rars?
Is there a way to force method2 when reconstructing rar files?
A lot of cue/bin releases do not work or need method2 which takes quiet some time reach.
The labeling is mostly based on the release names only. It is especially hard to differentiate between games and apps.
I removed the group from the game groups white list and added it to apps instead. There are many more apps on srrdb.
Someone (guest) 01 May 2017 12:56
in discussion General discussion / Other » Wrong labels for release group GAY
These releases are labeled as "GAME, PC" but they are "APPS"
search for "CBT Nuggets GAY"
search for "TomTom GAY"
Cisco.CCNP.Data.Center.642-035.DCUCT-GAY
iGO.My.way.2006.Plus.February.08.Map.Update-GAY
MP3
Eyeglasses-Is_What_I_Need-2008-GAY
Gayle_San_-_Live_At_Emotion_Club_Madrid_25-05-2003-KREMA
Destr0 (guest) 25 Apr 2017 03:32
in discussion General discussion / ReScene » Archive uses unsupported compression method
i get this error with PyReScene 0.6.1 "Archive uses unsupported compression method"
releases:
Doom.3.BFG.Edition.MULTi4.PAL.XBOX360-UNLiMTED
DOOM_II_READNFO_XBLA_XBOX360-XBLAplus
Ilomilo_XBLA_XBOX360-XBLAplus
Get those subs from somewhere else or wait for when there is a version that can reconstruct those vobsubs. There are known bugs.
EatMyShorts (guest) 15 Apr 2017 20:24
in discussion General discussion / Other » I can not rescene subs archive
Hello,
I downloaded from P2P some movies with subs files.
Now I would like to rescene all files with the srrdb files.
I used python to rescene the subs files.
My problem: The rescened archives are ok, but i got CRC-Errors.
What can I do?
Best regards
Hi,
here's how I do it… (in commandline on Windows)
srr -z C:\Apps\pyReScene-0.6.rc1-w32\Subs\rar -t C:\Apps\pyReScene-0.6.rc1-w32\Subs\temp big.1988.extended.dvdrip.xvid.fragment.cd1.srr
srr -z C:\Apps\pyReScene-0.6.rc1-w32\Subs\rar -t C:\Apps\pyReScene-0.6.rc1-w32\Subs\temp big.1988.extended.dvdrip.xvid.fragment.cd2.srr
srr -z C:\Apps\pyReScene-0.6.rc1-w32\Subs\rar -t C:\Apps\pyReScene-0.6.rc1-w32\Subs\temp big.frag.subs.srr
breakdown:
-z flag is what you specify after running the preprardir command to extract usable rar versions; -t flag is for which temporary folder for rar to use while recreating the original archives.
The last input line, with big.frag.subs.srr, recreates the original scene packed archive using the two sub-archives we made in the first two steps.
This should do the trick for the stuff which comes with .sub and .idx files (aka vobsubs).
Hope that clears things up for you.
*edit:
Btooom.E12.Bande.German.2012.ANiME.DL.1080p.BluRay.x264-STARS
Btooom.E11.Auferstehung.German.2012.ANiME.DL.1080p.BluRay.x264-STARS
Btooom.E10.High.Level.German.2012.ANiME.DL.1080p.BluRay.x264-STARS
Btooom.E09.Der.staerkste.Spieler.German.2012.ANiME.DL.1080p.BluRay.x264-STARS
Btooom.E08.Weisser.Geist.German.2012.ANiME.DL.1080p.BluRay.PROPER.x264-STARS
Btooom.E07.Virtuelle.Braut.German.2012.ANiME.DL.1080p.BluRay.PROPER.x264-STARS
Btooom.E06.Opfernacht.German.2012.ANiME.DL.1080p.BluRay.PROPER.x264-STARS
Btooom.E05.Angriff.German.2012.ANiME.DL.1080p.BluRay.PROPER.x264-STARS
Btooom.E04.Weltklassespieler.German.2012.ANiME.DL.1080p.BluRay.PROPER.x264-STARS
Btooom.E03.Ueberleben.German.2012.ANiME.DL.1080p.BluRay.PROPER.x264-STARS
Btooom.E02.Blutbefleckte.Oberschuelerin.German.2012.ANiME.DL.1080p.BluRay.PROPER.x264-STARS
Btooom.E01.Start.German.2012.ANiME.DL.1080p.BluRay.PROPER.x264-STARS
