Notifications
Clear all

Bugs found in 1.01 and 1.02

49 Posts
12 Users
10 Likes
8,801 Views
(@pianoralf)
Active Member
Joined: 4 years ago
Posts: 7
Topic starter  

I have an reproducible crash on 1.02 and 1.02 when I select BPM - PAD chord Dance 2a
I can play about 10- 30 seconds then it crashes the whole application.
I changed sample rate to 44.1 and buffer size  to 256 but  it does not help

--

Overlapping windows: If I scan for new plugins it found a VST plugin which has a licence problem.
Then the plugin pops up an error window "no valid licence" or similar, which is behind the unify scan window
It must come to foreground.

---

 

 


   
Quote
Topic Tags
(@rainbro)
Eminent Member
Joined: 4 years ago
Posts: 29
 

Where did you find the information for v1.02? And more important: where to get it?


   
ReplyQuote
(@mj_prod)
Trusted Member
Joined: 4 years ago
Posts: 46
 

Hello @pianoralf,

Posted by: @pianoralf

I have an reproducible crash on 1.02 and 1.02 when I select BPM - PAD chord Dance 2a
I can play about 10- 30 seconds then it crashes the whole application.

I assume this is with ASIO on Windows 10 because I cannot reproduce it on Mac mini and Win7 laptop with a Clarett 4 Pre USB with different buffers.

Posted by: @pianoralf

Overlapping windows: If I scan for new plugins it found a VST plugin which has a licence problem.
Then the plugin pops up an error window "no valid licence" or similar, which is behind the unify scan window
It must come to foreground.

Thanks for your report, @pianoralf!

Please have a look at the troubleshooting page if the plugin you mentioned is on the list.

 


Hello @getdunne,

I found a bug, too that affects the blue arp midi plugin or others on mac and windows.

If you play your mentioned BPM - PAD chord Dance 2a and change the sampling rate from 48kHz to 44.1kHz,

the arp plays slightly slower, but the delay is in time.

 

Greetings and God bless, Marius


   
ReplyQuote
(@mj_prod)
Trusted Member
Joined: 4 years ago
Posts: 46
 

@rainbro

Posted by: @rainbro

Where did you find the information for v1.02? And more important: where to get it?

Please look into your account at https://www.pluginguru.com

Greetings and God bless, Marius


   
ReplyQuote
(@leszek-1953)
Member
Joined: 5 years ago
Posts: 442
 

In version 1.02, there are double names of the same in poles, e.g. Pure Warmth MM, of which one game is silent, Should I delete the entire database and upload again? or maybe you only need to delete which MM or the other.

Leszek

 


   
ReplyQuote
(@mj_prod)
Trusted Member
Joined: 4 years ago
Posts: 46
 

@leszek-1953

Posted by: @leszek-1953

double names of the same in poles, e.g. Pure Warmth MM

You might want to rebuild your database (database operations) as shown here in the wiki. It is the icon shown in the top right hand right to the reset all icon in the browser.

Does this work for you?

Greetings and God bless, Marius 


   
ReplyQuote
(@leszek-1953)
Member
Joined: 5 years ago
Posts: 442
 

@mj_prod

I don't think we've understood each other, the point is that the same names appear on the list of sounds, with one playing and the other not. Because I have version 1.01 on the second computer, I noticed that version 1.01 does not have the ending MM in the names. I will try to delete all names with MM in the Database and everything will return to normal. Another Rebuild does not eliminate silent sounds. And by the way, where do you broadcast from?

Greetings and God bless, Leszek


   
ReplyQuote
(@mj_prod)
Trusted Member
Joined: 4 years ago
Posts: 46
 

@leszek-1953

Sorry, I didn't really understand you and sorry for the false hint with the database operations, it was quite a guess than knowing it.

If I remember correctly, John wanted to play a MM (Megamagic) sound in one of the last pluginguru youtube live streams that made no sound. This was because the patch was saved without the corresponding soundsource in Gurusampler. I think this wasn't intentional programming the mass of patches unify already comes with and I think not every patch is affected. 

Greetings and God bless, Marius from Germany


   
ReplyQuote
(@leszek-1953)
Member
Joined: 5 years ago
Posts: 442
 

@mj_prod

