Mixdown - Invalid Pointer Operation

I get an error on a particular mixdown selection. All the tracks seem OK bar the one that has a rather unique bit of Cue Editing on it…

The track is from a mix CD, so I’ve set the Fade Out about 30s from the end, and left the Cue Out blank. I’ve put a 4500 fade duration in the Properites dialogue. This works fine on Selection PFL, but on the Mixdown - it carries on playing the rest of the file. I’ve even tried putting a Cue Out marker on it, but to no avail. At the end of the mixdown, I get a msgbox with the error: “Invalid Pointer Operation”. The rest of the mixdown, as I said, is OK.

Here’s a sound clip of what happens: Mixdown Sample, then Selection PFL Sample

Can you provide the me audiofile which is causing the error, along with an MMD file of the cue settings?

Sure - it’d be about 6-8Mb at it’s present bit-rate. Your usual e-mail address or shall I upload it to my webspace for you ?

Upload would be nice. I will have a look at it tomorrow. Time to go to bed now.

Torben

Thanks for the file. Obviously, the problem is that BASSENC grabs the audio data before the change in volume is applied. This is confirmed in a post I found in the BASS forum. I will try to find a workaround.

Please keep the file on your server until tonight, I may need to download it to another computer.

Torben

I have found a solution now. Will be included in mAirList 2.1.8.

Torben

Torben,
I got another error on Mixdown - 3 songs, the last had a FadeOut about 15s prior to the end of the file (Moloko - The Time Is Now). I tried setting a Cue Out to see what would happen, and the WAV file is creates is the right size, yet not a valid audio file.

An MP3 mixdown also fails to work (produces no file).


mAirList

Call stack (Ctrl+C to copy to clipboard):

(0000386C) [0040486C]
(0000205E) [0040305E]
(0000386C) [0040486C]
(00003C62) [00404C62]
(0041BBFF) [0081CBFF]
(00006C69) [00407C69]
(00006B74) [00407B74]
(0010D954) [0050E954]
(00006C69) [00407C69]
(00006B74) [00407B74]
(0041C683) [0081D683]
(0010E61A) [0050F61A]
(000DC70A) [004DD70A]
(000DCA9E) [004DDA9E]
(0002E5C4) [0042F5C4]
(0008ACF8) [0048BCF8]
(0008AD32) [0048BD32]
(00087333) [00488333]
(0042262E) [0082362E]
(003CF924) [007D0924]
(00062833) [00463833]
(00063D37) [00464D37]
(00064E96) [00465E96]
(00022CF4) [00423CF4]
(0003AD7C) [0043BD7C]
(00070E1C) [00471E1C]
(00064DE5) [00465DE5]
(0002E5C4) [0042F5C4]
(0008ACF8) [0048BCF8]
(0008AD32) [0048BD32]
(0008AF52) [0048BF52]
(00440044) [00841044]


OK

Could you provide me the files again? Would be very helpful.

If it helps, this was part of an MLD file - I was compliling a 3hr show for tonight, mixing down 15min segments and then editing voicetracks and IDs over the top in Adobe - I’ll PM you a link to the 3 songs + MMDs from that mixdown, plus the MLD file.

My workaround was to play it out “manually” via the desk and record back into the PC :wink:

Hm, I cannot reproduce it here. What have you set as default fade duration in the config?

It’s 2500mS … I’ll keep an eye on it - I’ll have another go with it tomorrow, see if I can get it to occur again.

I’ve noticed that upon mixdown, items remain “playing”, despite the FadeOut in the mAirList Config - is this deliberate ? ie: the mixdown is not a true “as played” version of the Playlist.

Typical example would be a song still playing quietly as it fades even after a Jingle longer than the global FadeOut setting, as it plays into a quiet intro…

The mixdown has its own mechanism of chaining the items, but it tries to meet the behavior of the playlist as closely as possible. One different is that the mixdown does not use a fixed number of “players”, but it’s able to start and stop each item individually. This means that an unlimited number of items can be “playing” at the same time. (However, since v2.1.7, the ordinary playlist has been able to load the next item into a player while the previous one fades out in the background, so there should be no difference in the output anymore in this respect.)

By the way, this also applies to Selection PFL and Container items, all of which use the same mechanisms (the mixdown is nothing but a container item rendered into a file instead of the sound card).

I don’t quite understand what’s wrong in your example - do you mean that the 2500ms are ignored, and the fade takes longer than expected?

Torben

Yes - the problem would be the Mixdown ignoring the Global FadeOut setting of 2500mS and the song still playing after the jingle and into the next song. When I’ve put a Cue Out on the song (to force a fade to match the length of a jingle/transistion), I’ve ran into problems - Like that mix example we had the other week where I wanted to fade it about 30s prior to the end.