Login

Reaper Application Error crash with NEBULA

Serious issues

Re: Reaper Application Error crash with NEBULA

Postby RJHollins » Sun Jun 10, 2012 10:17 pm

enriquesilveti wrote:
RJHollins wrote:Hi Enrique,

?question? In which 'mode' setting, in Reaper, would you prefer that I load Nebula ?

thx


Sorry, what? I'm not a Reaper expert.


That's not what WE hear !!! :lol:

Loading plugs in Reaper can be a 'separate process', 'dedicated process', or the regular default mode [which I suppose is as any other daw would load a plug].

Which mode would be best to troubleshoot ?
i7-5820k, MSI X99A Plus, 16 GIG Ram, Noctua NH-D14, Win-7 Pro [64-bit], Reaper-64

NVC [Nebula Virtual Controllers]
RJHollins
Beta Tester
Beta Tester
 
Posts: 2624
Joined: Sun Mar 28, 2010 5:53 pm

Re: Reaper Application Error crash with NEBULA

Postby Mercado_Negro » Mon Jun 11, 2012 12:03 am

RJHollins wrote:
enriquesilveti wrote:
RJHollins wrote:Hi Enrique,

?question? In which 'mode' setting, in Reaper, would you prefer that I load Nebula ?

thx


Sorry, what? I'm not a Reaper expert.


That's not what WE hear !!! :lol:

Loading plugs in Reaper can be a 'separate process', 'dedicated process', or the regular default mode [which I suppose is as any other daw would load a plug].

Which mode would be best to troubleshoot ?


Default. Always troubleshoot with the basic (default) configuration) setup and then start adding variables.
i7 3770k :: Asus P8H77-V LE :: 16Gb DDR3 @1600MHz :: Geforce GT 520 :: OCZ-Vertex 128Gb :: WD Black Series 1Tb and Green Series 1Tb :: F*******e Liquid56 :: REAPER 64bit and StudioOne 64bit (both latest versions) :: Win 10 64bit
User avatar
Mercado_Negro
Global Moderator
Global Moderator
 
Posts: 1352
Joined: Sat Mar 27, 2010 9:30 am

Re: Reaper Application Error crash with NEBULA

Postby RJHollins » Mon Jun 11, 2012 1:48 am

Once again ... much appreciate your input Mercado 8-)

I'll get on this.

Thanks!
i7-5820k, MSI X99A Plus, 16 GIG Ram, Noctua NH-D14, Win-7 Pro [64-bit], Reaper-64

NVC [Nebula Virtual Controllers]
RJHollins
Beta Tester
Beta Tester
 
Posts: 2624
Joined: Sun Mar 28, 2010 5:53 pm

Re: Reaper Application Error crash with NEBULA

Postby RJHollins » Mon Jun 11, 2012 3:10 am

Hello Enrique,

OK ... I've tried to supply all the files you requested. They are contained in a single .RAR file.

The download link is:

http://speedy.sh/r6mju/Rep-Neb-troubles ... TEST-1.rar

I've included the 2trk audio file, cleared by the artist. This is just a rough mix ... NOT done yet!

Please contact me should you have any issue, or any info I can provide.

I'm certain you appreciate how important this 'problem' is to resolve.

Thank-you you very much for your time and support!

Sincerely,

RJHollins
i7-5820k, MSI X99A Plus, 16 GIG Ram, Noctua NH-D14, Win-7 Pro [64-bit], Reaper-64

NVC [Nebula Virtual Controllers]
RJHollins
Beta Tester
Beta Tester
 
Posts: 2624
Joined: Sun Mar 28, 2010 5:53 pm

Re: Reaper Application Error crash with NEBULA

Postby enriquesilveti » Mon Jun 11, 2012 12:03 pm