Thank you for the explanation, I deleted all MM patches that didn't play. This was the situation for the first time, but then it was enough to rebuild the data and everything was ok. Just in case I saved the MM in case. Maybe in the near future we will exchange our projects.
Best regards, I broadcast from Poland. Nice to correspond. Thanks.

Leszek

 


   
mj_prod reacted
ReplyQuote
Rob
 Rob
(@rob)
Member
Joined: 5 years ago
Posts: 138
 

Unify_Catalina_1.0.2 on Catalina 10.15.2

 

I did a clean install which completed ok, but popup window when trying to scan, it says:

"Missing helper program: An important file "Plugscanner" is missing from the Unify VST folder. Unify cannot scan your plug-ins without this"

I downloaded the full installer for Mac  (Unify_Catalina_1.0.2)  and the Unify Standard Lib

Greetings, Rob beta tester


   
ReplyQuote
(@pianoralf)
Active Member
Joined: 4 years ago
Posts: 7
Topic starter  
Posted by: @pianoralf

I have an reproducible crash on 1.02 and 1.02 when I select BPM - PAD chord Dance 2a
I can play about 10- 30 seconds then it crashes the whole application.
I changed sample rate to 44.1 and buffer size  to 256 but  it does not help

 

It's in BlueArp preset 26.  I changed it to 25 or 27 and it's stabile.

I also tried to use a different driver. Windows Audio, or the ESI Maya44Ex driver.

I also changed audiohardware, for my Maya Card came back from repair.

I have not studied BlueArp yet, so can not say which parameter inside the preset 26 causes the crash.
Ralf  


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4410
 

@rob

Our installer isn't smart enough to know where you may have moved your PlugInGuru/Unify data folder, so it puts everything into the C:\Users\Public\Documents\PlugInGuru on Windows, or /Users/Shared/PlugInGuru on Mac. The updated PlugScanner app goes inside the VST subfolder of that main folder, along with any bundled VST plug-ins might also have changed, so I recommend that you delete your old VST folder entirely, and replace it with the new one made by the installer.

I realize this isn't very nice, and fixing it is high on my list.

-shane


   
ReplyQuote
(@steve-moxi)
Active Member
Joined: 4 years ago
Posts: 13
 

PG-8X crashes Logic ProX

This post was modified 4 years ago 2 times by Steve moXi

   
ReplyQuote
(@steve-moxi)
Active Member
Joined: 4 years ago
Posts: 13
 

Blue Arp periodically loses sync in Logic Pro.  

Follow Host clicked. Tempo matches host


   
ReplyQuote
(@thsve)
MR
Joined: 4 years ago
Posts: 341
 

Since installing 1.0.2 (PC), I'm not able to drag'n'drop either plug-ins or the standard library file. When dragging a plug-in to the known plug-in window the icon is a "stop-sign". Same if I try to drag the standard library file to the main window. When I initially installed 1.0.1, dragging the standard library-file worked without problem. I scanned my plug-ins with just one exception so it is not a major problem for me. 

Is this only me or a general problem?

A question: I have moved my Plugin directory without problems, is it safe to completely delete the one that was created at "C:\Users\Public\Documents" or does that entry has to be there still?

Edit: Just found this problem mentioned in the manual/troubleshooting. But, it is still a problem since I only selects one file and it still does'n work.

Win 10 and 11/Cubase Pro 12/Unify/Wavelab 8/Vienna Pro 7/Spectrasonics all/NI 13 Ultimate/Izotope MPS2/Serum/Cthulhu/Scaler 2.5/MusicLab guitar vsts/BIAB 2022/TouchOSC/Metagrid Pro etc


   
ReplyQuote
(@leszek-1953)
Member
Joined: 5 years ago
Posts: 442
 

@getduune

The Dexed instrument has a foot sound (Dexed 0.94hf1) 1. Tekno BD. Where is it saved, how to find them.

Leszek

 


   
ReplyQuote
(@leszek-1953)
Member
Joined: 5 years ago
Posts: 442
 

@getduune

I already know I saved the cart setting in Cartridges as an additional .syx bank and I already have it on top.

I already know I saved the cart setting in Cartridges as an additional .syx bank and I already have it on top. I'm sorry to bother you.

