Ok... we are rolling.
Bug Reports here please... and I will do my best to fix them ASAP.
Thanks,
Bob L
Printable View
Ok... we are rolling.
Bug Reports here please... and I will do my best to fix them ASAP.
Thanks,
Bob L
Cool! :cool:
Looking at the upgrade page on the new site, there was no upgrade for SSLite to SSLite64. Just SSL to Full 64. Should I assume that there will be no SSLite64?
Yes... only Full64 for now.
Bob L
Bob,
Will there be a 64 bit version of SSLite?
Thanks
Most likely not... Lite existed because of lesser systems with less RAM... if you are going 64 bits, you will most likely have a serious machine and I see no point for Lite anymore.
Bob L
I should mention that you should not copy 32 bit program files (like fkeys and prfs... etc) to the new 64 bit installs... 32 bit sessions will be converted up to 64 bit sessions on the fly as you open them, but once you save the sessions in 64 bit mode you cannot go back... so keep copies of your 32 bit sessions in case there are problems.
Also realize that most plugin settings saved in 32 bit sessions will most likely not translate up to the 64 bit session on the fly... so you may need to reset your plugin settings when moving older sessions into the new program.
My native plugins settings are backward compatible and will translate automatically when opening older sessions.
Bob L
It looks like the 32bit shades are not compatable , can you confirm this Bob
Correct... 32 bit stuff has to be re-compiled for 64 bit... easy enough for shades... as long as the original project exists. These shades should be marked 64 so there is no confusion.
Bob L
Is there a Studio Reverb64?
No 64 Bit Reverb yet... designing a whole new plugin... need to get all this stuff sorted out first... there is a lot going on with the whole new website and storefront.
Bob L
Great news Bob,
I intend to purchase 64SAW and 64SAC. Quick question, will my existing 32 bit versions still be able to be used until I get the 62 bit versions up and running with plugins etc?
Cheers
Bruce
Yes... you can keep everything and run them both... just can't mix configuration files and settings between the two... keep the 32 bit separate from the 64 bit.
Bob L
Thanks Bob. One more question. Does the new website require us registered users to create a new user account? My previous login to the registered users area did not require an email address and the new site doesn't recognize any emails that I try to reset the password. I don't recall what email I would have used in the past to register as it is some time ago now.
Cheers
Bruce
Looks like superior drummer 3 no longer follows host. It was working in 32 bit Saw although I was using jbridge to run it because its 64 bit only.
EZ Keys also will no longer follow host.
Auto tune 7 is the only plugin so far that has given me any trouble.
Mike
Yes. When you press play in saw the midi player in sd3 and ez keys does not start playing. Now you can press the play button in ezkeys or sd3 , it won’t start playing , but when you press play in saw, the midi player will start , and when you press stop in saw it will stop , but if you move saws cursor to a different location and press play it doesn’t jump to the new location , just starts playing where it left off
Aside from that things seem pretty darn solid with a lot of plugins that used to give me problems , all of Steven Slates plugs are working great
Ok... I'll look into the tempo stuff.
The store accounts are all new if you want one... they are not the download registered User account... nothing has changed with that... you do not have to create an account on the store... you can check out as a guest...
Bob L
Bob,
...May I ask how this is achieved?Quote:
Correct... 32 bit stuff has to be re-compiled for 64 bit... easy enough for shades... as long as the original project exists. These shades should be marked 64 so there is no confusion.Bob L
PS: Glass House does not work. Also, PowerShades is not usable, but Resource Hacker does work.
NOTE: For posts regarding shades...please see new thread. 32-bit shades not working in a 64-bit app is really not a bug...so such content really has no place here.
Okay, call me old fashioned ... but I still like the Vintage Basic shade. Maybe because I've used it for so long. Not that the new default shade isn't snazzy ... but I hope 64-bit Vintage Basic comes along.
Roger
Ok... got a report of the midi workshop64 crashing on record... can anyone else verify on their setups.
Bob L
Ok... the bug has been chased down and fixed... there is a new MidiWorkShop64 ver 1.0a up for download.
Bob L
Okay, here's a weirdness.
Doing a Build Mix on a mono file. Minor processing. The progress bar gets to about 64%, and the percentage window the same.
Then the progress bar keeps going, but the % window resets to 0 and starts over.
The progress bar gets to about 75%, the % counter to 34% ... then the Build finishes. The mix seems to be complete.
Happened twice on two different mono files.
Roger.
I have a similar issue. Buildmix stops at 18% and the system looks like it has frozen...but, the mix file is complete. Except, playing in Soundfile view crashes SAW. Windows 10 can’t play the wave file...error -208. But, DBpoweramp converts it successfully and all the data is there.
Also, I am having some files when played from Library view crash the Soundfile view playback and poof SAW. It seems there may be a header issue with Soundfile view playback.
Wow... interesting...
Are these troublesome files aif files by chance... or wavs.
And... the mono buildmix... is that mono final mixfile or mono source mix files.
Bob L
Mine was a mono wav source file, building to a mono final.
Two iZotope plug-ins: noise reduction and click elimination. That's all.
BTW, I'm on Windows 10 with 16 gigs of RAM.
Roger
Can you try the buildmix bypassing the plugins.
I did find that the SF view has a bug in the 24 bit resolution file playback... I just fixed that... not sure if that is connected...
Try the buildmixs to 16 bits and see what happens.
Bob L
The failed SAW mixes were 24bit.
The waves that crashed SAW are 32bit
Also a 16bit AIF file crashed SAW.
I am sending you a link to the problem files in an email Bob.
16 bit mix of the same EDL compiles with the same pause in the counter, but the resulting file doesn’t crash SAW on playback.
The percentage meter works fine when all plugins are removed.
Okay, tried it with a different mono wav file. Fresh session, no plug-ins.
Build Mix happens the same (although faster). (See my previous post - appears to be the same.)
I also noticed that as the source file is imported, the percentage bar only gets about a third of the way through, and the percentage window gets really wonky, but seems to display similar problems. It goes so fast, I can't really tell, but it seems to go through a couple of resets, and ends at about 18%.
Hope this helps.
Roger
Roger,
Are you, by chance, using an nVidia graphics card... we have discovered that the graphics driver may be the case of the dialog bar weirdness.
In other words... the process continues normally in the background and it is just the display of the percentage bar dialog that freezes.
Currently looking for a solution.
Bob L
In fact, I am.
Thanks.
Roger
Hi, Bob. To test it out, I loaded 64 onto my Alienware laptop, which has Intel graphics video.
You're correct, the progress readout works fine on BuildMix.
But ... when I imported a WAV file to test, the import progress bar and readout displayed the earlier wonkiness. It went pretty quickly, but it reset to 0 midway at least once - maybe twice. As I mentioned before, it seemed to do the same on my desktop, which has nVidia graphics.
Hope this helps.
Roger
Hi Bob,
The plugin of Acustica Audio quits once it is inserted. I can only open it via Jbridge but it is not as efficient as in Reaper doing at the moment. Please check their plugins when you are available. I knew that they'd contacted you several years ago, perhaps you can communicate with them direct.
https://www.acustica-audio.com/pages/aquarius (have to create user account on the page before download those (trial) plugins from Aquarius)
Thanks!
Ok... the graphics driver lead was a wild goose chase... I believe I found the problem to the progress bar dialog issue and am creating an update to fix it.
Bob L
New update V1_0a is online.
Bob L