J-Bridge is just a variation on Bitbridge, but it seems to have better plugin compatibility than the latter.

Here's the website: http://jstuff.wordpress.com/jbridge/

Try the demo version out before you buy it.  Just make sure you change the plugin properties in the Plugin Manager so that Ivory uses J-Bridge instead (after you install it of course).  Please, let us know if it worked for you.


Good Luck!

Not a bug, just a really inconvenient, longstanding omission:

8.5 doesn't import your toolbar layouts (stored in the Windows registry) from your previous installation. You have to do it manually by copying registry keys, or by using the third-party SONAR UTILS applet: http://www.digifreq.com/digifreq/download.asp?ID=66

Jose7822


J-Bridge is just a variation on Bitbridge, but it seems to have better plugin compatibility than the latter.

Here's the website: http://jstuff.wordpress.com/jbridge/

Try the demo version out before you buy it.  Just make sure you change the plugin properties in the Plugin Manager so that Ivory uses J-Bridge instead (after you install it of course).  Please, let us know if it worked for you.


Good Luck! 
  
 

Thanks for the suggestion.  Forgive me, but I have 2 novice questions:
 
Arent all of these "bridge" programs specifically designed to allow 32bit pluggins to work with 64 bit apps?  The reason I'm asking is because Ivory is fully 64 bit which I thought would mean that a bridge wouldn't be needed.  I'm a newbie so forgive me if' I'm totally off base.
 
Secondly. Ivory 64 works just fine in 8.3.1.  I don't remember a bridge program being used, but I could be wrong.  I don't usually pay close enough attention to software dialog boxes when I install pluggins.

bitflipper


Some installation problems may be caused by failing to uncheck the "use defaults" option on the last dialog, where it copies settings from a selected previous SONAR install.

I don't remember the exact wording and wish I'd taken a screenshot, but when it came up I thought "whoa, that's gonna cause some people problems if they don't read the prompts!". If you accept the default, your settings will not be copied over from the previous SONAR install, and you'll be left wondering where your stuff is!

 
 
This is a very important one bit is mentioning here - This one got me - my fault for not reading closely enough

I have never used periods in file names at all. instead, I am using "_" and never had any problem

I've found a bug and it's working with all my loops.

Use the EXPLORER to insert a loop in a track (new track or existing one)
Let's say the loop is 2 measures long and you only want to keep the second measure of the loop.
So cut at measure 2 (that make 2 clips) and delete the first clip
Drag the second clip measure 1 (to the emplacement of the first clip you've just deleted)
Then bounce to clip (to make a new looping clip)...

The old first measure just appear !

Is this doing that for you ? I can reproduce the bug every time.

EDIT : Even if you don't bounce to clip, listen to the clip after you've dragged it... the first half of the clip is playing and showin the waveform of the second clip.

I don't know if anyone else experiences this but Sonar wont allow me to change sample rates on the fly.  (This has been true for me since V7).  Or:  The default audio setting is set to 96K, I open a 96K session, all is good, close it, then open a 44.1K session and it doesn't play.  (The RME Multiface hasn't been changed from 96K).  My workaround has been to go to Options|Audio and change the default sample rate to fit the 44.1K project that's open, close Sonar, re-open it.  Many times, Sonar crashes in the process.  (I believe this is a Sonar issue because CD Architect and Roxio will switch the RME device to 44.1 and play without any issues).
 
Also, experienced some bizarre behaviour in screen scrolling (happened once that the screen didn't scroll to the current time- but haven't been able to reproduce it again).
 

DjiDoe


I've found a bug and it's working with all my loops.

Use the EXPLORER to insert a loop in a track (new track or existing one)
Let's say the loop is 2 measures long and you only want to keep the second measure of the loop.
So cut at measure 2 (that make 2 clips) and delete the first clip
Drag the second clip measure 1 (to the emplacement of the first clip you've just deleted)
Then bounce to clip (to make a new looping clip)...

The old first measure just appear !

Is this doing that for you ? I can reproduce the bug every time.

EDIT : Even if you don't bounce to clip, listen to the clip after you've dragged it... the first half of the clip is playing and showin the waveform of the second clip.

 
 
Sorry, I'm not able to reproduce this one.  Seems to be working fine here.  Could anyone else confirm this?
 
Thanks!
 
EDIT:  Nevermind!  You're right.  I was able to repro this one.  It'd be nice if someone else to confirm it though.
 
 
 
 

D K

bitflipper


Some installation problems may be caused by failing to uncheck the "use defaults" option on the last dialog, where it copies settings from a selected previous SONAR install.

I don't remember the exact wording and wish I'd taken a screenshot, but when it came up I thought "whoa, that's gonna cause some people problems if they don't read the prompts!". If you accept the default, your settings will not be copied over from the previous SONAR install, and you'll be left wondering where your stuff is!

 
 
This is a very important one bit is mentioning here - This one got me - my fault for not reading closely enough

So what can a person do if they didn't "uncheck" this button during installation?  Is there something they can do?

Double Post, sry!

8.5 still exhibits a failure to distinguish between MIDI events arriving on different ports.

The simple test:

1. Open a new project using the default Normal template, and delete everything but one MIDI track.

2. Set the input of that track to a port (Omni or a specific channel - it doesn't matter) that is not connected to anything, and arm it to record.

3. Connect a MIDI controller keyboard to another port on your DAW - it doesn't even have to be on the same interface.

4. Start recording, watch the light red "confidence recording" bar draw out for a few beats, and then hit a key on the controller connected to the second (non-recording) port, and sending on any channel.

5. Note that the "confidence recording" bar on the MIDI track assigned to the open port goes dark red as if you are recording MIDI data on that track.

6. Stop recording, and confirm there is no clip in the track, and no MIDI data have been recorded. The confidence recording bar is registering events arriving on the other port.

I reported this bug to Cakewalk way back under 6.2.1. At the time, I was not aware that this was a problem with anything more than the confidence recording indicator. But it has since been discussed in other threads that this problem goes deeper, and can result in truncated notes by the misrouting of Note-Offs when two ports are recording on the same channel.

brundlefly


File Extension Bug:

When starting a new project from a template with per project folders enabled, if you enter a filename with a period in it, whatever you enter after the period will become the project file's extension. For example, if you enter Test Project 8.5, the file will be named "Test Project 8" with a filename extension of "5", which will not be recognizable as a Cakwalk Project File if try to re-open it later.

Windows has always used the period to name the file extension. If you have view file extensions enabled then of course you will be renaming what type of file it is by using a period.
 
I often open attachments with the no extension or the wrong extension by putting in a period and typing .doc or .ppt  or .pdf or .mid etc.......
 
You should never use periods in your naming conventions full stop.

D K bitflipper Some installation problems may be caused by failing to uncheck the "use defaults" option on the last dialog, where it copies settings from a selected previous SONAR install. I don't remember the exact wording and wish I'd taken a screenshot, but when it came up I thought "whoa, that's gonna cause some people problems if they don't read the prompts!". If you accept the default, your settings will not be copied over from the previous SONAR install, and you'll be left wondering where your stuff is! This is a very important one bit is mentioning here - This one got me - my fault for not reading closely enough So what can a person do if they didn't "uncheck" this button during installation? Is there something they can do?

Uninstall and re-install.

Audiosnap: Transient markers are not shown when Audiosnap is initially enabled.

Previously, I was in the habit of simply pressing F12 to enable Audiosnap, usually for aligning two vocal clips. I did not have to open the Audiosnap dialog.

Now, in order to see the transient markers, it is necessary to open the Audiosnap dialog and click on the "show/hide transients" button.

Reported to CW, report ID CWBRN-1712

Bit,

I was gonna say, could it be due to the new Transient Tool?  I mean, by clicking on the Transient Tool you're essentially activating Audio Snap.  Maybe Cakewalk decided to change the way worked with transients?  I don't know.  But I agree with you that the old way was better.