Regards

Leszek

 


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4410
 

@steve-moxi

Thanks for the report. In future please attach long listings as text files, rather than directly in the body of the forum post.

 


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4410
 
Posted by: @thsve

Since installing 1.0.2 (PC), I'm not able to drag'n'drop either plug-ins or the standard library file. When dragging a plug-in to the known plug-in window the icon is a "stop-sign". Same if I try to drag the standard library file to the main window. When I initially installed 1.0.1, dragging the standard library-file worked without problem. I scanned my plug-ins with just one exception so it is not a major problem for me. 

Is this only me or a general problem?

A question: I have moved my Plugin directory without problems, is it safe to completely delete the one that was created at "C:\Users\Public\Documents" or does that entry has to be there still?

Edit: Just found this problem mentioned in the manual/troubleshooting. But, it is still a problem since I only selects one file and it still does'n work.

Thank you for this report. The drag/drop problem is a new one; I hadn't heard about this before. Perhaps try uninstall (via Windows uninstall control panel) and then re-install?

You should be able to delete the old C:\Users\Public\Documents\PlugInGuru folder. HOWEVER note that our installer still isn't smart enough to know where you put your PlugInGuru folder, so anytime you re-install, it will always update (or re-create) the folder in that location. You will have to manually move updated items (e.g. VST folder) out of there, into the corresponding folder in your own PlugInGuru folder.

-shane


   
mj_prod reacted
ReplyQuote
(@steve-moxi)
Active Member
Joined: 4 years ago
Posts: 13
 

Logic Pro:  When bounce in place, BPM patches sync is off, does not match live play when compared. Slightly delayed

Example: BPM Split - Crowd Control patch

  • Instrument 4 soloed & bounced
    • Tried both midi Triggers
    • Follow Host clicked
    • Tempo matches host

 


   
ReplyQuote
(@steve-moxi)
Active Member
Joined: 4 years ago
Posts: 13
 

@getdunne

Will do. Keep up the great work, this is a fantastic plugin!  Just needs some ironing.  As an early adopter, I don't expect this to be perfect. : )

This post was modified 4 years ago by Steve moXi

   
mj_prod and getdunne reacted
ReplyQuote
(@thsve)
MR
Joined: 4 years ago
Posts: 341
 

@getdunne

Did a complete reinstall of 1.0.2. Same result, no drag'n'drop is working. But since the plug-in scanner seems to work ok for me and I un-zipped and moved the library files manually I am good to go. The plug-in that is not handled by the plug-in scanner, POD Farm 2 from Line 6, I can do without in Unify 😀 .

Win 10 and 11/Cubase Pro 12/Unify/Wavelab 8/Vienna Pro 7/Spectrasonics all/NI 13 Ultimate/Izotope MPS2/Serum/Cthulhu/Scaler 2.5/MusicLab guitar vsts/BIAB 2022/TouchOSC/Metagrid Pro etc


   
mj_prod reacted
ReplyQuote
(@leszek-1953)
Member
Joined: 5 years ago
Posts: 442
 

@getdunne

 

How to enable litched in Unify ?

Leszek

 


   
ReplyQuote
(@leszek-1953)
Member
Joined: 5 years ago
Posts: 442
 

@getdunne

I already know, I'm sorry.

Leszek.

 


   
ReplyQuote
(@leszek-1953)
Member
Joined: 5 years ago
Posts: 442
 

 

Please explain to me why there are two positions in my Unify, and in  manual 3, (as in the pictures)


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4410
 
Posted by: @leszek-1953

 

Please explain to me why there are two positions in my Unify, and in  manual 3, (as in the pictures)

It depends on the number of layers in the current patch. Add more layers, and you'll see more lines in the menu.


   
ReplyQuote
(@leszek-1953)
Member
Joined: 5 years ago
Posts: 442
 

@getdunne

Thank you very much.

Les


   
ReplyQuote
(@leszek-1953)
Member
Joined: 5 years ago
Posts: 442
 

@getdunne

Again

I may have expressed myself wrongly, but after pressing the cross in the Linked Parameters circle, only (inst) and (master) are shown to me, while the manual shows (inst) (aux) (master).


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4410
 

@leszek-1953