Code: Select all
5920-5264 >caching file 2/159: RELS_110SOLAIRE<
5920-5264 ***ERROR***> RELS_110SOLAIRE
5920-5264 >caching file 8/159: RELS_4KGTOHEAVEN<
5920-5264 ***ERROR***> RELS_4KGTOHEAVEN
5920-5264 >caching file 9/159: RELS_510SOLAIRE<
5920-5264 ***ERROR***> RELS_510SOLAIRE
5920-5264 >caching file 10/159: RELS_512PARKAVENUE<
5920-5264 ***ERROR***> RELS_512PARKAVENUE
5920-5264 >caching file 11/159: RELS_610SOLAIRE<
5920-5264 ***ERROR***> RELS_610SOLAIRE
5920-5264 >caching file 12/159: RELS_ANALOGCHANNEL<
5920-5264 ***ERROR***> RELS_ANALOGCHANNEL
5920-5264 >caching file 13/159: RELS_ANTHIGH2<
5920-5264 ***ERROR***> RELS_ANTHIGH2
5920-5264 >caching file 14/159: RELS_ANTHIGH4<
5920-5264 ***ERROR***> RELS_ANTHIGH4
5920-5264 >caching file 15/159: RELS_ANTHIGH6<
5920-5264 ***ERROR***> RELS_ANTHIGH6
5920-5264 >caching file 16/159: RELS_ANTHIGH8<
5920-5264 ***ERROR***> RELS_ANTHIGH8
5920-5264 >caching file 17/159: RELS_ANTLOW2<
5920-5264 ***ERROR***> RELS_ANTLOW2
5920-5264 >caching file 18/159: RELS_ANTLOW4<
5920-5264 ***ERROR***> RELS_ANTLOW4
5920-5264 >caching file 19/159: RELS_ANTLOW6<
5920-5264 ***ERROR***> RELS_ANTLOW6
5920-5264 >caching file 20/159: RELS_ANTLOW8<
5920-5264 ***ERROR***> RELS_ANTLOW8
5920-5264 >caching file 21/159: RELS_ANTPASS2<
5920-5264 ***ERROR***> RELS_ANTPASS2
5920-5264 >caching file 22/159: RELS_ANTPASS4<
5920-5264 ***ERROR***> RELS_ANTPASS4
5920-5264 >caching file 23/159: RELS_ANTPASS6<
5920-5264 ***ERROR***> RELS_ANTPASS6
5920-5264 >caching file 24/159: RELS_ANTPASS8<
5920-5264 ***ERROR***> RELS_ANTPASS8
5920-5264 >caching file 25/159: RELS_ANTSTOP2<
5920-5264 ***ERROR***> RELS_ANTSTOP2
5920-5264 >caching file 26/159: RELS_ANTSTOP4<
5920-5264 ***ERROR***> RELS_ANTSTOP4
5920-5264 >caching file 27/159: RELS_ANTSTOP6<
5920-5264 ***ERROR***> RELS_ANTSTOP6
5920-5264 >caching file 28/159: RELS_ANTSTOP8<
5920-5264 ***ERROR***> RELS_ANTSTOP8
5920-5264 >caching file 29/159: RELS_ASRADA<
5920-5264 ***ERROR***> RELS_ASRADA
5920-5264 >caching file 30/159: RELS_BACKTOGENESI<
5920-5264 ***ERROR***> RELS_BACKTOGENESI
5920-5264 >caching file 31/159: RELS_BEHTUBEAGTR<
5920-5264 ***ERROR***> RELS_BEHTUBEAGTR
5920-5264 >caching file 32/159: RELS_BEHTUBEBASS<
5920-5264 ***ERROR***> RELS_BEHTUBEBASS
5920-5264 >caching file 33/159: RELS_BEHTUBEEGTR<
5920-5264 ***ERROR***> RELS_BEHTUBEEGTR
5920-5264 >caching file 34/159: RELS_BEHTUBEGUITAR<
5920-5264 ***ERROR***> RELS_BEHTUBEGUITAR
5920-5264 >caching file 35/159: RELS_BEHTUBEKEYB<
5920-5264 ***ERROR***> RELS_BEHTUBEKEYB
5920-5264 >caching file 36/159: RELS_BEHTUBELIMIT<
5920-5264 ***ERROR***> RELS_BEHTUBELIMIT
5920-5264 >caching file 37/159: RELS_BEHTUBENEUTRAL<
5920-5264 ***ERROR***> RELS_BEHTUBENEUTRAL
5920-5264 >caching file 38/159: RELS_BEHTUBEVOCALI<
5920-5264 ***ERROR***> RELS_BEHTUBEVOCALI
5920-5264 >caching file 39/159: RELS_BEHTUBEVOCALII<
5920-5264 ***ERROR***> RELS_BEHTUBEVOCALII
5920-5264 >caching file 40/159: RELS_BEHVALVE<
5920-5264 ***ERROR***> RELS_BEHVALVE
5920-5264 >caching file 42/159: RELS_BMX<
5920-5264 ***ERROR***> RELS_BMX
5920-5264 >caching file 43/159: RELS_BMX376<
5920-5264 ***ERROR***> RELS_BMX376
5920-5264 >caching file 44/159: RELS_BMX376LIGHT<
5920-5264 ***ERROR***> RELS_BMX376LIGHT
5920-5264 >caching file 46/159: RELS_BONNIE&CLIDE<
5920-5264 ***ERROR***> RELS_BONNIE&CLIDE
5920-5264 >caching file 47/159: RELS_CALC1061<
5920-5264 ***ERROR***> RELS_CALC1061
5920-5264 >caching file 53/159: RELS_DUSTYOLDTAPE<
5920-5264 ***ERROR***> RELS_DUSTYOLDTAPE
5920-5264 >caching file 54/159: RELS_ELECTRONICVOX1<
5920-5264 ***ERROR***> RELS_ELECTRONICVOX1
5920-5264 >caching file 55/159: RELS_ELECTRONICVOX2<
5920-5264 ***ERROR***> RELS_ELECTRONICVOX2
5920-5264 >caching file 56/159: RELS_EMUBPF<
5920-5264 ***ERROR***> RELS_EMUBPF
5920-5264 >caching file 57/159: RELS_EMUBPFL<
5920-5264 ***ERROR***> RELS_EMUBPFL
5920-5264 >caching file 58/159: RELS_EMULPF<
5920-5264 ***ERROR***> RELS_EMULPF
5920-5264 >caching file 59/159: RELS_EMUPREAMP<
5920-5264 ***ERROR***> RELS_EMUPREAMP
5920-5264 >caching file 60/159: RELS_FNDBASSMAN<
5920-5264 ***ERROR***> RELS_FNDBASSMAN
5920-5264 >caching file 61/159: RELS_FNDFRONTMAN<
5920-5264 ***ERROR***> RELS_FNDFRONTMAN
5920-5264 >caching file 62/159: RELS_FNDGUITAMP1<
5920-5264 ***ERROR***> RELS_FNDGUITAMP1
5920-5264 >caching file 63/159: RELS_FNDVIBROLUX<
5920-5264 ***ERROR***> RELS_FNDVIBROLUX
5920-5264 >caching file 71/159: RELS_GOLDMANNTLM1<
5920-5264 ***ERROR***> RELS_GOLDMANNTLM1
5920-5264 >caching file 72/159: RELS_GOLDMANNTLM2<
5920-5264 ***ERROR***> RELS_GOLDMANNTLM2
5920-5264 >caching file 73/159: RELS_GROOVEPRE<
5920-5264 ***ERROR***> RELS_GROOVEPRE
5920-5264 >caching file 74/159: RELS_KAPPAG1<
5920-5264 ***ERROR***> RELS_KAPPAG1
5920-5264 >caching file 75/159: RELS_KAPPAG2<
5920-5264 ***ERROR***> RELS_KAPPAG2
5920-5264 >caching file 76/159: RELS_KGB007MIXER<
5920-5264 ***ERROR***> RELS_KGB007MIXER
5920-5264 >caching file 77/159: RELS_KGB625BASSPRE<
5920-5264 ***ERROR***> RELS_KGB625BASSPRE
5920-5264 >caching file 79/159: RELS_KGB625PRE<
5920-5264 ***ERROR***> RELS_KGB625PRE
5920-5264 >caching file 81/159: RELS_KINGKONG<
5920-5264 ***ERROR***> RELS_KINGKONG
5920-5264 >caching file 82/159: RELS_LOGICHISHELF<
5920-5264 ***ERROR***> RELS_LOGICHISHELF
5920-5264 >caching file 83/159: RELS_LOGICLOSHELF<
5920-5264 ***ERROR***> RELS_LOGICLOSHELF
5920-5264 >caching file 84/159: RELS_LOSANGELES2A<
5920-5264 ***ERROR***> RELS_LOSANGELES2A
5920-5264 >caching file 85/159: RELS_LOSANGELES2D<
5920-5264 ***ERROR***> RELS_LOSANGELES2D
5920-5264 >caching file 86/159: RELS_M5ROADSTER1<
5920-5264 ***ERROR***> RELS_M5ROADSTER1
5920-5264 >caching file 87/159: RELS_M5ROADSTER2<
5920-5264 ***ERROR***> RELS_M5ROADSTER2
5920-5264 >caching file 88/159: RELS_M5TURBO<
5920-5264 ***ERROR***> RELS_M5TURBO
5920-5264 >caching file 89/159: RELS_MACADAVLZ<
5920-5264 ***ERROR***> RELS_MACADAVLZ
5920-5264 >caching file 90/159: RELS_MACONYX<
5920-5264 ***ERROR***> RELS_MACONYX
5920-5264 >caching file 93/159: RELS_MACVLZHIGH2<
5920-5264 ***ERROR***> RELS_MACVLZHIGH2
5920-5264 >caching file 95/159: RELS_MACVLZPAN<
5920-5264 ***ERROR***> RELS_MACVLZPAN
5920-5264 >caching file 96/159: RELS_MARSATTACK<
5920-5264 ***ERROR***> RELS_MARSATTACK
5920-5264 >caching file 97/159: RELS_MICRODIST<
5920-5264 ***ERROR***> RELS_MICRODIST
5920-5264 >caching file 98/159: RELS_MIDIADA<
5920-5264 ***ERROR***> RELS_MIDIADA
5920-5264 >caching file 99/159: RELS_MOKAMBO<
5920-5264 ***ERROR***> RELS_MOKAMBO
5920-5264 >caching file 100/159: RELS_MOOGEDLOWPASS1<
5920-5264 ***ERROR***> RELS_MOOGEDLOWPASS1
5920-5264 >caching file 101/159: RELS_MOOGEDLOWPASS2<
5920-5264 ***ERROR***> RELS_MOOGEDLOWPASS2
5920-5264 >caching file 102/159: RELS_NEWMANMIC<
5920-5264 ***ERROR***> RELS_NEWMANMIC
5920-5264 >caching file 105/159: RELS_PEAVYAMP<
5920-5264 ***ERROR***> RELS_PEAVYAMP
5920-5264 >caching file 106/159: RELS_REVIVER<
5920-5264 ***ERROR***> RELS_REVIVER
5920-5264 >caching file 107/159: RELS_SONICTAPE1<
5920-5264 ***ERROR***> RELS_SONICTAPE1
5920-5264 >caching file 108/159: RELS_SONICTAPE2<
5920-5264 ***ERROR***> RELS_SONICTAPE2
5920-5264 >caching file 109/159: RELS_SONICTAPE3<
5920-5264 ***ERROR***> RELS_SONICTAPE3
5920-5264 >caching file 110/159: RELS_SONNIEWEATHER<
5920-5264 ***ERROR***> RELS_SONNIEWEATHER
5920-5264 >caching file 112/159: RELS_STATELOGICPRE1<
5920-5264 ***ERROR***> RELS_STATELOGICPRE1
5920-5264 >caching file 113/159: RELS_STATELOGICPRE2<
5920-5264 ***ERROR***> RELS_STATELOGICPRE2
5920-5264 >caching file 114/159: RELS_STATEOFLOGICFHI<
5920-5264 ***ERROR***> RELS_STATEOFLOGICFHI
5920-5264 >caching file 115/159: RELS_STATEOFLOGICFLO<
5920-5264 ***ERROR***> RELS_STATEOFLOGICFLO
5920-5264 >caching file 119/159: RELS_STRUDELA811<
5920-5264 ***ERROR***> RELS_STRUDELA811
5920-5264 >caching file 120/159: RELS_STRUDELA812<
5920-5264 ***ERROR***> RELS_STRUDELA812
5920-5264 >caching file 121/159: RELS_STRUDELA813<
5920-5264 ***ERROR***> RELS_STRUDELA813
5920-5264 >caching file 122/159: RELS_SUBBASSFX<
5920-5264 ***ERROR***> RELS_SUBBASSFX
5920-5264 >caching file 123/159: RELS_SUMMINGAMP<
5920-5264 ***ERROR***> RELS_SUMMINGAMP
5920-5264 >caching file 124/159: RELS_SUPERBASSTONE<
5920-5264 ***ERROR***> RELS_SUPERBASSTONE
5920-5264 >caching file 125/159: RELS_SURE571<
5920-5264 ***ERROR***> RELS_SURE571
5920-5264 >caching file 126/159: RELS_SURE572<
5920-5264 ***ERROR***> RELS_SURE572
5920-5264 >caching file 127/159: RELS_SURGICALHIPASS<
5920-5264 ***ERROR***> RELS_SURGICALHIPASS
5920-5264 >caching file 128/159: RELS_SURGICALLOPASS<
5920-5264 ***ERROR***> RELS_SURGICALLOPASS
5920-5264 >caching file 129/159: RELS_SURROUNDFX<
5920-5264 ***ERROR***> RELS_SURROUNDFX
5920-5264 >caching file 130/159: RELS_TAPE&BASS<
5920-5264 ***ERROR***> RELS_TAPE&BASS
5920-5264 >caching file 131/159: RELS_TASMANIA<
5920-5264 ***ERROR***> RELS_TASMANIA
5920-5264 >caching file 132/159: RELS_TEKA3340S1<
5920-5264 ***ERROR***> RELS_TEKA3340S1
5920-5264 >caching file 133/159: RELS_TEKA3340S2<
5920-5264 ***ERROR***> RELS_TEKA3340S2
5920-5264 >caching file 134/159: RELS_U5CABRIO1<
5920-5264 ***ERROR***> RELS_U5CABRIO1
5920-5264 >caching file 135/159: RELS_U5CABRIO2<
5920-5264 ***ERROR***> RELS_U5CABRIO2
5920-5264 >caching file 136/159: RELS_UP3HIGHPASS<
5920-5264 ***ERROR***> RELS_UP3HIGHPASS
5920-5264 >caching file 137/159: RELS_UP3LOWPASS<
5920-5264 ***ERROR***> RELS_UP3LOWPASS
5920-5264 >caching file 138/159: RELS_VINTAGEAMP<
5920-5264 ***ERROR***> RELS_VINTAGEAMP
5920-5264 >caching file 141/159: RELS_VIRHARD<
5920-5264 ***ERROR***> RELS_VIRHARD
5920-5264 >caching file 142/159: RELS_VIRHARD2<
5920-5264 ***ERROR***> RELS_VIRHARD2
5920-5264 >caching file 143/159: RELS_VIRHIGH12<
5920-5264 ***ERROR***> RELS_VIRHIGH12
5920-5264 >caching file 144/159: RELS_VIRHIGH241<
5920-5264 ***ERROR***> RELS_VIRHIGH241
5920-5264 >caching file 145/159: RELS_VIRHIGH242<
5920-5264 ***ERROR***> RELS_VIRHIGH242
5920-5264 >caching file 146/159: RELS_VIRLIGHT<
5920-5264 ***ERROR***> RELS_VIRLIGHT
5920-5264 >caching file 147/159: RELS_VIRLIGHT2<
5920-5264 ***ERROR***> RELS_VIRLIGHT2
5920-5264 >caching file 148/159: RELS_VIRLIGHT3<
5920-5264 ***ERROR***> RELS_VIRLIGHT3
5920-5264 >caching file 149/159: RELS_VIRLOW24<
5920-5264 ***ERROR***> RELS_VIRLOW24
5920-5264 >caching file 150/159: RELS_VIRLOW24D<
5920-5264 ***ERROR***> RELS_VIRLOW24D
5920-5264 >caching file 151/159: RELS_VIRLOW36<
5920-5264 ***ERROR***> RELS_VIRLOW36
5920-5264 >caching file 152/159: RELS_VIRMEDIUM<
5920-5264 ***ERROR***> RELS_VIRMEDIUM
5920-5264 >caching file 153/159: RELS_VIRMEDIUM2<
5920-5264 ***ERROR***> RELS_VIRMEDIUM2
5920-5264 >caching file 154/159: RELS_VIRSOFT<
5920-5264 ***ERROR***> RELS_VIRSOFT
5920-5264 >caching file 156/159: RELS_YAMMEDSPFAC<
5920-5264 ***ERROR***> RELS_YAMMEDSPFAC
5920-5264 >caching file 157/159: RELS_ZOOMBASS<
5920-5264 ***ERROR***> RELS_ZOOMBASS
5920-5264 >caching file 159/159: RELS_TIGHTSUBBASSFX<
5920-5264 ***ERROR***> RELS_TIGHTSUBBASSFX
Enrique Silveti.
Acustica Audio customer and technical support.

