Conquistador's Forum Page

Forum Replies Created

Viewing 15 posts - 451 through 465 (of 1,598 total)

← 1 2 3 … 30 31 32 … 105 106 107 →

January 8, 2009 at 17:27 in reply to: Render info… #13619

Conquistador
Participant

😛

January 8, 2009 at 11:43 in reply to: 2.07 #13616

Conquistador
Participant

2.0.7…

Windows and/or Podium generated this error…thought it might help to post it here.

Problem signature:
Problem Event Name: APPCRASH
Application Name: Podium.exe
Application Version: 2.7.0.0
Application Timestamp: 49286edd
Fault Module Name: kernel32.dll
Fault Module Version: 6.0.6001.18000
Fault Module Timestamp: 4791a81d
Exception Code: c0000005
Exception Offset: 00010e20
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 2057
Additional Information 1: fd00
Additional Information 2: ea6f5fe8924aaa756324d57f87834160
Additional Information 3: fd00
Additional Information 4: ea6f5fe8924aaa756324d57f87834160

January 8, 2009 at 11:32 in reply to: Need help please with GUI / graphics issues…thanks… #13615

Conquistador
Participant

Here is a screen shot of the black borders I mentioned earlier…

(click on the thumbnail for a full screen image). It would have been too big for a forum post.

My thoughts on it…

It sometimes appears when loading projects. I can understand Podium is busy doing something but even if an application becomes unresponsive for a short time (not regularly but under certain condidtions) it should not also shift the screen diagonally left, leaving black borders at the right and bottom of the screen (clearly visible in the image above) until the application (Podium in this case) becomes responsive again.

The appearance of black borders looks really odd and somewhat unfinished, which is the total opposite of the rest of Podium and of course I know it is not deliberate on your part. Simply some sort of glitch or similar.

At the very least if the “Podium is not responding” message is Windows telling me to simply wait…the graphical shifting looks like a Podium issue. None of my other applications have ever done that.

These kind of graphical issues gives the impression of Podium not being reliable. Strange really as it is very consistent elsewhere.

The image has captured the problem during an attempt to load a project. But I have seen it during playback as well (when tweaking a knob on a plugin for instance).

HTH

Some questions for you Frits…

1. Do you run Aero on Vista on your Dev machine?
2. Do you have any internet related software running when you use a finished version (not still in Beta) of Podium?

Why the questions…? Not troubleshooting your machine 😛 just trying to get a better idea as to why you have not seen this before thanks. It is an irritating problem.

January 6, 2009 at 09:33 in reply to: Podium running on an Asus Eee PC 900 #13611

Conquistador
Participant

Nice purchase…I can see the grin on your face from here 😛

Tech radar had a recent article on a new Asus notebook offering. They have certainly been a great success. I think attempting to write / update the Podium guide using your new ‘netbook’ is a very good idea… a good way to try and keep the Podium guide up to date. Just remember not to work too hard! 🙂

January 5, 2009 at 21:22 in reply to: Preview 2.08: Composite tracks (aka. multitake, comping) #13606

Conquistador
Participant

@Zynewave wrote:

The punch out still disables recording of MIDI and audio beyond the punch-out position, no matter if looping is enabled or not.

Ok I thought that behaviour was already / was going to be changed. Thats 100% fine then. 🙂

The only change is that the record button on the transport toolbar is not deselected once the punch-out position is reached. That is done with the new “deactivate record mode when playback is stopped” option.

Strangely enough that all sounds fine. Now that you explained it a bit more…its fine. Totally.

Please explain why you still want punch-out to deactivate recording?

Your last post clarified this for me so effectively punch out…

“still disables recording of MIDI and audio beyond the punch-out position, no matter if looping is enabled or not.”

…so its not a problem.

I will ask though why would one want to keep the record button enabled if punch out has disabled recording of midi and/or audio events…would that not confuse if the record button remains active? If you cannot record midi or audio why keep the button active? ❓ ❓ ❓

Ignore that, I found the answer…

“It will thus be possible to keep loop-recording with punch-out inside the loop.”

Heh… 😛

January 5, 2009 at 16:48 in reply to: Preview 2.08: Composite tracks (aka. multitake, comping) #13603

Conquistador
Participant

@Zynewave wrote:

After giving this some thought: Now that we have the “deactivate record mode when playback is stopped” option, it is no longer essential that punch-out disables record mode. It will thus be possible to keep loop-recording with punch-out inside the loop. It will also eliminate the confusion you had with why punch-out disables record mode when punch-in does not enable it. Anyone else have arguments against removing the record-disabling feature of punch-out?

The added flexibility is very welcome I must say. However Punch out disabling recording is still useful outside of loop recording. I would definitely want to keep it ❗

I think a global option should easily let a user set and forget the feature one way or another.

January 4, 2009 at 14:50 in reply to: Preview 2.08: Composite tracks (aka. multitake, comping) #13600

Conquistador
Participant

@Zynewave wrote:

@Conquistador wrote:

Wave form Peak Display.

As I understand it, this is not something that influences how comping should work, so I would prefer we discuss this another time. I’ve got plenty to do just implementing the composite track feature for this release.

Depends how you work IMO. It is more to do with making the process of managing takes easier. But yes no problem…a discussion about it at some other time is fine. 🙂

January 4, 2009 at 13:15 in reply to: Preview 2.08: Composite tracks (aka. multitake, comping) #13598

Conquistador
Participant

The current features recently added are pretty slick. My pick of the bunch would be the ease with which you can cycle through takes with the bar at the bottom of a sound event. Very easy. 🙂

However I think another extremely useful addition to managing and selecting takes is not there yet.

Wave form Peak Display.

In Sound Forge for instance you can set a user defined threshold at which peaks can be detected in an audio file.

When one is cycling through takes it will be much easier to choose a take if you can also see a db marker placed on the file that shows the db value of on audio file at the exact point of a peak.

If I am choosing a take in a recording some might be louder than others or too loud. If I could see where the peaks are (as a marker with a db value) it will make the process of choosing a take much faster and easier without having to bring up the mixer to see the peaks.

Of course such a feature would be extremely useful during the mixing process as well. Podium can show peaks in an audio file (with the mixer)and very useful it most certainly is but when cycling through takes I want full screen real estate which means…no mixer.

Peak information remains very useful and I really think it should be added to any recorded sound event in Podium in the form of markers placed on an audio file. Soundforge, Sonar and I think Samplitude have something similar.

Being able to see a Wave Form Peak display marker also has many corrective uses when editing audio in general. It is not a multi faceted or featured addition to take comping but it will speed up the process of managing takes and the uses for Wave form Peak display markers go far beyond take management.

Only one single marker needs to be displayed on a sound event. That will show the highest peak in the file. As in Soundforge a user defined threshold for detecting peaks could be offerred for more flexibility. The marker could be red when above a user defined threshold and green when below it.

Even without a user threshold setting a default peak detection value that matches the mixer peak values could be used instead.

December 31, 2008 at 11:32 in reply to: Restricted to Podium license owners

Conquistador
Participant

This content is restricted to Podium license owners.

December 31, 2008 at 11:30 in reply to: Automation problem #13581

Conquistador
Participant

@Zynewave wrote:

This is not a bug. I designed it to work this way, and it has worked this way since the first Podium release.

Thanks for the further clarification. 🙂

I assumed bug because of the automation behaviour discussed in this thread and also because of your own response to aMUSEd question “any chance for a fix soon” earlier in this thread” you responded but did not say it was “designed to work that way” in response to his post. So I guess I somehow misunderstood what kind of problem this is. Anyway…moving on…

I have acknowledged that the majority of users find this automation behaviour undesirable, and I will look at an alternative solution in a future update to the automation system.

Thanks a future revision will definitely help.

December 25, 2008 at 14:22 in reply to: Preview 2.08: Composite tracks (aka. multitake, comping) #13565

Conquistador
Participant

@Zynewave wrote:

Thanks. I’m going away for the holidays until the 26th, so merry christmas everyone! 🙂

Merry Christmas to you too. 🙂

December 25, 2008 at 14:16 in reply to: Automation problem #13564

Conquistador
Participant

@aMUSEd wrote:

Pity. I can’t understand why this isn’t seen as more of a priority. Is no-one else using automation with softsynths apart from me?

I agree. While I appreciate Frits has his hands full with other new developments there are more than a few hosts out there that have features that are left to wither. It starts with a few then goes down hill from there unless enough complaints are made about it.

Frits has a brilliant track record with bugs but this is not exactly a minor bug. Because Podium does not have the marketing muscle or adverstising consistency of bigger devs (or even some smaller devs)…bug fixing becomes quite necessary for it to stand out.