Add one AUX layer, and you'll see an AUX1 entry in the menu.


   
ReplyQuote
(@leszek-1953)
Member
Joined: 5 years ago
Posts: 442
 

@getdunne

I already know, I'm sorry but I'm still learning.

Thank you very much.

Les


   
ReplyQuote
(@larry-ludwick)
Trusted Member
Joined: 4 years ago
Posts: 78
 

I found a vst that has problems in Unify which is not on the list.

This is odd but for Modular V2.1 from Arturia, the vst screen loads and then begins to extend slowly to the right as if it is duplicating its image and shifting pixels over. At this point, you have to crash out of Windows 10 because the screen does not respond in front or back of the vst screen.

I've also tested Arturia's Analog Lab, Analog Lab 4, and Pigments 2. All these work fine.


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4410
 

Are you on Mac or Windows? have you tried VST3 or AU versions of the plug-in?

I have the V collection and will check this on my Mac when I get home from NAMM

 


   
ReplyQuote
(@larry-ludwick)
Trusted Member
Joined: 4 years ago
Posts: 78
 

I am on a PC with Windows 10.

Modular V2.1 has only a vst2 version, no vst3. 


   
ReplyQuote
(@adderoo)
Active Member
Joined: 4 years ago
Posts: 14
 

I found that some VSTs work on first usage, but that if you save a patch and re-start it later, there is no sound coming from the VST anymore. This happens with Pianoteq6 (VST3 version, VST2 is ok) and VB3-II (VST2). If one reloads the same VST it works again. Up on saving and next time opening, it is silent again.

It looks like MIDI goes in (left light is flashing), but no sound comes out. With e.g. a Piano + Strings patch with two instruments, only the strings do make sound after reloading a saved patch. 

Looks like a little bug to me. Hope you can fix

Thanks

Ad


   
ReplyQuote
(@adderoo)
Active Member
Joined: 4 years ago
Posts: 14
 

Hi

I have reported this to John but thought to put it here as well

If I do a factory install of Unify - whereby files end up on C:\users... etc, all works fine

When I do move everything to e.g. D:\PluginGuru\Unify, and identify this in the Settings as the Data Folder, rebuild the database etc, Unify does not find the libraries of patches nor the factory VST's.

I have retried, re-installed etc, but without success sofar

I am on windows 10 latest version 64 bit

Hope you can fix this as well, as I would like to some more space left on my C:\ drive for other stuff.

 

Thanks in advance

 

Ad


   
ReplyQuote
(@adderoo)
Active Member
Joined: 4 years ago
Posts: 14
 

John sent me a work-around solution for the issue of moving Unify to the D: drive (windows) which works:

In short:

- Basic Unify install on C:\

- Move everything in C:\users\public\documents\PluginGuru  to d:\ or wherever

- Start Unify; in settings, change the datafolder to D:\PlugInGuru\Unify

- Exit Unify

- Restart Unify

Now it finds all patches and VST's that came with Unify

Thanks John and Shane for hinting me to this work-around.

 

Ad

 

 

This post was modified 4 years ago by AdDeRoo

   
mj_prod reacted
ReplyQuote
(@larry-ludwick)
Trusted Member
Joined: 4 years ago
Posts: 78
 

I noted in the documentation for Unify that it lists that Sylenth does not work with Unify.

I am running Sylenth1 version 3.03 and having no problems. Is that one of those vsts that only has problems for some users?

 


   
mj_prod reacted
ReplyQuote
(@adderoo)
Active Member
Joined: 4 years ago
Posts: 14
 

@larry-ludwick

I have also no problems running Sylenth. Everything ok


   
ReplyQuote
(@larry-ludwick)
Trusted Member
Joined: 4 years ago
Posts: 78
 

Don't know if this bug is something that others have reported or just a glitch that hit me.

I updated on windows to 1.02 of Unify. All my created specific user libraries were there and the Categories I created for my instruments. But oddly, the Midi Effects list was set back to the default for the first installation of Unify. I had to go and move my own midi effects back on to the Midi Effects list. 

Fortunately, I created a log of each vst as I tested them with Unify and which lists I put them in. Therefore, I was able to get my midi effects list updated very quickly. I did try rebuilding the database to see if that would do the trick, but no go on that.


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4410
 