MBP 11.5 (i7-4870 | 16 GB | 512 SDD)
SP4 (i5-6300 | 8 GB | 256 SDD)
RME UFX | PS Lyra2 | SD USBPre2
VM U15 | VM W10 | VM OSX 10.12
N4/NAT4 | SPX3 | RX5 | LN2C | Smaart8 | R5 | PT12 | PX10
User avatar
enriquesilveti
Global Moderator
Global Moderator
 
Posts: 2662
Joined: Sun Mar 28, 2010 9:00 pm
Location: Lodi | Madrid | Buenos Aires

Re: Reaper Application Error crash with NEBULA

Postby enriquesilveti » Mon Jun 11, 2012 12:08 pm

1. Delete temp .XML files from Nebulatemprepository/temp folder.
2. Delete ~scanboot.xml file from Nebulatemprepository/Setups.
3. Reinstall all the emulation presets with ***ERROR***
4. Send me your .SER file. I'll request a new INITs files for you. (just in case...)
5. Check your HDD.
Enrique Silveti.
Acustica Audio customer and technical support.

MBP 11.5 (i7-4870 | 16 GB | 512 SDD)
SP4 (i5-6300 | 8 GB | 256 SDD)
RME UFX | PS Lyra2 | SD USBPre2
VM U15 | VM W10 | VM OSX 10.12
N4/NAT4 | SPX3 | RX5 | LN2C | Smaart8 | R5 | PT12 | PX10
User avatar
enriquesilveti
Global Moderator
Global Moderator
 
Posts: 2662
Joined: Sun Mar 28, 2010 9:00 pm
Location: Lodi | Madrid | Buenos Aires

Re: Reaper Application Error crash with NEBULA

Postby RJHollins » Mon Jun 11, 2012 8:47 pm

Hello Enrique,

OK ... several issues are coming up that are confusing me :roll:

First. Before doing anything drastic, I went searching through my C:\nebulatemprepository, both Programs & Vectors, to locate the libraries giving the error message [from your above post].

Problem ... I DON'T have most of those filenames in either directory !?!? I found 'SOLAIRE', and '4KGTOHEAVEN', 'BACKTOGENESI' and a few others, but many of the others are not being located ! :shock: I'm also using a disk cataloging app with search capability to help find things. This is strange.

Second.

Just got a message back from 'Ollie' over at the Reaper forum. It appears I can't follow directions, posting my report in the wrong section :roll:

His reply to my EVENTError logs:

Sorry for the trouble! Please keep bugs/help requests in the appropriate forums firt, not here in the issue tracker (a database for confirmed/confirmable REAPER bugs). Alas we can't move things between the tracker and the forums, please feel free to bump your existing forum thread if you need more help.

Also thank you for the event logs, the 32-bit host process crashing/hanging indicates that you're using the 32-bit Nebula version bridged into REAPER 64 (if Nebula is actually the culprit, could as well be an unsuspected other plug-in), so your problem may be related to that and needs further troubleshooting in the forums. We'll reopen the ticket if it turns out to be something wrong with REAPER.


