-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
auto colour/icon: certain jpegs seem to crash reaper when trying to auto icon new track #576
Comments
From musicbynumbers@gmail.com on May 19, 2013 11:46:56 Think I've solved it! :) I think "_" (underscore) is an illegal character which is causing the crash. Took that out and hasn't crashed since! |
From musicbynumbers@gmail.com on May 19, 2013 12:21:03 Sorry, still crashing :*( Trying to find the pattern. I've renamed files to be solely alphabetical now so no numbers or characters and I still get crashes on jpegs when naming a track that adds the dodgy jpeg and then straight after creating a new track. Will try converting them to PNG and see if it's a compression bug thing. Any ideas guys? :) thanks! |
From musicbynumbers@gmail.com on May 19, 2013 12:32:31 It seems to be with any files I have added recently since they don't show up in the same way on the list. They have full path names and not shorter ones which make me thing somehow autocolour is getting them in a different way? (see attached photo) Also here's another crash log in case it's different :) Problem Event Name: BEX Attachment: auto colour crash image.JPG |
From jeffos...@gmail.com on May 20, 2013 01:30:14 Thanks for all the details, Matt! Fixed for the next build ( r1080 ). For the record, "short paths" are used for files located in REAPER resources directories (or sub-directories), full paths are used otherwise. It's REAPER convention nout ours (less blabla in RPP files, portability, etc..). Status: Fixed |
From musicbynumbers@gmail.com on May 20, 2013 01:48:54 Thanks a lot! :) that's great news as I was just looking forward to Glad it was a quick one to find! Matt. |
From musicbynumbers@gmail.com on May 22, 2013 16:56:12 Hi Jeffos, Hope this isn't a silly question but build ( r1080 ), is that automatically part of what is now v17 (and therefore I can just download it again with auto icon fix) or is it only updated once v18 is out? :) I'm not trying to rush the release or anything just wasn't sure if I was somehow meant to test build ( r1080 ) somehow? If not, no worries, I have patience! :) |
From jeffos...@gmail.com on May 23, 2013 16:08:11 yes, this means this fix will be part of v18 (I put commit numbers like " r1080 " as notes, just to know how what was fixed when). |
From musicbynumbers@gmail.com on May 23, 2013 16:11:16 no worries! looking forward to it like the nerd I am! Have a big project here that's currently iconless and in need of that magic assignment that auto-icon brings! ;) |
From musicbynumbers@gmail.com on May 19, 2013 20:44:10
-What steps will reproduce the problem?
-What is the expected output? What do you see instead?
Expected a new track to be created but Reaper crashes with below report
Problem Event Name: BEX
Application Name: reaper.exe
Application Version: 4.4.0.15
Application Timestamp: 519646af
Fault Module Name: reaper_sws.dll
Fault Module Version: 2.3.0.17
Fault Module Timestamp: 51805e0d
Exception Offset: 0016b3a4
Exception Code: c0000409
Exception Data: 00000000
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 2057
Additional Information 1: 1abb
Additional Information 2: 1abbf100d028b68c92a2f47907642654
Additional Information 3: dd49
Additional Information 4: dd4966dee1b8a6083bbc6938b04565ca
-What version of SWS extension are you using? (Extensions -> About SWS...)
2.3.0.17 (latests as of may 19th)
-What is your Reaper version number and CPU architecture (e.g. Reaper 3.75 x64)? 441pre5 What operating system are you running? (e.g. Windows XP/7, OSX 10.5.8 etc, 64bit?) Win 7 64bit with reaper 32 bit
Attachment: footsteps_1.jpg
Original issue: http://code.google.com/p/sws-extension/issues/detail?id=576
The text was updated successfully, but these errors were encountered: