INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: MC18 crashes using VST Plogue playing sample rates: 44.1 to 88,96,176,192kHz  (Read 2693 times)

pschelbert

  • Galactic Citizen
  • ****
  • Posts: 459

JRiver: MC V18.0.106
Problems summary
Symptom: MC V18 does not respond anymore. Must be closed by force. This happens running Highresaudio, i.e. more than 44.1kHz, if the samplerate changes (from 44.1 to 88, 96, 176, 192kHz). Sometimes it even hangs from one file to another even with 96kHz on one file and 96kHz on the next file (no sample rate change there..)
Crashes in modules: Plogue VST, Bluecatgain ,MC18

Note: while I m not eager to change sample rate, the files unfortunately have now possible samplerates..

Configuration:
Win7 64Bit PC Intel I7P860
Soundcard: RME Fireface UFX, USB connected
Drivers selected in JRiver MC18: ASIO
Samplerates: all no changes unless >192kHz
Channel numbers selected: as source
VST Plug-in: Plogue Bidule VST 32bit, Version 0.9728
Plogue enabled and in there is only in ,out and Bluecatgain VST, no other processing!

Crash1
Problem signature:
  Problem Event Name:   APPCRASH
  Application Name:   Media Center 18.exe
  Application Version:   18.0.106.0
  Application Timestamp:   50e5edc8
  Fault Module Name:   PlogueBiduleVST_32.dll
  Fault Module Version:   0.9.7.2
  Fault Module Timestamp:   50cf6a6b
  Exception Code:   c0000005
  Exception Offset:   004e766a
  OS Version:   6.1.7600.2.0.0.256.48
  Locale ID:   2055
  Additional Information 1:   0a9e
  Additional Information 2:   0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:   0a9e
  Additional Information 4:   0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

Crash2
Problem signature:
  Problem Event Name:   APPCRASH
  Application Name:   Media Center 18.exe
  Application Version:   18.0.106.0
  Application Timestamp:   50e5edc8
  Fault Module Name:   PlogueBiduleVST_32.dll
  Fault Module Version:   0.9.7.2
  Fault Module Timestamp:   50cf6a6b
  Exception Code:   c0000005
  Exception Offset:   004e766a
  OS Version:   6.1.7600.2.0.0.256.48
  Locale ID:   2055
  Additional Information 1:   0a9e
  Additional Information 2:   0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:   0a9e
  Additional Information 4:   0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

Crash3
Problem signature:
  Problem Event Name:   APPCRASH
  Application Name:   Media Center 18.exe
  Application Version:   18.0.106.0
  Application Timestamp:   50e5edc8
  Fault Module Name:   Blue Cat Gain VST(Stereo).dll
  Fault Module Version:   0.0.0.0
  Fault Module Timestamp:   4d4c852c
  Exception Code:   40000015
  Exception Offset:   0019b1ae
  OS Version:   6.1.7600.2.0.0.256.48
  Locale ID:   2055
  Additional Information 1:   8f76
  Additional Information 2:   8f76898accdba04b33013e12d4c804a8
  Additional Information 3:   a6f6
  Additional Information 4:   a6f6b613e346603290c50a6a7c2aa121

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

Crash4
Description:
  A problem caused this program to stop interacting with Windows.

Problem signature:
  Problem Event Name:   AppHangB1
  Application Name:   Media Center 18.exe
  Application Version:   18.0.106.0
  Application Timestamp:   50e5edc8
  Hang Signature:   9ed4
  Hang Type:   4
  OS Version:   6.1.7600.2.0.0.256.48
  Locale ID:   2055
  Additional Hang Signature 1:   9ed449f4e35f6df12f3054d6503840fe
  Additional Hang Signature 2:   f76d
  Additional Hang Signature 3:   f76dac8d5158fcd4db932cea45c3225c
  Additional Hang Signature 4:   c04c
  Additional Hang Signature 5:   c04c221085381ea970ba2bc294eac365
  Additional Hang Signature 6:   138b
  Additional Hang Signature 7:   138b2f8961f5f5d1adec3d3a892c9787

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt
Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 72444
  • Where did I put my teeth?

Uninstall the plugin.
Logged

pschelbert

  • Galactic Citizen
  • ****
  • Posts: 459

I just tried without VST Plug-in (Plogue Bidule). I disabled it.
MC18 ts still hanging.

If I load music new musicfiles with a different sample-rate as the music before, then MC18 hangs.
If I close it and play again, eventually it runs the new musicfiles. Looks, that there is a problem between Audio-interface and MC18 to communicate the sample-rate changes.
This is the same issue if I use an RME Fireface UFX or if I use a Motu828mk3hybrid (both via USB connected).

What works, is just to let MC18 resample. If I set for whatever sample-rate form the audiofile, an output sample-rate of 44.1kHz, then it works with all files, whatsoever incoming sample-rate it is. Maybe that's what I have to do....

Peter

Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 72444
  • Where did I put my teeth?

...

If I load music new musicfiles with a different sample-rate as the music before, then MC18 hangs.

What works, is just to let MC18 resample ...
Some drivers have trouble switching sample rates.  Did you contact the manufacturer?
Logged

pschelbert

  • Galactic Citizen
  • ****
  • Posts: 459

okay, obviously Motu and RME have the same problem, or its an inherent problem of the setup (MC18 to VST to MC18 to Audio-Interface).

I can try to get information from Motu and RME.

Peter
Logged

pschelbert

  • Galactic Citizen
  • ****
  • Posts: 459

just to add, I have updated the Firmware of the audio-interfaces as well as installed the latest drivers of Motu and RME.
But still there may be something..

Peter
Logged

BradC

  • World Citizen
  • ***
  • Posts: 207

Hi

I have had similar problems before. In my case it turned out that a VST used inside plogue was not compatible with the sample rate I was asking it to do. It caused plogue to hang and crash MC.

I run plogue (inside MC) at a fixed 96kHz, as I have had trouble getting it to switch the sound card (RME fireface 800)
Logged

pschelbert

  • Galactic Citizen
  • ****
  • Posts: 459

okay.
I have tried just using only the in and out VST, no other operation in Plogue-Bidule (embedded VST Plogue-Bidule).
Same problem.
All my VST can do different sample rates, 44.1 up to 192kHz (I tested them in Plogue-Bidulestandalone. However also there the sampel-rate change is a bit weird. It takes long and eventually I have to restart Plogue-Bidule.
As you mentioned the change is the problem.
Yes may be its just that, I have to fix the rate.
This problem is with RME Fireface UFX and with Motu828mk3hybrid, same behaviour

Peter
Logged

pschelbert

  • Galactic Citizen
  • ****
  • Posts: 459

Hi BradC

it turns out not to be a known problem, was discovered in MC17 already:

http://yabb.jriver.com/interact/index.php?topic=62534.0
http://yabb.jriver.com/interact/index.php?topic=72045.0

Even more, this problem is  ocurring using VST and not using VST (standalone or in JRiver). Same problem using JRiver without VST.
Also same problem if I use Motu828mk3hybrid or RME Fireface UFX.

It is more and more probable, that Windows7 is the problem (they never could do sound right, despite a whole bunch of drivers and soundsystems...)

I have the impression, that Windows7 locks somehow the ASIO driver, so that no other program can change the sample-rate. Hence any program will hang...(if it wants to change sample-rate)

Solution?:
-it was proposed to put "Windows Sound" to another device (in my case Via Audio SPDIF from Asus Motherboard ) than the audio-interface running JRiver (in my case Motu or RME). I did this, did not help either.
-What else, ideas how to identify deeper the problem?

Peter



Logged

BradC

  • World Citizen
  • ***
  • Posts: 207

Peter,

I will disable convolution and resampling and investigate if I have the same problem.

Are you using any loopback in the RME totalmix? When you change to 96kHz in RME, you have less channels available.

Are you using the latest RME firmware and driver?

Brad
Logged

pschelbert

  • Galactic Citizen
  • ****
  • Posts: 459

Hi

yes I have the latest drivers and FW.
No now I dont use loopback.

I do the following now:

configA
1)JRiver playing file
2) sample read as is, sample rate output: would like same as in, now I do fixed, with 44.1kHz okay
3) Channels fix: 12
4) bitdebth: as source
5) output: ASIO USB RME Fireface

configB
1)JRiver playing file
2) sample read as is, sample rate output: would like same as in, now I do fixed, with 44.1kHz okay
3) Channels fix: 12
4) bitdebth: as source
5) VST Plug-in: Plogue-Bidule (in there Bluecat Volume, Crossover)
6) output: ASIO USB RME Fireface

What do you do? Is it that you have input file rate as is, and resample in output all to 96kHz?

Peter

Logged

BradC

  • World Citizen
  • ***
  • Posts: 207

yes in output format, i set all the output sampling rates to 96kHz
Logged

pschelbert

  • Galactic Citizen
  • ****
  • Posts: 459

Hi Bradc

If I fix the output rate to 96kHz or 44.1kHz, then it works.
Its then just resampling all rates less the one of the output rate (currently 96kHz is set as output rate).

I had no progress to make it work in "dynamic change" of sdample-rate.
I would like to have playing a file, while the whole system (JRiver, VST,Audio-Interface) is adjusting to the incoming sample rate of the music file I am playing.
Would mena: if I am playing
44.1kHz, output is 44.1kHz
48kHz, output is 48kHz
88kHz, output is 88khz
96kHz, output is 96kHz
176kHz, output is 176kHz
192kHz, output is 192kHz
more, output is 192kHz

Its great that JRiver allows a mapping, otherwise nothing would work.. (in DSP output format)

Meanwhile it must be an issue with Windows7 64Bit, i am sure.
The two audio-interfaces behave the same way: RME Fireface UFX, Motu828mk3hybrid (all latest drivers and FW)
VST: Plogue-Bidule. If I am running VST inside JRiver or standalone, the same problem
JRiver: If I am using JRiver with no VST or with VST same Problem.

Therefore: its not Motu, nor RME, nor Plogue VST, nor JRiver

I searched around in the net and have seen that a lot of people have issues with Windows sound. Even professional ones.

One thing I will try, is to completely disable windows built in sound on the built-in Asus Motherboared Via-Audio interface.
I have seen some professionals with DAW did this and some issues went away.

Peter

Logged

pschelbert

  • Galactic Citizen
  • ****
  • Posts: 459

I tried to disable all audio-interfaces in Windows7 sound.

I went back to sample-rate in=sample-rate out (no change in the DSP settings)

After doing this, at least JRiver is not hanging.

Sample-Rate in JRiver is still not  following the played file.
I noticed, If I close JRiver, then the sample rate is set to the file I wanted to play. Re-opening JRiver plays then the file with the new sample-rate.

No yet want i want. JRiver is somehow blocking the sample-rate??

What els can be done here?

Peter
Logged
Pages: [1]   Go Up