So now I wonder if I inadvertently installed a 64 bit program on my 32 bit system ?!?!? Is this even possible ??

So ... what I'll do is find as many of the 'error-ed' libs I can, and move them out of the way. [instead of re-installing them ... at least till I get the obvious errors out of the way].

I'll also clear the TEMP folder, and let NEB rescan, then check the debug logs to see what issues may linger.

anyway ... could I have installed the wrong versions ???

Sincere THANKS for helping me sort this craziness!
i7-5820k, MSI X99A Plus, 16 GIG Ram, Noctua NH-D14, Win-7 Pro [64-bit], Reaper-64

NVC [Nebula Virtual Controllers]
RJHollins
Beta Tester
Beta Tester
 
Posts: 2624
Joined: Sun Mar 28, 2010 5:53 pm

Re: Reaper Application Error crash with NEBULA

Postby RJHollins » Mon Jun 11, 2012 11:36 pm

my oh my ...

I've been going through the list of lib errors, and one by one, moving both .N2P & .N2V files over to a separate folder.

I've cleared the TEMP folder, deleted the 'scanboot.xml' from SETUP, deleted the Nebula.log file.

When I load up Reaper and insert 1 Neb ... everything scans fine, get to INIT screen, Load in a Preset. All GOOD and playing fine :D