@larry-ludwick Thank you for reporting this! It's not a bug, but it's not exactly ideal.

What happened is that the Unify installer includes the basic Presets folder, so if you had modified any of the files there, it replaced your updated files. I'm not sure of the best way to handle this. Simply checking dates and not overwriting newer files isn't ideal either, because you could then miss out on important updates. However it may be the safest approach.

Any suggestions about this would be very welcome.

 


   
ReplyQuote
(@larry-ludwick)
Trusted Member
Joined: 4 years ago
Posts: 78
 

I should think all you need to do is have a simple warning about messing with the "Basic Preset Folders". I certainly learned my lesson here.

I can see now why my Midi Effects folder got messed up. This is because I added my personal Midi Effects to the Basic Folder.

For my many Instruments, I created my own folder and left the delivered instrument folders alone. Therefore, my large list of Instruments was preserved.

My best suggestion would be to not allow users to change basic folders, but allow users to create there own as I did with my instruments. If that can't be done, then a warning should be given in the install notes.

I did create my own version of the Midi Effects list. I then reinstalled Unify 1.02 which proved that this time my personal effects list was preserved.

 


   
getdunne reacted
ReplyQuote
(@thsve)
MR
Joined: 4 years ago
Posts: 341
 

Hi,

I discovered an oddity with MusicLab plug-ins (Real Guitar 5 / RealStrat 5) i Unify. The layer output meter shows signal when no midi is coming in. See attached picture. Have only seen this for MusicLab plug-ins (both VST and VST3). It occurs both in stand alone and as plug-in in Cubase 10. I am running Windows 10. 

Win 10 and 11/Cubase Pro 12/Unify/Wavelab 8/Vienna Pro 7/Spectrasonics all/NI 13 Ultimate/Izotope MPS2/Serum/Cthulhu/Scaler 2.5/MusicLab guitar vsts/BIAB 2022/TouchOSC/Metagrid Pro etc


   
ReplyQuote
Rob
 Rob
(@rob)
Member
Joined: 5 years ago
Posts: 138
 

Unify STD v1.0.2 on Catalina 10.15.2

From FX pansion - Cypher2 and Strobe2 are correct scanned

Cypher2 and Strobe2 are now Catalina compatibel

 

Swap: all my instruments  -  Cypher2 shows up, no Strobe2

Swap: all instruments:  -  at FXpansion both shows up

Cypher 2 as AU and VST

Strobe2 without any indication like AU or VST

 

In the known plugins window Strobe2 does shows up as AU

Did rebuild database - several scans and also added Strobe2 manual to known plugin window, but same behaviour

 

Rob


   
ReplyQuote
(@getdunne)
Illustrious Member Admin
Joined: 5 years ago
Posts: 4410
 

@Rob,

Plug-in menus like "All my instruments" correspond to plug-in subsets which you must edit in the Plug-In Subsets view; see https://pluginguru.net/unify/manual/doku.php?id=plugin-subsets .

John included some pre-made Subsets for all his instruments and effects, so sometimes a newly-added plug-in will "magically" show up, because its plug-in/vendor names correspond to entries already there, but this may fail, especially if the subset-file entry was for e.g. VST and you scanned in e.g. AU.

The "rebuild database" function is only for the patch database, which serves as an index to all patch files in all libraries. (See https://pluginguru.net/unify/manual/doku.php?id=playing-patches .) Rebuilding the database won't help with anything to do with plug-ins.

-shane


   
mj_prod reacted
ReplyQuote
Andre Kuhn
(@andrekuhn)
New Member
Joined: 4 years ago
Posts: 3
 

Hi Shane,

I've found a crash bug in version 1.0 which is still 'active' in 1.02. It's reproducible on both of my boxes:

- Load Unify
- Create a MIDI layer and assign BlueARP (with or without a preset)
- In the BlueARP window: Click on the white preset name in the upper right corner (e.g. '- initial program -')

After 2 seconds of guru meditation, BOOM... Unify says goodbye... all Unify related windows closed.

I'am on Win10 Pro, Rel 1909, constantly patched.

Regards from Germany
André

 


   
ReplyQuote
Page 1 / 2
Share: