ZynewaveEnable both the B and R buttons on the bounce track. Enable record mode and start playback.
ZynewaveDue to the 32-bit data size, the maximum amount of memory that Podium can allocate is 2GB. There is a possibility to make it go up to 3GB, but I don’t think that is the problem as you mentioned you had the crash on one of your machines with 2GB or less.
Have you set up the /3GB option in boot.ini on your machine with 3GB RAM?
ZynewaveYou can hold down Shift and click/drag to edit the pitch in cents rather than semitones.
Zynewavein the interim, is there another option that might work?
You could try to do a realtime bounce recording of the amplitube track, and then remove the plugin from the track afterwards.
Zynewaveman, they are not very responsive, that was Feb 07!
It was Aug 02. The email form said to expect a couple of weeks delay before getting a reply.
ZynewaveHmm, this is probably the same issue as reported here:
http://www.zynewave.com/forum/viewtopic.php?t=1406
I have not received a reply from IK Multimedia yet.
ZynewaveI would suggest adding Amplitube as a normal insert track, and then add a bounce track above it. Bouncing the amplitube track then frees the CPU resources used by the plugin, and it’s fast to deactivate the bounce track to make changes to the original track and then redo the bounce.
ZynewaveTry opening the Windows Task Manager and watch if the available free memory is used up when the crash/freeze occurs.
ZynewaveI’ve experimented with this, and I found a problem. Currently all child tracks of a record-enabled track will inherit the record mode. This means that e.g. audio tracks playing into a record enabled plugin track will be muted. I’m currently changing the way that record mode is inherited by child tracks. Originally record enabled audio tracks were not muted during recording, which I think is why you remember that it used to work. This will be fixed for the upcoming 1.94 release.
ZynewaveI would need to see it in action to really judge but it sounds like a really useful idea!
The pulse indicator has always been there. I’ve just changed the appearance slightly and it now pulses on each beat rather than each bar.
ZynewaveWhat is the dual shaded box for next to the no.4 (far right of the lower screen area)?
That is a pulse indicator that animates the play position within the current beat. This will create a flash on the start of each beat, to aid with timing if you are far from your monitor. I think this is more useful than a frantically running percentage value.
ZynewaveAny chance on allowing a customization for U.S. nomenclature (our . are your ,)?
I’ve changed the comma to a period. I looked at screenshots of other hosts, and this seems to be the preferred way to display time.
ZynewaveHave any of you posted about this on the Jamstix support forum? I see that Jamstix2 was released yesterday, so it’s possible this is a bug in Jamstix.
ZynewaveWhen will it be released? And will there be the changes to the group panel that you described in another thread?
Maybe the coming weekend, including some of the planned group panel changes.
ZynewaveDoes the clicking occur during normal playback?
Are you doing a bounce render (ctrl+B) or realtime bounce recording?
Some plugins have a problem with processing faster than realtime, and so need to be bounce recorded realtime. Realtime bounce recording is done by enabling both the B and R buttons on the bounce track, enabling record mode and then pressing play.