On average new releases appear every 8 weeks so a post 2.09 fix could be at least a month to 3 months away. 🙁

I am sure First has a development schedule (for new features) and wants to focus on that but…this bug is not minor IMO.

I will say again that Frits has a fantastic record for fixing bugs but with little or no marketing here…bug fixing is essential for such a low profile host like Podium or really its a case of great features but “this does not work properly or that” e.t.c

I appreaciate Frits is human but this bug is not something that should be put off for two releases IMO. Sorry.

Just my 2pence worth. 🙂

December 19, 2008 at 18:23 in reply to: Preview 2.08: Composite tracks (aka. multitake, comping) #13537

Conquistador
Participant

@Zynewave wrote:

Beta1 of 2.08 is now available. The change-log so far:

• Added composite track feature, allowing for easier splicing of multi-take recordings. Composite tracks are handled similar to group tracks, where each take is a child track of the composite track. You can access the multiple takes from the events on the composite track. You can also expand the composite track group to make edits to the individual takes. The composite track option works both for audio and MIDI tracks.

• A track can be made into a composite track with the new “use as composite track” option in the track properties. A track is automatically converted to a composite track if looping is active during recording. The old loop-recording method of putting the recording track into a group track is thus no longer needed.

• Hovering the mouse over an event on a composite track shows a take selection bar at the bottom of the event. Clicking the bar will cycle through the available takes. Right-clicking the bar shows a popup menu with all available takes.

• Soloing a take track in a composite track group will make the take play instead of the main composite track. Pressing shift+solo will solo the take track and unsolo any other soloed take tracks within the composite group.

• Added “use as group track” and “use as composite track” options to the track properties submenu.

• The “fade properties” dialog is renamed to “sound event properties” and is extended with an “event name” setting. This makes it possible to enter different labels for track events, even if the events links to the same sound object. Leaving the event name blank will display the sound name as in previous Podium versions.

• Split the timeline ruler “zoom/slide” combined option introduced in 2.07 into two separate options.

Note that the .pod file format has been updated, so please make backups of your old projects before saving with this beta.

There are still plenty of improvements that can be made to the composite feature, so please share your thoughts.

Nice changes. 🙂

December 19, 2008 at 18:21 in reply to: Need help please with GUI / graphics issues…thanks… #13536

Conquistador
Participant

@Zynewave wrote:

My host provider was moving the server physically from LA to San Diego, so that’s why zynewave.com was offline for almost a day.

Ok that explains it. 🙂

Please try to disable the “enable plugin multiprocessing” option in preferences, and see if this changes the behaviour of the problems

.

Plugin multiprocessing changes do not make any difference. The task manager was the main culprit it appears, but even without it that black border around the edges seems to appear either at a projects start up or under heavy CPU load if I try and do something during playback.

December 4, 2008 at 21:40 in reply to: Need help please with GUI / graphics issues…thanks… #13514

Conquistador
Participant

Been trying to access this site for most of the evening..

@Zynewave wrote:

I have never experienced this symptom myself, and I’m on Vista Business 32-bit.

So this can happen with just one plugin loaded in the arrangement?

Not seen it yet with one plugin but if I for instance solo a track (reducing the CPU load to the plug on that track) then the problem is still there.

Can you refer me to a plugin (freeware or demo) that shows this behaviour? If you can only refer me to a plugin demo, then please confirm that the demo also fails on your system.

PSP Mix pack 2. The demo had the same issue. I was using the mix bass 2 plug.

Have you tried Podium on other Vista PCs with similar problems?

Same PC…different OS (Vista x64).

It would also be nice if you can grab a screenshot of the messed up screen.

Trying but the black border at the foot of the screen (right side and bottom) for some reason is not coming out in a print screen. ?!?!?

After some more testing the Task Manager appears to be the problem…at least in part. Plugins are much less likely to starve Podium graphically when knobs are moved…if the task manager is not open.

Leaving the task manager open was one of your suggestions though (if you are wondering) in response to a similar problem I had with Podiums CPU meter some time ago. 🙂

Even without the task manager open the black border still appears (with a “Podium not responding” message at the top left of the screen if Podium is busy…but not necessarily at a heavy CPU load.

Viewing 15 posts - 451 through 465 (of 1,598 total)

← 1 2 3 … 30 31 32 … 105 106 107 →