Close out Reaper .... load Nebula.LOG file into notepad ... the filenames with errors are STILL there :shock:

ex ... the Bonnie&Clyde lib from the 'Clyde_Channel_Strip_Line' has only 2 files per folder. BOTH have been removed, yet they still show up in the debug Nebula.log :roll:

What am I NOT doing correct :twisted:

Side note ... performed a 'disk scan' on main drive ... no errors 8-)
i7-5820k, MSI X99A Plus, 16 GIG Ram, Noctua NH-D14, Win-7 Pro [64-bit], Reaper-64

NVC [Nebula Virtual Controllers]
RJHollins
Beta Tester
Beta Tester
 
Posts: 2624
Joined: Sun Mar 28, 2010 5:53 pm

Re: Reaper Application Error crash with NEBULA

Postby RJHollins » Tue Jun 12, 2012 1:53 am

more testing ...

How 'bout this.

A while back I had heard of another DAW called 'PreSonus Studio 1'. Decided to check it out.

With the demo installed, I loaded in my test audio, and figure out how to get a Nebula on the track ... totally different layout/ design from Reaper ... anyway ...

I must have auditioned 20 or 30 Neb libraries ... EVEN while the track was playing ...

Not a single glitch ... not even a crash :shock:

Granted, this was just a single stereo trk, with 1 instance of Nebula. Yet when I try this same idea in Reaper, after about the 6th audition ... crash to the desktop :?

hmmm ... wasn't it stated here that Reaper was THE test platform for Nebula :oops:

I am mindful that, according to my Neb.LOG, that for some reason, a bunch of libraries are showing errors ... why this is is beyond me ... I was quite sure that they worked fine [although they are not in the main use arena].

I'm going to do another run using Studio-1 and see what the Nebula.Log shows.

At this point, if I MAY jump to conclusions ... we have a serious issue with Reaper v4.22 and Nebula Server.

waiting on comments!

Sincerely
i7-5820k, MSI X99A Plus, 16 GIG Ram, Noctua NH-D14, Win-7 Pro [64-bit], Reaper-64

NVC [Nebula Virtual Controllers]
RJHollins
Beta Tester
Beta Tester
 
Posts: 2624
Joined: Sun Mar 28, 2010 5:53 pm

Re: Reaper Application Error crash with NEBULA

Postby RJHollins » Wed Jun 13, 2012 1:38 am

Debugging continues !

Posting at the Reaper site, in discussion with 'Ollie'. He requested that I repost here my event logs. This is the main post below:
Quote:
Originally Posted by Ollie
- Can you try renaming your REAPER resource folder (the one that pops up when you click Options->"Show REAPER resource folder in Finder/Explorer") temporarily, so REAPER gets a full reset (you can rename it back after that and overwrite the newly created folder if it doesn't change anything)? This should take care of any setting related issues (I think Nebula should run with defaults).

Hello Ollie,

First, thank-you for your time !

As requested, I renamed the Reaper resource folder. Running Reaper, I then set my ASIO card and set the VST location folder. Basically running as a factory GUI, etc.

Using the same test scenario ... a single stereo audio file, and a single instance of Nebula. For the test, Nebula was run in 'Default mode'.

The crash issue has not changed ... after the 5th auditioning preset was loading in ... Reaper reported a crash ... then straight to the desktop.

From Windows 'Event Viewer' we have to error messages:

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 6/12/2012
Time: 2:11:37 PM
User: N/A
Computer: RJHQ9450
Description:
Faulting application reaper.exe, version 4.2.2.0, faulting module nebula3 reverb.dll, version 0.0.0.0, fault address 0x000a1951.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 72 65 61 ure rea
0018: 70 65 72 2e 65 78 65 20 per.exe
0020: 34 2e 32 2e 32 2e 30 20 4.2.2.0
0028: 69 6e 20 6e 65 62 75 6c in nebul
0030: 61 33 20 72 65 76 65 72 a3 rever
0038: 62 2e 64 6c 6c 20 30 2e b.dll 0.
0040: 30 2e 30 2e 30 20 61 74 0.0.0 at
0048: 20 6f 66 66 73 65 74 20 offset
0050: 30 30 30 61 31 39 35 31 000a1951
0058: 0d 0a ..



Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1001
Date: 6/12/2012
Time: 2:11:42 PM
User: N/A
Computer: RJHQ9450
Description:
Fault bucket -1277177848.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 42 75 63 6b 65 74 3a 20 Bucket:
0008: 2d 31 32 37 37 31 37 37 -1277177
0010: 38 34 38 0d 0a 848..

---------------------------------------------------



Ollies response:
Thanks for reporting back and the fresh event log, it names all participants and an offset address in Nebula. Please make sure you send this to the Nebula devs, it can be valuable for them in case the following tweak doesn't help: please right-click Nebula in the FX browser and check "save minimal undo states", if the problem persists we know at least that it wasn't that either.



I'm 'off to tweak the Reaper' !
i7-5820k, MSI X99A Plus, 16 GIG Ram, Noctua NH-D14, Win-7 Pro [64-bit], Reaper-64

NVC [Nebula Virtual Controllers]
RJHollins
Beta Tester
Beta Tester
 
Posts: 2624
Joined: Sun Mar 28, 2010 5:53 pm

PreviousNext

Return to Bugs

Who is online

Users browsing this forum: No registered users and 1 guest